Able to play an MMO but unable to browse the internet

[Miss_Lana]

So I've just finished building my first rig (this is a big feat for me as I'm not incredibly computer-savvy) and everything seemed to be ok up until last night. I have Google Chrome Canary installed, and was watching Netflix on it when I got the "He's dead Jim!" - on every tab I had open.

I tested whether it was just Canary having that problem, but every browser I have is having the same issue.

I was also downloading files for Elder Scrolls Online and playing Guild Wars 2 at the time. The weird part (to me at least) is that the ESO download stopped, but I was still able to play GW2 just fine, though I was not able to open the trading post. The ping in GW2 was completely normal.

I've restarted the computer, I've reset the modem and I'm still not sure what is causing it. I can't access the modem through any browser either, though I am able to access the internet with no problems on the laptop and phones.

Windows 7 Home Premium x64
Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz
MSI H97 Gaming 3 Motherboard
8.00GB RAM
GeForce GTX 660 GPU

If any other info is needed to make a diagnosis, let me know. Any help is greatly appreciated. This is puzzling me.

 

[bill001g]

Sounds like you lost the DNS server setting.

Open a cmd window and type
NSLOOKUP www.tomshardware.com

Then
NSLOOKUP www.tomshardware.com 8.8.8.8


You very well could get different results because of how this site is done but what you are looking for is to see if one responds and the other does not.

You could try to go into the ipv4 settings and put 8.8.8.8 in as the the DNS server and see if that works.

The pretty standard config is for your PC to ask your router which then asks your ISP DNS server. There are a number of things that can go wrong with that so if it works with a hardcoded DNS but does not work otherwise I would see if there is some setting wrong in the router.

I tend to always use google DNS (ie 8.8.8.8) because it seems to be more stable than my ISP dns.

If it resolves on both NSLOOKUP commands then you likely have some issue with the browser.