IPX was the LAN protocol of 1990s PC gaming, and the bundled IPXWrapper brings it back by emulating IPX on modern Windows and tunnelling the packets over UDP — so classics built for NetWare-era networks can find each other on a present-day LAN again. Windows removed the IPX stack after the XP era, which silently ended local multiplayer for a whole generation of strategy and action games. DxWnd ships IPXWrapper in its download bundle alongside its other period components, and this page explains what IPX was, why it died, and what the wrapper can and cannot resurrect.
The IPX Era
IPX/SPX was Novell’s networking suite, born for NetWare file-and-print networks and adopted by game developers because every office and LAN party already ran it. If you played multiplayer PC games in the 1990s, you played over IPX: it was the network option in StarCraft, Warcraft II, Diablo, Heroes of Might and Magic III, the early Command & Conquer games and hundreds more. The official IPXWrapper compatibility list reads like a hall of fame — and overlaps this site’s own coverage: Carmageddon, Grand Theft Auto II and Need for Speed: High Stakes are all on it.
Why It Stopped Working
TCP/IP won, and IPX had no role on the internet. Microsoft shipped the IPX protocol with Windows for years, then dropped it: as IPXWrapper’s own documentation puts it, the IPX driver is unavailable as of Windows Vista and Server 2008. There is no setting to re-enable and no official driver to install on Windows 10 or 11 — the protocol the games speak simply does not exist in the operating system anymore. The games are not broken; their language lost its last native speaker.
How IPXWrapper Works
IPXWrapper is a wrapper library: its DLLs are placed in the game’s folder, where they intercept the game’s IPX network calls and carry the resulting packets inside UDP over your ordinary modern network. The game believes it is talking IPX to a NetWare-era LAN; in reality every packet travels as standard IP traffic. Two practical consequences follow. First, every player must run the same wrapper setup — a machine without it cannot hear the others. Second, coverage extends beyond raw IPX: the package also handles DirectPlay-era titles through its registry files, which is why its quick-start mentions DirectPlay alongside IPX.
Credit where it is due: IPXWrapper is an independent open-source project by Daniel Collins (Solemn Warning), not a creation of DxWnd’s developer. ghotik bundles it — sensibly, since windowed-mode players and LAN-revival players are the same audience — and the wrapper remains actively maintained in its own right, with version 0.7.2 released in August 2025. Like DxWnd’s other bundled companions, it solves one period problem at one layer; the proxy mode explainer shows the same bundling philosophy on the graphics side.
Setting It Up, in Outline
The shape of a setup is the same for every title. The wrapper’s DLL files are copied into the game’s own folder — the official quick-start counts four DLLs — so the game loads them in place of the system’s (nonexistent) IPX support; DirectPlay-flavoured games additionally use the registry file supplied for 32- or 64-bit Windows. Every player repeats the identical setup with the same wrapper version. Inside the game, nothing changes: you choose its LAN/IPX multiplayer option exactly as in 1998, host or join, and play. The one configuration decision with real consequences is the network interface — the wrapper can be told which adapter is primary, and on a PC juggling Ethernet, Wi-Fi, VPN and virtual adapters, telling it beats hoping.
Why UDP as the carrier? Because it is IPX’s natural modern relative: both are connectionless datagram protocols — fire a packet, no session, no handshake — so wrapping one inside the other loses nothing in translation. The game cannot tell that its “LAN” is now a stream of UDP packets crossing a network stack designed decades later, which is precisely the standard a good compatibility layer is held to.
The Practical Picture
The intended stage is one local network: PCs on the same router, each running the wrapper, each launching the same game, and the game’s own LAN browser finding the hosted match as it did in 1997. The same trick works over a VPN that makes distant PCs behave like one LAN, which is how most modern “LAN parties” for these titles actually happen. Two mundane details decide most attempts: pick the right network interface in the wrapper’s settings if a PC has several (VPN adapters and virtual interfaces confuse it), and expect ordinary UDP traffic — firewalls and routers treat it as such.
Performance is rarely the worry it sounds like. IPX-era games were built for 10-megabit office networks and dial-up-grade assumptions; their traffic is a trickle by modern standards, and wrapping it in UDP on a home LAN adds nothing a player can feel. Latency only enters the story when the “LAN” is a VPN spanning the internet — then physics, not the wrapper, sets the delay, and the lockstep designs of classic RTS titles tolerate it about as well as they tolerated a congested 1998 hub. On a real local network, the experience is the original one: instant, free and faintly miraculous to anyone who watched this protocol pronounced dead.
Honest Limits
IPXWrapper revives a protocol, not a service. There is no matchmaking, no public server browser, no accounts and no internet lobby hiding inside it — if a game’s online scene died with its official servers, the wrapper does not bring that back; LAN and VPN-LAN are its whole territory. DOS games are also outside its scope: DOSBox provides its own IPX tunnelling for DOS titles, a different solution at a different layer. And remember that DxWnd itself only handles the window — multiplayer success here belongs to the wrapper, as our DxWnd explainer puts it: DxWnd is a host for era fixes, not their author. For the games themselves, start from the game guides hub — our Carmageddon and GTA 2 guides both cover titles on the wrapper’s proven list.