PDA

View Full Version : No reply from server


Senjak
12-07-2007, 05:09
Alright I noticed there are about 20 million threads with the same issue...however I couldn't find one with my exact problem.

So I've been able to connect to my group's TS server hundreds of times. Today I tried and I got this:

[22:58:09] No reply from server
Maybe the server is offline
or maybe teamspeak is not running on it

I went to the client log, and here is the full description:

11-07-07 22:36:51,2224,ERROR,ProcedureInfo,Client Open,Exception: Timeout on recv LoginStep2 wait

So I try accessing all the different servers I know of, and I connect to all of them just fine. It is just this single server. So someone I know recommends I run the connectivity test. This is what pops up.

Performing UDP test...
» Establish a connection with the server OK
» Verify that it is a TeamSpeak 2 server OK
» Perform connection handshake ERROR 2
» Retreive a list of active channels ERROR 2

Performing TCP test...
» Establish a connection with the server OK
» Verify that it is a TeamSpeak 2 server OK
» Retreive the servers global information OK

Performing HTTP test...
» Establish a connection with the server OK
» Verify that it is a TeamSpeak 2 server OK
» Retreive the servers version information OK

I'm not too computer savvy, and was just wondering if anyone knows what the heck is wrong. Everyone else in the guild can connect no problem, it is only me. I have not changed anything, it was working fine the day before. I'm at a loss at what to do. Any help would be appreciated. I'm running Windows XP Home Edition, Teamspeak 2. Server address is 66.103.151.6:8767. There is a password, but I always have it input and it hasn't changed.

BHKai
12-07-2007, 17:52
Do not use the wan ip if you are inside the lan. Use the LAN ip.

Senjak
13-07-2007, 01:51
It's not a LAN...sorry if I made it sound like one.

BHKai
13-07-2007, 05:21
Yeah the server if up. And you can not connect to it?

Try a traceroute.

start>run>cmd>tracert 66.103.151.6

Senjak
13-07-2007, 05:23
Ya it times out after the 8th hop at 4.68.103.130 when I trace route. I called my ISP, they said they can't do anything about it sorry. Fun times.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Ben>tracert 66.103.151.6

Tracing route to 66.103.151.6 over a maximum of 30 hops

1 5 ms 5 ms 5 ms 73.208.60.1
2 7 ms 5 ms 5 ms 68.85.249.97
3 6 ms 7 ms 5 ms 68.85.244.178
4 6 ms 7 ms 7 ms 68.85.244.133
5 7 ms 7 ms 15 ms 68.85.244.97
6 10 ms 11 ms 9 ms te-3-3.car2.Houston1.Level3.net [4.79.90.5]
7 49 ms 53 ms 54 ms ae-5-5.ebr1.Atlanta2.Level3.net [4.69.132.238]
8 47 ms 48 ms 47 ms ae-11-55.car1.Atlanta1.Level3.net [4.68.103.130]

9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

ScP
13-07-2007, 08:52
The error you've received indicates that the client has received a timeout while waiting for the server to response. In certain cases, a timeout issue can be solved by starting your TeamSpeak 2 client in debug mode.

The debug mode can be enabed in the clients Options dialog on the Other tab.

Senjak
13-07-2007, 22:02
I tried debug mode, that doesn't fix the problem.

Senjak
17-07-2007, 17:07
GAH! Now I get no reply from another server I connect to often! Does anyone know any solution to this? Without TS, I can't participate in the majority of the events my group has planned... :(

fillmein
18-07-2007, 09:29
I have about the same problem. Cannot connect to my clan server only. This just sucks cause everybody else does connect and I did connect before with no problems. TEAMSPEAK team please fix this No reply from server idiotic answer. Need more info than that. My tracert:
COCUME~1DUMITR~1>tracert 82.103.136.239

Tracing route to e82-103-136-239s.easyspeedy.com [82.103.136.239]
over a maximum of 30 hops:

1 7 ms 6 ms 11 ms 10.7.84.1
2 8 ms 6 ms 15 ms 82-76-243-109.rdsnet.ro [82.76.243.109]
3 10 ms 11 ms 9 ms qr10.bucuresti.rdsnet.ro [194.102.81.233]
4 9 ms 9 ms 9 ms bb01.bucuresti.rdsnet.ro [194.102.81.1]
5 40 ms 43 ms 39 ms bb01.craiova.rdsnet.ro [213.154.124.53]
6 39 ms 39 ms 41 ms bb01.timisoara.rdsnet.ro [213.154.124.49]
7 42 ms 48 ms 41 ms bb01.arad.bucuresti.ro [213.154.124.45]
8 * 43 ms 38 ms 213-154-124-61.rdsnet.ro [213.154.124.61]
9 44 ms 42 ms 41 ms xr01.frankfurt.rdsnet.ro [213.154.124.14]
10 42 ms 40 ms 40 ms t3-3.mpd02.fra03.atlas.cogentco.com [130.117.14.
193]
11 39 ms 40 ms 38 ms g6-0-0.core02.fra03.atlas.cogentco.com [130.117.
0.245]
12 48 ms 48 ms 49 ms p12-0.core01.ham01.atlas.cogentco.com [130.117.1
.186]
13 53 ms 54 ms 54 ms p0-0.core02.cph01.atlas.cogentco.com [130.117.2.
126]
14 64 ms 53 ms 56 ms netgroup.demarc.cogentco.com [130.117.21.198]
15 59 ms 55 ms 55 ms 213.242.108.155
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
I looked at previous answers with Port forwarding issue but I dont know my modem username and password. So I guess i'm stuck. Why this happens only with teamspeak and no other programs????

Senjak
19-07-2007, 17:58
Well the other server I was talking about went down actually now it's back up, it wasn't on my side. But the original problem with the first server still stands.