Windows 10: 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 milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms-----------------------------------tried editing Network properties. Adaptor settings.Expecting responce to be 127.0.0.1

:)

 

Windows 10 Pro unable to ping localhost or its own IPv4.

I have multiple Windows 10 pro computers on my domain network that now have this same issue:

These computers are unable to ping it's own localhost or IPv4 address, they can ping ::1 and IPv6 address!

These computers can ping other computers on the network.

Other computers on the network can ping these computers on the IPv4 address and they echo!

I have checked the firewall, AV settings, checked the registry and policies.

I have ensured our routers are not the issue.

I am meticulous about network settings, updates, policy settings ect...

Nothing anywhere that would prevent ICMP echo.

I have disabled IPv6 and components with no effect and re-enabled them again with no effect.

What is really strange is that it is only on a handful of computers.

Other computers on the same subnet/domain do not have this issue!

Several of those computers are brand new builds, hardware and OS, like within the last month!

This seems rather random and this one has me completely stumped!

HELP! Anyone suggestions?

 

Prefer ipv4 over ipv6

hi,

I want to set ipv4 to be preferred over ipv6, the other day i've used the tips from this Ping returns IPv6 Address, ping IPv4 in Command Prompt - TheITBros on my 2 windows10 computers and everything worked out great!

Now, i just did a win10 update and i noticed that that no longer works even by doing the very same "command" and it kinda gets ignored. Did they just remove the functionality?

This is what i get from netsh interface ipv6 show prefixpolicies (i don't get the longer list anymore but just these):





So it seems to be preferring ipv4, yet when i ping my site (available on both ipv4 and ipv6), i get output with ipv6, same as google.com - the other day it was working nicely to ipv4 and i only used these 2 commands they suggested:

netsh interface ipv6 set prefix ::/96 60 3

netsh interface ipv6 set prefix ::ffff:0:0/96 55 4

what's going on? I don't want to disable it completely (i know i can disable it from the router or from the network card properties, i just want to de-prioritise it)

[Version 10.0.19044.1387]

thank you,
Gabrio

- - - Updated - - -

might have answered myself, i've added

netsh interface ipv6 add prefixpolicy ::/0 40 1

and it did the trick... i wonder if it will stick now

 

Windows 10 Pro unable to ping localhost or its own IPv4.

Hi Johan,

To isolate the issue, please provide the error message that you see when you try to ping the computers' localhost or IPv4 address.

You may also check out this
thread about a similar issue that happens when pinging localhost.

Regards.