Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.os.windows-10 > #184251
| From | Marion <marion@facts.com> |
|---|---|
| Newsgroups | alt.comp.os.windows-10, alt.comp.os.windows-10, alt.comp.microsoft.windows |
| Subject | After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates |
| Date | 2025-05-03 05:56 +0000 |
| Organization | BWH Usenet Archive (https://usenet.blueworldhosting.com) |
| Message-ID | <vv4b6h$3052$1@nnrp.usenet.blueworldhosting.com> (permalink) |
Cross-posted to 3 groups.
UPDATE!
For years, a day or two after a Microsoft Update (I think - but I'm not
sure), about once a month (or so) stunnel and/or adb would fail because
they couldn't bind to the ports that they normally bind to every day.
Privileged ports: Ports 0–1023
Registered Ports: Ports 1024–49151
Dynamic/Private Ports: Ports 49152–65535 (99 of these ports are excluded!)
They'd both fail because a port they normally use, wasn't available.
Binding service [x] to 127.0.0.1:53537: Permission denied (WSAEACCES) (10013)
For years, I tried to find out WHAT was "using" those ports.
It turns out nothing was using them, per se, so netstat returned nothing!
C:\> netstat -ano | findstr :53537
So did procmon. So did resmon. So did task manager. As did everything else.
I could bind to any port that was not in a range of 99 ports unavailable.
C:\> ncat -l -p 56789
But I could NOT bind to a port that was in the range that was unavailable.
C:\> ncat -l -p 56789
Ncat: bind to :::56789: An attempt was made to access a socket
in a way forbidden by its access permissions. . QUITTING.
In desperation, I went to AI and after HOURS with AI, I finally got closer
to the problem, where this command lists 99 ports which are unavailable.
C:\> netsh interface ipv4 show excludedportrange protocol=tcp
C:\> netsh interface ipv6 show excludedportrange protocol=tcp
I still have no idea what is making the 99 ports unavailable after a reboot
(often after a Windows Update) but AI thinks it's an underlying Windows
process that has administrator capabilities. We don't know what that is.
But now I at least have a solution without resorting to another reboot!
Instead of rebooting (which was my only solution for years!) all that was
needed was to run these stop/start commands to free the 99 excluded ports!
C:\> net stop winnat
The Windows NAT Driver service was stopped successfully.
C:\> net start winnat
The Windows NAT Driver service was started successfully.
C:\> netsh interface ipv4 show excludedportrange protocol=tcp
Protocol tcp Port Exclusion Ranges
Start Port End Port
---------- --------
5357 5357
50000 50059 *
* - Administered port exclusions.
Voila! (almost)
The only thing left is WHY those 99 ports are sometimes made unavailable.
When you run (as admin) those commands, do you ever get 99 ports locked up?
Anyone have any experience with this problem set for debugging information?
If not, at least others can benefit from the troubleshooting hours today.
Back to alt.comp.os.windows-10 | Previous | Next — Next in thread | Find similar | Unroll thread
After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-03 05:56 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Paul <nospam@needed.invalid> - 2025-05-03 13:38 -0400
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-03 22:24 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Uncle Bob <uncle.bob@nospam.net> - 2025-05-03 18:58 -0400
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Victor <victorheyne@notreal.org> - 2025-05-06 11:32 -0500
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-09 20:36 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-09 20:56 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-04 22:59 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-04 23:54 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-05 00:58 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2025-05-06 22:06 +0800
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-06 15:45 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-06 15:50 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-06 17:25 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2025-05-21 02:16 +0800
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-20 19:51 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-06 15:58 +0000
csiph-web