PLEASE help with connecting

[Yoda4u]

Friend of mine trying to get on Teamspeak3. He can get on all other servers but ours. He has uninstalled and reinstalled TS3 with no difference. Does anyone have a suggestion to fix this? our server is jedi.teamspeak3.com He says it keeps saying failed to connect, but he CAN get on other TS3 servers. Any help would be appreciated.


Yoda

[PotaBlava]

Friend of mine trying to get on Teamspeak3. He can get on all other servers but ours. He has uninstalled and reinstalled TS3 with no difference. Does anyone have a suggestion to fix this? our server is jedi.teamspeak3.com He says it keeps saying failed to connect, but he CAN get on other TS3 servers.

It seems to be a mess the connection to this server...

24/11/2013 18:36:09	ClientUI	Info	Connect to server: jedi.teamspeak3.com	
24/11/2013 18:36:09	ClientUI	Info	Trying to resolve jedi.teamspeak3.com	
24/11/2013 18:36:09	TSDNS	Info	DNS resolve successful, "jedi.teamspeak3.com"=216.127.64.25	
24/11/2013 18:36:09	TSDNS	Info	SRV DNS resolve successful, "_ts3._udp.jedi.teamspeak3.com"=>"ts106.light-speed.com:4572" = 216.127.64.25:4572	
24/11/2013 18:36:09	ClientUI	Info	Lookup finished: 216.127.64.25 4572 jedi.teamspeak3.com 0 0	
24/11/2013 18:36:09	ClientUI	Info	Resolve successful: 216.127.64.25:4572	
24/11/2013 18:36:09	ClientUI	Info	Blacklist check ok	
24/11/2013 18:36:09	ClientUI	Info	Initiating connection: 216.127.64.25:4572 jedi.teamspeak3.com	
24/11/2013 18:36:10	TSDNS	Info	TSDNS found at "jedi.teamspeak3.com" and queried successfully. Result: 216.127.64.25:4572	
24/11/2013 18:36:10	ClientUI	Info	Connect status: Connecting	
24/11/2013 18:36:10	PktHandler	Devel	Puzzle solve time: 21	
24/11/2013 18:36:11	ClientUI	Info	Connect status: Connected	
24/11/2013 18:36:11	ClientUI	Info	Connect status: Establishing connection	
24/11/2013 18:36:12	ClientUI	Info	Connect status: Connection established	
24/11/2013 18:36:12	PermManager	Info	Requesting permissions from server	
24/11/2013 18:36:12	TSDNS	Info	SRV TSDNS found at "_tsdns._tcp.teamspeak3.com"=>"tsdns.light-speed.com:80" and queried successfully. Result: 216.127.64.25:4572

There are three resolutions for the server, 2 different SRV records (cases 1 and 3) and a TSDNS Server entry (case 2):
1) 24/11/2013 18:36:09 TSDNS Info SRV DNS resolve successful, "_ts3._udp.jedi.teamspeak3.com"=>"ts106.light-speed.com:4572" = 216.127.64.25:4572

2) 24/11/2013 18:36:10 TSDNS Info TSDNS found at "jedi.teamspeak3.com" and queried successfully. Result: 216.127.64.25:4572

3) 24/11/2013 18:36:12 TSDNS Info SRV TSDNS found at "_tsdns._tcp.teamspeak3.com"=>"tsdns.light-speed.com:80" and queried successfully. Result: 216.127.64.25:4572

Your friend could try to connect one of these two alternatives:
a) ts106.light-speed.com:4572
b) 216.127.64.25:4572

And maybe someone with criteria better should order the confussion with the SRV Records and the TSDNS Server entry.

[Yoda4u]

Thanks for responding. I had the person try the 2 alternatives with no success. Im going to include his IP address here.
76.104.143.101

Im not a PC expert, so the options 1-2-3 mean very little to what I can do.

I appreciate any help on this.

Yoda

[PotaBlava]

Thanks for responding. I had the person try the 2 alternatives with no success.
Im not a PC expert, so the options 1-2-3 mean very little to what I can do.

Well, if you are an user then options 1-2-3 are not in your hands... it's an admin matter.

Is your friend connecting from home (personal network) or from a public/private network as university, college, "at work"?
Usually "public networks" have rules that block the connection.

I would try to connect using 216.127.64.25:4572
If it fail again, then
Tools --> Client log
and compare with mine

