Rick,
It's not the firewall because I can see the hits coming in on our network analyzer. The problem appears to be between the card and IIS. We suspected a corrupt TCP/IP stack but we uninstalled TCP/IP and reinstalled it for this card with no change. I didn't suspect WC as being the problem but was wondering if others had encountered this on WC systems.

Ken

P.S. If my head wasn't shaved, I'd be pulling my hair out now. :-)

>HI Ken,
>
>I'm not quite sure I understand what's going on.
>
>You are saying that you can access the machine locally through your internal network but not externally? If that's so stop looking on the server and start looking at your router and firewall configurations.
>
>It doesn't sound like a software problem but a network or network permission issue...
>
>+++ Rick ---
>
>
>>Rick,
>> We've already replaced the card once but the problem persists. We even reinstalled TCP/IP on it. We update our server at least twice weekly with Windows Update patches as needed. We're running Win 2K SP4. I'm assuming that SP4 has all IIS patches up to that date. Nothing is showing up in the Win2K event logs. The IIS logs show all the hits up to the point of failure. We know we're continuing to get hits on the card because we have a network analyser running on it.
>> We have two network cards. One to our firewall and the internet and one to our internal network. We don't have much traffic on the internal one and it continues to work fine. We originally had 2 websites hosted on this box but moved our download site to an ISP. From our download site our customers can download our latest software. Some downloads are as large as 25MB. That's what we thought was originally causing our problem. But the download site is running rock solid at the ISP. The remaining site doesn't fail as often as before which seemed to maybe point to the number of hits being a problem. However, we're getting less than 100K hits per day.
>>
>>'Tis a puzzler.
>>
>>>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