Cannot bind to some ports due to permission denied

Question

For the last 3 months or so I\'m having random errors where I can\'t bind a specific port where our Identity server is running on my local development workstation. At first

Answer 1

When I looked for it, the explanation was

An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST).

Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4.0 with SP4 and later), another application, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4.0 with SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option.

Answer 2

Expanding on the selected answer: if you have Hyper-V enabled, you can temporarily disable it during boot by using bcdedit:

bcdedit /Set {current} hypervisorlaunchtype off

Restart and exclude the necessary ports via:

netsh int ipv4 add excludedportrange protocol=tcp startport=<your port> numberofports=1

Then simply re-enable Hyper-V, then restart:

bcdedit /Set {current} hypervisorlaunchtype auto

This prevents having to completely remove and re-add the Hyper-V feature, which requires several restarts.

Answer 3

If you face this issue on Win10 2004 that's because of of an issue in this update do the following

netsh int ipv[46] set dynamic tcp start=49152 num=16384

reg add HKLM\SYSTEM\CurrentControlSet\Services\hns\State /v EnableExcludedPortRange /d 0 /f

I face this on opening Jetbrains IDEs and and many other program that use sockets

Answer 4

The reason is that Hyper-V takes over these ports, to prevent it from happening do the following:

1. dism.exe /Online /Disable-Feature:Microsoft-Hyper-V (will have to restart)
2. netsh int ipv4 add excludedportrange protocol=tcp startport=<your port> numberofports=1
3. dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All

The original solution is here.

If after that you still can't bind to the port do the following:

• netsh http add iplisten 0.0.0.0 for IPv4
• netsh http add iplisten :: for IPv6

More information is here.

Answer 5

A faulty Windows upgrade is the reason for the problems with reserved tcp ports. See https://github.com/docker/for-win/issues/3171#issuecomment-554587817

With this the problem should be fixed: netsh int ipv4 set dynamic tcp start=49152 num=16384

That would explain why a clean install fixes these type of problems.

Answer 6

In case someone lands up here after facing similar issues post updating Windows to May 2020 update which contains WSL2. In my case I also switched docker to WSL2 post which I started facing similar issues with some of my containers.

Note: Run the following commands in powershell (Run as administrator)

1. Disable Hyper-V.

   dism.exe /Online /Disable-Feature:Microsoft-Hyper-V

2. Remove all hyper-v related network adapters.

   Get-HNSNetwork | Remove-HNSNetwork

3. Reboot.