Failed to bind to ports 61234 & 61235 - again.

[Andrew Neil]

Previously:

In that thread, ​@Pavel A. said:

The helpful AI informs that user can define several ranges of ports to exclude from automatic allocation - but this won't prevent other apps to use these ports explicitly. The command is netsh int ipv4 add excludedportrange protocol=tcp startport=<port_number> numberofports=<N

(Unfortunately, linking to specific posts within a thread is broken at the moment)

 

The problem has now recurred:

 

 

and, indeed, it does seem that the mentioned ports - 61235 & 61234 - are in an excluded range 

C:> netsh int ipv4 show excludedportrange tcp active

Protocol tcp Port Exclusion Ranges

Start Port    End Port
----------    --------
      5357        5357
     49679       49778
     49879       49978
     50000       50059     *
     50160       50259
     59330       59429
     59541       59640
     59864       59963
     61196       61295

* - Administered port exclusions.

This was working fine this Moring, so the question remains: Why has this range suddenly got excluded??

 

In this thread:

The accepted solution (from ​@LaurentL) is:

check that there is no ST-LINK_gdbserver.exe running with task manager ?

If it is the case, kill the process and it should be fine

But I have checked that, and Task Manager shows no such process running 

 

This is CubeIDE v2.1.1 on Windows 11 Pro

[Andrew Neil]

Repeating that command again today, after a restart, I get:

C:> netsh int ipv4 show excludedportrange tcp active

Protocol tcp Port Exclusion Ranges

Start Port    End Port
----------    --------
     49531       49630
     49702       49801
     50000       50059     *
     50060       50159
     50160       50259
     50260       50359
     50371       50470
     50903       51002

* - Administered port exclusions.

Which is quite different - and, indeed, the 61196-61295 range (which caused the problem) is no longer excluded.