IIS 5 & IIS 6
Non responsive NICS
Last post Aug 01, 2008 05:30 PM by sfarmer
Jul 30, 2008 05:35 PM|sfarmer|LINK
I'm having an issue with sites that I have published via multiple IPs on the same NIC. The problem is random. Each site is published via it's own IP and is available from the Internet. However, every few days or so they are no longer available from the
Internet. First I thought it was the firewall and tried rebooting it with no fix. The only thing that fixes it (and makes the sites available to the Internet) is to right click on the NIC card an choose repair. Again, the sites stay up for a few days and
then it will happen again. I must mention that during an outage I can sit at the web server and the sites come up. It's only external access that is affected.
The web server is a Windows 2003 R2 server (fully patched) with dual NICs. Both have private IPs on different networks. However one of the NICs is in my DMZ. The DMZ NIC is the card I'm using to publish my websites. NAT is being used by my firewall to
route the public IP address of the site to the private DMZ IP address that the websites has been assigned to in IIS.
Can anyone possibly tell me what the problem may be? The event logs show absolutley NO Errors that correspond to the time of the outages.
Thanks in advance!
Jul 30, 2008 06:41 PM|Rovastar|LINK
Run a packet sniffer like netmon to make sure that nothing is coming to your server via the NIC.
If that lower part of the OSI model is not working then there nothing worth fixing above it.
I would suggest first you update (or even downgrade) your network drivers.
Run diagnotics tools for the network cards (I still remember DOS 3c5x9cfg.exe)
Then swap over the network cards as you seem to think that one of these works.
But maybe to be sure buy a new good quality network card for it.
Aug 01, 2008 05:30 PM|sfarmer|LINK
I tried a new switch yesterday and it worked all day until 5 o'clock ;-) However now I think I may have had my NICS configured wrong.
DNS 1 10.0.0.2
DNS 2 10.0.0.3
DNS 1 188.8.131.52
DNS 2 184.108.40.206
I think I should have left out the gateway on the LAN side. I'm thinking that somehow the routing was getting confused. I have since removed the gateway IP from the LAN saide and so far it has been working.....for now.
Does this make sense to you?