Page 1 of 1

Dedicated server port and networking

Posted: Tue Mar 08, 2016 2:53 pm
by oneprince
Hello. Question on dedicated servers. I have one set up on Azure and it works fine from home. But at work, they have a stronger firewall (aka with egress filtering). I had them poke UDP:34197 through but I still cannot connect. Anyone know of something I'm missing? Does it need both tcp/udp? Does the peer-to-peer part try to hit out on other ports after the initial connection?

Thanks.

Re: Dedicated server port and networking

Posted: Tue Mar 08, 2016 6:29 pm
by Bisa
try adding/removing "--peer-to-peer" as an argument to the server when you troubleshoot, by default the server kinda act as a proxy of sorts channeling all connections via itself between all clients, enabling true peer-to-peer mode would allow clients to connect to each other. The latter of which is a pain in the **** for less tech savvy users as it requires all clients to port forward their udp port (default port unless you manually change it in the config)

.... in any case, if you have not enabled --peer-to-peer I suppose it would simply only ever use the same udp port rather than open a connection on some other port but I won't take poison on that, just figured Id name drop the peer argument