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

Discus and support Windows 10 since 1803 cant ping (most of the time) by ipv6 or rdp? in Windows 10 Support to solve the problem; 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... Discussion in 'Windows 10 Support' started by markm75, Aug 20, 2018.

  1. markm75 Win User

    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

    :)
     
    markm75, Aug 20, 2018
    #1

  2. 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.
     
    Stephen Albright, Aug 20, 2018
    #2
  3. Eric Ber Win User
    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.
     
    Eric Ber, Aug 20, 2018
    #3
  4. Windows 10 since 1803 cant ping (most of the time) by ipv6 or rdp?

    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.
     
    bradlymathews, Aug 20, 2018
    #4
Thema:

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

Loading...
  1. Windows 10 since 1803 cant ping (most of the time) by ipv6 or rdp? - Similar Threads - since 1803 cant

  2. ping localhost gives ipv6 responce , how to change to ipv4

    in Windows 10 Gaming
    ping localhost gives ipv6 responce , how to change to ipv4: c:\>ping localhost Pinging XXXXXXXXX[::1] with 32 bytes of data: Reply from ::1: time<1ms Reply from ::1: time<1ms Reply from ::1: time<1ms Reply from ::1: time<1ms Ping statistics for ::1: Packets: Sent = 4, Received = 4, Lost = 0 0% loss, Approximate round trip times in...
  3. ping localhost gives ipv6 responce , how to change to ipv4

    in Windows 10 Software and Apps
    ping localhost gives ipv6 responce , how to change to ipv4: c:\>ping localhost Pinging XXXXXXXXX[::1] with 32 bytes of data: Reply from ::1: time<1ms Reply from ::1: time<1ms Reply from ::1: time<1ms Reply from ::1: time<1ms Ping statistics for ::1: Packets: Sent = 4, Received = 4, Lost = 0 0% loss, Approximate round trip times in...
  4. ping localhost gives ipv6 responce , how to change to ipv4

    in Windows 10 Customization
    ping localhost gives ipv6 responce , how to change to ipv4: c:\>ping localhost Pinging XXXXXXXXX[::1] with 32 bytes of data: Reply from ::1: time<1ms Reply from ::1: time<1ms Reply from ::1: time<1ms Reply from ::1: time<1ms Ping statistics for ::1: Packets: Sent = 4, Received = 4, Lost = 0 0% loss, Approximate round trip times in...
  5. Windows 10 Quality Update failure since 1803

    in Windows 10 Installation and Upgrade
    Windows 10 Quality Update failure since 1803: My bottomline issue is that Windows 10 'quality' updates have been failing to complete since 1803. Feature updates complete successfully. Message received is currently "2020-02 Cumulative Update for Windows 10 Version 1803 for x64-based Systems (KB4537762) (92) Last failed...
  6. Windows 10 randomly freezes since 1803 update

    in Windows 10 Installation and Upgrade
    Windows 10 randomly freezes since 1803 update: Hi, Before 1803 update I never had any freezing problem. But after that laptop started to freeze randomly, usually after working a few hours. Then I could not reset it and sent it to the service. They could not find any problem but reset the laptop (formatted) to version...
  7. Sound issue since Windows 10 v. 1803

    in Windows 10 Installation and Upgrade
    Sound issue since Windows 10 v. 1803: Hi! Since updating to the creators update, my sound is experiencing some serious issues. This is an example of what I get: http://puu.sh/Bt9WO/9e0b05ec30.m4a I have a MB Gigabyte 170 hd3, an intel core i7 6700k, an NVIDIA GT 740. I'm mainly using my monitor as a speaker...
  8. Windows 10 since 1803 cant ping (most of the time) by ipv6 or rdp?

    in Windows 10 Network and Sharing
    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...
  9. cant update to windows 10 1803

    in Windows 10 Installation and Upgrade
    cant update to windows 10 1803: i am running windows 10 1607. while using update assistant for windows 1803 i am getting error 0x800700b7 while installation. please help [ATTACH]...
  10. Can ping ipv6 but not ipv4 on LAN

    in Windows 10 Network and Sharing
    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...