Here it is. Some of my terminology might be a little goofed up but I really do have some idea of what's what:
I set up a small home network at my folks house some time ago that has hummed along for at least a year. There's 4 computers on it at the moment, 2 WIFI (one XP-pro, one XP-home) and 2 wired (both XP-home) on the Belkin F5D7530-4 Wireless-G + 4 port router.
Sometime today, one of the wired PC's could not connect to the net. 'No problem', I thought and went about cycling power to everything (PC, router, modem). I tried another port on the router then another ethernet cable...no result.
I ipconfig /release'd, then renewed from the command prompt to no avail. When /renew was performed, it apparently was properly reassigned as the display confirms the expected IP address of <192.168.2.3> for this machine and the default gateway is the expected <192.168.2.1>. DNS and DHCP appear properly configured (defaults/automatically assign/etc). I can ping the router but not out to the internet. When I try to reach the router browser-based config screen, I get time-outs using both IE and Opera. If I use another comp to view the router settings, the broken machine shows on the list of connected devices with the proper MAC and IP.
The device manager shows the NIC functioning properly. I disabled the NIC in the device manager, then cycled power, enebled the NIC, then cycle power = no joy. I disabled the onboard NIC in the BIOS at start up, reboot, reenable, reboot = nada. I am seeing the conection lights lit on both the router and at the PC's ethernet port.
This thing was working fine for months up to some time today. All other machines on the network are working 100%. I probably tried a few other things that I've forgotten.
Help!?!
No 'net on single pc on network
Moderator: Queue Moderator
- jnglmassiv
- Batboard $upporter
- Posts: 512
- Joined: Sun Feb 24, 2002 4:00 pm
Dead NIC, unless the computer in question had a firewall installed at the same time it quit working i would say you covered all the possibilities.
Disable the onboard NIC and try buying a PCI NIC and toss it in and see what happens.
Disable the onboard NIC and try buying a PCI NIC and toss it in and see what happens.
Duct tape is like the force, it has a dark side and a light side and it holds the universe together.
"I Reject Your Reality And Substitute My Own!" - Adam Savage
"I Reject Your Reality And Substitute My Own!" - Adam Savage
- jnglmassiv
- Batboard $upporter
- Posts: 512
- Joined: Sun Feb 24, 2002 4:00 pm
- jnglmassiv
- Batboard $upporter
- Posts: 512
- Joined: Sun Feb 24, 2002 4:00 pm
I had someone tell me a long time ago that there was either a virus or spyware that screwed up the Winsock stack. You can try this link to download a reapir utility. Maybe it will help, maybe it will do nothing.
http://www.shareup.com/XP_TCP_IP_Repair ... 10883.html
http://www.shareup.com/XP_TCP_IP_Repair ... 10883.html