Windows 10: Windows 11 unable to ping local IPv4 network after 1-2 minutes of uptime.

The issue only occurs on Windows 11, on the same hardware I am able to use multiple version of Linux, Windows 10, Windows Preboot, and a FreeBSD live disk to ping the internal network without issue via both IPv4 directly with the IP and via DNS lookup. The issue arose after setting up dual boot, while using this before it was a matter of fully shutting down the PC rather than restarting to switch back to Windows, only listed updates for the days between were security definitions. Now when booting into Windows 11, for the first few seconds I can open powershell, ping my gateway, ping other

:)

 

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?

 

Device in the same local network pings but the other one not.

If you can ping one device (192.168.0.251) but not the other (192.168.0.252) from your Windows Server 2012 R2 machine, it indicates that there might be an issue with the network configuration or connectivity of the second device. Here are some troubleshooting steps you can follow:

1. Check Device Configuration:
   
   • Ensure that the device with IP address 192.168.0.252 is correctly configured with the subnet mask (usually 255.255.255.0) and gateway (192.168.0.1).
     
   • Verify that there are no IP conflicts. Make sure that no other device on the network is using the same IP address (192.168.0.252).
     
2. Physical Connectivity:
   
   • Check the physical connections between the server and the device. Ensure that the Ethernet cable is securely connected to both ends.
     
   • Inspect the device's Ethernet port and cable for any physical damage or loose connections.
     
3. Firewall and Security Software:
   
   • Disable any firewall or security software on the Windows Server temporarily to rule out any interference with ping requests.
     
4. ARP Cache:
   
   • Sometimes, ARP (Address Resolution Protocol) cache can cause issues. You can try flushing the ARP cache on the Windows Server using the following command:
     
     
   • This command will clear the ARP cache, and the server will re-discover devices on the network.
     
5. Packet Capture:
   
   • You can use packet capture tools like Wireshark to capture network traffic between the server and the device (192.168.0.252). This can help you identify if the ping requests are reaching the device and if the device is responding.
     
6. Device Logs:
   
   • Check the logs or diagnostic information on the device itself (192.168.0.252) for any errors or issues that might be preventing it from responding to ping requests.
     
7. Network Switch/Router:
   
   • If there is a network switch or router between the server and the devices, check its configuration for any access control or firewall rules that might be blocking traffic to 192.168.0.252.
     
8. IP Configuration Conflict:
   
   • Double-check that there are no IP address conflicts within the network. No other device should be using the same IP address (192.168.0.252).
     

By following these steps, you should be able to identify and resolve the issue preventing you from pinging the device with IP address 192.168.0.252 from your Windows Server. If the problem persists, please provide more details about the error message or any specific issues you encounter during these troubleshooting steps, and I'll be happy to provide further assistance.

 

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