Cannot ping or tracert But internet works fine...

Zakster · 27 Dec 2016

Computer gets online fine, can not ping or tracert. Tried default DNS and custom 8.8.8.8 - 8.8.4.4. Problem persist with AV on or off.

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Windows\system32>tracert google.com

Tracing route to google.com [2607:f8b0:4007:808::200e]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 2605:e000:d403:fc00:fe52:8dff:fe50:1012
2 8 ms 8 ms 7 ms 2605:e000:efc0:39::1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 ^C
C:\Windows\system32>ping google.com

Pinging google.com [2607:f8b0:4007:808::200e] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 2607:f8b0:4007:808::200e:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Windows\system32>

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-SNQ7LLE
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-CC-82-38
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2605:e000:d403:fc00::3(Preferred)
Lease Obtained. . . . . . . . . . : Tuesday, December 27, 2016 9:26:05 AM
Lease Expires . . . . . . . . . . : Tuesday, December 27, 2016 10:56:05 AM
IPv6 Address. . . . . . . . . . . : 2605:e000:d403:fc00:e9d1:5ad0:b00f:8dab(Preferred)
Temporary IPv6 Address. . . . . . : 2605:e000:d403:fc00:405:e148:498b:6f35(Preferred)
Link-local IPv6 Address . . . . . : fe80::e9d1:5ad0:b00f:8dab%3(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, December 27, 2016 9:26:08 AM
Lease Expires . . . . . . . . . . : Tuesday, December 27, 2016 10:39:26 AM
Default Gateway . . . . . . . . . : fe80::fe52:8dff:fe50:1012%3
192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 64539530
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-E5-59-F8-D8-CB-8A-CC-82-38
DNS Servers . . . . . . . . . . . : 24.25.227.55
209.18.47.61
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Kaspersky Security Data Escort Adapter
Physical Address. . . . . . . . . : 00-FF-C6-FF-68-C6
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{12618AD9-C327-4BAD-8F5B-7B6FC90A3F13}:

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

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
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

C:\Windows\system32>

Neemobeer · 27 Dec 2016

Ipv6(icmpv6) may be blocked try ping <host/ip> -4

bro67 · 27 Dec 2016

Neemobeer said:

Ipv6(icmpv6) may be blocked try ping <host/ip> -4

They do not need the last part. They just need the url or ipv4 ip.

Zakster · 09 Jan 2017

Neemobeer said:

Ipv6(icmpv6) may be blocked try ping <host/ip> -4

Thank you for that, it worked. No other way has worked for me. Could you maybe tell me how to fix my problem? I would really appreciate it. Thanks in advanced.

EdTittel · 09 Jan 2017

Actually, the correct syntax is tracert -4 <hostname> or ping -4 <hostname>. By default Windows 10 seeks to use IPv6, so if it's not enabled on your outbound network device or connection (for many folks IPv6 will not be turned on at their routers) a basic ping or tracert command that lacks the -4 IPv4 designator may not work (as yours did not). I just got a huge and welcome surprise when I started doing some local testing here:

Cannot ping or tracert But internet works fine...-ipv6-ping.jpg

Apparently, TimeWarner/Spectrum has recently shifted over to IPv6 and everything is working fine. They did this without telling us poor users anything but I'm totally jazzed to be catching up to the 1990s on my LAN!
The good news is this is handled on the ISP side of your connection and/or at the router (especially when, as in my case, the boundary device is rental equipment from the ISP itself). You can't really do anything to fix this, except to make sure that IPv6 is enabled on your client PCs (and if you haven't turned it off, it is enabled in Win10 by default).
HTH,
--Ed--