The problem was actually the following:
Somehow ipv6 protocol got installed and when ipv6 is installed with ipv4
(microsoft's tcp/ip protocol is ipv4), your machine name and localhost
resolve to ::1: for an address instead of the ipv4 typical octet of
127.0.0.1. So when I was trying to connect through debug of visual
studio.net 2003 through ie 6.1 sp1 to iis 5.1 using ipv6, somewhere in that,
it resolved localhost to ::1: and failed to connect.
what let me find this was simply pinging localhost. That showed me
localhost resolving to an address of ::1:
then I looked at my network connection and it had ipv6 installed. I removed
that and things worked fine after that.
"Ganesh" <anonymous.DeleteThis@discussions.microsoft.com> wrote in message
news:074901c39455$ab1077a0$a301280a@phx.gbl...
> Check the link below.
>
<font color=purple> > <a style='text-decoration: underline;' href="http://support.microsoft.com/default.aspx?scid=kb;en-</font" target="_blank">http://support.microsoft.com/default.aspx?scid=kb;en-</font</a>>
> us;290766
>
>
>
> >-----Original Message-----
> >I'm running IIS 5.1 on xp with .net 1.1. Whenever I do a
> >request locally either localhost or machine name to any
> >page .htm .asp .aspx the system process on my machine
> >spikes. My cpu goes to 100% with system being the main
> >culprit. inetinfo and dllhost both show 0%. Anywhere
> from
> >2 to 10 minutes later the page may show up or one of two
> >errors show up. Page doesn't exist or a dns error. Then
> >I refresh and the page shows immediately. Until I type
> in
> >a different page, then we wait all over again. From
> other
> >machines the pages are served fine. My problem is I need
> >to be able to get the pages locally so I can debug out of
> >visual studio. I have no proxies configured on any of my
> >lan settings or connections.
> >
> >Where should I start looking to solve this?
> >.
> ><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: system process spiking on any type page request from local.. 
FAQ
Profile
Private Messages
Log in
