The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Teamspeak 3 Server Was Working, now it isn't

    Discussion in 'Networking and Wireless' started by HTWingNut, Aug 9, 2013.

  1. HTWingNut

    HTWingNut Potato

    Reputations:
    21,580
    Messages:
    35,370
    Likes Received:
    9,877
    Trophy Points:
    931
    I have had a TS3 server running on my home server for some time. No issues. Using default ports: TDP: 10011, 30033 / UDP: 9987.

    Using latest Server: 3.0.7.2
    Using latest Client: 3.0.11.1

    I recently upgraded about a month ago to an Asus RT-AC66U router, but TeamSpeak still worked once I opened up the same ports on the TS3 Server.

    Just today, TS3 Client asked me to update. I did, and tried to connect and it didn't work. I thought it was client/server incompatibility, but I haven't tried to connect to TS3 server for a few days, so it may have been this way for a few days, although nothing has changed in the last few days in my setups.

    Things I have tried:
    - Turned off Windows Firewall on my home server
    - Turned on DMZ for my home server
    - Removed all TS3 entries from Firewall and created new entries
    - Started a whole new TS3 server
    - Opened UDP port 9987 in Windows Firewall on server
    - Tried a few different ports (opening ports in router and firewall): 9989, 9999, 12345
    - Powered down and Reset the router, modem, all switches
    - Connected to server through LAN just fine

    Ports are open for TDP 10011 and 30033, but the server is still not recognizing the UDP voice port.

    Log says:

    2013-08-09 23:28:40.980642|INFO |VirtualServer | 1| listening on 0.0.0.0:9987

    So I know to use that port, but it clearly isn't listening!

    I have other services like my Windows Home Server, Minecraft, Slingbox, Trackmania, all that make their way through the router just fine too.

    Could Comcast somehow be blocking it? But then again I tried other ports and it still wasn't working.

    HELP!

    HELP!

    !

    EDIT: Sheesh! I just renamed the .exe to something else, added the new file to the firewall and BAM, it worked. Curious is up with that? I opened DMZ and turned off firewall and it still wouldn't work.

    Do you think Comcast could block it based on filename or something?

    EDIT2: Well that was short lived now it can't connect again. GAAAAAA!
     
    HTWingNut, Aug 9, 2013
    #1
  2. downloads

    downloads No, Dee Dee, no! Super Moderator

    Reputations:
    7,729
    Messages:
    8,722
    Likes Received:
    2,230
    Trophy Points:
    331
    No. They wouldn't know the file name. They could block it based on port or protocol but that's not the case since renaming worked.
     
    downloads, Aug 9, 2013
    #2
  3. HTWingNut

    HTWingNut Potato

    Reputations:
    21,580
    Messages:
    35,370
    Likes Received:
    9,877
    Trophy Points:
    931
    It's working again. Don't know what the heck is going on. As long as it stays working.
     
    HTWingNut, Aug 10, 2013
    #3