Not Responding

[caddo65590]

Hi All,
I have a couple of w2k adv servers one with sp3 and the rest with sp4 all
running different applications.
There are times that these servers becomes unresponsive that no one can get
to it by either pinging by name or ip.
If you logon physically to the server, everything seems normal except you
can't ping anything from the server too.
When rebooted everything becomes normal and part of the network again. There
are no events logged during this periods that
the servers becomes unresponsive.
Has anyone experience this problem before or have any ideas WHY?
Thanks

 

[Craig Mercer \(MCT\)]

Without knowing your network setup it is kind of hard
to give you an authoratative answer to your question. So here are a couple
of things to look into which I hope can help.
1. Look at your DNS, there may be some name resolution problems, in
particular the reverse lookup zones.

2. Routing, if you are using a W2k box as a router look and the routing
tables and see if there are any issues their. (this one got me a while ago).

3. Normal networking issues, such as slow/bad connections, conflicting
applications causing the servers to lock up (look at event logs for this
one) etc.

This list could go on forever, but that seems like a start point. Good Luck
and let me know the outcome.

Craig Mercer (MCT)

 

[Guest]

We had a similar problem with a Dell server. Suddenly it
would go offline - not network accessible. It was still
up, no errors logged, it just couldn't be accessed from
the network, and when logged in directly to the server
console, you could not get out to any network resources.

It turned out that the Gigabit NIC embedded on the
motherboard had a flaw in it. Occasionally, and for no
reason we could ascertain, the NIC would suddenly lose
it's default gateway configuration. On the command
prompt, the command: netstat -nr displays the routing
table, and no entry existed for the default route.
Looking at the NIC properties showed the static IP, the
mask, and the default gateway all configured, but the
ipconfig command at the command prompt displayed only the
IP address and the mask. No address for the default
gateway was listed.

While the server was in this state, starting a command
prompt and using the route add command we could enter at
route for network 0.0.0.0 (the default route) and point
it to the router that should be the defaut gateway.

This would resolve the issue and the server was suddenly
working fine. It would stay that way for a few days, then
lose the route again. We finally or a new motherboard and
the problem has been fixed ever since.

Not sure if this is what you are experiencing, but I
thought I'd throw it out here just in case...