Windows 8.1 Update DNS problem

[Ian_Balisy]

Just yesterday I updated to Windows 8.1 from a (basically) 100% stable Windows 8 build. It seems I am completely unable to connect to the internet despite being connected to the wifi and every other device connecting just fine.

The issue shows upon troubleshooting as "Windows can't communicate with the device or resource (Primary DNS Server)".

I have done everything I knew to do plus everything I found online in the past several hours that has solved the problem for others. Switching to Google's public DNS, flushing DNS and cache, reinstalling drivers which haven't changed since 2012, disabling IPv6 connections, disabling Windows Firewall and Defender, ensuring router firmware is up to date... Nothing has worked.

I'm open to any and all suggestions short of replacing my router.

System: Asus Z97-A (with all correct drivers), Core i5 4690K, Rosewill RNX-N150HG wireless adapter, Apple Airport Express (2012)

[Ssoele]

Could you give us the output of the following command in CMD?

ipconfig /all

[1hitwonder]

First ping the default gateway to ensure connectivity to your router.  Then try to ping another device on the network to ensure you are on the same network as your PC.  Then try to ping 8.8.8.8, this is a google DNS server.  Pinging by IP address rather than the name will test DNS.  

 

Also have you tried statically configuring an IP address and default gateway?

[Ian_Balisy]

 

Could you give us the output of the following command in CMD?

ipconfig /all

 

 

First ping the default gateway to ensure connectivity to your router.  Then try to ping another device on the network to ensure you are on the same network as your PC.  Then try to ping 8.8.8.8, this is a google DNS server.  Pinging by IP address rather than the name will test DNS.  

 

Also have you tried statically configuring an IP address and default gateway?

 

It seems that this time around setting a static IP address did the trick (I think perhaps I had previously entered an IP already taken by another device connected to the router). This time around, the troubleshooter actually resolved and now I am posting this from my desktop gaming rig, yay! DNS server set to 8.8.8.8 and 8.8.4.4 and seems to work just fine. I may call my ISP later to check what DNS they recommend, but I would think Google's would be as reliable as any.

 

Thanks guys!

 

P.S. If this doesn't permanently resolve the issue I will post my ipconfig /all results.

[Ian_Balisy]

First ping the default gateway to ensure connectivity to your router.  Then try to ping another device on the network to ensure you are on the same network as your PC.  Then try to ping 8.8.8.8, this is a google DNS server.  Pinging by IP address rather than the name will test DNS.  

 

Also have you tried statically configuring an IP address and default gateway?

 

After some time, it seems the same problem occurs. I configure a static IP address and it works for a while on Google's public DNS servers, but eventually stops working. Interestingly, I've been continuously running Steam and downloading Thief (20 GB download) to have a running log of what happens to the connection and it hasn't dropped out at any time when the internet browsing does. Here are the results of pinging 8.8.8.8:

 

Microsoft Windows [Version 6.2.9200]

© 2012 Microsoft Corporation. All rights reserved.

 

C:\Windows\system32>ping 8.8.8.8

 

Pinging 8.8.8.8 with 32 bytes of data:

Reply from 8.8.8.8: bytes=32 time=368ms TTL=45

Reply from 8.8.8.8: bytes=32 time=134ms TTL=45

Request timed out.

Request timed out.

 

Ping statistics for 8.8.8.8:

    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

Approximate round trip times in milli-seconds:

    Minimum = 134ms, Maximum = 368ms, Average = 251ms

 

C:\Windows\system32>

 

 

Could you give us the output of the following command in CMD?

ipconfig /all

 

Here are the results:

 

Microsoft Windows [Version 6.2.9200]

© 2012 Microsoft Corporation. All rights reserved.

 

C:\Windows\system32>ipconfig /all

 

Windows IP Configuration

 

   Host Name . . . . . . . . . . . . : Desktop

   Primary Dns Suffix  . . . . . . . :

   Node Type . . . . . . . . . . . . : Hybrid

   IP Routing Enabled. . . . . . . . : No

   WINS Proxy Enabled. . . . . . . . : No

 

Ethernet adapter Ethernet:

 

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . :

   Description . . . . . . . . . . . : Intel® Ethernet Connection (2) I218-V

   Physical Address. . . . . . . . . : 78-24-AF-88-94-85

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

 

Wireless LAN adapter Wi-Fi:

 

   Connection-specific DNS Suffix  . :

   Description . . . . . . . . . . . : Qualcomm Atheros AR9271 Wireless Network

Adapter

   Physical Address. . . . . . . . . : 68-1C-A2-00-09-6C

   DHCP Enabled. . . . . . . . . . . : No

   Autoconfiguration Enabled . . . . : Yes

   IPv4 Address. . . . . . . . . . . : 192.168.1.28(Preferred)

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Default Gateway . . . . . . . . . : 192.168.1.1

   DNS Servers . . . . . . . . . . . : 8.8.8.8

                                       8.8.4.4

   NetBIOS over Tcpip. . . . . . . . : Enabled

 

