Server help
#9
tempest: you're wrong - UDP is different from TCP in many ways, the sites posted above do not tell you anything about accessibility of your AC.
See: key differences between TCP and UDP and difference between TCP and UDP.

If the MS reports your server could not be "pinged" it means it could not reach you on your INFO-port - if that worked you'll be visible in the server list on remote clients - but you also need to forward the GAME-port, so people do not get a connection-attempt-failure when selecting your server from the serverbrowser.
The ports need to be forwarded as UDP only and you should have two forwards - do not use a range. We've experienced it a couple of times where either the router was set to forward BOTH TCP and UDP - and it FAILED; or when the router was set to forward the range of (default ports:) 28763-28764 and it also FAILED.
Your best bet is to have two seperate forwardings, on UDP only for the GAME- and the INFO-port; if you select your own GAME-port (n) the INFO-port will be (n+1).
The MasterServer-Port is 28760 - but in the usual home-router-setup you'll not be needing any forwarding here, because it's only used via an outgoing connection and your router will DNAT your traffic automatically - that's it's job after all :-)
HTH
Thanks given by:


Messages In This Thread
Server help - by Dark$aint - 03 Nov 10, 04:38PM
RE: Server help - by spamma - 03 Nov 10, 05:24PM
RE: Server help - by Dark$aint - 04 Nov 10, 02:52PM
RE: Server help - by JGAN - 04 Nov 10, 03:46PM
RE: Server help - by Faron8 - 09 Nov 10, 05:38PM
RE: Server help - by tempest - 09 Nov 10, 07:15PM
RE: Server help - by JGAN - 10 Nov 10, 11:23PM
RE: Server help - by tempest - 10 Nov 10, 11:34PM
RE: Server help - by flowtron - 11 Nov 10, 03:28PM
RE: Server help - by |KU$H|KidCuDi - 27 Nov 10, 09:59PM
RE: Server help - by JGAN - 27 Nov 10, 10:18PM
RE: Server help - by |KU$H|KidCuDi - 28 Nov 10, 04:44AM
RE: Server help - by JGAN - 28 Nov 10, 06:01AM