Software

Ask something
Discussion Locked

Internet Explorer SSL connection failure

0 helpful
3 replies

by bkduke 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have 4 servers running Lotus Domino 5.06a providing secure web pages using 128 bit Verisign Server Pro certificates via the Internet. Netscape users can get to all four servers. All IE 4 and 5 users can get to one of the four servers. However only some of the IE 4 and 5 users can get to the other three servers.

This is not a firewall issue. The same firewall rules are used for all 4 servers. A sniffer trace shows a total of 14 packets exchanged between the client and Domino server with the server initiating an orderly disconnection. There does not appear to be any common denominator as far as the IE version and update levels of who can get to the secure web pages and who can not. The IE Internet Options all appear to be the same, including use HTTP 1.1, SSL 2.0 or SSL 3.0, (but not PCT or TLS). None of the Microsoft Knowledge Base issues appear to be the cause such as duplicate winsock dll's. This is happening on Win95, 98, NT and W2K Professional workstations. It isnot appear to be a server or certificate issue since some workstations can get to the web pages in question.

The only message is the generic IE page - The page cannot be displayed. Cannot find server or DNS Error.

I have not been able to findany good information on troubleshooting SSL connection problems such as this. Any ideas, suggestions or better yet, solutions would be most appreciated.

3 replies

by ehughbanks

I had this problem with IE 5.01, the only way I could get it fixed to be able to go to secure sites was to reinstall IE, after doing this I was able to get to the sites

by bkduke

Thanks for the response. We had already reinstalled IE 5 again on several workstations with no success.

We have since found out that our Verisign certificate generated for a Microsoft ISS rather than Lotus Domino. The installtion of the correct certificate fixed the problem. However the only thing I do not understand is why it would work for some IE browsers and not for others.

This discussion is closed to new replies.