Biglybt port forwarding update#
Biglybt port forwarding windows 10#
Biglybt port forwarding windows#

Biglybt port forwarding windows#

Also shutting down docker for windows doesn't make any difference and when a colleague mentioned that for them it's enough to restart docker for windows (in the UI go to Reset->Restart) and right now for me, even restarting with the shutdown command doesn't work anymore. I've noticed that it always seems to be 160 or 180 (exact numbers) of ports which have permission denied in the ranges of 40,000+ This seems oddly coincidental to me, so obviously something is occupying the ports on purpose, but what? I can't seem to find anything in the windows event logs (although I wouldn't know what to look for exactly) and none of those ports shows up any any of my firewall rules. Here a screen from the occupied ports (I marked the bordering occupied ports which are right before or after the group of permission-denied-ports)

Biglybt port forwarding update#

The last time it was a bios update (probably due to the meltdown / spectre issues?).Īlso trying to open up the ports explicitly on the firewall didn't help.Īccording to this answer TCPView and netstat shouldn't miss any occupied ports, but even when I enable showing unconnected endpoints in TCPView, I don't see any of the ports where I get permission denied when trying to bind them. In both cases after some windows updates where installed. And it also worked normally for ~10 months before it broke the first time and afterwards for 2 months. So everything should be on default values.

Biglybt port forwarding windows 10#

None of us modified anything on the windows firewall or has any additional anti virus tools installed except the windows 10 default ones. Those ports in question are for instance:

I can't even connect to the port via telnet, it says nothing is listening on the port. I also tried running netstat in an administrator console and similar commands inside bash on windows, but couldn't find anything.

All of us are pretty sure that the port isn't occupied by anything.

I've also found - but netstat -o doesn't list the port, neither does the tool TCPView. When I looked for it, the suggested solutions where to restart the machine, but that seems more like a work around, not a real solution. The exact error message I get isĪn attempt was made to access a socket in a way forbidden by its access permissions I wrote a small f# script to test which ports are affected. After I restart normally (due to windows updates or similar) the issue comes up again an I need to shut down windows with that command. Restarting windows after it was shut down with shutdown /s /f /t 0 is the only reliable solution to open up the port again. All of us who experience the issue are running Windows 10, but not everyone with Windows 10 has that issue. In the meanwhile other developers saw the same issue. At first I thought it's my broken machine, so I reset everything, which kinda fixed the issue for 2 months and now it is back. 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.