Discussion Locked

NIC is not sending or recieving packets

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Here is my dilema. I was asked to attend to a client who was having trouble with their DSL install. After sorting out the horror story they had for a network everyone seemed to be connecting good except one machine. This particular workstaion does not seem to be sending or recieving packets over the network. It will detect a connection when plugged in but the packets sent and recieved remain at zero and I am unable to ping out. I am bringing a new NIC in tomorrow to make sure it is not a hardware issue but I wanted to see if anyone had any other ideas before I had to preform surgery.

p.s. I found out later (much later) that the client was suddenly unable to print to a network printer earlier today (one of those lovely, "oh I forgot to mention" moments). The PC is a WIN 2K box that is approx. 5 years old. The sudden loss of connectivity and the workstations age is what initialy led me to suspect hardware failure.

5 replies

by ltop

Hi,

Mmmmm, Workstation indicates network cable plugged in but can't ping, unable to send / receive packets.

Device manager indicating any problems with the NIC?

Any chance you checked the Ip config. Ping the loopback address successfully?

Otherwise a faulty ethernet cable ?

Anyone been making alterations on the patch panel which may cause the PC to be not on the network anymore.

Let us know how u get on,

cheers

by sgt_shultz

i agree very likely hardware, except in your case i bet it is bad ip address on account of the dsl/dhcp server changed and probably is serving up a different subnet. i bet they are screaming about printing being down right about now also...
it can't hurt to replace the nic and would be a good thing probably.
before replacing nic:
got link light? if no, maybe it's the cable or jack. bring a known good replacement patch cable with you to try. if you have a really long one you can plug pc into known good network jack at next cubicle or something pretty fast to prove it doesn't work with a new cable and a new jack and show customer some action...
if not cable or jack, maybe got bad ip address. check to see if dhcp client and any gateway settings. then do Start/run/cmd ipconfig and see if looks llike good ip address (do same thing on working pc to get reference)
this is very likely in your situation imho given mode of failure (new dsl). so put bad workstation on dhcp and reboot. if already dhcp client, check that gateway address is correct (again, check on other box. gateway will be dhcp server and new dsl router probably)
then do ipconfig /release then ipconfig /renew at command prompt and watch screen for dhcp errors
then look at device manager, see if nic is banged.
then get properties of nic and note the media type. probably 'auto' but if locked down to say '10mb half duplex' or '100mb full duplex' you probably want to set the new one up likewise.
you can try uninstalling and reinstalling the nic which has outside chance of working but if me i would be replacing nic at that point due to age and inexpensiveness of new nic and fact that customer already shelling out for my visit.
if your new nic has powersaving 'feature' turn that off imho.
but even more likely is that bad machine not getting good ip address anymore. maybe it had static ip address before and it is invalid now. i have also seen a corrupt tcpip stack.

This discussion is closed to new replies.