Member Avatar for JohnnyMonk

forgive me if this should be listed under viruses... i just setup a pc for a lady i work with today, and when she came back from lunch the network card wasn't sending or receivign packets. so i assume the nic is dead. put a new one in same problem. then i notice i forgot to install norton my b. i checked for a few viruses, i ran stinger, and some fix tools from norton, such as netsky, mydoom and beagle, i also installed norton corporate edition but i am unable to update it due to me not being able to get out on the network. anyone have anyideas on why this machine would be acting up the way it is?

  • 6 Contributors
  • 9 Replies
  • 1K Views
  • 7 Years Discussion Span
  • Latest Post Latest Post by smferoz

Dani AI

Generated

Good pointers from on cabling/ports and from on basics. Given the symptoms reported by and (link LEDs active, can ping self, but timeouts to anything else, and sometimes it just starts working), the next likely culprits are a speed/duplex negotiation mismatch, a corrupted Winsock/TCP/IP stack, or stale ARP information after a power event.

Quick, targeted checks that build on the thread without repeating earlier steps:

  • Force speed/duplex on both ends. In Device Manager, open the NIC, Advanced tab, set Speed & Duplex to 100Mb Full (or 10Mb Full to test). If you control the switch, match it there too. Mismatches often show link lights but give CRC/errors and timeouts.

  • Check OS-level counters. If errors climb, you almost certainly have a duplex or physical-layer problem: 

    netstat -e

  • Verify ARP to the default gateway. If there is no entry or it shows as incomplete, clear and repopulate:

    arp -a
arp -d *
ping <gateway_ip>

  • If you recently removed malware or security software, repair the networking stack (reboot after):

    netsh winsock reset
netsh int ip reset c:\resetlog.txt

For post-outage: power-cycle the switch or move the server to a known-good port; disable/enable the NIC; update the NIC driver; and check System logs for driver resets or link flaps (eventvwr.msc). If this is a managed switch, ask the admin to look for port-security/802.1X/VLAN changes on that port. A quick isolation trick: boot Safe Mode with Networking; if pings work there, a third-party filter driver (VPN/AV/IPS) is likely interfering.

Finally, as hinted, keep a spare NIC and cable handy, and note the exact driver version and switch port settings when you find a stable combo.

Recommended Answers

All 9 Replies

Member Avatar for bentkey

The NIC may not be dead, you may have a bad cable connection or the switch port you are plugging into does not correctly negotiate autoconnect speed with the NIC you are using. Try a new cable first. Best choice is to borrow one from a pc you know is working.

Member Avatar for DMR

... or the switch port you are plugging into does not correctly negotiate autoconnect...

Yes- if changing the cable doesn't hep, try a different port as well.

If those suggestions don't do the trick, it might be time to look "inside the box":

- Have you verified that the TCP/IP stack is functioning correctly by pinging the loopback device?:

ping 127.0.0.1
or
ping localhost

- Can you ping the IP of the NIC? Can you ping the computer by its hostname?

- When you say that it isn't sending or receiving packets, what utility are you using to determine this?


<edit>

This being essentially a networking question, I'll move this thread to the networking forum...

</edit>

Member Avatar for JohnnyMonk

i'm able to ping the nic with the ip address that i have assigned to it. but if i try to ping another computer by ip or name it times out. by looking at the local area connection status. it claims there are no packets being sent. however the lights on the card are blinking away. i have put a new nic in and am working off of a different port and have the same problem.

Member Avatar for DMR

Do the following commands show the proper default gateway and routing information?:

ipconfig /all
route print

If so, you might want to look further into the possibility of damage by a malicious program. Look through the threads in our Security form for information on using Ad Aware, SpyBot, HijackThis, and other tools. If running those tools leads you to suspect an infection, start a new thread in Security and post as much info there as possible in terms of waht you've done and the results you've gotten.

Member Avatar for JohnnyMonk

too put closure to this post, the damn card just started working on its own again...

Member Avatar for DMR

Uh-oh... I'm not entirely sure that's a Good Thing. Better make sure you have a spare NIC hanging around just in case... :p

Member Avatar for kdommie

I have a similar problem, I run win 2003 server, over there weekend there were long period of power outage in the office and thus the server went off. on Booting, the Nic card could blink but but cant send or receive data. in Nic card properties it shows sent and receive packets but on ping other computers on network can't reply.
Ping self IP replies. Please help.

Member Avatar for jingda

Have you follow the suggestion above. Does other colleagues of yours have this problem. How about a spare NIC card and test it out.

Member Avatar for smferoz

Hi,

To check whether your NIC is working properly run this command in command promt as below :

Ping 127.0.0.1 if the ping response is complete then your nic is working properly and moreover check the slot where the NIC is installed could be problem with the slot or cabling sequence or check whether you have installed NIC Drivers properly in device manager if there is exclamation mark then NIC drivers are not installed properly try to install nic drivers install a Microsoft Loop Back Adapter present in os by defult and check .

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.