Testing VLM TCP Communication Ports Using Telnet

Publish Date: Jul 11, 2018 | 0 Ratings | 0.00 out of 5 | Print

Overview

NI License Manager communicates with Volume License Manager (VLM) using TCP communication. For that communication to be successful, the Volume License Server must be configured to allow incoming TCP communication through the ports used by VLM. This article explains how to test to ensure VLM TCP Communications are not blocked and are open on both machine-specific and domain firewalls.

This article is part of the Volume License Manager (VLM) Troubleshooting Guide.

Table of Contents

  1. Introduction
  2. Testing Ports
  3. What the Results Mean
  4. Additional Resources

1. Introduction

The two ports used by Volume License Manager are the Licensing Port (27000 by default) and the Communication Port (4637 by default). The next step in troubleshooting is to ensure that NI License Manager (NILM) can communicate with the Volume License Server through those ports. An easy way to test this is to use Telnet.

Note:  For some versions of Windows, the Telnet client is disabled by default.  You may turn it on by navigating to Start»Control Panel»Programs»Programs and Features when your view is set to category and selecting the link to Turn Windows features on or off.  In this window check the Telnet Client box.  See the screenshot below for more information on this setting.

 

Back to Top

2. Testing Ports

  1. Check which ports Volume License Manager is using on the license server:
    1. Go to Tools » Preferences
    2. Write down the port numbers used for the Licensing Port and Communication Port.
  2. Open the Telnet client and attempt to open a connection to the two ports recorded in the previous step:
    1. Open a command prompt by going to Start Menu»Run and typing in cmd.
    2. Execute Telnet with the following syntax in the command prompt window:
         telnet <servername> <main licensing or communication port>
          Ex: telnet ServerX 27000
    3. When the Telnet connection to the server is successful, a window will pop up with a cursor. The name of server will be in the title bar.


    4. If the Telnet connection is not successful, the error will be: Could not open connection to the host, on port <port>: Connect failed

    5. If the telnet connection does not work, make sure that both Main Licensing and Communication ports used by VLM are open. See Getting Started with FlexNet Publisher Configuration and My Software Licensing Is Not Working with the NI VLM Server for more information.
  3. Observe whether a connection was established.

 

Back to Top

3. What the Results Mean

Unable to Establish a Connection Over One or Both Ports

This means that something between the client and the volume license server is blocking the TCP communication. The most common cause is a firewall. It’s recommended to work with an IT team (if applicable) to resolve this issue.

Both Connections are Successful

The ports used by NI License Manager to communicate with Volume License Manager on the Volume License Server should be open and should allow for interaction between NI License Manager and Volume License Manager.  Next, check NI License Manager (NILM) and Volume License Manager (VLM) configuration and connectivity.

 

Back to Top

4. Additional Resources

Back to Top

Bookmark & Share


Ratings

Rate this document

Answered Your Question?
Yes No

Submit