Multiplayer troubleshooting collects the known connection notes for Multiplayer games in Star Wars: Rebellion, from the original 1998 readme and from later community packages that list firewall ports.

Notes from the 1998 readme

The "Multiplayer Issues" section of the LucasArts readme gives these points:

• No games found. The game shows no message when a search finds nothing. If no game names appear after 2 minutes, the player cancels the screen and searches again.
• TCP/IP over the Internet. The dialog asking for a computer name or IP address of the session host must be filled in for an Internet game. Leaving it blank starts a search that works only on a TCP/IP local network.
• Starting. The readme recommends that both players wait until both have finished the introduction before opening the options screen.
• Dropped players. When a player loses the connection or crashes, the other side takes around 2 to 3 minutes to receive a message that the player left. Meanwhile the opponent can still move around and open windows, but time stops for both players, and after about a minute the opponent can seem locked up even though the game is waiting for the message.
• Internet Gaming Zone. The Zone launches the game and drops the player straight into it. Returning to the cockpit ends access to that Zone game, so another Zone game requires quitting and restarting from the Zone. The readme also asks players to disconnect from the Internet before starting a single-player game after leaving the Zone. See Internet Gaming Zone.
• "Awaiting Opponent Response". This tactical status text means the player's machine is ready but is waiting on the other machine. It appears when the other player has paused, switched to another application, has network trouble, or is still moving into or out of the strategic game.
• Disconnect button. On the multiplayer options screen, Disconnect returns to the cockpit and removes the game from the active game list.
• Saved games. The table of contents lists "Loading a Saved Game in Multiplayer" as a topic; the section text in this file does not include it.

Firewall ports

Two community files list the network entries needed for Internet play on current Windows:

Program	Protocol	Port
dplaysvr.exe (in %SystemRoot%\SysWOW64)	TCP and UDP	47624
REBEXE.EXE	TCP	2300
REBEXE.EXE	UDP	2350

The post-install readme of the GOG patch package says the GOG installer normally handles this and that, if it does not, these flows should work in both directions through the Windows firewall and the router. A small text table named REBEXE.dplaysvr.Multi-player.txt, shipped with the Rebellion 2.63.1.0 Fix download, gives the same three entries.

The Community Fix installer's own documents describe a wider range instead: TCP and UDP ports 2300 to 2400 should be open in the firewall. The sources do not explain the difference. For the fix itself, see Rebellion Fix.