Laptop is connected to the internet but can't browse [Solved/Closed]

afranklin98 3 Posts Thursday November 5, 2015Registration date November 6, 2015 Last seen - Nov 5, 2015 at 07:46 PM - Latest reply:  fatlinoff
- Nov 24, 2017 at 06:01 PM
Its been so long, and i'm trying to make it up to her so im trying to fix her laptop, because im pretty good with computers otherwise. Basically shes wirelessly connected and I tried connecting my computers ethernet cord to it, and shes 100% connected, no other application or browser says shes connected though. So that made me think hm maybe there is a virus, so I ran it in safe mode with networking and it let me browse, so I know there is a virus on it. But mainly my question is, any tips to fix or could I somehow get a windows 10 download off this laptop and just wipe the other one hard installation of windows 10 and just factory new brand new computer settings. I'm currently running MalwareBytes, I know its a virus though, I just don't know how to fix it. What other computer can browse in safe mode but can't in regular.
See more 

11 replies

xpcman 18717 Posts Wednesday October 8, 2008Registration dateModeratorStatus March 19, 2018 Last seen - Nov 5, 2015 at 08:05 PM
Perhaps this tip might help:

Try the following:

Open Command Prompt as Administrator (click Start, type "command prompt" in the search bar, right-click the Command Prompt icon that will appear and choose "Run As Administrator" from the menu).

Enter the following commands followed by enter:

netsh I i r r

netsh winsock reset

You will be resetting the tcp/ip stack and the winsock catalog. You will need to restart afterwards. That usually fixes the problem. Follow this up with a malware check. Something has messed with your networking stacks.

Are you running multiple anti-virus programs and/or firewalls? You should only be running one at a time.
Was this answer helpful?  
I'm using Windows 8..Thank you..really it works
U are a genius man.God bless worked
Thankyou so much. It worked. :)
Your article on resetting the tcp/ip stack and the winsock catalog was excellent and solved a problem I had been experiencing for many months. Regards, Trevor