There's a sporadic issue when using the netclient on windows machines, in conjunction with other software (Hyper-V etc, but not only).
The problem is that after a successful login on the portal, the "callback" to localhost:53000 fails due to the port being reserved and assigned to other things.
By default, Windows reserves ports in the range 49152–65535 for dynamic and private use. The port used by netclient, 53000, falls within that range.
It would be advisable for netclient to:
- Use a lower port that is not in the private windows range and/or
- Check if it can bind to the port and report an error and/or bind to a dynamic and free port.
If such possibility is not available, there's a workaround that might fix the issue in some cases. From an administrator cmd shell exclude the port from the reserved range, like this:
netsh int ipv4 add excludedportrange protocol=tcp startport=53000 numberofports=1
There's a sporadic issue when using the netclient on windows machines, in conjunction with other software (Hyper-V etc, but not only).
The problem is that after a successful login on the portal, the "callback" to localhost:53000 fails due to the port being reserved and assigned to other things.
By default, Windows reserves ports in the range 49152–65535 for dynamic and private use. The port used by netclient, 53000, falls within that range.
It would be advisable for netclient to:
If such possibility is not available, there's a workaround that might fix the issue in some cases. From an administrator cmd shell exclude the port from the reserved range, like this:
netsh int ipv4 add excludedportrange protocol=tcp startport=53000 numberofports=1