Problem w/ Server Not Showing on Master List

[rmdashrf]

Hello all!

Currently, I am helping a friend set up a server on windows. His ports are all properly forwarded, his firewall's rules are set, etc. I can connect to him directly by connecting to his IP. Everything is fine.

I run his server (as well as all my others) with
tremded.exe +set dedicated 2 +exec server.cfg +map atcs +set net_port 30720
The server sends a heartbeat to the master server nor are there any rules on his firewall that blocks outpound/inbound packets sent to/recv from this address. (master.tremulous.net)

Resolving master.tremulous.net
master.tremulous.net resolved to 67.222.136.108:30710
Sending heartbeat to master.tremulous.net
Resolving master.tremulous.net:30700
master.tremulous.net:30700 resolved to 67.222.136.108:30700

Tracing route to master.tremulous.net [67.222.136.108]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.0.1
  2     3 ms     2 ms     1 ms  192.168.1.254
  3    79 ms    33 ms    36 ms  adsl-xx-xx-xxx-xxx.dsl.pltn13.sbcglobal.net [99.
30.227.254]
  4    15 ms    15 ms    14 ms  64.164.107.130
  5    22 ms    18 ms    18 ms  69.220.8.95
  6    16 ms    16 ms    17 ms  ex2-p10-0.pxpaca.sbcglobal.net [151.164.190.83]

  7    15 ms    23 ms    16 ms  as4323-twtelecom.pxpaca.sbcglobal.net [151.164.2
48.110]
  8    57 ms    63 ms    57 ms  hagg-03-ge-1-0-0-459.dlfw.twtelecom.net [64.129.
234.20]
  9    58 ms    60 ms    57 ms  206.123.64.21
 10    58 ms    57 ms    58 ms  72.249.0.66
 11    69 ms    59 ms    58 ms  master.tremulous.net [67.222.136.108]

Trace complete.

I have tried isolating the problem by running without a qvm, running with different tremded clients (tremfusion 0.9/tremfusion 0.99r2/MGtremded), etc.

Could someone please help me try to resolve this issue? Any help is appreciated. Thanks

[Celestial_Rage]

I had a similar problem. For some reason, putting the net_port inside a .cfg file fixed the problem. Not really sure why though.

[kevlarman]

it's likely that your friend's nat translates the port to something else (especially if another trem client was running when the server started up, then it has to), then when the master checks to see if there's an actual trem server running on that port, it finds nothing and doesn't list it. try running the server on a different port (make sure you properly forward the new port), and if that doesn't work, you need a new router pretty much.

[David]

Code: [Select]

New server added: 99.30.227.172:53022; 186 servers are currently registered
99.30.227.172:53022 timed out; 186 servers currently registered
New server added: 99.30.227.172:53032; 182 servers are currently registered
99.30.227.172:53032 timed out; 184 servers currently registered
New server added: 99.30.227.172:53041; 186 servers are currently registered
99.30.227.172:53041 timed out; 182 servers currently registered

So pretty much confirms what kev said, the router is munging the ports.
It might be worth looking to see if there is any firmware upgrades for the router, or options to make the nat slightly less aggressive.