Logo Platform
logo amplifiers simplified

I got the multiplayer to work without any issues.

Copied to clipboard!
12 years ago
Dec 29, 2012, 9:46:19 PM
Now this was only for a friend and I. Here is what we did.



1. Made sure no antivirus software was affecting the program.



2. Forwarded the following ports.



27015 TCP

3478 UDP

4379-4380 UDP

27000-27050 UDP



Basically all the ports listed here: https://support.steampowered.com/kb_article.php?ref=8571-GLVN-8711



I remember Wargame: European Escalation requiring that you forward 27015 TCP to interact with their servers.



After this we did not have the slightest issue.



Hope it helps!
0Send private message
0Send private message0Send private message
12 years ago
Dec 31, 2012, 11:54:35 PM
I will lose the rest of my life explaining it to people.



And half of you are probably not even allowed access to your router or you are in a dorm where you have a dynamic ip.



I hunted down the problem for the devs and CM's. This post was mostly for them. I'm less than pleased that my offer to assist in solving the problem was never replied to by the CM that I PM'd on these forums. I went ahead and solved the problem anyways. It was a simple port issue.



Lets see if they have the sense to make a sticky about the ports to forward.
0Send private message
12 years ago
Jan 1, 2013, 2:14:03 AM
I personally have never had a problem with Endless Space, and i've just now realised this is probably because i have these ports open. Doesn't help a smeg though if your not the host :/
0Send private message
12 years ago
Jan 1, 2013, 6:18:21 PM
Gameslayer989 wrote:
I personally have never had a problem with Endless Space, and i've just now realised this is probably because i have these ports open. Doesn't help a smeg though if your not the host :/




You might have. These are nothing more than the standard steam multiplayer ports.



I suspect the 27015 TCP is the big culprit. WarGame: EE also needed that port for multiplayer.
0Send private message
12 years ago
Jan 1, 2013, 6:24:27 PM
I don't have 27015 open, and I've almost never had an issue with ES multiplayer. Not discounting the possibility that its a factor.
0Send private message
12 years ago
Jan 2, 2013, 4:41:46 AM
Protocol Port Range Translate To ... Trigger Protocol Trigger Port







TCP 27014 - 27050 27014 - 27050 - -





UDP 4380 - 4380 4380 - 4380 - -





UDP 3478 - 3478 3478 - 3478 - -





UDP 4379 - 4379 4379 - 4379 - -





UDP 27000 - 27030 27000 - 27030 - -



All open.

Still goes out of sync.
0Send private message
12 years ago
Jan 3, 2013, 7:32:55 AM
Is it open for everyone?



I'm suspecting its the 27015 TCP thats the big issue. Wargame used a modded server for steam multiplayer and it needed that port.
0Send private message
12 years ago
Jan 3, 2013, 10:20:50 AM
Kab wrote:
Protocol Port Range Translate To ... Trigger Protocol Trigger Port







TCP 27014 - 27050 27014 - 27050 - -





UDP 4380 - 4380 4380 - 4380 - -





UDP 3478 - 3478 3478 - 3478 - -





UDP 4379 - 4379 4379 - 4379 - -





UDP 27000 - 27030 27000 - 27030 - -



All open.

Still goes out of sync.




every player in the game might need the ports open, though ireally don't think the sync issues will fix even if they are.
0Send private message
?

Click here to login

Reply
Comment

Characters : 0
No results
0Send private message