PDA

View Full Version : No reply from Server message. plz help


Vanilla
01-07-2009, 09:03
ok im new at Teamspeak, but have been using it for last 2weeks without
a problem until 2days ago now i am unable to connect anymore. tried un-installin re-installing
still cant connect, i know the IP is right and password is correct.
i know other ppl who can connect to this TS server. but i cant :(
i have tried connecting to voice.teamspeak.org:8767
and i can sucessfully connect.

The IP i am trying to connect to is 62.214.177.77:8767
i know that server is in Germany an im from Australia but i doubt that
would make a difference to why i cannot connect.

plz help i have no idea whats goin on :confused:

Tomas
01-07-2009, 09:36
[09:32:44] Connecting to 62.214.177.77:8767
[09:32:44] Bad Login (name and/or password wrong)
that message is obvious(why) but lets skip that
// I am not registered and server is propably password protected.

try ping the server from your pc.
>>> what results do you get?
Windows ( Start - Run - cmd )
Linux ( Alt F2 I think and type bash ..... to stop ping in linux press ctrl C)
ping 62.214.177.77

Příkaz PING na 62.214.177.77 s délkou 32 bajtů:

Odpověď od 62.214.177.77: bajty=32 čas=48ms TTL=46
Odpověď od 62.214.177.77: bajty=32 čas=46ms TTL=46
Odpověď od 62.214.177.77: bajty=32 čas=55ms TTL=46
Odpověď od 62.214.177.77: bajty=32 čas=47ms TTL=46

Statistika ping pro 62.214.177.77:
Pakety: Odeslané = 4, Přijaté = 4, Ztracené = 0 (ztráta 0%),
Přibližná doba do přijetí odezvy v milisekundách:
Minimum = 46ms, Maximum = 55ms, Průměr = 49ms

root@rout0:~ # ping 62.214.177.77
PING 62.214.177.77 (62.214.177.77): 56 data bytes
64 bytes from 62.214.177.77: icmp_seq=0 ttl=46 time=49.037 ms
64 bytes from 62.214.177.77: icmp_seq=1 ttl=46 time=47.876 ms
64 bytes from 62.214.177.77: icmp_seq=2 ttl=46 time=48.199 ms
64 bytes from 62.214.177.77: icmp_seq=3 ttl=46 time=47.985 ms
64 bytes from 62.214.177.77: icmp_seq=4 ttl=46 time=47.997 ms
64 bytes from 62.214.177.77: icmp_seq=5 ttl=46 time=47.662 ms
64 bytes from 62.214.177.77: icmp_seq=6 ttl=46 time=47.335 ms
--- 62.214.177.77 ping statistics ---
7 packets transmitted, 7 packets received, 0% packet loss
round-trip min/avg/max/stddev = 47.335/48.013/49.037/0.491 ms
root@rout0:~ #

if there is no reply then it is possible that something is blocking you.

Vanilla
01-07-2009, 09:46
lol im a female dont ask me to do so complex stuff :p
anyway my b/f did ping that server for me last night an it stops at a place in Germany not far from the server.
he alson tried to ping it on a diff PC with a diff internet connection an still the same problem :confused:

Tomas
01-07-2009, 09:57
sry chick{oups,.... I didnt know that word before someone told me in game but dont take it personal}, but imho that isnt so complex.

well then I assume that its problem of telehouse / server
if teamspeak server is hosted make a punch on admins of the hosting server to make preasure on their telehouse/ISP to fix the damm "country BAN" .....
even thru its more like AS ignored I think.....

tracert 62.214.177.77

Výpis trasy k 62.214.177.77 s nejvýše 30 směrováními

1 1 ms 1 ms 1 ms ***
2 11 ms 12 ms 11 ms ***
3 19 ms 18 ms 20 ms 88.103.203.49
4 18 ms 18 ms 18 ms 198.18.96.153
5 20 ms 19 ms 19 ms 198.18.10.49
6 19 ms 18 ms 19 ms 194.228.190.154
7 20 ms 19 ms 19 ms 194.228.190.153
8 77 ms 18 ms 19 ms 194.228.190.2
9 20 ms 19 ms 20 ms Xe7-1-3-0-grtprana1.red.telefonica-wholesale.net
.10.16.84.in-addr.arpa [84.16.10.37]
10 27 ms 26 ms 26 ms Xe10-3-0-0-grtfraix2.red.telefonica-wholesale.ne
t [213.140.49.114]
11 29 ms 25 ms 26 ms ffm-b2-link.telia.net [213.248.85.37]
12 27 ms 27 ms 26 ms ffm-bb1-link.telia.net [80.91.252.173]
13 27 ms 26 ms 26 ms ffm-b7-link.telia.net [80.91.249.105]
14 44 ms 43 ms 43 ms versatel-ic-127969-ffm-b7.c.telia.net [213.248.8
9.110]
15 43 ms 41 ms 40 ms 10g-7-4.fra020isp006.versatel.de [62.214.110.66]

16 138 ms 177 ms 62 ms 10g-8-4.dor002isp006.versatel.de [62.214.110.145
]
17 91 ms 42 ms 41 ms 10ge-9-4.dor002isp005.versatel.de [62.214.110.13
4]
18 47 ms 47 ms 46 ms 10g-9-1.rec001isp005.versatel.de [62.214.110.249
]
19 61 ms 202 ms 208 ms 62.214.110.245
20 46 ms 46 ms 46 ms 10g-9-1.esn001isp006.versatel.de [62.214.110.241
]
21 47 ms 46 ms 46 ms 62.214.34.118
22 44 ms 44 ms 44 ms 212.7.158.38
23 45 ms 44 ms 44 ms 62.214.177.37
24 48 ms 48 ms 47 ms 62.214.177.77

trace complete
thats my tracert / traceroute

ok for you in short(I got lots of complains that I am advanced for this comunity all the time):
talk_to/message your server admins. tell them that you cant connect and also your packets are dropped on way to them. Tell them that it is most likely problem at their ISP. send them/or your boyfried your IP/IPs where it doesnt work with request that they will ping and tracert you back FROM SERVER.

if you can put your boyfriend behind screen with this post.
and for him I have a task post here tracert you made first pls just for check

Vanilla
01-07-2009, 10:05
lol thanx.
ill get my b/f to read ur post an hopefully he can help me figure it out :)
btw how do i find out who my server Admins are? possibly ask my guild leader who signed us up to TS?

