cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Beginner
566 Views
Message 11 of 18

Re: TS3 Connection Issues tracert

Go to solution

@fluffyman24 wrote:

 

This is what apears.


That says to me you should be able to connect. It's just number 1 & 2 that I think is causing your problem. Unfortunately I don't know how to fix this.

CMD Tracert

 

This is what mine looks like.

0 Ratings
Highlighted
Newbie
532 Views
Message 12 of 18

Re: TS3 Connection Issues tracert

Go to solution

i cant connect aswell this is mine...
cMGqACJ.png

0 Ratings
Highlighted
Beginner
491 Views
Message 13 of 18

Re: TS3 Connection Issues tracert

Go to solution

kkingcobra this is pretty much exactly what is happening to me. Like I said in my origional post, I can connect to other servers just not my own. I'll try phoning BT today.

0 Ratings
Highlighted
Contributor
465 Views
Message 14 of 18

Re: TS3 Connection Issues tracert

Go to solution

https://community.bt.com/t5/Other-Broadband-Queries/Multiplay-Teamspeak-3-Blocked/td-p/1321931

 

Someone from Multiplay has posted in that thread regarding this issue they are aware of.

0 Ratings
Highlighted
Expert
449 Views
Message 15 of 18

Re: TS3 Connection Issues tracert

Go to solution

@He-Man wrote:

https://community.bt.com/t5/Other-Broadband-Queries/Multiplay-Teamspeak-3-Blocked/td-p/1321931

 

Someone from Multiplay has posted in that thread regarding this issue they are aware of.


I'm able to return half-decent traceroutes to both of those IPs, but they don't like being traced by their names. Smiley Frustrated

Also, what I've noticed is the traceroutes take an age to complete, regardless of the timings measured.

Last login: Mon Jul 21 15:59:44 on ttys000
DS9:~ kev$ traceroute -I 85.236.100.96
traceroute to 85.236.100.96 (85.236.100.96), 64 hops max, 72 byte packets
 1  192.168.1.1 (192.168.1.1)  0.485 ms  0.176 ms  0.172 ms
 2  217.32.146.68 (217.32.146.68)  5.040 ms  5.175 ms  4.950 ms
 3  217.32.146.94 (217.32.146.94)  5.242 ms  5.416 ms  5.221 ms
 4  217.32.147.194 (217.32.147.194)  5.769 ms  6.118 ms  5.684 ms
 5  217.41.168.61 (217.41.168.61)  5.736 ms  5.887 ms  5.723 ms
 6  217.41.168.107 (217.41.168.107)  5.981 ms  6.153 ms  6.965 ms
 7  acc1-te0-0-0-21.l-far.21cn-ipp.bt.net (109.159.249.94)  5.968 ms  6.028 ms  5.673 ms
 8  core4-te0-10-0-26.faraday.ukcore.bt.net (109.159.255.197)  6.321 ms  6.092 ms  5.908 ms
 9  peer4-te0-5-0-11.telehouse.ukcore.bt.net (109.159.255.111)  13.004 ms  10.540 ms  7.970 ms
10  194.74.65.58 (194.74.65.58)  6.978 ms  6.831 ms  6.704 ms
11  te0-0-2-0.telehouse-north.core.enta.net (188.39.127.127)  6.760 ms  6.968 ms  6.956 ms
12  te5-2.gs1.core.enta.net (188.39.127.71)  7.018 ms  7.189 ms  6.970 ms
13  te1-1.interxion.core.enta.net (188.39.127.72)  6.750 ms  6.548 ms  6.478 ms
14  gi4-3.enta-transit.as35028.net (84.45.252.122)  6.681 ms  6.627 ms  6.725 ms
15  quad32.multiplay.co.uk (85.236.100.96)  6.443 ms  6.547 ms  6.683 ms
DS9:~ kev$ traceroute -I 85.236.100.98
traceroute to 85.236.100.98 (85.236.100.98), 64 hops max, 72 byte packets
 1  192.168.1.1 (192.168.1.1)  0.448 ms  0.181 ms  0.149 ms
 2  217.32.146.68 (217.32.146.68)  5.052 ms  5.117 ms  4.954 ms
 3  217.32.146.94 (217.32.146.94)  5.223 ms  5.284 ms  5.210 ms
 4  217.32.147.234 (217.32.147.234)  5.985 ms  6.009 ms  5.925 ms
 5  217.41.168.61 (217.41.168.61)  5.950 ms  5.649 ms  5.484 ms
 6  217.41.168.107 (217.41.168.107)  5.676 ms  6.027 ms  5.754 ms
 7  acc1-10gige-0-2-0-6.l-far.21cn-ipp.bt.net (109.159.249.101)  5.992 ms  5.932 ms  5.742 ms
 8  core3-te0-10-0-26.faraday.ukcore.bt.net (109.159.249.53)  5.770 ms  7.222 ms  5.918 ms
 9  62.6.201.217 (62.6.201.217)  14.549 ms  9.763 ms  7.973 ms
10  194.74.65.58 (194.74.65.58)  6.710 ms  6.543 ms  6.725 ms
11  te0-0-2-0.telehouse-north.core.enta.net (188.39.127.127)  7.047 ms  6.878 ms  6.980 ms
12  te5-2.gs1.core.enta.net (188.39.127.71)  6.712 ms  6.737 ms  6.807 ms
13  te1-1.interxion.core.enta.net (188.39.127.72)  6.380 ms  6.326 ms  6.761 ms
14  gi4-3.enta-transit.as35028.net (84.45.252.122)  12.448 ms  42.903 ms  6.409 ms
15  dedicated28.multiplay.co.uk (85.236.100.98)  6.761 ms  7.200 ms  7.069 ms
DS9:~ kev$ 

 

0 Ratings
Highlighted
Community Manager
Community Manager
412 Views
Message 16 of 18

Re: TS3 Connection Issues tracert

Go to solution

Hi Guys,

 

Thanks for all the comments and sorry for the problem you are having.

 

Our tech teams are investigating however we don't believe this is an issue on BT's side of things.  We are however working with the Multiplay teams.

 

TDU222 - I note that you have written that you are no longer experiencing this issue.  Is that still the case?

 

Is anyone else that experienced this problem still having issues?

 

Cheers

Sean

0 Ratings
Highlighted
Beginner
400 Views
Message 17 of 18

Re: TS3 Connection Issues tracert

Go to solution
Hi guys, the above is correct. The issue appears to be a reverse path fault between BT and Multiplay, this is caused by a network in between the two rather than networks operated by either company.

We're working closely with BT to resolve the issue, if anyone is experiencing further problems please submit a ticket to support.multiplay.co.uk to let us know and help solve any new issues as quickly as possible.

Thanks!
Skitrel/Jason Page
Community Manager at Multiplay
0 Ratings
Highlighted
Beginner
361 Views
Message 18 of 18

Re: TS3 Connection Issues tracert

Go to solution

SeanD, sorry it has taken me so long to respong, I haven't checked the post in a few days. You are correct I am no longer experiencing the problem. I've got a bit of information to add though before I close this post. I have recently met some people that have BT internet/fibre, they own a 'Mumble' server and at the same time as me, they couldn't connect to it. But at the same time I was able to reconnect so were they. I'm not sure if this will help and I'm not sure if the mumble server was provided by Multiplay.

For the future maybe if this probem happens again it's worth getting people to the the tracert thing because that's how I first knew that A. I couldn't connect to the serve.r And B.I kenw when I could connect to the server. This also helped me find  at which IP the request (trace) went AWOL. 

 

Thanks all for the Help

Ben

0 Ratings