Ken,

Are you all patched? There are some serious viruses around for IIS 5 that caused that sort of thing to happen, specifically a number of RPC holes. You might want to check your event log and see if there's anything to be found there...

I'm not quite sure I understand what you mean by: "Web Connect keeps working fine because we can still get to it via our internal network."

If it's a problem with the network card wouldn't that stop working too? It sounds like the problem then is in the network infrastructure...

If it is really a card issue, the easiest thing is to swap network cards and see if that fixes it. given cards are cheap and easy to replace this will be quicker than trying to troubleshoot a hardware or driver problem. Actually first thing to do is update everything you can: Patch and get the latest SP, get the latest drivers for the card, and if all that fails swap cards.

+++ Rick ---





>Has anyone experienced a problem with IIS 5.0 no longer responding to hits? About once or twice a day IIS just plain stops responding on the network card. We know the hits are coming in OK from the firewall because we have a network analyzer on. Web Connect keeps working fine because we can still get to it via our internal network. The trouble is with IIS and the network card. We've replaced the network card with a card from a different maker but the problem persists. To clear the problem all we have to do is 'disable' the network card and then 'enable' it again. Restarting IIS does not clear the problem. For all I know this may be a Win 2000 issue.
>
>I located a KB article (#229814) that tells how to configure IIS for heavy usage. The problems explained in the article fit our situtation to a 'T'. However, even applying the changes stated in the article did not solve our problem.
>
>
>Thanks,
>Ken Penrod