ill let ya know if i get the prob fixed. hopefully its soon :D

thanx for ur help :)

Tomas
01-07-2009, 10:12
lol thanx.
ill get my b/f to read ur post an hopefully he can help me figure it out :)
btw how do i find out who my server Admins are? possibly ask my guild leader who signed us up to TS?

ill let ya know if i get the prob fixed. hopefully its soon :D

thanx for ur help :)
you can try it there. I checked upon it (the mail and links are propably useful)

mail> isp_adminemail=c.biesenbaum[@@@]gmx[dddottt]de
isp_countrynumber=4428

online is
"SunnY aka Sunnylein" "ProColi"
"elisha" ""

list of channels have propably no benefit for ya

server_name=Command & Conquer Community
link1> server_welcomemessage=Willkommen bei der Command & Conquer Community www.cuc-community.de
server_webpost_linkurl=http://www.cuc-community.de/teamspeak/webpost.php
link2> webpost >> alias http://www.cuc-community.de/teamspeak/

Vanilla
01-07-2009, 11:49
no matter what i do i can't get to the TeamSpeak server..

Pinging 62.214.177.77 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 62.214.177.77:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),





Tracing route to 62.214.177.77 over a maximum of 30 hops



1 2 ms 2 ms 2 ms DD-WRT [192.168.1.253]

2 3 ms 3 ms 3 ms 10.0.0.138

3 24 ms 23 ms 22 ms lns02.ispone.net.au [124.254.72.19]

4 24 ms 23 ms 23 ms lns.gw.ispone.net.au [124.254.72.129]

5 122 ms 138 ms 23 ms IOP-0002.gw2.mel1.asianetcom.net [203.192.136.229]

6 66 ms 35 ms 36 ms ge-1-2-0-949.gw4.syd1.asianetcom.net [202.147.42.125]

7 43 ms 40 ms 34 ms gi3-2.cr1.syd1.asianetcom.net [202.147.40.165]

8 182 ms 182 ms 182 ms po2-2-0.gw3.lax1.asianetcom.net [202.147.55.82]

9 183 ms 186 ms 184 ms ge-2-0-0-207.ip.tiscali.net [77.67.69.89]

10 345 ms 347 ms 345 ms so-5-1-0-0.fra44.ip.tiscali.net [89.149.185.62]

11 367 ms 343 ms 343 ms fra20isp6.versatel.de [213.200.86.2]

