Sometimes the connection between the client and your local license server is blocked by a firewall or anti-virus software.
Note that a ping is not sufficient, since the ping protocol does not use a port number and will not make contact with your local license server.
telnet <host> <port>
For example:
telnet license.yourdomain.com 8080
When a connection is established, you get a blank screen. If not, a connection error shows up:
Connecting To license.yourdomain.com...Could not open connection to the host, on port 8080: Connect failed
This may indicate that the server and/or port number is blocked by your server firewall or other security software, or that the license server itself is down.
As telnet is only available on newer Windows versions after explicit installation – which may not be available to all users, Windows PowerShell should be available to most Windows users without any major installation being necessary.
Using Windows PowerShell you can run the commands listed below to check the ports of the TASKING remote license server:
Test-NetConnection -Port 8080 -ComputerName lic1.tasking.com -InformationLevel Detailed
Test-NetConnection -Port 8080 -ComputerName lic3.tasking.com -InformationLevel Detailed
Test-NetConnection -Port 8936 -ComputerName lic1.tasking.com -InformationLevel Detailed
Test-NetConnection -Port 8936 -ComputerName lic3.tasking.com -InformationLevel Detailed
Test-NetConnection -Port 80 -ComputerName lic1.tasking.com -InformationLevel Detailed
Test-NetConnection -Port 80 -ComputerName lic3.tasking.com -InformationLevel Detailed
Note that -ComputerName can also be an IP address.
When you run:
Test-NetConnection -Port 8080 -ComputerName lic1.tasking.com -InformationLevel Detailed
the response in case of success looks similar to the message below:
ComputerName : lic1.tasking.com
RemoteAddress : 18.170.85.205
RemotePort : 8080
NameResolutionResults : 18.170.85.205
52.56.83.76
13.42.161.89
MatchingIPsecRules :
NetworkIsolationContext : Internet
InterfaceAlias : Ethernet
SourceAddress : 192.123.1234.56
NetRoute (NextHop) : 192.123.1234.1
TcpTestSucceeded : TrueDetailed
In case of a failure to connect, the response will contain a failure message and a reason indicating the cause of the failure.