Ok. I turned the SPI Firewall Protection to off. That still came up with the same error. So I desided to restart the router and it still comes up with the same error.
Should I try calling my ISP tomorrow like Numma_Cway suggested?
thanks,
IamKZ
We are migrating towards a new forum system located at community.teamspeak.com, as such this forum will become read-only on January 29, 2020
Ok. I turned the SPI Firewall Protection to off. That still came up with the same error. So I desided to restart the router and it still comes up with the same error.
Should I try calling my ISP tomorrow like Numma_Cway suggested?
thanks,
IamKZ
:O!
voice.teamspeak.com:9988 works!
what does that mean o,o
It's that numma_cway said in his post, #12:
http://forum.teamspeak.com/showthrea...426#post394426
You have checked thatYou might want to check if it only affects servers on certain/default (9987) ports. Because DNSs can resolve into a non-default port via SRV, please check your log if the port is default. If it only affects the default port, please ask your ISP about their internet censorship.
voice.teamspeak.com:9987 --> that meants voice.teamspeak.com --> you can't connect
voice.teamspeak.com:9988 --> you connect to.
So, it seems that your ISP could have some kind of "filtering" for UDP traffic for destination port 9987.
Verify, one more time, that
voice.teamspeak.com:9987 fails
and
voice.teamspeak.com:9988 works
and try to contact your ISP about this.
Ok so.
voice.teamspeak.com:9987 fails
but
voice.teamspeak.com:9988 works
So I will call my ISP asap
There are currently 1 users browsing this thread. (0 members and 1 guests)