Unable to bind a socket to port %1
Probable cause
The network layer was unable to bind a socket to the given port. Check the following. 1) (Server only) Verify that the port
isn't already in use. If the port is in use, either shut down the application listening on that port, or specify a different
port. 2) (Server only) Verify that there are no firewall restrictions on the use of the port. 3) (Client only) If the client_port
option was used, verify that the given port isn't already in use. If only one client port was specified, consider using a
range (for example, NNN-NNN). If a range was specified, consider making it a wider range, or a different range. 4) (Client
only) If the client_port option was used, verify that there are no firewall restrictions on the use of the port.