Topic: [Solved] D2GS 1.13c on Wine: "Diablo II was unable to connect..."
I'm having trouble setting up D2GS (1.13c from https://pvpgn.pro/download/d2gs/D2GS-113-build01.rar) via headless Wine 2.01. with the latest PVPGN (from github) on Ubuntu 16.04 behind NAT.
Here is what I did:
Compiled PVPGN with MYSQL support
Compiled the Wine 2.0.1 source with applied sock.c patch
Configured all PVPGN files, the d2gs.dll, the port forwarding of ports 6112,6113,6114 and 4000
Imported the .dll in the Wine registry, copied the D2 data files (MPQs and such)
(the above steps are much more detailed and may serve as a HOWTO as long as I get it all to work )
All servers run from a single IP.
All ports can be reached from the machine I'm running the game from (telnet to the public IP and the desired port connects).
However, when I run D2LOD (1.13c, I was surprised that the game itself reports 1.13 without the 'c', but the 1.13c patch said the game versions are the same and nothing is to be patched) I can successfully log in my test realm, but after a little waiting on screen showing
I get the following error:
Diablo II was unable to connect to the realm server. The realm you selected may be unavailable or you may be encountering connection issues. Please make sure your internet connection is working properly and/or your firewall has port 6112 opened.
I've increased the log verbosity for bnetd, d2cs and d2dbs, but they do not show anything interesting (I've attached a zip file with all 4 logs to the thread).
I hope that ports 6112 and 4000 on the client machine do not have to be reachable from the server since port forwarding from my ISP is not a viable option at the moment and that would be a major inconvenience.
Has anyone come across such an issue?
Thanks for any help!