SSL down?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Guest
Archived from groups: microsoft.public.win2000.setup (More info?)

Hello,

Our SSL function went down yesterday on two different W2K servers, yielding
https:// protocol out of commission. The system log entry is shown below.
Rebooting the server seems to fix the problem, but I'm wondering why this
happened on two different servers in two separate data centers. We're also
using different digital certs, one from Thawte and the other from
InstantSSL. Has anyone else seen this problem?

---------------
The security package Microsoft Unified Security Protocol Provider generated
an exception. The package is now disabled. The exception information is the
data.
 
Archived from groups: microsoft.public.win2000.setup (More info?)

I don't know any specific details, but the first thought going through my
head is to check whether you've applied the patch for vulnerability
MS04-011. There may have been an attack on your server. Just a thought.

Regards

Oli


"Dean J. Garrett" <deanj_garrett@yahoo.com> wrote in message
news:uo9ssuVKEHA.2380@TK2MSFTNGP09.phx.gbl...
> Hello,
>
> Our SSL function went down yesterday on two different W2K servers,
> yielding
> https:// protocol out of commission. The system log entry is shown below.
> Rebooting the server seems to fix the problem, but I'm wondering why this
> happened on two different servers in two separate data centers. We're also
> using different digital certs, one from Thawte and the other from
> InstantSSL. Has anyone else seen this problem?
>
> ---------------
> The security package Microsoft Unified Security Protocol Provider
> generated
> an exception. The package is now disabled. The exception information is
> the
> data.
>
>
 
Archived from groups: microsoft.public.win2000.setup (More info?)

"Dean J. Garrett" <deanj_garrett@yahoo.com> wrote in message
news:uo9ssuVKEHA.2380@TK2MSFTNGP09.phx.gbl...
> Hello,
>
> Our SSL function went down yesterday on two different W2K servers,
yielding
> https:// protocol out of commission. The system log entry is shown below.
> Rebooting the server seems to fix the problem, but I'm wondering why this
> happened on two different servers in two separate data centers. We're also
> using different digital certs, one from Thawte and the other from
> InstantSSL. Has anyone else seen this problem?

Hi,

There's an exploit code for this vulnerability. Try applying the MS04-011
hotfix.

--
________________________________
Nicolas

"This behavior is by design" (Microsoft)
________________________________
 
Archived from groups: microsoft.public.win2000.setup (More info?)

Thank you for the reply. I found out about this hack and tweaked the
registry to prevent w/o applying MS04-011





"Kirioss" <niconews@ifrance.com> wrote in message
news:408a6cb7$0$15682$626a14ce@news.free.fr...
> "Dean J. Garrett" <deanj_garrett@yahoo.com> wrote in message
> news:uo9ssuVKEHA.2380@TK2MSFTNGP09.phx.gbl...
> > Hello,
> >
> > Our SSL function went down yesterday on two different W2K servers,
> yielding
> > https:// protocol out of commission. The system log entry is shown
below.
> > Rebooting the server seems to fix the problem, but I'm wondering why
this
> > happened on two different servers in two separate data centers. We're
also
> > using different digital certs, one from Thawte and the other from
> > InstantSSL. Has anyone else seen this problem?
>
> Hi,
>
> There's an exploit code for this vulnerability. Try applying the MS04-011
> hotfix.
>
> --
> ________________________________
> Nicolas
>
> "This behavior is by design" (Microsoft)
> ________________________________
>
>