Heh, it looks like your NIC is faulty. dmesg shows that NIC is connected to the network. You can play a bit with mii-diag (setting line between 10/100base with/without full duplex), but changing of the NIC will save your time.
Gregory On Thursday 24 March 2005 15:20, Keith Vassallo wrote: > IP has not bound to the NIC... > > 1) What does that mean? > 2) How do I check it? > > Thanks, > > Keith > > On Thu, 2005-03-24 at 14:37 +0100, Iain Sims wrote: > > > ifconfig: > > > eth0 Link Encap:Ethernet HWaddr:00:0B:2B:0D:D3:D9 > > > inet addr:192.168.1.101 Bcast:192.168.1.255 MasK:255.255.255.0 > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > > collisions:0 txqueuelen:1000 > > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > > Interrupt:19 Base address:0xc000 > > > > > > >From 192.168.1.101 icmp_seq=2 Destination Host Unreachable > > > > IP has not bound to the NIC it would seem. Can you check and confirm > > this is correct?? > > > > Iain. > > > > _______________________________________________ > > MLUG-list mailing list > > [email protected] > > http://mailserv.megabyte.net/mailman/listinfo/mlug-list > > _______________________________________________ > MLUG-list mailing list > [email protected] > http://mailserv.megabyte.net/mailman/listinfo/mlug-list
