Unable to bind ports: Docker-for-Windows & Hyper-V excluding but not using important port ranges

[veqryn]

• I have tried with the latest version of my channel (Stable or Edge)
• I have uploaded Diagnostics
• Diagnostics ID: BB0297BB-C287-4F0B-A007-72B5F2D7BD72/20190102235413

Expected behavior

Be able to bind specific ports that I have always used.
Be able to specify which ports docker/hyperv exclude or use, and/or I expect that docker/hyper-v actually use the ports that it is excluding and that they show up in netstat -ano as being used or listened on.

Actual behavior

If I start a service that binds on port 50051 (it is a grpc service, and that is the traditional port used by grpc), it says:
listen tcp :50051: bind: An attempt was made to access a socket in a way forbidden by its access permissions.

Information

• Is it reproducible? Yes
• Is the problem new? Yes. My previous installation of docker for windows, from a year ago when I was on Windows 1709, didn't have this problem.
• Did the problem appear with an update? Yes, you could say that. I wiped my harddrive and started over with Windows 1809 and the latest version of Docker for Windows.
• Windows Version: Windows 10 Pro 1809 (Version 10.0.17763 Build 17763)
• Docker for Windows Version: 2.0.0.0-win81
• Docker version: 18.09.0

Steps to reproduce the behavior

MinGW 12:11:50 ~$ docker run -p 50051:50051 hello-world
C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: driver failed programming external connectivity on endpoint infallible_lehmann (906354afc8855cc38fc8ac3e9e5b0642c9470f48f99c48e188ed3c8cfe236c9e): Error starting userland proxy: Bind for 0.0.0.0:50051: unexpected error Permission denied.

My own investigation:

I was extremely confused by this problem, because I was able to bind other ports, such as 8080 or 60000, yet it did not appear that 50051 was in use by anything on my system.

Running netstat -ano shows nothing using 50051.

Running Get-NetTCPConnection in powershell with admin privileges shows nothing using 50051.

Even if I disconnect from the internet and disable both windows firewall and my antivirus, and run everything as admin, I still get the errors.

After hours of google searching, I found a command that showed what happened to 50051:

PS C:\WINDOWS\system32> netsh interface ipv4 show excludedportrange protocol=tcp

Protocol tcp Port Exclusion Ranges

Start Port    End Port
----------    --------
     49692       49791
     49792       49891
     49892       49991
     49992       50091
     50092       50191
     50214       50313
     50498       50597

* - Administered port exclusions.

It seems that 50051 is excluded (whatever that means?!), even though it isn't in use by anything.

After lots of trial and error, I discovered that Docker for Windows and Hyper-V are responsible for all of those excluded port ranges above.

It also seems like all those port ranges change or increase by 1 every time I reboot, so I suppose 450 reboots from now my problem will go away, maybe...

I have never had this problem, despite using docker for years now.

I run lots of containers and setups that other people at my company work on and rely on, so it is not feasible for me to be changing the ports around on them to work around this issue. (Other people use the kube templates and docker-compose, and some of them connect with other docker-compose networks, etc, and expect things on certain ports.)

When I try to delete that excluded port range, I get this, despite running the command as administrator:

PS C:\WINDOWS\system32> netsh interface ipv4 delete excludedportrange protocol=tcp startport=49992 numberofports=100
Access is denied.

[rramsden]

Solution in googlevr/gvr-unity-sdk#1002 works for me but not ideal

[veqryn]

That workaround does not work for me, unfortunately, despite having admin rights.

[enashed]

@veqryn the workaround worked for me, the steps are:

1. Disable hyper-v (which will required a couple of restarts)
   dism.exe /Online /Disable-Feature:Microsoft-Hyper-V

2. When you finish all the required restarts, reserve the port you want so hyper-v doesn't reserve it back
   netsh int ipv4 add excludedportrange protocol=tcp startport=50051 numberofports=1

3. Re-Enable hyper-V (which will require a couple of restart)
   dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All

when your system is back, you will be able to bind to that port successfully.

[docker-robott]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[veqryn]

/remove-lifecycle stale

[dozer75]

What's the status for this?

