Could be an hardware issue. Try mii-tool. On Centos it is provided by the package net-tools.
http://www.netadmintools.com/html/mii-tool.man.html Also grep 'dmesg' output for eth0. There might be some hints there, whether the interface came up, if so at what speed, etc. - Sukanta On Sun, Apr 19, 2009 at 2:52 PM, Edwin Lee <[email protected]>wrote: > > Hi, > > > Ok. Can you run a ping instead of telnet? Just try to ping > > 192.168.1.254 and > > then see whether it shows up in your arp table. > > > > ping -c 2 192.168.1.254 > > arp -an > > > Here it is, following up in the same terminal session as the last post: > > $ ping -c 2 192..168.1.254 > PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data. > From 192.168.1.64 icmp_seq=1 Destination Host Unreachable > From 192.168.1.64 icmp_seq=2 Destination Host Unreachable > > --- 192.168.1.254 ping statistics --- > 2 packets transmitted, 0 received, +2 errors, 100% packet loss, time > 1006ms, pipe 2 > $ arp -an > ? (192.168.1.254) at <incomplete> on eth0 > > > > Thanks and Regards, > Edwin > > > > New Email names for you! > Get the Email name you've always wanted on the new @ymail and @rocketmail. > Hurry before someone else does! > http://mail.promotions.yahoo.com/newdomains/sg/ > > > _______________________________________________ > Slugnet mailing list > [email protected] > http://wiki.lugs.org.sg/LugsMailingListFaq > http://www.lugs.org.sg/mailman/listinfo/slugnet >
_______________________________________________ Slugnet mailing list [email protected] http://wiki.lugs.org.sg/LugsMailingListFaq http://www.lugs.org.sg/mailman/listinfo/slugnet
