probably mii-tool will tell you something about the card. ifconfig -a reports any nic errors? run tcpdump -n -i <interface_name> to see what hapens.
Also, if you are using a hub try to "force" all things attached to the hub to "10mb half" (no autonegotiate). Jon Miller wrote: >Recently I had to replace a motherboard and 2 network card due to a static >discharge in a rack. I've now have 2 networks cards in the server and they >load ok, both can be seen with lspci. The interrupts are not being shared or >anything of the sort. Yet one of the cards (Netgear FA311) will not respond >to a ping. This the is tests that I've done. >1) connect a cable from the FA311 to a hub, put my workstation on the hub and >the Cisco 2821 router's gigabit interface on the same hub. > from there I ping the router - that was good, ping the gateway server with > the FA311 (no reply, times out). >2) from the router I was able to ping the workstation yet when pinging the >gateway server again times out and no reply. > >Had a look at the interrupt the card is on irq19 whereas the other card is on >irq 16. >I've unloaded the driver and reloaded it and still nothing and no errors when >it loads. > >Can anyone suggest any test or a fix that may help in resolving this issue? > >Summary: >Gateway server Debian 3.x >eth0 - Netgear FA311* *fa3xx.o (notice that it states that it is running a >half duplex if this helps) >eth1 - Realtek 8129 > >a crossover cable connects the gateway server (eth0 192.168.100.2) to the >Cisco 2821 router (gigaethernet0/0 192.168.100.1), whereas the other nic >(eth1) connects to a Cisco 2950 switch. > >Thanks > > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