Tunnel adapter Teredo Tunneling Pseudo-Interface:

 

   Connection-specific DNS Suffix  . :

   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

   DHCP Enabled. . . . . . . . . . . : No

   Autoconfiguration Enabled . . . . : Yes

   IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6abd:4b0:bbe6:b52a:15bf(Prefe

rred)

   Link-local IPv6 Address . . . . . : fe80::4b0:bbe6:b52a:15bf%14(Preferred)

   Default Gateway . . . . . . . . . : ::

   NetBIOS over Tcpip. . . . . . . . : Disabled

 

Tunnel adapter isatap.{12617E40-908D-4A37-94BF-7D87E04FA8B7}:

 

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . :

   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3

   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

   DHCP Enabled. . . . . . . . . . . : No

   Autoconfiguration Enabled . . . . : Yes

 

C:\Windows\system32>

[1hitwonder]

Your ping results.

Pinging 8.8.8.8 with 32 bytes of data:

Reply from 8.8.8.8: bytes=32 time=368ms TTL=45

Reply from 8.8.8.8: bytes=32 time=134ms TTL=45

Request timed out.

Request timed out

 

The ones that do reply are extremely slow.  I guess the next thing I would look at would be to do a speedtest from your desktop and compare them to speedtests to on your other devices.   Is this a laptop or a desktop? do you have the ability to wire it in to test?

[Ian_Balisy]

 

Your ping results.

Pinging 8.8.8.8 with 32 bytes of data:

Reply from 8.8.8.8: bytes=32 time=368ms TTL=45

Reply from 8.8.8.8: bytes=32 time=134ms TTL=45

Request timed out.

Request timed out

 

The ones that do reply are extremely slow.  I guess the next thing I would look at would be to do a speedtest from your desktop and compare them to speedtests to on your other devices.   Is this a laptop or a desktop? do you have the ability to wire it in to test?

 

 

 

It is a desktop, about 15 ft away from the router, with one rather thin wall in between. From the same location, my Macbook Air registers 64 byte pings averaging about 70 ms.

[1hitwonder]

well then it does seem like the issue is completely with  that desktop.   Are you sure the drivers for the Rosewill USB Wi-Fi adapter are the most current??  Can you try to completly uninstall the driver for the USB device and then install with the most current drivers?  My thought is that the upgrade messed with the drivers.   Also have you tried another USB port?

 

http://www.rosewill.com/products/1808/ProductDetail_Download.htm

[Ian_Balisy]

well then it does seem like the issue is completely with  that desktop.   Are you sure the drivers for the Rosewill USB Wi-Fi adapter are the most current??  Can you try to completly uninstall the driver for the USB device and then install with the most current drivers?  My thought is that the upgrade messed with the drivers.   Also have you tried another USB port?

 

http://www.rosewill.com/products/1808/ProductDetail_Download.htm

 

Got the newest non-beta, beta and beta v2 and clean installed, and tested all with same results. I still get the response "The DNS server is not responding" when I configure a static IP myself, and when I set it to auto it tells me that my computer appears to be configured correcctly but the device or service (DNS server) is not responding. I may try to run Windows repair to see if that works, though I've had that.

[ionbasa]

Got the newest non-beta, beta and beta v2 and clean installed, and tested all with same results. I still get the response "The DNS server is not responding" when I configure a static IP myself, and when I set it to auto it tells me that my computer appears to be configured correcctly but the device or service (DNS server) is not responding. I may try to run Windows repair to see if that works, though I've had that.

Does the issue still occur if trying DHCP? Why are you using a static IP if I may ask?

[Ian_Balisy]

If trying to use DHCP mode, there is no internet signal at all. Configuring a static IP allows access (albeit unstable and inconsistent at best) for some time so that I can at least use the internet. Of course, the goal is to get back to using DHCP so that I don't have to bother, but it seems Windows has a problem with allowing DHCP, or it's "spamming" the router (which has been reported by many in similar situations).

[1hitwonder]

Do you have any internet security software installed?  I have seen Norton's Internet security cause weird issues...    If you reboot your machine does it work again for a short time?  Also check your internet settings, is your PC configured to use proxy at all? Malware or a virus can change these settings to route all your traffic through their servers.

[Ian_Balisy]

Do you have any internet security software installed?  I have seen Norton's Internet security cause weird issues...    If you reboot your machine does it work again for a short time?  Also check your internet settings, is your PC configured to use proxy at all? Malware or a virus can change these settings to route all your traffic through their servers.

 

