Re: Help!! Web Server outage - ping failure

From: Roland Hall (nobody_at_nowhere)
Date: 02/18/05 

Date: Thu, 17 Feb 2005 20:11:49 -0600

wrote in message
news:1108686645.116051.311820@g14g2000cwa.googlegroups.com...

1. Not a good idea to post a valid email address on usenet.

:I have a Windows 2003 web server running IIS sitting behind a pix 506.
: Internally, I use ip 10.0.0.3 for this web server.

Thanks for the info. That minimizes my recon efforts. (O:=

: I am getting
: erratic outages where no one (external or) internal can even ping this
: server (www.dwyer.com).

Why would you allow ping responses from your router, must less your internal
network? That's a very bad idea.

: It has multiple Intel NIC's on the
: motherboard, and I have tried using both, only one, teaming, etc, plus
: I have tried popping in a 3com spare NIC card. I tried plugging into
: another switch but made no difference.

It's probably not the NIC then?

: I ran 3Com's Network Supervisor
: and it simply reports the failure, but notes no connection
: configuration problems.

Then it's not a connection configuration problem or it fails before that can
be fully tested?
Ping is not an accurate test for connectivity since it can easily be
blocked.

: If I leave a 2nd NIC in that server, I can ALWAYS ping the NIC that is
: NOT being used as the web site ip (every time without fail,
: internally).

My corvette runs well but my truck is currently down. Apples and oranges.
Ping is software, a NIC is hardware. A 2nd NIC is in a different slot on
the bus and has a different channel, IO, etc.

: I even tried new ip #'s (it used to be 10.0.0.11 for
: example). Most often, when I sit at my station and go to ping the
: server, I get one ping (maybe) and then time outs:

Funky!

: Pinging 10.0.0.3 with 32 bytes of data:
:
: Reply from 10.0.0.3: bytes=32 time<1ms TTL=128
: Request timed out
: Request timed out
: Request timed out

Ping doesn't tell you where it failed. Do you have a protocol
analyzer/packet sniffer?

: I called Microsoft and paid for an incident and spent 6 hours on the
: phone with them but we spent the entire time working on ip stacks and
: NIC's and drivers. Ouch, I blew my whole day. At one point, it worked
: briefly (GREAT, RESOLVED!! NOT!!). My local IT consultant basically
: said HMMMMM.

Not a good sign when your IT consultant scratches their head.

: Any ideas? I don't know if I should order a new motherboard and see if
: that works (sigh).

Guessing should not be a technical process of troubleshooting.

: I tried swapping memory SIMMs since I had extras and
: that did not help.

What does a SIMM have to do with network connectivity?

: I wouldn't think pinging a plug in card would be
: affected much by motherboard anyway, but maybe...

I'm not sure what that statement means. You haven't eliminated all the
physical aspects yet or everything in between. How about pinging the NIC
locally? Have you run hardware diagnostics? Did you run in safe mode to
eliminate other application interference? Did you try the NICs in other
systems to help eliminate the NIC itself? How about the local firewall?

: I can start unpeeling Microsoft service packs???

You're not ready to go there yet but you're right, you can but after you
change the software aspects, you're now not working with the original issue
and may introduce others. 

-- 
Roland Hall
/* This information is distributed in the hope that it will be useful, but 
without any warranty; without even the implied warranty of merchantability 
or fitness for a particular purpose. */
Online Support for IT Professionals - 
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
How-to: Windows 2000 DNS: 
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
FAQ W2K/2K3 DNS: 
http://support.microsoft.com/default.aspx?scid=kb;EN-US;291382

Relevant Pages

  • Re: Multihomed server 2000
    ... I have a server with 2 NICs; ... and everything on this NIC is normal and active; I can ping it ... for 192.168.200 to the RRAS router. ...
    (microsoft.public.windows.server.networking)
  • Re: Ping reply through the same interface
    ... You are *not* supposed to have two nics in the same subnet unless they are ... If they are in the same subnet they will not work as you want. ... If the source of the Ping is not in the same subnet as the nic it pinged ... Routes leaving the server are determined by the Destination and how the ...
    (microsoft.public.windows.server.networking)
  • Re: Remote Web Desktop Connection - DHCP scope
    ... ping the server and the isp dns as well as access the 'net. ... the workgroup computers can access the internet through the server. ... workgroup computer I can ping 192.168.16.2 but not the router 192.168.1.1 see ... I have a couple of questions, when setting up the two nics, I have not ...
    (microsoft.public.windows.server.sbs)
  • Re: FreeBSD 2 nic one to route one to DB - how do I?
    ... The second nic should route to the DB server. ... PING db.reck.dk: 56 data bytes ... Option 1 needs both NICs, option 2 only needs one NIC. ...
    (comp.unix.bsd.freebsd.misc)
  • Re: NLB IP Address Query (load balanced IIS)
    ... MVP - Windows Server - Clustering ... anyway and the convergence goes through fine on NLB Manager. ... web server how it didn't get hacked - just pure luck I guess! ... Gonna put the 2 web server nodes' NLB NICs in a VLAN and ...
    (microsoft.public.windows.server.clustering)