Monday 15 April 2019

windows 7 - TCP/UDP ports that cannot be bound (permission error), but don't show up in netstat

When attempting to listen on certain TCP or UDP ports, I get weird error messages regarding permissions (or generic messages, depending on the program used to bind).


The message in German is "Der Zugriff auf einen Socket war aufgrund der Zugriffsrechte des Sockets unzulässig", I believe this equals "An attempt was made to access a socket in a way forbidden by its access permissions". (Some programs just return a more generic error, this is the one reported by ncat).


The affected ports seem to change across reboots. This time, ports 61974-63949 seem to be affected. Last session, 63014-64989 were affected. (Both ranges are exactly 1976 ports long.) Both TCP and UDP are affected on the same ports.


TCPView/netstat do not show anything regarding those ports. A nmap port scan did not see any difference between the affected and unaffected ports.


Any idea what may cause such behavior?

No comments:

Post a Comment

How can I VLOOKUP in multiple Excel documents?

I am trying to VLOOKUP reference data with around 400 seperate Excel files. Is it possible to do this in a quick way rather than doing it m...