Windows 10: Network 2 No Internet Access -> Your DNS Server Might Be Unavailable

Skyferia

Posts: 17   +0
Issue as per subject.

What I have tried:
1. Update device (Realtek PCIe GBE Family Controller) driver to 10.8.311.2016

2. Reset Windows

3. Changed LAN cable

4. ip config (elevated command prompt):
Microsoft Windows [Version 10.0.10586]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>ipconfig /flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

C:\WINDOWS\system32>ipconfig /release

Windows IP Configuration


Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::687c:1fc1:68ce:7fa%3
Default Gateway . . . . . . . . . :

C:\WINDOWS\system32>ipconfig /renew

Windows IP Configuration


Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::687c:1fc1:68ce:7fa%3
IPv4 Address. . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

Tunnel adapter isatap.{35F584B8-6E1D-449C-9566-361470742917}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

C:\WINDOWS\system32>ipconfig /release6

Windows IP Configuration

No operation can be performed on isatap.{35F584B8-6E1D-449C-9566-361470742917} while it has its media disconnected.

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::687c:1fc1:68ce:7fa%3
IPv4 Address. . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

Tunnel adapter isatap.{35F584B8-6E1D-449C-9566-361470742917}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

C:\WINDOWS\system32>ipconfig /registerdns

Windows IP Configuration

Registration of the DNS resource records for all adapters of this computer has been initiated. Any errors will be reported in the Event Viewer in 15 minutes.

C:\WINDOWS\system32>ipconfig /all

Windows IP Configuration

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

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : D8-CB-8A-E2-8A-E2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::687c:1fc1:68ce:7fa%3(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, June 8, 2016 11:08:50 AM
Lease Expires . . . . . . . . . . : Thursday, June 9, 2016 11:08:50 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 47762314
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-E9-1B-59-D8-CB-8A-E2-8A-E2
DNS Servers . . . . . . . . . . . : 192.168.1.1
192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{35F584B8-6E1D-449C-9566-361470742917}:

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

C:\WINDOWS\system32>

5. This (elevated command prompt):
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>nslookup google.com
Server: UnKnown
Address: 192.168.1.1

*** UnKnown can't find google.com: Query refused

C:\WINDOWS\system32>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

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

C:\WINDOWS\system32>tracert -d 8.8.8.8

Tracing route to 8.8.8.8 over a maximum of 30 hops

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\WINDOWS\system32>
 
Power cycle your equipment and try again...
(turn off router, modem and system...wait >30 seconds...power up in order, allowing time to 'go green' ...modem, router, system)
 
Remove and reconnect all connections to modem and router.
Change port on router.
If other computers on network can connect to internet and this is the exception, skip next two steps.
If no fix, replace router with known good.
If no fix, replace modem with known good.
Check Device Manager for status of network controller.
 
I found the root cause, and it's very silly!
What happened was that the LAN/Ethernet cable was connected to the modem, not the router.

When called the ISP customer service:
  • 1st Representative (8th June): Asked to connect the phone line to the TEL1 port, disregarding the DSL port
  • 2nd Representative (9th June): Asked to connect the LAN/Ethernet cable from modem to computer*
  • 3rd Representative (today, 10th June): Said connecting to modem is incorrect, should be connected to the router -> connect to router -> issue resolved
*Point after when I started this thread

Thanks for the help Cycloid, this thread can be closed.
 
Back