License activation from client to license server failing when not on VPN

- April 20, 2023 at 2:43 pm
  
  farally
  Subscriber
  
  Good morning, we are having an issue with local installs of Ansys not communicating with the license server while on campus unless connected to the VPN. Our networking and license server team have been looking into the issue and with ports 1055, 1056, and 2035 open and allowed through our firewall it seems as though the client machines are attempting to reach the licensing server through port 64286. This port is being denied by the licensing server and appears to be a dynamic port used by Ansys. On our Ansys license we have the line:
  VENDOR ansyslmd PORT=2325, however it is still attempting to communicate with the license server through 64286.
  Is there a way to set a static communication port on the client machine, do you have any other advice on how to fix the issue?
- April 21, 2023 at 1:34 pm
  
  VJ
  Ansys Employee
  
  2325 is the Licensing Interconnect Port. You cannot assign it to the ansyslmd process as it will create conflict. Can you stop the license manager and replace vendor ansyslmd port from PORT=2325 to PORT=1056 and restart? Now try launching the application.
  - April 26, 2023 at 3:02 pm
    
    farally
    Subscriber
    
    Any other ideas about the issue? We have students entering finals week unable to access the software needed to complete projects?
    - April 26, 2023 at 3:42 pm
      
      VJ
      Ansys Employee
      
      When on VPN, open a command prompt on Client Computer and try this command..
      telnet SERVERNAME 1055
      telnet SERVERNAME 1056
      
      it should pop a blank cmd screen after each command if the ports are communicating.
    - April 26, 2023 at 4:27 pm
      
      farally
      Subscriber
      
      Interestingly enough 1055 communicates successfully whether connected to VPN or not, however 1056 fails whether connected or not. Activation is successful while connected to VPN though?
    - April 26, 2023 at 4:54 pm
      
      VJ
      Ansys Employee
      
      Can you try setting up inbound rule on your Firewall for port 1056 and try the telnet command again? Did the software ever work when not on VPN?
    - April 26, 2023 at 4:55 pm
      
      farally
      Subscriber
      
      Set up the inbound rule on the client PC or the license server? It did work as far as we know up until about a month ago.
    - April 26, 2023 at 5:05 pm
      
      VJ
      Ansys Employee
      
      setup in both the PC and server. Telnet to server via 1056 should work without vpn
    - April 26, 2023 at 5:12 pm
      
      farally
      Subscriber
      
      Set the rule on both PC and server however it will still not telnet on 1056.
    - April 26, 2023 at 5:31 pm
      
      VJ
      Ansys Employee
      
      When you launch the Ansys application, you mentioned it was trying to communicate on 64268.. can you relaunch the application and see if it tries the same port? Share a screenshot of the log as well.
  - April 26, 2023 at 3:03 pm
    
    farally
    Subscriber
    
    hank you both client file and licensing server file are set to port 1056 and the license has been restarted however the problem still exists. The client PC communicates back to the license server through port 64286 which is causing an issue and the only way to connect successfully is when the client PC is connected to VPN.
- April 21, 2023 at 1:55 pm
  
  farally
  Subscriber
  
  Thank you both client file and licensing server file are set to port 1056 and the license has been restarted however the problem still exists. The client PC communicates back to the license server through port 64286 which is causing an issue and the only way to connect successfully is when the client PC is connected to VPN.