Today I had 100 of reservations which caused Skype for Business to stop working since it couldn't find any available ports. Uninstall docker/hyper-v/containers removed these reservations and Skype for Business had ports to work with again.

This is a critical error that should be focused on since it reserves so many ports that isn't in use. I can't uninstall docker/hyper-v/containers or similar workarounds each time I get problems with Skype for Business in conjunction with meetings.

[Sureiya]

This makes hyper-v unusable for me and most of my company.

[sbley]

@enashed Does your solution (disabling and re-enabling HyperV) have any side effects? Will my virtual switches and virtual machines still be there after applying your solution?

[sbley]

Answering myself: This actually does have side effects. It deletes your virtual switches. You should keep that in mind when applying this solution.

[ciprian-chichirita]

this issue is still present
/remove-lifecycle stale

[danidemi]

Hi guys, I've the same problem. This is really blocking me.

[tarikguney]

@enashed's answer worked for me perfectly! Thanks!

[vamseekm]

IntelliJ idea community edition doesn't start because it tries to bind first available the port in the range 6942-6991.

source: https://intellij-support.jetbrains.com/hc/en-us/community/posts/360004973960-Critical-Internal-Error-on-Startup-of-IntelliJ-IDEA-Cannot-Lock-System-Folders-

And following command shows this port range is reserved/blocked by hyper-v/docker-for-windows. Frankly I don't know whether it's because of docker or some other app.

netsh interface ipv4 show excludedportrange protocol=tcp

Protocol tcp Port Exclusion Ranges

Start Port End Port

---

  1583        1682
  1683        1782
  2480        2579
  4492        4591
  5357        5357
  5614        5713
  5834        5933
  5940        6039
  6045        6144
  6276        6375
  6491        6590
  6897        6996
  7003        7102
 28385       28385
 50000       50059     *

• • Administered port exclusions.

[eXtreme]

The "hns" service is very... greedy.

• I have a boot setup where I can boot windows without hyper-v enabled, so that I can use virtualbox
• If I boot "without hyper-v" the hns service starts, even when it says that autostart for that service is disabled
• That service reserves large port ranges preventing me from starting winnfsd service (used with virtualbox/vagrant vm), I have to stop hns, and hope that this time it does no reserve that port and boot the vm
• Even if i stop the service it starts after a few seconds, reserving this time a different range of ports
• Sometimes it reserves ports that are normally used for local web development, like 3000/5000 for nodejs
• Sometimes it reserves a port IntelliJ IDEA needs for starting

[cpietrzykowski]

This is /obviously/ not docker's problem (as best I can tell), it's probably not even hyperv's. Commenting here as this seems to be a frustrating and common end of journey for googlers. What follows is at least "one" of the resolutions/explanations.

On one of my machines the dynamic port range was not updated to the "new" start port, and I guess related to a resolved bug in windows has now "exposed" this as a serious problem (e.g.: I couldn't even bind to port 3000 for node dev -- access denied is I think a valid response, but it's not the typical "port in use" root cause).

Current dynamic port config:
> netsh int ipv[46] show dynamicport tcp

Unless you know you've mucked with these settings, and if it doesn't specify 49152 as "Start Port" and is set to 1025, it's not "current". I don't know if there is some kind of migration bug when they were patching this new value or what. Dynamic start port for udp was set correctly for example.

To set it to the current config:
> netsh int ipv[46] set dynamic tcp start=49152 num=16384

(Likely a reboot of your host is required.)

ref: https://support.microsoft.com/en-ca/help/929851/the-default-dynamic-port-range-for-tcp-ip-has-changed-in-windows-vista

While it's bizarre that I only just ran into this issue less than 4 hours ago -- been doing docker/node/go dev for the last few months straight, using docker edge, etc. This appears to have resolved my port exclusion issues (I have no large ranges of reserved ports below 50000 now, previously had 1000 port range exclusions all over the place.)

[snaeqe]

@crozone As a docker desktop end user, I'd like docker to take care that ports it is using are really useable for docker.
Whether this is by individually "liberating" ports for docker at the moment they are used in a dockerfile/docker-compose or randomly assigned, or if it is by ensuring to set the dynamic port mapping persistently or at least every time docker starts.
Or, at least include a link in the errormessage to sth like a knowledgebase article with explanations how to do that

