Hosting and Joing SS2 Multiplayer on XP

Capt. Queeg on 21/1/2007 at 22:44

I've got SS2 up and running on XP Pro SP2, and so does a friend.

I've installed Bobrucked Fixed exe, the STUP textures and Rebirth Complemented.

We would like to play multiplayer games.

When I host a game, it shows my local IP address and not my external address. I don't know if this is a problem. Is it?

When he hosts a game his system goes boom.

When either of us try to join a game, our systems go boom.

Is muliplayer possible on XP? And if so, how?

Thanks!!!!

Capt. Queeg
(http://www.TheCodeCave.com)

Kolya on 22/1/2007 at 02:18

Well we had a talk on (irc://irc.starchat.net/systemshock) #systemshock already. I'd just like to add that he needs your external IP of course. What your game shows as your adress is irrelevant.

Sparks001 on 22/1/2007 at 17:03

Yes MP is possible. If I recall correctly you need a program called hamachi. It will setup a private network. Has been a while since I did all this so don't hold your breath

Capt. Queeg on 22/1/2007 at 19:41

We finally got it working.

The BIG thing is that it, like many other peices of software (including Azureus), is incompatible with NVidia on board network cards. The network filtering stuff, which you can't completely get rid of without uninstalling network card, is simply incompatible with SS2. We tossed in another network card and uninstalled all of the NVidia software, and it stopped crashing.

At that point, we kept on his external IP addess as the ip address he was hosting from. We realized that, probably because Hamachi was installed before the current network card, SS was using his actual network card as the default network.

I tried hosting on my side, but while the player count would go up, his player name was never shown and we always got a player disconnect.

So, we used FPort to diagnose what ports were in use when hosting the game. We were unable to get SS2 to work correctly until we finally openned port 2300 for TCP and 3000-3999 for UDP, which now, after the fact, I find is a subset of what I found here: (http://www.ttlg.com/forums/showthread.php?p=1501616)
Forward port range (TCP & UDP): 2300-2400
Forward port range (TCP & UDP): 28800-28900
Trigger port: Outgoing: 47624, Incoming: 47624

So... What I think I'll do is try my smaller range of ports and connect it to the triggering port and see how that works. Thanks for your help!

This is what we'll be trying:
Forward port range (TCP): 2300
Forward port range (UDP): 3000-2999
Trigger port: Outgoing: 47624, Incoming: 47624

Sparks001 on 22/1/2007 at 19:55

I don't remember having to open ports... strange.

Hamachi should bypass all that because it creates a virtual private network over the internetz...

Player A creates a network using hamachi, Player B connects to that network. Player A hosts, player B connects to the IP hamachi creates (as above this is all from memory, from waaaay back)

Capt. Queeg on 22/1/2007 at 21:12

I think it had something to do with his primary network card being used - at least in part, by SS2. Once you VPN in, you should be past all of that stuff, but I'm not so certain the VPN was being used for 100% of the communication.

We'll diagnose further later.