12 339 ms 341 ms 341 ms 10g-8-4.dor002isp006.versatel.de [62.214.110.145]

13 339 ms 339 ms 341 ms 10ge-9-4.dor002isp005.versatel.de [62.214.110.134]

14 463 ms 384 ms 475 ms 10g-9-1.rec001isp005.versatel.de [62.214.110.249]

15 344 ms 344 ms 341 ms 62.214.110.245

16 342 ms 344 ms 345 ms 10g-9-1.esn001isp006.versatel.de [62.214.110.241]

17 345 ms 344 ms 342 ms 62.214.108.222

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.


Tracing route to 62.214.177.77 on port 8767
Over a maximum of 30 hops.
1 4 ms 4 ms 4 ms 192.168.1.253 [DD-WRT]
2 6 ms 4 ms 4 ms 10.0.0.138
3 100 ms 23 ms 25 ms 124.254.72.19 [lns02.ispone.net.au]
4 25 ms 23 ms 23 ms 124.254.72.129 [lns.gw.ispone.net.au]
5 25 ms 25 ms 23 ms 203.192.136.229 [IOP-0002.gw2.mel1.asianetcom.net]
6 39 ms 38 ms 38 ms 202.147.42.125 [ge-1-2-0-949.gw4.syd1.asianetcom.net]
7 37 ms 35 ms 37 ms 202.147.40.165 [gi3-2.cr1.syd1.asianetcom.net]
8 185 ms 266 ms 184 ms 202.147.55.82 [po2-2-0.gw3.lax1.asianetcom.net]
9 188 ms 184 ms 186 ms 77.67.69.89 [ge-2-0-0-207.ip.tiscali.net]
10 336 ms 336 ms 371 ms 89.149.186.118 [so-3-1-0.fra44.ip.tiscali.net]
11 407 ms 463 ms 364 ms 213.200.86.2 [fra20isp6.versatel.de]
12 350 ms 354 ms 342 ms 62.214.110.145 [10g-8-4.dor002isp006.versatel.de]
13 342 ms 342 ms 342 ms 62.214.110.134 [10ge-9-4.dor002isp005.versatel.de]
14 346 ms 410 ms 412 ms 62.214.110.249 [10g-9-1.rec001isp005.versatel.de]
15 342 ms 344 ms 342 ms 62.214.110.245
16 344 ms 346 ms 346 ms 62.214.110.241 [10g-9-1.esn001isp006.versatel.de]
17 348 ms 346 ms 344 ms 62.214.108.222
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.

Tomas
01-07-2009, 13:35
yop it should be exactly as suspected.

12 339 ms 341 ms 341 ms 10g-8-4.dor002isp006.versatel.de [62.214.110.145]
13 339 ms 339 ms 341 ms 10ge-9-4.dor002isp005.versatel.de [62.214.110.134]
14 463 ms 384 ms 475 ms 10g-9-1.rec001isp005.versatel.de [62.214.110.249]
15 344 ms 344 ms 341 ms 62.214.110.245
16 342 ms 344 ms 345 ms 10g-9-1.esn001isp006.versatel.de [62.214.110.241]
17 345 ms 344 ms 342 ms 62.214.108.222
18 * * * Request timed out.
....

correct/healthy
16 138 ms 177 ms 62 ms 10g-8-4.dor002isp006.versatel.de [62.214.110.145]
17 91 ms 42 ms 41 ms 10ge-9-4.dor002isp005.versatel.de [62.214.110.134]
18 47 ms 47 ms 46 ms 10g-9-1.rec001isp005.versatel.de [62.214.110.249]
19 61 ms 202 ms 208 ms 62.214.110.245
20 46 ms 46 ms 46 ms 10g-9-1.esn001isp006.versatel.de [62.214.110.241]
21 47 ms 46 ms 46 ms 62.214.34.118
22 44 ms 44 ms 44 ms 212.7.158.38
23 45 ms 44 ms 44 ms 62.214.177.37
24 48 ms 48 ms 47 ms 62.214.177.77
trace complete
ok for you in short(I got lots of complains that I am advanced for this comunity all the time):
talk_to/message your teamspeak server admins. tell them that you cant connect and also your packets are dropped on way to teamspeak server. Tell them that it is most likely problem at their ISP. send them(or your boyfried) your internet IP/IPs(www.whatismyip.com) where it doesnt work with request that they will ping and tracert you back FROM SERVER.
mail / links above(in my post) too
its just that someone there might did mistake