On Wed, Dec 26, 2001 at 10:38:01PM +0000, Rachel Andrew wrote: > > > > > > >How exactly are you pinging? Something like ping 192.168.0.XXX or ping > >myhost.mydomain.com? What exactly are the results when you try? > > neither work - my gateway for instance is 10.0.0.10 > > if I ping that (I then have to ctrl-C out of it): > ----10.0.0.10 ping statistics ---- > 4 packets transmitted, 0 packets received, 100% packet loss > > I've posted the relevant ifconfig, route -n in my previous post.
As others have said, your software config looks good. If you are using a kernel older than 2.2.17 you might want to try a newer one since there have been many different tulip compatable chips and some did require newer versions of the tulip driver to work well. It probably wouldn't hurt to try the "old_tulip" module as well. You could have a look at Donald Becker's site to see if there is a newer version of the drivers then what is in your kernel although I think the ones in 2.2.19 are reasonably current. BTW what kernel messages are reported when you load the tulip module? Beyond that, I'd suspect the cable or connector. I know you said you tried the cable with other devices and it worked fine but I've seen situations where either the cable end or the card connector was just bad enough to fail some of the time but not allways. Also, make sure the cable is plugged in securely before you power up the machine (or at least before the tulip module loads) otherwise it won't detect the correct duplex (half/full) and speed (10/100) properly. Two other questions, when you try to ping from this machine, does the light on the hub blink? Also what type of hub is this? -- Ray
