Teamspeak help

ImmortalZ · Post by **ImmortalZ** » Mon Jul 21, 2008 6:25 pm

You and Mesial have the same problem - your ISP is blocking access. There is no other way the trace can stop at hop 2 and be the server's fault unless you are connected to the same router as aarm's server.

rockraider · Post by **rockraider** » Mon Jul 21, 2008 6:36 pm

It has worked in the past...is there anything I can do to fix this?

ImmortalZ · Post by **ImmortalZ** » Tue Jul 22, 2008 8:48 am

Call up your ISP.

guitarism · Post by **guitarism** » Tue Jul 22, 2008 11:23 am

and now it's back to not working?

Post by **FreeBeer** » Tue Jul 22, 2008 12:17 pm

I can confirm that.. just tried it and I could not connect.

mr_e · Post by **mr_e** » Tue Jul 22, 2008 3:50 pm

Just tried it and I can connect.

Grimmwolf_GB · Post by **Grimmwolf_GB** » Tue Jul 22, 2008 4:53 pm

Tried it as well and it works just fine.

guitarism · Post by **guitarism** » Tue Jul 22, 2008 9:24 pm

I don't know what aarm did from sunday to monday, but its back to being unconnectable.

badpazzword · Post by **badpazzword** » Tue Jul 22, 2008 10:06 pm

badp@bPortatile:~$ tracepath 72.36.154.122
1: bPortatile.local (192.168.0.2) 0.233ms pmtu 1500
1: 192.168.0.1 (192.168.0.1) 5.035ms
1: 192.168.0.1 (192.168.0.1) 1.600ms
2: no reply
3: no reply
4: no reply
5: no reply
6: no reply
7: no reply
8: no reply
9: no reply
10: no reply

I can connect though.

D-boy · Post by **D-boy** » Tue Jul 22, 2008 10:52 pm

I missed the window when it was working, so I don't know if that fixed it for me. But it is still borked here.