Failed to bind to port 61235, error code -1: No error

[Andrew Neil]

IF it’s failed to connect, and given an error code of -1, how can that be “No error” ?!

 

 

Also the suggestion “Please check power and cabling to target” is useless here - it’s not a target connection issue!

 

The focus of this thread is the silliness/unhelpfulness of the messages.

Not looking for solutions to the underlying issue here.

For that, see:

 

 

[NiTr0man]

looks like windows becomes fubar after last update

do “netsh interface ipv4 show excludedportrange protocol=tcp” in console - ports will be in excluded range.

do .”net stop winnat” (needs admin rules) and check excluded ranges again

then - do “netsh int ipv4 add excludedportrange protocol=tcp startport=61218 numberofports=2” (it might prevent winnat to lock port range again) and “net start winnat”

[Andrew Neil]

Again: 

The focus of this thread is the silliness/unhelpfulness of the messages.

Not looking for solutions to the underlying issue here.