It worked immediately, didn't even require a restart. I found a solution somewhere that worked for me: net start winnat There are lots of questions about this in Stackoverflow (which I think is not the adequate place for this question, but anyway). So, that's the question: how can I find which applications are reserving those TCP port ranges ?
So, now I would like to try another approach: find out which applications are excluding those TCP port ranges.Īlthough this is a corporate machine, it does not belong to a Windows domain (and indeed is in my house right now, as I'm working from home because of the pandemic). I can also try to delete some excluded ranges, but mostly netsh refuses to do so, showing errors "access denied" (even inside an administrative shell) or "element not found". Indeed I can see the ranges of excluded ports with the command netsh int ipv4 show excludedportrange protocol=tcp Searching the internet I think that this explanation here is the most likely: the ports were administratively excluded by some application(s), most likely being reserved for their own use. Recently in my development machine some TCP ports started being unavailable for applications, giving the error 10013.
In Windows 10, how can we find out which applications reserved TCP port ranges as shown by netsh?
0 kommentar(er)
