Page 1 of 1
LAN and WAN issue with TS 3 server - weird
Posted: Thu May 14, 2015 2:14 pm
by Sharky Tree
Didn't have an issue till I needed to replace my router/modem provided by Comcast due to upgrades and now have a SMCD3G.
Running a Server for Teamspeak 3
This is what happens every morning:
Server gives "Failed to connect to server" every morning when using the WAN IP (others cannot connect either)
Log into Server connecting via LAN IP
(others can connect now)
Server then is fully accessible through WAN IP
It probably is something really simple but I need help.
Thanks
Posted: Thu May 14, 2015 7:21 pm
by Philip
Sounds like ports being forwarded by the router are not all forwarded, or somehow "forgotten" (UPnP?).. Another possibility is that the port forwarding to accounting.teasmspeak.com is not configured. Have you manually forwarded all the ports that TS3 needs ?
TS3 uses those ports:
9987 UDP (default voice port)
30033 TCP (default filetransfer port)
10011 TCP (default serverquery port)
41144 TCP (default tsdns port)
TS3 also connects to: accounting.teamspeak.com:2008 (TCP for license checks) and weblist.teamspeak.com:2010 (UDP). TS3 weblist also uses ports 2011-2110 (UDP out, first available port in range).
Posted: Thu May 14, 2015 7:47 pm
by Philip
Once you make sure the ports are properly forwarded, you can verify that they are open by looking up the port in our SG ports database, and clicking on the "SG Security scan: port NNN" button for each related listening port (the first 4). here is a link:
http://www.speedguide.net/port.php?port=9987
Posted: Tue May 19, 2015 6:18 pm
by Sharky Tree
think i found the issue...will see tomorrow.
(Private) port recognition 30033 was set to 3033
Posted: Wed May 20, 2015 12:54 pm
by Sharky Tree
Sharky Tree wrote:think i found the issue...will see tomorrow.
(Private) port recognition 30033 was set to 3033
AAARG ... solved a different problem with that but still having the same problem with connection.
I verified that ports are set to forward:
9987 UDP
30033 TCP
10011 TCP
never used the other port - wasn't a problem before this router.
Posted: Wed May 20, 2015 1:16 pm
by Philip
You may be experiencing name resolution (DNS) issues if you do not forward 41144.. I would forward it. Also, look at the logs for any errors/clues as to what is happening. Do the ports still appear open from the WAN side when people are unable to connect ?
Posted: Wed May 20, 2015 5:52 pm
by Sharky Tree
Philip wrote:You may be experiencing name resolution (DNS) issues if you do not forward 41144.. I would forward it. Also, look at the logs for any errors/clues as to what is happening. Do the ports still appear open from the WAN side when people are unable to connect ?
I have not used (DNS) - ports look open only after I connect via LAN ### only login via a LAN IP and all of a sudden they are then open.
Posted: Wed May 20, 2015 8:42 pm
by Philip
I am not sure what exactly TS3 resolves using the TS DNS port. As to the port forwarding, is there any information logged in the TS log at night when it goes idle until the morning when you are able to login ?