Windows 10: Windows 10 since 1803 cant ping (most of the time) by ipv6 or rdp?

I have a problem with my desktop since i ran the update to 1803..If i do a ping machinename (in this case a 2016 server)..
it will say cannot find host name.. if i keep hammering it, eventually one ping might go through.Same deal with RDP.

My network consists of a netgear wifi accesspoint/router with the server and desktop (i also have this same issue with a laptop that was updated).

Has anyone ran into this and found a fix?I have already tried netsh resets to the stack and winsock without success. I'm pretty sure if i were to disable ipv6 on the desktop/server it would be fine and use that as the preferred connection (ping -4 machinename works all the time).. but thats not a solution either.

Thanks in advance

:)

 

IPV6 Ping Not Working?

I am running Windows 10 and am having some connectivity problems with the Internet and my WiFi router. While investigating this, I saw some strange behavior while trying to ping external websites. The command prompt defaults to IPv6, and the pings appear
to be blocked. If I provide a -4 flag on the ping, it goes through.

C:\Users\User>ping google.com

Pinging google.com [2607:f8b0:4009:816::200e] with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 2607:f8b0:4009:816::200e:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\User>ping google.com -4

Pinging google.com [172.217.6.110] with 32 bytes of data:

Reply from 172.217.6.110: bytes=32 time=31ms TTL=56

Reply from 172.217.6.110: bytes=32 time=36ms TTL=56

Reply from 172.217.6.110: bytes=32 time=31ms TTL=56

Reply from 172.217.6.110: bytes=32 time=31ms TTL=56

Ping statistics for 172.217.6.110:

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

Approximate round trip times in milli-seconds:

Minimum = 31ms, Maximum = 36ms, Average = 32ms

Any ideas how I can either default to the IPv4 ping or hopefully successfully ping a IPv6 address? When I test my IPv6 compatibility through the Google test site (Ready for the future of the Internet?), I get this response:

Ready for the future of the Internet?

No problems detected.

You don’t have IPv6, but you shouldn’t have problems on websites that add IPv6 support.

 

IPV6 Ping Not Working?

We are glad that you are now able to ping IPv6 addresses. Since your device issue is different from what is previously posted, we suggest that you post a new thread so other community members would be able to assist you.

Should you have further queries, feel free to post it.

 

Can ping ipv6 but not ipv4 on LAN


I just moved into my business partner's home office and I am trying to get Dev (computer #1, Win10 Pro) to see DbServer's (computer #2, also Win10 Pro) Postgres Database to no avail so far.

He has a Comacast router which seems to be using using IPv6 primarily. When I go to WhatisMyIP, I get a v6 address. Ok, I think finally time to get my head around IPv6.

During debugging I ran an interesting effect which may or may not be the related to my connectivity problems.

Dev can ping DbServer's v6 address but not its v4. DbServer can ping Dev's v4 address but not its v6. *Eek I can RDP into DbServer from Dev using either v6 or v4 just fine.