PDA

View Full Version : TeamSpeak Server problem :(


XelNaga
09-09-2004, 01:53
We have a serious problem with our TeamSpeak server.

The installation caused no problems at all, and everything worked fine. I connected, talked to a mate, and it worked exactly the way it should. So I gave the other team members the IP, and suddenly, someone couldn't join.

I thought he was too stupid, but then, even my brother, who is connected to the internet through MY OWN PC (WinXP I-Net Sharing), couldn't connect. So random people have timeout, as if the server wouldn't exist, although they can ping the VServer where the TS server is hosted. Also they can join any other TeamSpeak server without problems.

I changed the port to default and to other ones, but it didn't change anything. And it seems like it has nothing to do with the ISP neither, as different ISPs had both affected and not affected people.

The concerned server can be found here: 195.24.74.203:9999

I would be really glad if someone could tell me how to solve this problem, as I really tried everything I can think of, and couldn't even identify the source of the problem, nor the problem itself.

Label2021
09-09-2004, 02:45
Please tell me you have opened up the right port on your firewall/router...

If not, tell me what firewall or router you have, and Ill see if I can help.




-LabeL-

SatanClaus
09-09-2004, 03:47
does the problem linger when the affected persons switch to debug-logging (ts-client / settings / options / other)

please answer the questions in the forum rules, as you basically tell us that there's a problem, but our scrying-skills aren't that advanced.

cu
SatanClaus

XelNaga
09-09-2004, 09:36
Please tell me you have opened up the right port on your firewall/router...

If not, tell me what firewall or router you have, and Ill see if I can help.




-LabeL-

Your reply is somewhat nonsense, as I explained in all due detail that the problem affects different ISPs (Inter Server Providers) and different people with different setup of their PC and different firewalls.

Plus, the problem is only to join OUR server, and not any other server, no matter which port. And it's random, so sometimes you can connect, but if you can't it won't work for maybe an hour or even some days. All other servers work, on any port.

XelNaga
09-09-2004, 09:45
does the problem linger when the affected persons switch to debug-logging (ts-client / settings / options / other)

please answer the questions in the forum rules, as you basically tell us that there's a problem, but our scrying-skills aren't that advanced.

cu
SatanClaus

I will try to check whether the debug-logging helps.

TeamSpeak version: latest...of course...


as far as the

Operation System + Service packs: different ones
Soundcard + Driver versions

I believe it is a serverside problem, my personnal configuration doesn't matter, and I don't know if it is TS related, but I couldn't find any other possibility, as the web server on the same machine is being reached by everyone.

What error message do you receive?

Connection timed out, as if the server wasn't online. The affected client can ping the server and reach the webpage hosted on the same IP/machine though.

How often does the error appear?

I couldn'tfind any system or pattern, it's just plain random on plain random machines, but it seems that if people are affected, they stay affected until reconnect to the internet (dynamic IP --> refreshes IP address). It also seems that only a certain group of people are affected and others aren't. Those who are not affected never get the problem, those who are can't connect most of the time.

What did you do to resolve the problem?

I tried different ports, told the people to update their TeamSpeak and their DirectX, told them to disable firewalls, open the ports etc., but nothing changed anything.

and last but not least: Are you a hot looking girl? (I think it might be better of not asking that)

I'm not, but my gf is Oo


All in all, I don't know whether the problem lies in the TeamSpeak server or in the VServer itself (DNS problem or something similar), but there is nothing left to do from my side to solve the problem, as far as I can think.

P.S.: one of the clients affected has finnished his informatics studies at the university and works as network and program developer for a science institute, I REALLY exclude a client-side problem.

m&m's
09-09-2004, 17:38
a Connection timed out is most likely a networking proublem of some kind . nic card , router or isp has slow service some between point A -- B. i would get the same error when i tryed to conect to a hosted server "hosted for me by 3rd party" all i did was open a port in my router so the info would pass thru unmolested by the router and i no longer got the errors any longer ??? i know were noy sapose to have to open ports to conect as clients but i had to too stop that same error ....and thats all i did.... my two cents worth !

XelNaga
09-09-2004, 17:59
Why could the people ping the server then? Oo And why could some people join and others not, in case the server doesn't have the port open?

guldi
09-09-2004, 19:51
Did the debug mode helped you ?
I assume the NAT thread in the FAQ will not help in your case. However, just to be sure, did you checked it ?

XelNaga
10-09-2004, 08:35
Yes.

One interesting thing we found out: those who can't connect through the server list (although everything is entered correctly) are able to join the server through quick connect. Sound very weird.

But doesn't matter anymore, because a new server will go online soon, and the old one will be shut down.