High latency.

[Autumnlicious]

I notice that Jehanne can talk to an IPv4 destination but cannot talk to AF's IPv6 address.

What does ping'ing AF's IPv4 result in, Jehanne? It is 104.28.16.10 - tell us what you see.

[Jehanne]

I notice that Jehanne can talk to an IPv4 destination but cannot talk to AF's IPv6 address.

What does ping'ing AF's IPv4 result in, Jehanne? It is 104.28.16.10 - tell us what you see.

Much better results:

Pinging 104.28.16.10 with 32 bytes of data:
Reply from 104.28.16.10: bytes=32 time=33ms TTL=56
Reply from 104.28.16.10: bytes=32 time=27ms TTL=56
Reply from 104.28.16.10: bytes=32 time=30ms TTL=56
Reply from 104.28.16.10: bytes=32 time=32ms TTL=56

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

[Autumnlicious]

I think you have an IPv6 connectivity issue. On some older versions of Windows, I recall they screwed up their IPv6 implementation to always be tried first even if the network didn't support IPv6.

[Jackalope]

If that's the issue IPv6 can be turned off in the adapter settings from the network control panel. I don't remember the exact sequence but the setting is fairly obvious - once you find it.

[ignoramus]

or reset the ipstack?

Reset WINSOCK entries to installation defaults: netsh winsock reset catalog
Reset IPv4 TCP/IP stack to installation defaults. netsh int ipv4 reset reset.log
Reset IPv6 TCP/IP stack to installation defaults. netsh int ipv6 reset reset.log