TeamSpeak Issue?

[Paul Mawson 1297619]

Hello,

 

Is there currently an issue with the TeamSpeak server as I am unable to connect?

 

I could connect perfectly fine yesterday but I have tried numerous times today without any success.

 

Is anyone else having the same issue?

 

Thanks.

[Bradley Grafelman]

Worked fine for me just now, and several other users are connected as well (the longest is going on 5 hours).

 

EDIT: What error(s) does the TeamSpeak client give you?

[Paul Mawson 1297619]

This is what I have had my last tries:

 

<14:31:26> Trying to resolve hostname ts.vatsim-uk.co.uk

<14:31:31> Trying to connect to server on ts.vatsim-uk.co.uk

<14:31:36> Failed to connect to server

<14:50:52> Trying to resolve hostname ts.vatsim-uk.co.uk

<14:50:56> Trying to connect to server on ts.vatsim-uk.co.uk

<14:51:01> Failed to connect to server

<15:09:55> Trying to resolve hostname ts.vatsim-uk.co.uk

<15:09:59> Trying to connect to server on ts.vatsim-uk.co.uk

<15:10:04> Failed to connect to server

[Bradley Grafelman]

Strange. Can you try pinging the TS server address from a command prompt? Here's what I get (don't mind the latency/TTL; I'm on the other side of the pond ):

 

Pinging ts.vatsim-uk.co.uk [109.169.48.150] with 32 bytes of data:
Reply from 109.169.48.150: bytes=32 time=141ms TTL=40
Reply from 109.169.48.150: bytes=32 time=153ms TTL=40
Reply from 109.169.48.150: bytes=32 time=138ms TTL=40
Reply from 109.169.48.150: bytes=32 time=138ms TTL=40

 

Looks like all is well as far as I can see, so it sounds like it's either a local network issue with you or your ISP (or somewhere between your ISP and the TS server itself).

[Paul Mawson 1297619]

Pinged it and got this back

 

ping ts.vatsim-uk.co.uk

PING ts.vatsim-uk.co.uk (109.169.48.150): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

Request timeout for icmp_seq 4

Request timeout for icmp_seq 5

 

I can connect to other TS servers just not this one

[Bradley Grafelman]

You could try to get a little more information by doing a tracert/traceroute/mtr/etc. to see where the trail goes cold. Here's the last few hops from my end:

 

 16   154 ms   160 ms   142 ms  ldn-b3-link.telia.net [213.155.136.203]
17   201 ms   144 ms   232 ms  iomart-ic-154087-ldn-b3.c.telia.net [80.239.195.134]
18   135 ms   135 ms   135 ms  610.net2.north.dc5.as20860.net [62.233.127.182]
19   147 ms   156 ms   139 ms  87.117.212.38
20   145 ms   223 ms   185 ms  109.169.48.150

 

I'm out of ideas/guesses... best of luck to you.