

If this is performed correctly (the way to do it depends on your router this is a good reference, already with the needed ports preselected. Second, in order to have a network connection, not only does the host have to do port forwarding, but also the clients! The ports to forward are the same in both cases: Both TCP and UDP 47624 (doc says TCP is enough, but my testing shows UDP is being listened too), and both TCP and UDP 2300-2400. On Wine (Linux or OS X), this means running winetricks directplay. 10.205952/ (note that it is on by default already, so for the most part you don't need to do anything here). On recent Windows (8.0, 8.1, 10), this is achieved by checking Legacy → DirectPlay in Windows Features, as seen here. First, both the host and clients have to have DirectPlay installed. A useful Microsoft document about it can still be found here: However, its support still survives to this day with varying degrees of functionality.ĭirectPlay relies on a server (dplaysvr.exe) that is game-agnostic and that creates a two-way link between the host and the clients. Since DirectX 8, DirectPlay has changed considerably, and since DirectX 9 it has been deprecated altogether. HoMM3 was made in the early days of DirectX (in 1999, DirectX 6 was the latest version), using its DirectPlay as middleware to set up network games.


That's quite a feat, but turns out that it's pretty simple in the end, one just has to understand how the underlying technology works. Using no external tools whatsoever (yes, no bloody GameRanger, Hamachi, VPN, etc.!), via TCP/IP. Between three people, who were using Windows 8.1, Windows 10 and Linux. Today I managed to set up a network play in vanilla HoMM3 Complete.
