People unable to stay connected to my TS Server

[Graeme]

TS Version: 2.0.19.40
Windows XP Pro Version 2002, Service Pack 1, updated to current date
Creative Audio PCI (Soundblaster) Microsoft Native Driver 5.1.2535.0
DirectX 9.0b


I currently am running 2 computers behind a Siemens 2604 Router with NAT firewall. The UDP port 8767 (TS default) is forwarded to the computer's (which is running the TS server) internal address. This is the only port I currently have forwarding.

My other computer running the 2.0.19.40 TS client software can connect and stay connected to the server with no difficulties using the Internal address.

People connecting from outside my network however connect and time out in 2 seconds.

My firmware for the Siemens Speedstream 2604 router is the current version- v1.0 Release 5

I have tried the BoundToIp solution suggested on the forums. This did not fix the problem and added a further difficulty in that I could not connect with any of the systems behind the firewall either.

Teamspeak was working fine before I downloaded the newest version. Unfortunately I did not write down what the previous version was and had done a complete uninstall (as well as deleting the install download) so I cannot tell you what version it was, sorry...mistake deleting that I know.

Any suggestions? External systems can connect, but time out. Internal systems can connect and stay connected. The single other difference I have noticed is that when using the tray icon my external IP address no longer shows. While I have read this has nothing to do with the functionality of Teamspeak I feel its another 'symptom' of not being able to 'keep' an external connection despite having the UDP port forwarded.


Any suggestions would be appreciated.

[Graeme]

Just to clarify-

The tray icon does show my internal address as it always has, it however no longer displays my external IP address that clients outside my network use to connect.

[Graeme]

My router is acting as my DHCP server for my network. It is the only DHCP server.

I had read (but no details were given) that having a router act as the DHCP server could cause problems.

[Dummer Sack]

There are quite a few reports about timeouts after upgrading to the latest client (2.0.32.62) and server (2.0.19.40) version.

However I still have to see someone who was able to isolate the problem. It just seems that something has changed in the network code that some router NAT systems do not like.

To the DHCP:
It can only cause a problem if the computer that is running the TS server is configured by DHCP. Since the IP address is configured via DHCP you have no control (with most DHCP servers) what IP is given to your TS server. And if the new IP is different form the IP in the port forwarding then no one will be able to connect from the outside.
Also I don't know if all connections staty established when the computer requests a new IP after the old one expired even if it gets the same IP again. This can cause a problem if the expiration time of the IP given out by DHCP is really short.

I recommend to configure the IP of the computer that runs the TS server manually anyway. I doubt it but if this solves the problem please post here.

EDIT: The person in this thread had the DHCP porblem. But as you can see the timeout occured after 24 hours not 2 seconds.

[Dummer Sack]

Update: In the German Forum someone could solve the problem by updating to server .46. Though I don't know if your porblem is really related to his. He got the following error in the TSClient.log when he set the client to debug mode:

07-12-03 09:12:13,1480,WARNING,All,procedure TClientReadThread.Execute,Socket Error # 10054
Connection reset by peer.

You can get the .46 server in the Developer Releases Forum and try if this also solves your problem.

[Graeme]

I have tried updating the firmware on the router but unfortunately it did not solve my problem.

Once the TS server box was moved out from behind the router however it functioned normally. The problem is with the interaction between the router and the TS server software. That said my current configuration is working fine. I will continue to try various 'fixes' to resolve it and if I get lucky I will post it here.

Thank you for the assistance.

[Dummer Sack]

I mean that he updated TS to version 2.0.19.46 (the developer release), not his router firmware.
Maybe there were some changes in the netcode of TS so that it did work with his router.
But maybe your problem and his only have the same symptoms and are not related otherwise.

[Graeme]

Will try that as soon as possible. Thanks for the suggestion!

[Limpo]

I thought upgrading fixed my problems, but apparently it hasn't. Oh well.

[Dummer Sack]

Yes, many reported that upgrading did not help.
But apparently upgrading helped the guy I mentioned.

[pim]

Have had the same problem and it drove me mad. Older TS-server versions worked very wel, but the last version kept disconnecting everyone after 2-4 seconds. After having swapped the router for a different one (different brand too) the problem was gone.

However now i have the problem that the server goes down every 24 hours or thereabouts. See other thread inclusing the log, for this prob

I am interested to find out about the IP thing though. I keep getting errors in the serverlog showing that the server can not determine external IP

[bliSSter]

Having the same issue here...I'm using the Seimens SpeedStream 2624 router and have the UDP ports forwarded to my server from port 8767, but no one can connect to TS from outside the firewall. They can get into the web server for UT 2k3 on port 80, so the router is good to go there. I can get into TS from an internal 192.168.1.xxx addy, but no one can get there using my 12.215.234.xxx external IP. Something freaky is going on with this router, and I need to keep using it for the wireless to my wife's laptop.

FYI: I'm also getting the "ERROR,All,frmMain, unable to detect external ip" error in the server.log file - if that helps anyone.

- bliSS

[pim]

It's the router, it's an OEM Efficient networks box and see the other threrads on this piece of kit, like my Sitecom it refused to work, now I've got a Linksys I am OK