Unable To Ping Gateway...

[karenko]

There's probably a good/easy answer to this but I'm at a loss...

I'm running a small LAN with Win 2008 Server and (for the purpose of this discussion) a single Win 2000 Professional "workstation". It's a new/fresh install of 2008 Server. I thought I set up DNS and DHCP properly (we'll see ).

I'll call the server "S", the workstation "W", and the gateway "G" (a Linksys hard-wired unit). On S (a static IP addr), an ipconfig will show my static address, the ip address of G, I've set up forwarding to my ISP DNS's so I can ping "G", "W", out to the internet, get DNS translation/resolution, IE works fine, ... (it's just as it should).

However, on "W", an ipconfig shows the same gateway address (divied out by the server), I can ping "S", I can loopback, but when I try to ping "G" - I get timeouts (e.g. I can't get there). Yes, all physical connections are good. Consequently I can't get out to the internet, I can't get DNS resolution, ...

Hence (succinctly) - why can I ping "G" from "S" but not "W"? Have I inadvertently set up some sort of filtering/routing to nowhere?

I appreciate any thoughts/suggestions!

AMK

 

[karenko]

An update...

I guess the good news is that I solved the problem (and perhaps I got the server configuration correct ).

The short version of what subsequently transpired was that I took the server down and booted the workstation ("w") locally (not part of the domain but still physically connected to the LAN). I still couldn't ping the gateway (yes, the ipconfig still showed it as the default gateway - yes, I released it and manually entered the gateway). I put in another NIC, configured it, and voila - all works well. Server up and all is well...

(I'm laughing) If there is a theoritician who might want to explain why the defective NIC would allow me to ping everything but the gateway (e.g. W -> S works, S -> W works, S -> G works, but W -> G doesn't work), I'd buy him/her a coffee.

Sorry for the diatribe - maybe somebody else will have this problem (e.g. try the NIC/hardware).

As this wasn't truly a Server problem, I'm to work on the next Server "mystery"; there are plenty of them...

(Thanks)

AMK