Search results for query: *

But the httpd is logging the messages happily so I assume that the httpd is handling the packets. Considering that the httpd was the one logging the errors saying that the packet was not a hello but when I go from the console it shows all the packets with the appropriate destination ports and...

Thanks for the posts. I think I may have it liked. I'm in the process of testing a theory. I don't think it is a problem with the SEF but in fact may be the internal proxy and how it forwards SSL client messages. When we try and access the same site from the SEF console all is happy. I will post...

As mentioned, the log on the SEF shows that the outgoing packet has the appropriate destination and port, it shows that packets are going fro the client to the SEF (otherwise there would be no log of the activity) and the fact that I can connect to other server cert only SSL sites proves that...

I am probably to late for this to help, but here goes anyway. If the Win2k Advanced Server is a Domain Controller then you have to modify the user rights in the default domain controller policy (GPO). This policy will overide the local user rights set on the server itself. Simon Powell. MCSE...

An internal client using clinet certificates can't connect to the external SSL site. After checking the SEF6.5.2 logs, the error is that the first packet is not a Hello, and as such the SEF won't let it out. Some needed info, The client is Windows based using IE5.x through a Proxy to the...