I have a network of 3 pc's. They are all running FC3. I have an old pc running RH9 that acted as a router connecting to the web via a speedtouch usb modem. All worked fine. I disconnected the router pc and I am no longer using it. I replaced it with a netgear DG834GT router/modem (supplied by Sky, UK) running firmware Version V1.02.28. I am using cables to connect. Two of the pc's connect to the web just fine using DHCP. The third will not. If I try to ping www.google.com or the google ip address on the pc that is not working I get:

and yet if I type in the ip address of the netgear router I can access the the netgear configuration pages of the router and all diagnostics and tests indicate all is well so there is no problem between the pc and the netgear router and no problem with the router. When I review the network config of the working pc's and the faulty one I can't see any difference.

If anyone has any ideas I would appreciate some assistance.

Regards,

Matthew

Well, it's probably either (a) the PC doesn't have its gateway properly configured, or (b) the router isn't letting the PC access the internet.

You can check if it's (a) by running ip route list on the PC. It should have a line like default via address.of.router. If not, the dhcp isn't working properly, so the PC doesn't know how to get out.

If it's (b), you'll have to check on the router to make sure it's not doing anything special with the IP address that the wonky PC is using.

If the PC still isn't working, try posting the response from ip route list. That'll at least give us an idea what's going on.

the response from ip route:
The router is out the box - never been used. I am pretty sure it won't have been configured to treat this pc in any special way.

Thx

Thanks guys. I came across a topic where a similar issue was being discussed and I found this advice:
I replaced myrouter with the ip of the netgear linux gateway and the web browser etc started working.
The next reboot and they were not working again. I went to system-config-network and navigated to the dialogue where you choose dhcp and noticed in the greyed out unselected area for static assignments (theoretically not applicable if you are using dhcp) the default gateway had somehow been set to another PC on the network. i.e. it was picking up the wrong PC to use as a gateway. I selected static assignment to enable the field, set the gateway ip to the right address and saved/reactivated the config. As such it was now running as static (risky because the dhcp server might try and use the ip I had assigned for the box). I then went in again and selected dhcp again and saved/reactivated and it is now permanently looking at the right gateway and therefore functional. If it is the case that the designers are expecting you to follow this procedure to set the default gateway on a dhcp box I think it is a poor design. Anyway it works. Hope you will help me spread the message around!
Regards,
Matthew