Forum


Notice to all users

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

Page 2 of 2 FirstFirst 12
Results 16 to 20 of 20
  1. #16
    Join Date
    October 2014
    Posts
    10
    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

  2. #17
    Join Date
    January 2010
    Location
    El Prat de Llobregat (Barcelona, Spain)
    Posts
    2,698
    Quote Originally Posted by iamkz View Post
    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?
    Yes, you should.

    And, a last try. Try to connect to voice.teamspeak.com:9988
    Same result??

  3. #18
    Join Date
    October 2014
    Posts
    10
    :O!

    voice.teamspeak.com:9988 works!

    what does that mean o,o

  4. #19
    Join Date
    January 2010
    Location
    El Prat de Llobregat (Barcelona, Spain)
    Posts
    2,698
    Quote Originally Posted by iamkz View Post
    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 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.
    You have checked that
    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.

  5. #20
    Join Date
    October 2014
    Posts
    10
    Ok so.

    voice.teamspeak.com:9987 fails
    but
    voice.teamspeak.com:9988 works

    So I will call my ISP asap

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. can't connect to certain Teamspeak servers
    By bozza72 in forum Windows
    Replies: 0
    Last Post: September 4th, 2015, 06:21 AM
  2. Replies: 3
    Last Post: June 7th, 2015, 08:46 PM
  3. Replies: 10
    Last Post: September 11th, 2014, 08:43 PM
  4. Cant connect to *any teamspeak servers
    By Lumpy_Stew in forum Windows
    Replies: 4
    Last Post: July 16th, 2011, 11:26 PM

Tags for this Thread

Posting Permissions

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