Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > alt.comp.os.windows-10 > #184293

Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates

From Marion <marion@facts.com>
Newsgroups alt.comp.os.windows-10, alt.comp.os.windows-10, alt.comp.microsoft.windows
Subject Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates
Date 2025-05-05 00:58 +0000
Organization BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID <vv92fu$jpf$1@nnrp.usenet.blueworldhosting.com> (permalink)
References <vv4b6h$3052$1@nnrp.usenet.blueworldhosting.com> <vv8rh9$299h$1@nnrp.usenet.blueworldhosting.com> <vv8uoh$v14$1@nnrp.usenet.blueworldhosting.com>

Cross-posted to 3 groups.

Show all headers | View raw


On Sun, 4 May 2025 23:54:58 -0000 (UTC), Marion wrote :


> This is getting long, but I document it carefully so that others
> can make use of the debugging technique as these work on your system.

Update... doublechecking my assessments of fact are turning out correct.

This was run before rebooting to reserve a block of 101 ports.
 C:\> netsh int ipv4 add excludedportrange protocol=tcp startport=55500 numberofports=101

I just rebooted and confirmed that 1400 ports (i.e., 14 random sets of 100 
ports) are being excluded by "something" (likely Winnat) after every boot.

 C:\> netsh interface ipv4 show excludedportrange protocol=tcp
      Protocol tcp Port Exclusion Ranges
      Start Port    End Port
      ----------    --------
           2438        2537        (100 ports) 
           5357        5357        (1 port)
          22110       22209        (100 ports)
          48744       48843        (100 ports)
          48844       48943        (100 ports)
          49044       49143        (100 ports)
          49144       49243        (100 ports)
          49344       49443        (100 ports)
          49444       49543        (100 ports)
          49544       49643        (100 ports)
          49668       49767        (100 ports)
          49768       49867        (100 ports)
          49868       49967        (100 ports)
          50000       50059     *  (60 ports)
          50060       50159        (100 ports)
          55500       55600     *  (101 ports) 
      * - Administered port exclusions.

 C:\> net stop winnat
      The Windows NAT Driver service was stopped successfully.

 C:\> netsh interface ipv4 show excludedportrange protocol=tcp
      Protocol tcp Port Exclusion Ranges
      Start Port    End Port
      ----------    --------
         5357        5357          (1 port)
         50000       50059     *   (60 ports)
         55500       55600     *   (101 ports)
      * - Administered port exclusions.

I wonder... Do we event need the Winnat functionality?
To find out what happens if I don't restart it, I won't.
How else can I find out what uses Winnat on Windows 10?

Back to alt.comp.os.windows-10 | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


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