Posted June 04, 2022
For those who still wonders, the problem is because the game was created at some point in history where people did have just one network interface. Nowadays, with multiple ethernet interfaces (wired, wifi) plus VPN, plus Hamachi, plus WSL, plus VMWare virtual interfaces, the game doesn't know on which interface to listen. When you start a local LAN TCPIP game, you need to make sure it shows the proper IP, the one on your LAN which normally starts with 192.168.0.xxx
The easy way to fix it is to open ncpa.cpl to manage the network interfaces and disable them all and then start the server. You just have to do this on the server, the client will find it easily.
Normally, when you start the server, the Windows firewall will ask to add a rule for incoming connections. If it doesn't, you just open wf.msc and add an inbound exception for that particular program (hota.exe or homm3.exe).
The hard way would be to modify priorities of interfaces, like the broken link above was supposed to explain. I don't recommand that.
Harder way would be to patch the executable to listen properly :)
The easy way to fix it is to open ncpa.cpl to manage the network interfaces and disable them all and then start the server. You just have to do this on the server, the client will find it easily.
Normally, when you start the server, the Windows firewall will ask to add a rule for incoming connections. If it doesn't, you just open wf.msc and add an inbound exception for that particular program (hota.exe or homm3.exe).
The hard way would be to modify priorities of interfaces, like the broken link above was supposed to explain. I don't recommand that.
Harder way would be to patch the executable to listen properly :)