Unreachable --- suzy.suseland.net ping statistics --- 7 packets transmitted, 0 received, +7 errors, 100% loss, time 8773ms, pipe 3
If I run ifconfig I get:
eth0 Link encap:Ethernet HWaddr 00:10:DC:1F:95:78 inet addr:192.168.3.70 Bcast:192.168.255.255 Mask:255.255.0.0 inet6 addr: fe80::210:dcff:fe1f:9578/10 Scope:Link 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:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:18 Base address:0x6000
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:503 errors:0 dropped:0 overruns:0 frame:0 TX packets:503 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:49204 (48.0 Kb) TX bytes:49204 (48.0 Kb)
The thing that immediately strikes me is that it is the RX and TX packet count on lo rather than eth0 that is incrementing after each ping.
If I look at /var/log/messages I see the following message repeated several times:
Jul 13 22:59:52 chocchip kernel: NETDEV WATCHDOG: eth0: transmit timed out Jul 13 22:59:52 chocchip kernel: eth0: Tx queue start entry 4 dirty entry 0. Jul 13 22:59:52 chocchip kernel: eth0: Tx descriptor 0 is 00002000. (queue head) Jul 13 22:59:52 chocchip kernel: eth0: Tx descriptor 1 is 00002000. Jul 13 22:59:52 chocchip kernel: eth0: Tx descriptor 2 is 00002000. Jul 13 22:59:52 chocchip kernel: eth0: Tx descriptor 3 is 00002000. Jul 13 22:59:52 chocchip kernel: eth0: Setting half-duplex based on auto-negotiated partner ability 0000.
Can someone more knowledgeable than myself suggest what is going on?
If I dual boot into Microsoft Windows the network / remote hosts can be accessed without problems.
Help!
Ian.