Teamspeak 3 Server Was Working, now it isn't

[htwingnut]

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!

 

[htwingnut]

OMFG!

Sheesh! I just renamed the .exe to something else, added the new file to the firewall and BAM, it worked. Curious wtf 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?

 

[Mushkins]

OMFG!

Sheesh! I just renamed the .exe to something else, added the new file to the firewall and BAM, it worked. Curious wtf 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?

Comcast can't block it based on filename. 99%, what happened was the updated server exe was returning a different enough signature that the firewall was denying access, and since there wasnt an active connection it didnt prompt you to allow it through. Removing the firewall exception and re-adding it made the signatures match and properly identifies the program so it can let it through.

Windows firewall is way better than nothing, but its far from perfect

 

[John Connor]

I have TS3 server running on a thin client and recently upgraded the client and still could log in. On the thin client I log in with 127.0.0.1. I have a domain name with an update client on the thin client so when I change the IP address the domain name updates. The fire wall I use is private fire wall.