On January 25, 2004 10:54 pm, sting sting wrote: > Hello, > > thnxs . > More Info that was required is: > ping 127.0.0.1 and ping to the ip of the machine does succeed. > Ping from machines in the network does not succeed. > route -n returns: > Destination GW mask Flags Metric Ref Use > Iface > 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 > eth0 > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 > 0 lo > 0.0.0.0 192.168.0.254 0.0.0.0 UG 0 0 0 > eth0 > > > indeed 192.168.0.254 is the GW (and ping to 192.168.0.254 does not succeed > even physically other machines on the same hub may ping it successfully) > regards > sting > This is starting to look like a bad cable or swith/hub port if no-one can talk to your machine and it cannot talk to the others. Also, the nic could still be broken but the chip is working and the physical interface is not. Try: -check for link lites at both ends (doesn't mean much really) -plugging another machine into your port on the switch/hub (you may need to reboot the switch or otherwise clear the arp cache) -if that works, try you machines cat5 cable on another machine -if that works, try and plug another machine into your data drop if you have in-wall wiring. (again, a hub is ok, but a switch may need the cache cleared) The idea here is to test each of your connection components in a known-good environment. It will cut through the pile faster than changing things in the broken environment. -- Pete Nesbitt, rhce -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
