Problems connecting to server machine. License Client Settings (or Client Admin Utility Manager) show that the server machine is down or not responding.

There are several things that may cause this issue.

There are several things that may cause this issue. Some common troubleshooting include:
1.) Verify that the server machine and client machine are connected to the same network. Do a quick ping command to make sure the 2 machines can communicate with one another. On the client machine, open the command prompt and type in ping server_ip. You should see a response. If not, there is a communication problem the company's IT needs to resolve.
2.) If the customer is using Structures/Fluids software, check the Ansys Licensing Client Settings (under Start --> Ansys 2022 R1 --> Ansys Client Licensing Settings) to make sure that the "Server 1" line is pointed towards the correct machine. If there is an external server that the license is hosted on, that external machine's name should be listed in the "Server 1" line of the Ansys Client Licensing Settings. After it is enterred, click "Test" and "Save" to make sure the information is logged. Check the ansyslmd.ini file under C:\Program Files\ANSYS Inc\Shared Files\licensing (assuming they've installed on the C: drive). This file should have been automatically updated after saving the information from the Ansys Client Licensing Settings and should show the server name. If the customer is using Electronics Software, the Ansys Client License Settings tool will not be in the Ansys folder in the start menu and we will need to edit the ansyslmd.ini file directly. For versions of the software older than 2021 R1, the customer may be using the Client Utility Manager, which has a slightly different interface, but has the same function (to point to the server machine and indirectly edit the ansyslmd.ini file).
3.) Use the IP Address in the Ansys License Client Settings instead of the host name. This will ocassionally fix the issues, but is not a common solution.
4.) Verify the name of the Server machine and that it matches what is needed for the setup process. First, check the Server name of the machine and compare it to what has been enterred in the License Client Settings (or the Client Utility Manager for older versions), the license file and the the ansyslmd.ini file. If there is a mismatch, this will be an issue.
5.) Verify that all the relevant executables are allowed passed the firewall on the server machine. See YouTube link listed in the adjacent cell for more info on this. This is a common solution to this problem. These executables are to be allowed on the Server machine.
6.) Verify that ports 1055 and 2325 are open using the telnet command. For this, you will need the IP address of the server machine. This can be found by running the ipconfig command on the server machine and looking at the IPV4 address. Once you have the server ip, go to the command prompt of the client machine and use the telnet command. The syntax is telnet server_ip port#. Check both ports 1055 and 2325.
7.) Set a static port for the vendor daemon. This can be done by editing the ansyslmd.lic file under C:\Program Files\ANSYS Inc\Shared Files\licensing\license_files on the server machine. In this file, you can enter PORT=1056 in the vendor line, then save the file to the same location. The License Manager on the server machine should also be reset before testing.