Users getting disconnected

[adams]

I have users that are constantly getting disconnected after anywhere from 5-20 minutes. We are all running Windows 2000 and the server is on windows 2000 as well.

Sometimes the person is in the middle of talking and poof..

Are some of you behind a router or firewall?
I had the same problem until I increased udp+tcp timeouts for my NAT firewall/router.
This line should do it for linux with ipchains:
/sbin/ipchains -M -S 7200 20 320

[adams]

We are all behind the same firewall including the server.

[~oe~]

so increasing the timeouts of the routers should alleviate the disconnect problem? i'm behind a linksys (CRAP) router and after about 10 minutes i get disconnected if someone leaves or joins the TS server.

I'll look into the router settings this evening.

[Bravehart]

hey ~oe~ Im also behind a Linksys Router, BEFSR41 to be exact. I cant figure out how to increase the udp+tcp timeouts. Can ya let me know how to do this???btw I also get the same problems, get disconnected from TS like 10-15 minutes majority of the time. Then when I reconnect there are two of my names on the server.

[~oe~]

well i'm pretty sure it's going to have to do w/ the port forwarding feature. As of right now i have every port forwarded to my IP on the local network. This effectively eliminates the firewall, but hell, i want to play games not worry bout someone stealing my information.

I'm sure you could find the correct ports to open up for TS but i was too lazy to look. I've also been reading a site that has information on the linksys router and common problems but to no avail.
linktified

i think the bottom line is this:
1. wait for TS 2.0
2. buy an SMC or other router (i have an SMC at school, and it works great)

oe

Did you try to look for firmware upgrades for your router? Maybe the problem is already solved?
I suggest www.google.com to look for upgrades.

[tarbizkit]

this fix has worked for me


i have a linksys router too
the way i fixed it was to put the computer that i have as the teamspeak client in the dmz. there are some security issues with this, but, it WILL work.

[Unregistered]

Originally posted by Bravehart
hey ~oe~ Im also behind a Linksys Router, BEFSR41 to be exact. I cant figure out how to increase the udp+tcp timeouts. Can ya let me know how to do this???btw I also get the same problems, get disconnected from TS like 10-15 minutes majority of the time. Then when I reconnect there are two of my names on the server.

In order to setup a public IP server for TeamSpeak, you must first do the following:

Assign a static IP Address to the computer that is going to be the designated server. If the LAN IP and DHCP Settings were not modified in any way from default, an address of 192.168.1.3 will work. Don't forget the Subnet Mask, Default Gateway, or the DNS Information. For more on setting up a static IP Address, refer to "How to set up a static IP address" in this Knowledgebase.

Access the Router's Setup page and select the Advanced tab. Click on the Forwarding tab and make the following modifications: [using an IP Address of 192.168.1.3]

Service Port Range......Protocol.........IP Address
8765...........................TCP............192. 168.1.3
8766...........................UDP............192. 168.1.3

Once this is done, the server address for clients outside of the LAN will be your WAN IP Address* from the Router's Status page.

* If your service provider has provided you a dynamic IP Address or you are running a PPPOE DSL service, clients may drop unexpectedly due to changes in the IP Address. The use of a dynamic dns hosting service is recommended if hosting a server with one of these connections.

[st1971]

Originally posted by Bravehart
hey ~oe~ Im also behind a Linksys Router, BEFSR41 to be exact. I cant figure out how to increase the udp+tcp timeouts. Can ya let me know how to do this???btw I also get the same problems, get disconnected from TS like 10-15 minutes majority of the time. Then when I reconnect there are two of my names on the server.

I could not find this either on my router. I am running the newest firmware.

I did hook up a Windows 2000 server and set up Routing and Remote Access Services then I used this as my router (2 NICS). When using this PC as a router TeamSpeak runs great but not when using the linksys. Like I stated before I hope the developers of this application are in communication with Linksys to fix the issue.

[InvictuZ]

Ok I'm confused. Is users disconnecting a problem with the servers configuration, or is it the clients?

If it's the clients, can't they just open up the port range on their routers config? But what are the port #'s?

2ndly If it is the server, does the #2 post above mine fix this?

3rd, is their anyway to disable the ping timeout feature that is causing this, within the server?

Because I am too behind a router, and having the same problem, with users connecting to my server. They keep getting ping timeout. A simple solution IMO would be to disable it on the server itself. But if that cannot be done what is the port range for each client?

Thanks for your help,
InvictuZ

[T. Boonstra]

If users can connect and talk at the server but timeout after a while then it is really the timeout issue and you'll need to increase the timeout setting on the router or put the server in the DMZ (which isn't the securest thing in the world).
When these timeouts occur it isn't a port mapping issue..

If all the users have the disconnect problem with that server then it is an Server issue, if only 1 client (or maybe 2) have this problem it could be a Client issue. (i'm not sure if clients experience this problem if they are behind a problem router, or if the problem only lies for servers behind problem routers)

[InvictuZ]

I belive it has to be a clients as well. The server is setup as a DMZ host, with a static IP. Users connect and talk just fine. It just times them out, and they drop from the server.

IMO there can be 2 work arounds.

#1 Is that we find which ports are used for the ping method and have clients open those ports on their routers config / firewall's.

or

#2 Disable the ping timeout setting on the server itself.

However on either of the 2 I have no ideas, I tried maxing the setting out within the server, and it still times people out. And I have no ideas what ports are used client side for the ping option. But those are our 2 options, and we have to tackle either of those to put this problem to rest.

[Johann]

Originally posted by ~oe~
so increasing the timeouts of the routers should alleviate the disconnect problem?

So how does one increase the timeouts of the router? Or can this be done via tsserver.ini file?

I have a few peeps having timeouts yet they don't know that they have - Tspeak doesn't say (player left) when it happens. Then there are peeps that don't timeout and it runs great for them.

I am also running a TSserver behind the Linksys BEFSR41 router and have recently upgraded the firmware before I even tried to host a TSserver. I didn't see any obvious place in the firmware setup that allows one to increase timeouts (really not sure what this is anyways).

Btw, when is TS 2.0 coming out?

Would like to try to solve this problem before TS 2.0! Any help is greatly appreciated.

[Solitaire]

its a UDP timeout issue with NAT. i am going to give a very simple explanation and try not go over anyones head. those of you that do understand this in detail correct it if you want but like i said im trying to give a very simple and short answer. UDP is a connectionless protocol where TCP actually establishes a connection. UDP is faster (which we want out of this app) but in achieving that speed does not have error correction nor does it maintain state in the normal sense. Your router opens the UDP port per the clients request and sends the data across the wire. since UDP is connectionless the router opens this port for a set amount of time since it has no idea how long you are going to use it. once that time expires the router considers that connection closed. the server sends information back to the client and since the router considers it closed all of a sudden has no clue which pc behind it that packet was intended for and just drops the packet. since the server did not hear back from your client it now considers your client gone. you try and transmit and the server recieves your packet but treats it as trash because you are "no longer there"

"For a detailed understanding of the above, an investment in TCP/IP Illustrated might behoove you"