This is likely the curse of a Windows Update patch.  The same thing
happens to me when I apply the patches since SP1 on my Windows 2003
server.  A repair makes the problem go away.

I do know networking in and out, and still have not come up with an
answer to this other than repair and disable windows update.  But
clearly, this is not how I want to keep things for long from a security
perspective.

Brian

In article <43bf4ff3.1615246281@msnews.microsoft.com>,
jeff.nospam@zina.com says...
> There really isn't anything in IIS that should affect this.  My guess
> is it's not IIS related.  But you'll need to test network
> connectivity, check routing, NAT, firewalls, IP rnages, etc. to see
> where there may be an error.  Not something you can be taught in a
> newsgroup post.
>
> Jeff

[ Post a follow-up to this message ]