Client Versions 2021 R2 & Later

Two processes and ports must be running and able to be communicated with on the license server in order for clients to connect to it.

• FlexLM Process - Port:1055
• Vendor Daemon Process - Port: Dynamic‍

Test	Success	Failure
FlexLM & Vendor Daemon From the client computer > Windows Search > Search for Ansys Client Licensing Settings [latest version #] > right click and select Run as Administrator > click FlexNet Publisher License Status		Two possible failures can occur:

Client Version 2021 R1

Two processes and ports must be running and able to be communicated with on the license server in order for clients to connect to it.

• FlexLM Process - Port:1055
• Vendor Daemon Process - Port: Dynamic‍

Test	Success	Failure
FlexLM & Vendor Daemon (Ansys Client Software is Required) From the client computer with Ansys installed > Open a command prompt‍ and run the following command using your license server hostname: "C:\Program Files\ANSYS Inc\Shared Files\Licensing\winx64\lmutil.exe" lmstat -a -c 1055@YourLicenseServerName		Two results are possible:

Client Versions 2020 R2 & Prior

Three processes and ports must be running and able to be communicated with on the license server in order for clients to connect to it:

• FlexLM Process - Port:1055
• Vendor Daemon Process - Port: Dynamic‍ 
• Ansys Licensing Interconnect Process (Client Ver 2020 R2 and Prior only) - Port:2325

Test	Success	Failure
FlexLM and Vendor Daemon From the client computer > Windows Search > Search for Client ANSLIC_ADMIN Utility [latest version #] > right click and select Run as Administrator > View Status/Diagnostic Options > Display the License Status > Scroll to Top		Two possible failures can occur:
Ansys Licensing Interconnect Open a command prompt‍ on the client computer >Run the following command: "C:\Program Files\ANSYS Inc\Shared Files\Licensing\winx64\ansysli_util.exe" -printavail

Any Version - Alternative Test Methods (Client Software Not Required)

Below are some alternative methods to test connectivity with the License Manager, in particular, three of the methods below do not require the client software to be installed or functioning.

Three processes and ports must be running and able to be communicated with on the license server in order for clients to connect to it:

• FlexLM Process (lmgrd.exe) - Port:1055
• Vender Daemon Process (ansyslmd.exe) - Port: Dynamic‍ 
• Ansys Licensing Interconnect Process (ansli_server.exe) - Port:2325 (Required for Client Versions 2020 R2 and Prior only)

Test	Success	Failure
FlexLM (Ansys Client Software Not Required) From the client computer > Open Powershell and run the following command Test-NetConnection -ComputerName YourLicenseServerNameOrIP -Port 1055		Can take up to 30 sec to fail
Ansys License Interconnect (Ansys Client Software Not Required) From the client computer > Open Powershell and run the following command: Test-NetConnection -ComputerName YourLicenseServerNameOrIP -Port 2325		can take up to 30 sec to fail
Vendor Daemon (Ansys Client Software Not Required, but License Server Access is required) Step #1 - Identify the Port # From the License Server Computer > Search for and Open Resource Monitor > Network tab > Listening Ports section > locate ansyslmd.exe and view the port column (see picture) Step #2 - Test From the client computer > Open PowerShell and run the following command: Test-NetConnection -ComputerName YourLicenseServerNameOrIP -Port YourPort# ‍		This can take ~30secs to fail
FlexLM & Vendor Daemon (Ansys Client Software is Required) From the client computer with Ansys installed > Open a command prompt‍ and run the following command using your license servername: "C:\Program Files\ANSYS Inc\Shared Files\Licensing\winx64\lmutil.exe" lmstat -a -c 1055@YourLicenseServerName		Two results are possible:

A)  The specified  license server  is incorrect

1. Verify you specified the correct license server‍, that it's spelled correctly.
2. You can also inspect the specified license server(s) manually, follow HOW TO - Verify Specified License Servers Manually (ansyslmd.ini)

B)  The License Manager Service is not running or Out of Date

Update the License Manager

1. Ensure the License Manager is running the most current version - License Manager Upgrade/Installation Instructions‍ 

Verify The License Manager Server is Running

1. Can other users/computers connect and checkout licenses?  If so, the License Manager Service is running, and you can skip this step.
2. These next steps need to be performed on the license server computer. 
   1. If you do not have access to the license server computer, you will need to have your IT Administrator perform this step.
3. Windows Search> search for Ansys License Management Center >Right click it and select Run as Administrator
4. Once open select View Status/Start/Stop License Manager > verify you see a green check mark.
   1. 
5. If not, start the server and repeat the License Manager Connectivity Test.
6. If you cannot start the server, follow ERROR - Ansys License Server Won't Start‍.

C)  DNS is Not Resolving Properly

DNS is the system looks up the license server host name and converts it to an IP address. If this doesn't work, the client can't talk to the license server.  Perform the following test to see if DNS is a problem.  

1. Specify the license server via IP address instead of computer name / hostname and re-run the License Manager Connectivity Test.
   1. Success?- You have a DNS resolution problem and will need to contact your IT administrator.  
      1. Alternatively, you can manually edit your Windows host file‍ as a work around.
   2. Failure?  -  Continue troubleshooting.
2. Go back and change license specified to the hostname.  Do not leave your license server specified via IP address as not all Ansys features will work properly.

D)  Firewall ports on the license server or network firewall  are blocked

1. Can other users/computers on the same network as you (local is different than VPN, which is different than another office) and running the same version as you (different versions use different ports) connect and checkout licenses? If so, the firewall ports are opened and you can skip this step.
2. Add necessary Firewall Rules on the License Server Computer
3. Add necessary Firewall Rules to any network firewalls/VPN's/routers. This is not common in smaller network environments, but more common in highly secure, enterprise networks, and you will need to contact your network team. 
4. Repeat the License Manager Connectivity Test.

E)  Client Computer is not connected to license server network

1. Verify the client computer Wi-Fi or physical network cable is connected to your office network.
2. If working remotely, ensure the client computer VPN is connected.
3. Run the following commands to test network connectivity

   1. Test	Success	Failure Examples
      Ping Server Hostname Open a Command Prompt‍ on the client computer and run the following command: ping YourServerName
      Ping Server IP Address Open a Command Prompt‍  on the client computer and run the following command: ping YourServerIPAddress

4. If ping responses are disabled on the license server, attempting to connect via Windows File share can sometimes be an alternative way to test.

   1. Test	Success	Failure
      File Share Test - Server Hostname
      File Share Test - Server IP Address

5. If these tests fail the server is either offline or not configured to respond to ping requests/file sharing and you'll need to contact your IT Administrator.

F)  The License Server Computer is Offline

1. Can other users/computers connect and checkout licenses?  If so, the server is online, and you can skip this step.
2. Perform the tests above in the section Client Computer is not connected to license server network.  These tests will also help determine if the license server is online or not.
3. If these test fails, the only other way to confirm if the license server is online is to remote desktop into it or physically go to the computer and verify it's online and connected.

G)  Client Antivirus/Firewall is causing the issue

Please following the following article - Troubleshooting Antivirus Related Issues