26/11/2013 8:25:12	ClientUI	Info	Connect to server: 216.127.64.25	
26/11/2013 8:25:12	ClientUI	Info	Blacklist check ok	
26/11/2013 8:25:12	ClientUI	Info	Initiating connection: 216.127.64.25:4572 216.127.64.25	
26/11/2013 8:25:12	ClientUI	Info	Connect status: Connecting	
26/11/2013 8:25:13	PktHandler	Devel	Puzzle solve time: 14	
26/11/2013 8:25:14	ClientUI	Info	Connect status: Connected	
26/11/2013 8:25:14	ClientUI	Info	Connect status: Establishing connection	
26/11/2013 8:25:14	ClientUI	Info	Connect status: Connection established	
26/11/2013 8:25:14	PermManager	Info	Requesting permissions from server	
26/11/2013 8:25:39	ClientUI	Info	Connect status: Disconnected	
26/11/2013 8:25:39	ClientUI	Info	Disconnected or forced to leave, want autoreconnect = 0	
26/11/2013 8:25:39	Bookmarks	Info	Disconnect, total time: 25 - 5094

The server IP answers to PING and is reached by TRACERT. Your friend could test both.

Microsoft Windows [Versión 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.

C:\Users\PotaBlava>ping 216.127.64.25

Haciendo ping a 216.127.64.25 con 32 bytes de datos:
Respuesta desde 216.127.64.25: bytes=32 tiempo=214ms TTL=46
Respuesta desde 216.127.64.25: bytes=32 tiempo=212ms TTL=46
Respuesta desde 216.127.64.25: bytes=32 tiempo=214ms TTL=46
Respuesta desde 216.127.64.25: bytes=32 tiempo=210ms TTL=46

Estadísticas de ping para 216.127.64.25:
    Paquetes: enviados = 4, recibidos = 4, perdidos = 0
    (0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
    Mínimo = 210ms, Máximo = 214ms, Media = 212ms

C:\Users\PotaBlava>tracert 216.127.64.25

Traza a 216.127.64.25 sobre caminos de 30 saltos como máximo.

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    49 ms    48 ms    47 ms  84-18-16-1.usul.arrakis.es [84.18.16.1]
  3    61 ms    62 ms    61 ms  84-18-0-238.usul.arrakis.es [84.18.0.238]
  4     *        *        *     Tiempo de espera agotado para esta solicitud.
  5    61 ms    60 ms    60 ms  t2c2-ge0-0-0.es-mad3.eu.bt.net [166.49.199.105]
  6    74 ms    74 ms    75 ms  t2c2-ge3-0-0.es-bar.eu.bt.net [166.49.195.138]
  7    74 ms    75 ms    74 ms  t2c1-ge6-2.es-bar.eu.bt.net [166.49.164.41]
  8   104 ms   105 ms   105 ms  t2c3-xe-11-0-0-0.nl-ams2.eu.bt.net [166.49.195.0]
  9   106 ms   104 ms   104 ms  t2c4-xe-1-3-1-1.nl-ams2.eu.bt.net [166.49.237.211]
 10   106 ms   106 ms   104 ms  xe-0-1-2.ams20.ip4.tinet.net [141.136.99.85]
 11   105 ms   105 ms   106 ms  xe-1-1-1.ams12.ip4.tinet.net [89.149.180.149]
 12     *        *        *     Tiempo de espera agotado para esta solicitud.
 13     *        *        *     Tiempo de espera agotado para esta solicitud.
 14   113 ms   113 ms   114 ms  . [72.8.181.50]
 15   187 ms   190 ms   186 ms  ae1.bbr02.eq01.wdc02.networklayer.com [50.97.18.214]
 16   174 ms   176 ms   175 ms  ae7.bbr01.eq01.wdc02.networklayer.com [173.192.18.194]
 17   201 ms   202 ms   201 ms  ae0.bbr01.tl01.atl01.networklayer.com [173.192.18.153]
 18   224 ms   225 ms   224 ms  ae13.bbr02.eq01.dal03.networklayer.com [173.192.18.134]
 19   215 ms   213 ms   215 ms  ae6.dar01.sr01.dal05.networklayer.com [50.97.18.195]
 20   236 ms   309 ms   231 ms  po1.fcr01.sr01.dal05.networklayer.com [173.192.118.131]
 21   223 ms   225 ms   226 ms  xe0-0-1.cr1.dal01.light-speed.com [50.22.63.227]
 22   214 ms   214 ms   215 ms  216.127.64.25

Traza completa.

Ping --> it has to get answer ('Respuesta') in time and statistics of 0% lost
Respuesta desde 216.127.64.25: bytes=32 tiempo=....

Tracert --> it has to reach or complete the final IP ('Traza completa') (The steps will differ from mine but at the end he should reach the final IP)
xx --- ms --- ms --- ms 216.127.64.25
Traza completa.