• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Windows 2003 machine cannot ping default gateway

S

svizi

n00b
Joined
Apr 6, 2011
Messages
23
Hi!
I have a machine running Windows 2003 R2 that cannot ping the default gateway.This is a machine joined in AD domain. All other machines can ping gateway and get access to the internet except from this one.
Settins are checked million times, but cannot find a way through.
Any suggestions accepted.

Thanks
 
192.168.10.xx
255.255.255.0
192.168.10.1

Same settings as the other machines in the domain that can get to the internet through the gateway.
 
Check the physical connection between the two. I would also closely examine the IP configuration to make sure that it indeed has the correct subnet mask and default gateway.
 
The machine can be pinged, rdp and do anything else from the machines of domain, except from getting outside of the gateway and ping it. Settings are correct. Strange...
 
Is this a VM or a physical machine? Do you have any pseudo interfaces on the machine that are 192.168.10.x?
 
So the only symptom is that your sick machine can't communicate at all with the default gateway? It can communicate with all other devices on the network? And all devices can communicate with the default gateway?

What's the default gateway? Any way to get a packet dump on it? The issue is either that the packets aren't arriving at the gw, or that the gw isn't sending anything back. Without knowing more, I'd take a quick look at the arp tables on both your sick machine and the gw.
 
This is a physical machine with one interface.
Yes the only symptom is that it cannot communicate with the gateway. It can communicate with all other devices and all other devices can communicate with the gateway.
Default gateway is a linux machine doing the routing. I cannot see anything strange in the route concerning this IP. The gw allows to be pinged.
I have erased the arp tables and tried to ping again with no success though.
 
Linux makes diagnostics pretty easy then. Read up on tcpdump. You'll want to get it started then try passing some traffic. See what's going on.

It's like wireshark for linux. Speaking of wireshark, I'd throw it on your windows box and watch the traffic there too.
 
Which was called etherfind before linux even existed ;)

/kicks CEpeep off his lawn
 
Between the linux and the server there is a Gigabit switch, where all the other computers and the router are connected.
I think i will follow the next steps.
1. Unjoin the domain and join back to see if anything changes. You never know.
2. Update the drivers of the network card. They are now 3 years old.
3. Install wireshark and figure out the problem.

I have also saw that this is the only machine that i cannot rdp with it's hostname. That's strange as dns works as expected and nslookup gives the name of the machine.
 
You must log in or register to reply here.
Back
Top