IIS 5 SSL Failure after SP4??

From: Blah (webmaster_at_calgarytech.com)
Date: 09/25/03 

Date: Thu, 25 Sep 2003 20:56:54 GMT

Hi,
After installation of SP4 on IIS5 (win2k) SSL no longer functions
consistantly. It will load https pages occasionally (from outside clients)
but normally just gets a DNS error. SSL pages will never load browsing from
the server. Non-ssl the site will work ok both on the server's browser and
outside clients. The site is bound to the main IP and the port is set to
443. sspifilt.dll is loaded and running ok. I have tried removing SP4 but it
did not help. Are there any other options short of reinstalling IIS or Win2k
server?

Thanks,

Relevant Pages

  • IIS 5 SSL Failure after SP4??
    ... After installation of SP4 on IIS5 SSL no longer functions ... It will load https pages occasionally (from outside clients) ... Are there any other options short of reinstalling IIS or Win2k ...
    (microsoft.public.inetserver.iis.security)
  • Re: IPSec to encrypt SMB traffic?
    ... How does Etercap decrypt ssl protected data payload without the shared ... >> all of our clients are within our own Domain. ... >> particular Windows 2003 file server. ... Removed all entries under Key Exchange Security Method except ...
    (microsoft.public.windows.server.security)
  • Re: IPSec to encrypt SMB traffic?
    ... How does Etercap decrypt ssl protected data payload without the shared ... >> all of our clients are within our own Domain. ... >> particular Windows 2003 file server. ... Removed all entries under Key Exchange Security Method except ...
    (microsoft.public.windowsxp.security_admin)
  • Re: OWA Basic not possible without SSL?
    ... There is no FBA in Exchange 2000, ... >> server with SSL. ... >> You could issue a Cert from a Windows 2000 RootCA, but then your clients ...
    (microsoft.public.exchange.clients)
  • Re: AD SSL, what impact?
    ... you could just install a self-signed certificate. ... client's trusted roots store if it is using Windows Schannel for SSL ... You'll just have a deployment nightmare getting other clients to trust the ...
    (microsoft.public.windows.server.active_directory)