https://bugs.winehq.org/show_bug.cgi?id=53499
--- Comment #12 from Stanislav Slow stanislav.rimsha@gmail.com --- (In reply to Hans Leidekker from comment #11)
Following your theory about client IDs you could try to capture network packets from the game running on Windows and identify this ID. Then grep for strings with same format, or stuff surrounding it.
More generally comparing packets from clients running on Windows and Wine and see where they diverge may a good approach.
I finally made things work properly (somewhat) and found the culprit. I have connected one of the machines via ethernet while the second linux machine is connected via wlan. They were able to see each other with no problem. I have checked the logs again and the difference was that winsock did not try to bind to 0.0.0.0 and only bound to LAN address. Therefore I suppose that the client ID is the primary binding IP.
The question now is - why does it try to bind to a DOWN state interface under wine but doesn't do it on windows? Does GetAdaptersInfo supply state info?