DNS not working properly after Windows 10 update

Archived From: Technology
  • Page :
  • 1
  • Text Only
rated:
Windows 10 did the anniversary update. 

Solved problem:
it couldn't find the boot drive anyway.  I did a system reset which reinstalled Windows 10.   I have setup DNS manually to 8.8.8.8 and 8.8.4.4 for testing

Once the system comes up now something is wrong with network settings. 

This is a dual-boot box and Fedora is having no problems with the exact same hardware. 

nslookup is working but ping isn't

C:\WINDOWS\system32>nslookup fatwallet.com
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
Name:    fatwallet.com
Addresses:  52.8.137.179
          50.18.209.119


C:\WINDOWS\system32>ping fatwallet.com
Ping request could not find host fatwallet.com. Please check the name and try again.


I have reset dnscache,
I did a release / renew on ipconfig

I have rebooted multiple times.

I ran the windows troubleshooting thing and got nothing out of it. 

I disabled all the adapters except my wireless connection. 

here is netstat /all

C:\WINDOWS\system32>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . :
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Local Area Connection* 4:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
   Physical Address. . . . . . . . . : DA-EB-97-DD-03-FC
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : TRENDnet TEW-807ECH AC1200 Dual Band Wireless PCIE Adapter
   Physical Address. . . . . . . . . : D8-EB-97-DD-03-FC
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.1.221(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Wednesday, August 03, 2016 9:54:29 PM
   Lease Expires . . . . . . . . . . : Thursday, August 04, 2016 9:55:35 PM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DNS Servers . . . . . . . . . . . : 8.8.8.8
                                       8.8.4.4
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{1D6D19E9-5C3E-433E-B467-8F10C20F9178}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes



Any ideas?


 

Member Summary
Staff Summary
Thanks for visiting FatWallet.com. Join for free to remove this ad.

Try another site - fatwallet appears to be blocking ping. I just tried www.cdw.com and that worked.

Another thought - have you tried installing the latest drivers for your NIC instead of keeping the ones Windows installed?
http://www.trendnet.com/support/supportdetail.asp?prod=105_TEW-8...

ok.  I did a ping on google.com   Only works if you give it the actual IP address. 

Driver is confirmed to be from Realtek.   I did install the specific drivers for it from the web site

C:\WINDOWS\system32>nslookup google.com
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
Name:    google.com
Addresses:  2607:f8b0:4009:80f::200e
          216.58.192.238


C:\WINDOWS\system32>ping google.com
Ping request could not find host google.com. Please check the name and try again.

C:\WINDOWS\system32>ping 216.58.192.238

Pinging 216.58.192.238 with 32 bytes of data:
Reply from 216.58.192.238: bytes=32 time=27ms TTL=53
Reply from 216.58.192.238: bytes=32 time=21ms TTL=53
Reply from 216.58.192.238: bytes=32 time=22ms TTL=53
Reply from 216.58.192.238: bytes=32 time=36ms TTL=53

Ping statistics for 216.58.192.238:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 36ms, Average = 26ms



TRENDnet TEW-807ECH AC1200 Dual Band Wireless PCIE Adapter
Driver Provider:  Realtek Semiconductor Corp.
Driver Date:  7/21/2015
Driver Version: 2023.15.701.2015

Are you using a third party AV that has a firewall, like something from McAfee or Symantec? I've seen those break during 10 Upgrades. If you are, do a full uninstall and see if things start working.

Wiped the drive and did a reinstall.  Everything seems to be working so far. 

Thanks for the help!



Disclaimer: By providing links to other sites, FatWallet.com does not guarantee, approve or endorse the information or products available at these sites, nor does a link indicate any association with or endorsement by the linked site to FatWallet.com.

Thanks for visiting FatWallet.com. Join for free to remove this ad.

While FatWallet makes every effort to post correct information, offers are subject to change without notice.
Some exclusions may apply based upon merchant policies.
© 1999-2017