Most probably network issues. To narrow down enable only one network interface ipv4 and put fixed IP address with proper MASK.
Go to settings–>system–>network–>
a) enable eth0 if you’re using cable, keep only one interface enabled.
b) Put IP address e.i. 192.168.1.5/24
c) Put gateway e.i. 192.168.1.1 (that’s router’s address)
d) Put DNS (can be router’s address if router is propagating that)
e) Click save of this section
f) Scroll down to the bottom and choose adapter (don’t allow autoconfig). Click save.
g) Allocate this IP address on the router (bind MAC of HA to the IP address you have chosen)
h) Restart router, restart HA
I had the same problem pinging a Windows 11 machine that was turned on. Solution was in the Windows Defender Firewall. Instructions and source:
Open Windows Defender Firewall and select Advanced Settings in the sidebar. Switch to Inbound Rules via the Getting Started page or the sidebar. Find the rule named “Core Networking Diagnostics - ICMP Echo Request (ICMPv4-In)” with Profile of “Private, Public” (unless you’re on a corporate domain…). You can right-click the rule and Enable Rule.
You might also want to do the same for the IPv6 version named “Core Networking Diagnostics - ICMP Echo Request (ICMPv6-In)”. I don’t know why Microsoft decided to disable these by default.
I’ve just found the solution.
My server doesn’t have a dedicated port for ILO and the home assistant VM and ilo shared the same port on the network card …