Forum

Results 1 to 7 of 7
  1. #1
    Join Date
    May 2016
    Posts
    4

    Cannot connect to a certain ts3 server

    One day I was in the server then all of a sudden I got disconnected from it and could not get back in. I can get onto any server but this certain one. I checked with friends and I am not blacklisted as it says this on the client log. I've tried resetting my router, trying a different one, basically anything I could to try and get back in.

    6/8/2016 22:00:46 Windows Audio Session Devel DeviceDeleteList::waitForDeletes - enter
    6/8/2016 22:00:46 Windows Audio Session Devel DeviceDeleteList::waitForDeletes - leave
    6/8/2016 22:00:47 ClientUI Info Connect to server: ts.thunderr.net
    6/8/2016 22:00:47 ClientUI Info Trying to resolve ts.thunderr.net
    6/8/2016 22:00:47 TSDNS Info SRV DNS resolve successful, "_ts3._udp.ts.thunderr.net"=>"104.223.1.73:998 7" = 104.223.1.73:9987
    6/8/2016 22:00:47 TSDNS Info DNS resolve successful, "ts.thunderr.net"=185.28.20.184
    6/8/2016 22:00:47 ClientUI Info Lookup finished: 104.223.1.73 9987 ts.thunderr.net 0 0
    6/8/2016 22:00:47 ClientUI Info Resolve successful: 104.223.1.73:9987
    6/8/2016 22:00:47 ClientUI Info Blacklist check ok
    6/8/2016 22:00:47 ClientUI Info Initiating connection: 104.223.1.73:9987 ts.thunderr.net
    6/8/2016 22:00:47 Windows Audio Session Devel DeviceDeleteList::waitForDeletes - enter
    6/8/2016 22:00:47 Windows Audio Session Devel DeviceDeleteList::waitForDeletes - leave
    6/8/2016 22:00:47 ClientUI Info Connect status: Connecting
    6/8/2016 22:00:52 ClientUI Info Connect status: Disconnected
    6/8/2016 22:00:52 ClientUI Info Failed to connect to server, want autoreconnect = 0


    Any help with this issue would be greatly appreciated.

  2. #2
    Join Date
    January 2013
    Location
    Thüringen
    Posts
    329
    Try without the TSDNS.

  3. #3
    Join Date
    May 2016
    Posts
    4
    Don't suppose you could tell me how? New to Teamspeak in general.

  4. #4
    Join Date
    January 2013
    Location
    Thüringen
    Posts
    329
    Quote Originally Posted by yoshi263 View Post
    Don't suppose you could tell me how? New to Teamspeak in general.
    Go to: Connections --->
    With the normal IP: 104.xxx.1.xxx:9987

  5. #5
    Join Date
    May 2016
    Posts
    4
    Didn't work I'm afraid.

    6/11/2016 04:13:32 ClientUI Info Initiating connection: 104.223.1.73:9987 104.223.1.73
    6/11/2016 04:13:32 Windows Audio Session Devel DeviceDeleteList::waitForDeletes - enter
    6/11/2016 04:13:32 Windows Audio Session Devel DeviceDeleteList::waitForDeletes - leave
    6/11/2016 04:13:32 Windows Audio Session Debug WAS:penDevice-enter
    6/11/2016 04:13:32 Windows Audio Session Debug WAS Buffer size: 960
    6/11/2016 04:13:32 Windows Audio Session Debug WAS:penDevice-leave
    6/11/2016 04:13:32 Windows Audio Session Debug WAS::startDevice-enter
    6/11/2016 04:13:32 Windows Audio Session Debug WAS::startDevice-leave
    6/11/2016 04:13:32 Windows Audio Session Devel DeviceDeleteList::waitForDeletes - enter
    6/11/2016 04:13:32 Windows Audio Session Devel DeviceDeleteList::waitForDeletes - leave
    6/11/2016 04:13:32 Windows Audio Session Debug WAS:penDevice-enter
    6/11/2016 04:13:32 Windows Audio Session Debug WAS Buffer size: 960
    6/11/2016 04:13:32 Windows Audio Session Debug WAS:penDevice-leave
    6/11/2016 04:13:32 PreProSpeex Info Speex version: speex-1.2beta3
    6/11/2016 04:13:32 Windows Audio Session Debug WAS::startDevice-enter
    6/11/2016 04:13:32 Windows Audio Session Debug WAS::startDevice-leave
    6/11/2016 04:13:32 ClientUI Info Connect status: Connecting
    6/11/2016 04:13:37 ClientUI Info Connect status: Disconnected
    6/11/2016 04:13:37 ClientUI Info Failed to connect to server, want autoreconnect = 0

  6. #6
    Join Date
    January 2010
    Location
    El Prat de Llobregat (Barcelona, Spain)
    Posts
    2,698
    Quote Originally Posted by yoshi263 View Post
    Didn't work I'm afraid.

    6/11/2016 04:13:32 ClientUI Info Initiating connection: 104.223.1.73:9987 104.223.1.73
    It seems the resolved address and port are correct. So, verify you can ping and reach the final IP from your computer, using PING and TRACERT. Here the results from my side:

    Code:
    Microsoft Windows [Versión 6.0.6002]
    Copyright (c) 2006 Microsoft Corporation.  Reservados todos los derechos.
    
    C:\Users\PotaBlava>ping 104.223.1.73
    
    Haciendo ping a 104.223.1.73 con 32 bytes de datos:
    Respuesta desde 104.223.1.73: bytes=32 tiempo=210ms TTL=51
    Respuesta desde 104.223.1.73: bytes=32 tiempo=203ms TTL=51
    Respuesta desde 104.223.1.73: bytes=32 tiempo=203ms TTL=51
    Respuesta desde 104.223.1.73: bytes=32 tiempo=211ms TTL=51
    
    Estadísticas de ping para 104.223.1.73:
        Paquetes: enviados = 4, recibidos = 4, perdidos = 0
        (0% perdidos),
    Tiempos aproximados de ida y vuelta en milisegundos:
        Mínimo = 203ms, Máximo = 211ms, Media = 206ms
    
    
    
    C:\Users\PotaBlava>tracert 104.223.1.73
    
    Traza a la dirección 104.223.1.73.static.quadranet.com [104.223.1.73]
    sobre un máximo de 30 saltos:
    
      1    10 ms     7 ms     3 ms  192.168.1.1
      2    67 ms    33 ms    33 ms  192.168.144.1
      3    33 ms    35 ms    34 ms  57.red-81-46-71.customer.static.ccgg.telefonica.net [81.46.71.57]
      4    33 ms    39 ms    35 ms  46.red-80-58-81.staticip.rima-tde.net [80.58.81.46]
      5    35 ms    48 ms    33 ms  et3-0-0-400-grtbcntb1.net.telefonicaglobalsolutions.com [94.142.103.177]
      6    51 ms    50 ms    51 ms  xe1-1-4-0-grtpareq2.net.telefonicaglobalsolutions.com [94.142.121.41]
      7    51 ms    51 ms    51 ms  prs-b8-link.telia.net [80.239.195.193]
      8   141 ms    56 ms    56 ms  prs-bb2-link.telia.net [62.115.118.46]
      9   141 ms   171 ms   128 ms  nyk-bb2-link.telia.net [80.91.253.126]
     10   202 ms   215 ms   202 ms  las-b3-link.telia.net [62.115.116.96]
     11   208 ms   165 ms   170 ms  dls-b21-link.telia.net [80.91.248.209]
     12   225 ms   199 ms   211 ms  colo-lax9.as8100.net [96.44.180.6]
     13   214 ms   210 ms   200 ms  las-b3-link.telia.net [62.115.116.168]
     14   209 ms   212 ms   203 ms  104.223.1.73.static.quadranet.com [104.223.1.73]
    
    Traza completa.

  7. #7
    Join Date
    May 2016
    Posts
    4
    The TRACERT looks fine to me, still don't have any idea.


    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\Craig>ping ts.thunderr.net

    Pinging ts.thunderr.net [185.28.20.184] with 32 bytes of data:
    Reply from 185.28.20.184: bytes=32 time=168ms TTL=44
    Reply from 185.28.20.184: bytes=32 time=147ms TTL=44
    Reply from 185.28.20.184: bytes=32 time=174ms TTL=44
    Reply from 185.28.20.184: bytes=32 time=161ms TTL=44

    Ping statistics for 185.28.20.184:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 147ms, Maximum = 174ms, Average = 162ms

    C:\Users\Craig>tracert ts.thunderr.net

    Tracing route to ts.thunderr.net [185.28.20.184]
    over a maximum of 30 hops:

    1 27 ms 19 ms 20 ms blackstock-vl4000.vianet.ca [74.119.90.1]
    2 14 ms 14 ms 26 ms 24-138-126-13.vianet.ca [24.138.126.13]
    3 20 ms 15 ms 19 ms marshhill-g1-0-7.vianet.ca [24.138.126.38]
    4 18 ms 19 ms 19 ms marshhill-north-g0-3.vianet.ca [24.138.126.42]
    5 66 ms 54 ms 44 ms 24-138-127-85.vianet.ca [24.138.127.85]
    6 * 35 ms 58 ms 10.10.12.89
    7 49 ms 37 ms 54 ms 87.128.235.177
    8 72 ms 73 ms 43 ms nyc-sa3-i.NYC.US.NET.DTAG.DE [62.156.131.97]
    9 95 ms 66 ms 67 ms 193.159.164.86
    10 88 ms 63 ms 78 ms nyk-bb2-link.telia.net [213.155.135.78]
    11 130 ms 125 ms 134 ms ldn-bb2-link.telia.net [62.115.116.86]
    12 126 ms 147 ms 136 ms ldn-b1-link.telia.net [62.115.114.139]
    13 140 ms 144 ms 119 ms m247-ic-313694-ldn-b1.c.telia.net [213.248.104.1
    50]
    14 427 ms 164 ms 164 ms te-6-4-0.bb1.man2.uk.m247.com [193.27.65.166]
    15 128 ms 124 ms 119 ms te-5-1-0.core-dc1.man4.uk.m247.com [77.243.185.0
    ]
    16 198 ms 129 ms 125 ms 176.10.80.150
    17 159 ms 174 ms 140 ms 185.28.20.184

    Trace complete.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. [Resolved] Can't connect to a specific server (Failed to connect to server)
    By MightyB in forum Client Support
    Replies: 7
    Last Post: July 29th, 2015, 02:21 PM
  2. Replies: 0
    Last Post: March 28th, 2015, 09:42 PM
  3. Replies: 2
    Last Post: January 21st, 2014, 10:57 PM
  4. Replies: 1
    Last Post: August 31st, 2013, 03:47 AM
  5. Replies: 3
    Last Post: August 21st, 2010, 11:17 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •