Member Avatar for viperman224

I just got an Emachine in to repair. It is running windows XP Home. The original complaint was she could connect to her wireless router but couldn't go online. I brought it back to the shop and tried to connect to my wired network. I can connect to the network, ping the router etc. I can not go online or see any of the machines on the network. I know that there are firewalls within windows. I have shut them off along with any other setting I could think of that would stop it from going online. I scanned all of the user accounts for spyware and viruses. I removed the few that were found. I still can not go online. I even tried pluging in a Linksys NIC card that I am positive works. I still have the same problem. I am leaning towards a full reload. I also installed Fire Fox and still had the same issue. Netscape also has the same issue. I can not get online. The browsers are set to automaticaly detect the proxy settings etc. I went throught the Windows XP network configuration settings as well. Still no internet. I stuck one of my own hard drives in and loaded it with my copy of windows just to double check that it was a windows issue on the Emachine drive. It was. It went online no problem with my drive. Any Ideas? Thanks.

  • 2 Contributors
  • 3 Replies
  • 218 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by caperjack

Dani AI

Generated

Short summary and background: the symptom described — the machine can join the LAN and ping the router but browsers (IE, Netscape, Firefox) cannot access the Internet — is a classic sign of Winsock or TCP/IP stack corruption rather than a physical NIC failure. The tool suggested by and used successfully by repairs the Winsock layer and is the correct first step before doing a full OS reload. ()

Practical checklist to try before reinstalling Windows (run these from an Administrator command prompt):

ipconfig /all
ping 127.0.0.1
ping <default-gateway-IP>
ping 8.8.8.8
nslookup www.google.com
ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh int ip reset c:\resetlog.txt
netsh winsock reset
(reboot)

The netsh int ip reset and netsh winsock reset sequence is the documented, supported repair for many XP-era networking failures; back up any custom network settings before running them. (support.microsoft.com)

If netsh winsock reset does not work (or if the machine is pre-SP2), the alternate supported path is to remove the corrupted Winsock registry keys and reinstall TCP/IP — this is more invasive and requires a registry backup / restore point. If you see errors like “an operation was attempted on something that is not a socket” or IP renew failures, follow the manual recovery steps in the Winsock guidance. ()

Cautions and follow‑ups: resetting Winsock/TCP-IP can break third‑party network filters (antivirus, VPN, firewall, proxy clients); note which programs are installed and be prepared to reinstall or re-enable them after the reset. If LSP/filter drivers remain after these repairs, uninstalling the NIC driver and reinstalling it (or restoring from a known good system image) is the next safe move — a full reload is only necessary when registry/OS corruption cannot be repaired. ()

Recommended Answers

All 3 Replies

Member Avatar for caperjack

go HERE and try the winsoc fix#18

Member Avatar for viperman224

Thanks for the reply. I ran the software on the Emachine and it worked. Thanks.

Member Avatar for caperjack

Thanks for the reply. I ran the software on the Emachine and it worked. Thanks.

great. it nice when something actually works

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.