Hi all. Wondering if anyone has had an issue with this. My server & clients are on the same subnet and my server has stopped being able to detect the clients. I haven’t changed any firewall configurations. Tried disabling firewalls on the server/client and also adding client IPs via hint. I believe the network is able to handle UDP broadcast packets (it was doing that before without an issue and I haven’t changed the config). I’ve only been able to get this to work by setting the clients up as Internet clients. Any suggestions for other things I can try?
To follow up on this, we were able to work around the issue by using a HyperV “legacy network adapter” instead of the regular network adapter. It appears that a recent HyperV update broke broadcast traffic for regular network adapters (at least for generation 1 VMs).
Had the same problem, after uninstalling KB5015808 (Hyper-V 2016) and KB5015874 (Hyper-V 2012R2) on the Hyper-V server it works again. Now I’m looking for Hyper-V 2022 (the problem remains). You have to look for the parameter to be fixed so as not unistalling KB in all server version.
Does anybody know exactly what is being restored by uninstalling KB5015808? What “parameter” are you looking for to be fixed? I’ve been struggling to find any other recent reports of this behavior more broadly, want to avoid installing on bare metal to fix the issue, and want to avoid having to hold back certain updates.
Sorry to necro an old thread, but I just wanted to put this out there. This week I experienced an issue where my native ubuntu server suddenly stopped being able to discover a native windows client. Did some troubleshooting and found out that the UDP packets were being dropped at the level of the windows firewall. Very strange considering that the default urbackup allow ingress rules are all there. Anyway, issue was resolved by adding a manual ingress rule for the proper port.