[ReSpawN]

Also getting this problem. My RabbitMQ image could not bind to a random of 4 different ports. The winnat solution below worked

I fix this issue by running:

net stop winnat
net start winnat

But after that i have no internet in wsl

But as stated: no subsequent internet in WSL thus I can't monitor kube pods or whatever.
This problem occurs for me with the latest Docker and WSL.

[pmorch]

At the very least, docker should report an error that it can't get the ports it needs and not fail silently.

…

On Mon, Mar 13, 2023, 13:02 Mark Ernst ***@***.***> wrote: Also getting this problem. My RabbitMQ image could not bind to a random of 4 different ports. The winnat solution below worked I fix this issue by running: net stop winnat net start winnat But after that i have no internet in wsl But as stated: no subsequent internet in WSL thus I can't monitor kube pods or whatever. — Reply to this email directly, view it on GitHub <#3171 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABG4PEBGQEXVZCHVISW6TTW34EGDANCNFSM4GM6VP3A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ReSpawN]

@pmorch defenitly not silent, no. But there is a big red bar with the error up there though, which is enough for me to notice it. Still strange because the ports are open but claimed by WSL for some reason. Definite problem since the new WSL.

[pmorch]

@ReSpawN : Ok perhaps with the newest version it does show an error. I totally expect docker run to also show an error in the terminal. It didn't when I hit this.

Thankfully I don't use Windows any longer, so this is no longer an itch of mine.

[saadat99]

This bug gave me a lot of headaches for a year and I just found this issue. I had to disable Hyper-V every time I needed a program to work. Hyper-V is supposed to make development easier, not harder!

[Wolvverine]

Example solution:

netsh advfirewall firewall add rule name="TCP Port KMS 1688" dir=in action=allow protocol=TCP localport=1688
netsh int ipv4 set dynamicport tcp start=35001 num=30535
net stop winnat
net start winnat
netsh int ipv4 add excludedportrange protocol=tcp startport=1688 numberofports=1

[ReSpawN]

The net stop winnnat && net start winnat worked perfectly.

[ahbanavi]

The net stop winnnat && net start winnat worked perfectly.

but after that, i don't have access to internet in wsl.

[ReSpawN]

but after that, i don't have access to internet in wsl.

Weird, it worked for me? I havent had the problem since but I'll try and verify when it pops up again.

[geertschuring]

How is this still not solved.... very frustrating problem.

[ducpham01]

but after that, i don't have access to internet in wsl.

I'm having the same issue. But sometimes it says "The service is starting or stopping. Please try again later" after I run "net stop winnat", then I can't make it start again, and I get stuck there. :(

[pplmx]

Still encouner this bug from time to time,

Error response from daemon: Ports are not available: exposing port TCP 0.0.0.0:9000 -> 0.0.0.0:0: listen tcp 0.0.0.0:9000: bind: An attempt was made to access a socket in a way forbidden by its access permissions.

but following this can fix it:

#issuecomment-7

[CelestialArcadia]

SOLUTION: The right solution TLDR version

Source Article

The correct solution is simply to reset the “TCP Dynamic Port Range” so that Hyper-V only reserves ports in the range we have set. You can reset the “TCP Dynamic Port Range” to 49152–65535 by running the following command with administrator privileges, but you can also change it to a smaller range if you think it is too large.

netsh int ipv4 set dynamic tcp start=49152 num=16384
netsh int ipv6 set dynamic tcp start=49152 num=16384

The article discusses a problem encountered while using Docker. The issue involves ports of Docker containers not working, leading to a common error related to access permissions. The root cause is attributed to the "TCP dynamic port range" in Windows, with potential conflicts arising from Hyper-V's reserved port numbers.

The article acknowledges that while stopping and starting the Winnat service may offer a temporary solution, it explicitly states that this method is essentially a simplified version of rebooting the computer. The author points out that relying on this approach may not guarantee a resolution, as the probability of success is random, with some users reporting it works while others say it doesn't. The article strongly recommends against this method as a reliable or optimal solution due to its unpredictable nature.