Unable to access the internet, no proxy setti

November 12, 2010 at 08:48:02
Specs: Windows XP, 2.4 GHz / 4093 MB
Ok, so here is one that stumped me, and be ready because it is about to get complicated. I was working on a computer today, and I noticed no icon for the networking card was displaying under network connections in Windows XP. I promptly refreshed the network card by uninstalling it in device manager and allowing plug and play to do its thing in recognizing it in a check for new hardware. This got the icon back, and I was able to verify the protocols were alright. However, the internet was still inactive on the machine (no registration with the router), so I went ahead and defaulted to these commands: netsh winsock reset, netsh int ip reset reset.log, ipconfig /release, ipconfig /renew. This allowed the computer to register with the dhcp of the router and receive an IP address. It also recognized the dns of the network router, but it still would not get online. However, the computer thought it had access and tried to connect to the automatic update server, but it could not. My guess was that the winsock dll files had become corrupted, but I wasn't sure. Now, this could be a simple fix like updating the drivers for the networking adapter after refreshing it, or it could be complicated. What is your best advice as to the nature of the problem? If you have seen this before how did you solve it? No there is no proxy setting on the computer :p of course I checked that first.

See More: Unable to access the internet, no proxy setti

Report •

#1
November 12, 2010 at 10:17:38
did you confirm with a ipconfig /all that it has the proper gateway and dns settings?

How to properly post a question: http://tinyurl.com/2fsqqmu


Report •

#2
November 12, 2010 at 13:36:36
Yes. Everything appears normal, but the internet doesn't work. I've been doing personal research on the problem because I hate not having an answer, and it appears that checking msinfo32 and verifying the protocols under the networking section is the easiest way to check for winsock corruption. Then the registry keys need to be deleted, and then you have to manually reconfigure the protocol for tcp/ip. If that doesn't work then I guess it is just a bad NIC?

Report •

#3
November 12, 2010 at 14:13:48
post the results of an ipconfig /all and a tracert to yahoo.com for review

How to properly post a question: http://tinyurl.com/2fsqqmu


Report •

Related Solutions

#4
November 12, 2010 at 15:33:11
I'm off duty atm, so I don't have the computer in front of me. I can tell you that tracert will time out at the station itself and not reach the router based on the symptoms, and ipconfig /all is going to look normal - I'm an IT computer technician at a company, and i see a lot of ipconfigs.

Report •

Ask Question