I do have AVG installed, but it doesn't seem to be the cause of the problem as I have uninstalled it and tested and the problem persists. No malware or virus to speak of to my knowledge and no proxy. I've redone my internet settings a number of times since the problem began and haven't found anything to solve the issue of the computer not getting a response from the DNS server. When I reboot, I usually have to set my IP configuration again before getting any internet access.

 

I've had the Windows 8.1 boot drive run a repair but that hasn't done anything good or bad for this issue. Using a static IP still works for a time but isn't consistent.

 

When I try DHCP mode and "Validate upon exit", the troubleshooter tells me "'Wi-Fi' doesn't have a valid IP configuration". This would seem to be the primary symptom of the issue, though I honestly have no idea how to address it.

[Ian_Balisy]

I may have just had an "I'm an idiot" moment. I realized that my router had been set to Bridge mode and so I used Apple's Airport Utility to change it to DHCP and NAT mode, and all of a sudden my desktop connects via DHCP (no more static IP configuring). While the Airport Utility still tells me that I'm running "Double NAT" and that I should configure it for Bridge mode, I can't see why that would be necessary considering all connected devices receive internet.

 

Any thoughts on this new development?

[ionbasa]

I may have just had an "I'm an idiot" moment. I realized that my router had been set to Bridge mode and so I used Apple's Airport Utility to change it to DHCP and NAT mode, and all of a sudden my desktop connects via DHCP (no more static IP configuring). While the Airport Utility still tells me that I'm running "Double NAT" and that I should configure it for Bridge mode, I can't see why that would be necessary considering all connected devices receive internet.

 

Any thoughts on this new development?

What type of router do you have. Please detail your network setup: include modem, routers, wireless APs, and any switches.

 

If you have an airport extreme connected to a router, the airport extreme needs to be in bridge mode but have NAT and DHCP disabled.

[Ian_Balisy]

What type of router do you have. Please detail your network setup: include modem, routers, wireless APs, and any switches.

 

If you have an airport extreme connected to a router, the airport extreme needs to be in bridge mode but have NAT and DHCP disabled.

 

My setup is a ZyXel P660R-F1 modem connected to an Airport Express router, thats it for the setup except for the Rosewill USB network adapter connected to my desktop.

 

I've been trying to disable NAT on the ZyXel P660R-F1 by going to http://192.168.1.1, but there aren't any options to click on and "Bridging" is greyed out. Not sure if there is a work around for this but I'll be calling my ISP to figure it out. If I can disable NAT on the modem, then I think DHCP only, or DHCP and NAT mode should work on the Airport Express.

[ionbasa]

My setup is a ZyXel P660R-F1 modem connected to an Airport Express router, thats it for the setup except for the Rosewill USB network adapter connected to my desktop.

 

I've been trying to disable NAT on the ZyXel P660R-F1 by going to http://192.168.1.1, but there aren't any options to click on and "Bridging" is greyed out. Not sure if there is a work around for this but I'll be calling my ISP to figure it out. If I can disable NAT on the modem, then I think DHCP only, or DHCP and NAT mode should work on the Airport Express.

Ahh, still on ADSL? That sucks.

If you can't disable DHCP and set it to bridged mode on the ZyXel modem, then chances are you need a newer modem.

 

Harras your ISP to provide a better/newer one, or check to see if this TP_Link is approved for use on your ISP: http://www.amazon.com/TD-8616-Downstream-Bandwidth-Lightning-Protection/dp/B0034JSYZ2/ref=sr_1_1?s=electronics&ie=UTF8&qid=1409870288&sr=1-1&keywords=ADSL+modem

For $25 you can't go wrong, considering it is from a reputable networking company.

[Ian_Balisy]

Ahh, still on ADSL? That sucks.

If you can't disable DHCP and set it to bridged mode on the ZyXel modem, then chances are you need a newer modem.

 

Harras your ISP to provide a better/newer one, or check to see if this TP_Link is approved for use on your ISP: http://www.amazon.com/TD-8616-Downstream-Bandwidth-Lightning-Protection/dp/B0034JSYZ2/ref=sr_1_1?s=electronics&ie=UTF8&qid=1409870288&sr=1-1&keywords=ADSL+modem

For $25 you can't go wrong, considering it is from a reputable networking company.

 

After a terrible conversation with a customer service agent (who was extremely rude and consistently told me I needed to replace my router when I said I was having problems with the modem they provided), I figured out that this was the problem. Basically, I've set the router back to Bridge mode and configured a static IP for my desktop. I know the ISP won't replace a technically working modem so probably I will need to force them to take the provided one back and get a new one (probably the one you listed). Too bad the apartment complex I'm in only has these guys and Verizon for internet options, Verizon is ridiculously expensive and hit or miss in terms of signal.

 

Anyways, thanks for the help everyone! Internet is reasonably stable with a manually configured static IP for now and I don't have to reconfig it very often it seems. Now onto researching a new graphics card!