Communication Troubleshooting
Sometimes in troubleshooting problems with client applications connecting to license servers, it’s useful to have a tool outside RLM which can tell you whether messages can get through to the server. If a firewall or anti-virus package or proxy is blocking communications, a separate tool will have the same problems connecting to the server as RLM.
macOS and Linux (Telnet)
Simply attempt to connect to the running RLM license server with telnet (a terminal application). Note down the name of the license server you’re trying to check licenses out from, the main RLM port number, and the ISV server port number. The port numbers can be found in the server side diagnostics.
For example, if RLM is running on the machine server123 and is listening on port 5053, and the ISV server is listening on port 12345, try:
telnet server123 5053 telnet server123 12345
If successful the response will look like:
Trying xxx.xxx.xxx.xxx... Connected to server-123 (xxx.xxx.xxx.xxx). Escape character is '^]'. Type control-] and quit to exit telnet
If not successful:
Trying xxx.xxx.xxx.xxx... telnet: connect to address xxx.xxx.xxx.xxx: Connection refused telnet: Unable to connect to remote host: Connection refused
Windows (PowerShell)
If you have telnet available you can use it as you would on Linux/Unix. If you have access to PowerShell on your system you can run Test-NetConnection.
For example, if RLM is running on the machine server123 and listening on port 5053, and the ISV server is listening on port 12345 try:
Test-NetConnection -ComputerName server123 -Port 5053 Test-NetConnection -ComputerName server123 -Port 12345
If successful the response will look like:
ComputerName : server123 RemoteAddress : xxx.xxx.xxx.xxx RemotePort : 5053 InterfaceAlias : Ethernet SourceAddress : xxx.xxx.xxx.xxx TcpTestSucceeded : True
If not successful:
WARNING: TCP connect to (xxx.xxx.xxx.xxx : 12345) failed ComputerName : server123 RemoteAddress : xxx.xxx.xxx.xxx RemotePort : 5053 InterfaceAlias : Ethernet SourceAddress : xxx.xxx.xxx.xxx PingSucceeded : True PingReplyDetails (RTT) : 94 ms TcpTestSucceeded : False
Windows (PortQry)
If you don’t’ have access to PowerShell, there is a useful tool called PortQry which can be downloaded here. The download is a zip file, and the PortQry executable is in the zip. Download it to the client machine and unzip it. Note down the name of the license server you’re trying to check licenses out from, the main RLM port number, and the ISV server port number. The port numbers can be found in the server side diagnostics. Run PortQry once to try to contact the RLM port, and again to try to contact the ISV server port. PortQry will report success or failure.
For example, if RLM is running on the machine server123 and is listening on port 5053, and the ISV server is listening on port 12345, try:
portqry -n server123 -e 5053 portqry -n server123 -e 12345
If PortQry can talk to the port, you’ll see a message like this:
Querying target system called: server123 Attempting to resolve name to IP address... Name resolved to xxx.xxx.xxx.xxx querying... TCP port 5053 (unknown service): LISTENING
But if PortQry can’t get through, you’ll see a message like this:
Querying target system called: server123 Attempting to resolve name to IP address... Name resolved to xxx.xxx.xxx.xxx querying... TCP port 12345 (unknown service): NOT LISTENING
