I've been running an application which binds to port 50005 for quite some time and it seems that something changed recently and no application on my machine is able to bind to any TCP port above 49690 .. on 127.0.0.1.
Does anyone know when / what changed?
OS Name Microsoft Windows 10 Enterprise
Version 10.0.17763 Build 17763
The problem was related to this: https://support.microsoft.com/en-za/help/929851/the-default-dynamic-port-range-for-tcp-ip-has-changed-in-windows-vista
It seems the Windows reserves the bottom range of these dynamic ports. The only way I could free up the port, allowing any application to bind to port 50005 was to move the dynamic port range up a little.
After the below change and a reboot all applications were once again able to bind to the port.
It turned out the real problem was Docker.
netsh int ip show excludedportrange protocol=tcp
netsh int ip add excludedportrange protocol=tcp startport=50005 numberofports=2
https://github.com/docker/for-win/issues/3171
netsh int ipv4 show excludedportrange protocol=tcp
netsh int ip delete excludedportrange protocol=tcp startport=50005 numberofports=100
