Windows Server 2008 - unable to bind any TCP port

Posted by Kalphiter on Server Fault See other posts from Server Fault or by Kalphiter
Published on 2011-11-21T23:49:52Z Indexed on 2011/11/22 1:55 UTC
Read the original article Hit count: 450

Filed under:
|
|

OS: Win Server 2008 RC2 Windows firewall on (no effect when off)

I have suddenly been plagued by an issue in which I cannot find any similar ones with a search.

I am running about 20 game servers that bind to a UDP port, then bind to a TCP port 1 above the UDP port. Suddenly, a day ago, new TCP binds stopped functioning.

Now, I have confirmed that other applications cannot listen on most ports. For example, I have a java program that I made a copy of, and tried the following ports: 33001, 23789, 89... completely random ports.

As far as the applications already that have TCP bindings, such as HTTP and MySQL, only port 8080 was one port I discovered could work, and only for Apache. If applications would leave their default port they could not bind, however they returned to normal when the port was default.

I've checked for listening applications through netstat and curports, also checked for any connections on these ports, and they're completely free.

© Server Fault or respective owner

Related posts about Windows

Related posts about tcp