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 (NOTE: In versions 2023 R1 and later click on "Features in Use."		Two possible failures can occur:

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 is Required) From the client computer > 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:

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

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.  Ansys Software is not required to be installed to perform this test.

• 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 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
Vendor Daemon Step #1 - Identify the Port # from the License Server Computer > Search for and Open Resource Monitor > Network tab > Listening Ports section > locate & select ansyslmd.exe and view the port it's using in the port column (see picture).   Tip: Set a Static Vendor Daemon Port to prevent this port from changing and make this test easier. Step #2 - Test From the client computer > Open PowerShell and run the following command: Test-NetConnection -ComputerName [YourLicenseServerNameOrIP] -Port YourPort#		*Can take ~30secs to fail
Ansys License Interconnect 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

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 & 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:

1. Verify the license server specified‍ is spelled correctly.
2. Check if the servername you have specified uses a combined hostname and domain name (ex. ansysserver.simutechgroup.com) instead of just a hostname (ansysserver).
   1. If it does, set it to just the hostname and run a connectivity test.
   2. If the test fails, set the server back to what it was originally specified as and continue ruling out additional causes.

Can other users/computers connect and checkout licenses?  If so, the License Manager Service is likely running, and you can skip this step.

1. Verify the License Manager is Running 

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 hostname and re-run the Connectivity Test.
   • Success?  If the test succeeds, this means you have a DNS resolution problem and will need to contact your IT administrator.  
     • Alternatively, you can manually edit your Windows host file‍ as a work around.
   • 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.

Can other users/computers on the same network as you and running the same version as you connect and checkout licenses?  If so, the ports are likely open, and you can skip this step.  Note - VPN connections are on a different network than local connections.  Different offices/building are on different networks as well.

1. Add Firewall Rules on the License Server
   1. HOW TO - Add Firewall Exceptions for Ansys License Manager 
   2. If you have done this in the past, please repeat this process again, to ensure nothing has changed.
2. Repeat the Connectivity Test
   1. If the problem still persists, this means something between the client and the server is blocking traffic. This could be:
      1. 3rd Party Software Firewall on the Server (Symantec, McAfee, etc.)
      2. VPN Configuration
      3. Network Router/Firewall
      4. AV/EDR Protection
      5. 3rd Party Firewall on the Client Machine (Symantec, McAfee, etc.)
3. Set Custom Static Vendor Daemon Port
   1. HOW TO - Set Custom/Static License Server Ports
   2. This will allow your Network Administrator to allow it through necessary network devices.
4. Contact your Network Administrator
   1. Have them allow required ports through all network devices/services.
5. Repeat the Connectivity Test

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
   Note:  If ping responses are disabled on the license server, this test will not be accurate.
    

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. Attempting to connect via Windows File share can sometimes be an alternative way to test.

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.

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.

1. Verify the specified license server matches the server listed in the installed license file.
   
   
2. If these server names do not match, you have 3 options:
   1. Change your specified license server to match the server listed in your license file.  If you do this and the connection test still fails, follow the next option.
   2. In addition to changing your specified license server to match the server listed in your license file, you must edit the host file on the client computer. 
      1. HOW TO - Edit Your Windows Host File
      2. This is considered a work around and will need to be performed on all other similar computers. For a more permeant solution see the next option.
   3. Modify the server name listed in your installed license file to your desired full domain name.
      1. Stop the License Manager‍ 
      2. Modify the server name found in your installed license file as pictured above > start the license manager.
      3. All Ansys users will need to update their specified license server to this new server name. 
      4. In the future, when you attempt to install a license, you will need to manually edit the provided .txt file before installing it and change the server name to YourServerName.company.com before it will successfully install.

1. HOW TO - Troubleshoot Antivirus Software with Ansys‍

1. HOW TO - Manually Reset Your Specified License Servers (ansyslmd.ini)‍