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>
[Windows 10]Network 2 No Internet Access -> Your DNS Server Might
#1
Posted 08 June 2016 - 05:53 AM
#2
Posted 08 June 2016 - 08:55 AM
Open an Elevated Command Prompt http://www.eightforu...indows-8-a.html
Type with an Enter after the line:
nslookup geekstogo.com
Do you get something like:
C:\Windows\system32>nslookup geekstogo.comServer: cdns01.comcast.netAddress: 2001:558:feed::1Non-authoritative answer:Name: geekstogo.comAddresses: 104.28.28.94104.28.29.94
ping 192.168.1.1
This should give you something like this:
C:\Windows\system32>ping 192.168.1.1Pinging 192.168.1.1 with 32 bytes of data:Reply from 192.168.1.1: bytes=32 time=3ms TTL=64Reply from 192.168.1.1: bytes=32 time=3ms TTL=64Reply from 192.168.1.1: bytes=32 time=3ms TTL=64Reply from 192.168.1.1: bytes=32 time=3ms TTL=64Ping statistics for 192.168.1.1:Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:Minimum = 3ms, Maximum = 3ms, Average = 3ms
Now try:
tracert -d 8.8.8.8
Do you get trace complete at the end or does it give you 29 lines of stars after the first line?
C:\Windows\system32>tracert -d 8.8.8.8Tracing route to 8.8.8.8 over a maximum of 30 hops1 1 ms 1 ms 1 ms 192.168.0.12 9 ms 10 ms 10 ms 96.120.12.373 10 ms 9 ms 9 ms 68.85.221.414 11 ms 11 ms 12 ms 68.86.103.55 11 ms 12 ms 11 ms 68.86.92.1216 13 ms 13 ms 13 ms 68.86.86.777 13 ms 13 ms 12 ms 68.86.83.148 11 ms 12 ms 11 ms 75.149.228.1749 12 ms 12 ms 12 ms 209.85.241.13110 13 ms 13 ms 18 ms 209.85.241.17511 12 ms 12 ms 12 ms 8.8.8.8Trace complete.
#3
Posted 08 June 2016 - 07:31 PM
The result from the commands:
Microsoft Windows [Version 10.0.10586] (c) 2016 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>nslookup geekstogo.com Server: UnKnown Address: 192.168.1.1 *** UnKnown can't find geekstogo.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>
#4
Posted 08 June 2016 - 08:19 PM
Looks like your router is not connected to the Internet, Are there any lights on it?
#5
Posted 08 June 2016 - 09:09 PM
Looks like your router is not connected to the Internet, Are there any lights on it?
Yes.
Router
Light ON: Power, Internet
Light OFF: LAN1, LAN2, LAN3, LAN4
Light Flickering: WAN
Light Blinking: Wi-Fi
Modem
Light ON: TEL2, TEL1, VOIP, LAN4 (connected to desktop PC), DSL
Light OFF: LAN2, LAN3
Light Flickering: LAN1 (connected to router)
Light Blinking: Internet
#6
Posted 08 June 2016 - 09:29 PM
Disconnect the power from the modem. Disconnect the LAN4 cable to the PC. Disconnect the power to the router.
Plug in the modem.
Connect up the LAN4 to the PC.
Once the lights settle down try the nslookup or tracert command again and see if you get anything different.
#7
Posted 08 June 2016 - 10:14 PM
Disconnect the power from the modem. Disconnect the LAN4 cable to the PC. Disconnect the power to the router.
Plug in the modem.
Connect up the LAN4 to the PC.
Once the lights settle down try the nslookup or tracert command again and see if you get anything different.
Here (I even changed to another LAN cable) :
Microsoft Windows [Version 10.0.10586] (c) 2015 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>nslookup geekstogo.com Server: UnKnown Address: 192.168.1.1 *** UnKnown can't find geekstogo.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>
#8
Posted 09 June 2016 - 12:31 AM
It appears your modem is not working. Call your ISP. They can do a loopback test and also check the status
#9
Posted 09 June 2016 - 08:26 AM
Erm, well, where I live, let's just say the ISP technicians are completely textbook-oriented, i.e. they don't seem to be capable of critical thinking, in that if it's 'not in the book', it cannot be solved. I say this confidently due to past many experiences, where all of which I had to sort the issues by myself, ever since dial-up days.
If any, I called them up yesterday, they were supposed to come today, and this was what I received this morning (it's night time here now):
Dear Valued Customer, there may be some delay in restoring your service. We apologise and will update you accordingly. TQ.
and 2 hours prior:
Dear Sir/Madam, restoration works for your service is in progress. TQ
I could bring up asking them to perform the loopback test & status check, but I don't see much hope. What can I do meanwhile?
Edited by Skyfer, 09 June 2016 - 08:27 AM.
#10
Posted 09 June 2016 - 08:37 AM
Sounds like they are aware that they have a problem. If it's on their end there is not much you can do.
I suppose you could log in to the modem and see if it tells you anything. Often there is a password on the modem's label. If not Google the make and model number of the modem and get the default password and see if you can get in that way. To logon just open a browser and put in 192.168.1.1 and hit Enter.
#11
Posted 09 June 2016 - 12:29 PM
Ah, you really trust them.
Sorry, anyway, for mine is 192.168.0.1 and no I cannot log into it:
BUT I can log into that wirelessly:
Also, does this mean anything, can this help with the troubleshooting?:
Edited by Skyfer, 09 June 2016 - 12:42 PM.
#12
Posted 09 June 2016 - 04:18 PM
Your router may be 192.168.0.1 but the modem which you tell me you are directly connected to is 192.168.1.1
Default Gateway . . . . . . . . . : 192.168.1.1
#13
Posted 09 June 2016 - 08:12 PM
- 1st Representative (8th June): Asked to connect the phone line to the TEL1 port, disregarding the DSL port
- 2nd Representative (8th 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
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users