IIS Stops responding sometimes.

Sometimes my IIS 6 stops responding. It stil responns on my local
network on the local network adress thu.

It does not help to restart using iisreset.exe , or to restart in other
ways.

If I click the network connection, and chosse repair, then after the
repair is finish everything works again.

I have no clue what is going on . Does someone have an idear og what
the problem could be, or maybe where i could see some Log from the IIS,
that could give a clue .

I happens about every 48 hours.

* *

p.s. I am using DisableSocketPooling (as desriped here :
http://support.microsoft.com/kb/813368) to prevent IIS from listening
to a second network adapter on the server. I am not sure if that could
be part of the problem.

Kristofer
Thu Jan 18 14:33:06 CST 2007

Hello,

IIS does not stop responding, based on your description. You say that you
can still access it from the local network, and that restarting IIS does
not help. This tells me that the problem is not with IIS.

It seems to be network related if the problem goes away when repairing the
network connection. It could be a faulty NIC driver, but it can also be
something else.

Perhaps you want to continue with this question in the networking newsgroup.


--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


andersboth@gmail.com wrote:

>
>Sometimes my IIS 6 stops responding. It stil responns on my local
>network on the local network adress thu.
>
>It does not help to restart using iisreset.exe , or to restart in other
>ways.
>
>If I click the network connection, and chosse repair, then after the
>repair is finish everything works again.
>
>I have no clue what is going on . Does someone have an idear og what
>the problem could be, or maybe where i could see some Log from the IIS,
>that could give a clue .
>
>I happens about every 48 hours.
>
>* *
>
>p.s. I am using DisableSocketPooling (as desriped here :
>http://support.microsoft.com/kb/813368) to prevent IIS from listening
>to a second network adapter on the server. I am not sure if that could
>be part of the problem.