SystemLink Client Cannot Communicate to the SystemLink Server at All

Issue Details

A SystemLink client acts like it can’t contact the SystemLink server at all, I'm unable to have the SystemLink server detect the client.

Solution

This can be caused if the server doesn't have the resources to reply to the client, or if there are network communication issues between both sides. To try to fix the issue, follow the next suggestions:
 

Verify resource usage

The SystemLink server can fail to respond because it is too busy, having more load than resources. The Systems Management requires a lot of resources, so make sure that at least the minimum server resource requirements are fulfilled on the SystemLink server.

• The Windows Task Manager can show high CPU / RAM / Ethernet usage if this is the case.

Verify TCP/IP connectivity

If the SystemLink client fails to reach the SystemLink server over Ethernet / TCP, test the network connectivity with the following DOS commands on the client:

• ping server_address
• telnet server_address 4505
• telnet server_address 4506
  • Where server_address is the host name entered in the SystemLink Client dialog.
  • A blank Telnet result represents a success, if you receive a "cannot connect error message" it indicated the port is unreachable.
  • You may need to activate telnet in the Windows “Programs and Features” dialog, alternatively you can use a PowerShell script to test port connectivity:
    • Test-NetConnection -ComputerName <server> -Port 4505
    • Test-NetConnection -ComputerName <server> -Port 4506
• If there is no connectivity, work with your IT department to verify the network traffic between the client and the server.

Verify Salt connectivity

The SystemLink client should be able to talk to the SystemLink server using the salt-minion layer. This can be tested by running the following DOS shell command on the client:

• "C:\Program Files\National Instruments\Shared\salt-minion\salt-call.bat" test.ping
  • The salt-minion test.ping usually takes about 10 seconds to return “True”, which indicates a successful connection in the salt layer between server and client.
  • If the salt-minion returns after 20 seconds or more, check the user_port.txt files.
  • If the salt-minion test.ping throws errors about a missing minion.pub file, browse to the C:\ProgramData\National Instruments\salt\conf\pki\minion\minion.pub folder:
    • You will likely find only the minion.pem private key file. In that case, delete the minion.pem file and restart the NI Salt-Minion service.
    • The salt-minion will recreate both private (.pem) and public (.pub) keys

Additional Information

The Salt Minion service found in clients allow the communication required to connect a SystemLink client to a server. TCP ports 4505 and 4506 are used for this.