Contact Us

If you still have questions and are an active SimuTech customer, please submit a request.

  • Ansys Training
  • Consulting
  • About
  • Contact Support
  • Home
  • Installation

  • Troubleshooting

  • Errors & Solutions

  • How To's

  • Info

  • Remote Solve Manager

  • Employee Login

Can't find what you're looking for?

Contact Support

Installation & Licensing Center

Contact Us

If you are an active or future SimuTech customer and have questions or simply prefer to get help directly from an engineer, we'd be happy to help!

  • Home
  • Installation
  • Troubleshooting
  • Errors & Solutions
  • How To's
  • Info
  • Remote Solve Manager
+ More

Make Your Ansys License Server Public Facing (BYOL)

Authored by Caleb Scharf December 13th, 2022 2799 views 1 likes KB956149

Description

Generally, setting up a VPN to the network where your Ansys license server is installed, is the most common way for Ansys clients to access the license server so they can work remotely.  There are also several other solutions you can read about Choosing a Remote Connection Type‍. However, there are three common scenarios where you may need to make your Ansys license server directly available to a client computer on the public internet: 

  • You are using Ansys Cloud Bring Your Own Licensing (BYOL) - BYOL requires the Ansys Cloud service, which acts as an Ansys client, to be able to access your privately hosted license server.
  • You Don’t Have a VPN - You may not have a VPN setup, that allows you to access the private network that your license server resides on, when you are working from home.
  • You're Using a Cloud Virtual Machine - You may need to install your Ansys License Server on a cloud virtual machine hosted on AWS, Azure or Google and that cloud environment/VM is not networked to your local environment where your Ansys clients reside.


Considerations

Making your license server public facing is not always the best option and can have several downsides depending on your situation.  There are several main requirements unique to this scenario which may be limitations for some.  If you have many clients or they will be traveling to different locations frequently, setting up a VPN to your network where the license server is located is often the best solution.  

Requirements

  • IT Expertise to setup firewall rules and IP/Port forwarding.
  • Your License Manager must be running Windows (While it may be possible do to this on a Linux machine, this guide does not specifically cover that scenario)
  • A public domain with the ability to add an A record/subdomain.
    • Obtainable for Free from a service provider such as NoIP.com
    • Obtainable for ~$12/year from a registrar of your choice (Ex. godaddy.com, networksolutions.com , etc.)
  • A public static IP address that you can configure to point traffic to your license server.
    • Obtainable for ~$5/mo from your ISP.  While you use a dynamic IP (one that changes intermittently), you'll end up needing to reconfigure your Ansys Cloud settings and your public domain A record anytime your IP changes.
  • A public static IP address that your client computer will be connecting from.
    • Obtainable for ~$5/mo from your ISP.
    • You will only be able to access the license server from IP's that have been allowed through the cloud VM firewall.  If your clients are not connecting from a static IP, this can still work, however, you may need to frequently update your firewall rules as residential ISP's can change your IP address at random.  The frequency varies widely by ISP - we've seen IP's change daily/monthly/yearly.
    • Another option that doesn't require your clients to have a static IP is to setup a VPN connection to your cloud VM environment.  

Solution

Step #1 - Setup Static IP and Domain Name

  1. Obtain a public static IP address from your Internet Service Provider (ISP) where your license serveris located.
    1. Residential ISP's do not generally issue static IP's by default and you will need 
  2. Obtain a public domain name from a provider listed above. 
    1. For this article, we will use the example domain "mycustomdomain.com"
  3. Create a public DNS hostname that points to your public static IP address.
    1. From your domain providers DNS management console, add an A record using the following values"
      1. Host = name of your choice (example: license)
      2. Points To = your public static IP address
      3. TTL = 10min - 1hr is normal (this value is not critical)
    2. Your public DNS hostname is now "license.mycustomdomain.com"

Step #2 - Modify Windows Host File

  1. These steps must be performed on the license server
  2. Search for Notepad in your start menu > right click and select Run as Administrator
  3. File > Open > Paste this path into the file name field   "C:\Windows\System32\drivers\etc\hosts" > Open
  4. Add the following line to the file and save the file.   
    1. "127.0.0.1       license.mycustomdomain.com"

Step #3 - Configure Ansys License Manager

  1. Install the Ansys License Manager software if you have not already done so.
  2. Modify the license file host name and vendor port:
    1. First, Stop the Ansys License Manager‍ 
    2. Open the installed license file in notepad.  The path is:
      1.  "C:\Program Files\ANSYS Inc\Shared Files\Licensing\license_files\ansyslmd.lic"
    3. Set at a static ansyslmd vendor port of 1056 by adding the term PORT=1056 to the second line as seen in the picture below. 
    4. Replace the existing hostname/computer name in the license file to license.mycustomdomain.com as seen in the picture above.
    5. Start‍ your license manager

      Warning

      If you are using LM version 2021R1 or later, after making this change, you must not start the license manager from the License Management Center webpage.  You must now start it from the services.msc console window.  If the license server is ever started from the License Management Center webpage, it will revert the manually specified hostname back to the actual host name of the computer and your configuration will not work.

Step #4 - Configure Your Ansys Cloud Server (BYOL Setup Only)

If you are setting up Ansys Cloud Bring Your Own License (BYOL), your cloud environment will act like any other Ansys client in regard to pulling licenses and must be able to communicate with your private license server.  Therefore, you must allow the public static IP(s) of your Ansys Cloud Server(s) through your network firewall.  This public IP address of your Ansys cloud address is referred to as the Ansys Proxy Address.

Important

  • This proxy address is unique to each customer and region that is being activated
  • If you are using multiple regions, you will have multiple proxy addresses
  • If you ever deactivate and then reactivate a region, these IP's will change, and your firewall configuration will need to be updated.  

Obtain Ansys Proxy Address:

  1. To obtain your Ansys Proxy Address(s) you will need to setup and activate a region.  
  2. Visit https://cloud.ansys.com/companyAdmin/licenseSettings
  3. Select License Server Connection> expand Region> Expand License Server Connection Settings>Activate>Fill in the settings as follows:
  4. Once activated, the Ansys Proxy Address will be listed. Take note of this address as it will be used when creating your firewall rules.

Step #5 - Firewall Configuration

  1. Ensure you're Ansys license server is using a static IP address.
  2. On your network firewall, open and forward traffic destined for your public facing static IP address on ports 1055, 1056 and 2325 to the internal static IP address of your Ansys License Server.  
    1. Limit the scope of this traffic to only the public IP addresses of the Ansys client computers that will be accessing your license server.  (This will be or include the Ansys Proxy Address if setting up BYOL).
    2. Warning

      If you do not do this limit the scope as instructed in this last step, any computer on the public internet can access your Ansys license server which is a severe security risk.

Step #7 - Complete BYOL Setup (BYOL Setup Only)

If setting up BYOL, there are still several remaining steps you need to follow in order to complete this process.  Those steps can be found here: https://ansyshelp.ansys.com/account/secured?returnurl=/Views/Secured/Cloud/v000/en/ans_cloud_compute/verify_conn.html

Step #6 - Test Connectivity

Once you've complete the above steps, it's now time to test to see if everything works. 

  1. Standard Ansys Client - launch and run your Ansys software to insure it can pull a license.  
  2. BYOL Test -  submit a very small job to the cloud.  Follow the instructions found here:
    1. https://ansyshelp.ansys.com/account/secured?returnurl=/Views/Secured/Cloud/v000/en/ans_cloud_compute/verify_conn.html
If something isn't working properly, either review the steps/settings above for accuracy and or utilize the following guide to troubleshoot communication. Testing Network Port Communication in the following article is a good place to start:

    HOW TO - Verify the Ansys Client Can Communicate With the License Server‍ 

Did you like this article?

Yes
No

1 out of 1 liked this article

Related Articles

HOW TO - Check Ansys License Server Version

HOW TO - Verify Licenses Can be Checked Out

HOW TO - Check & Repair Windows Installation

Popular Articles

INFO - Ansys Hardware Recommendations & Supported 3rd Party Software

Ansys Download & Installation Guide (Start Here!)

Ansys Troubleshooting Guide

ERROR - Hostid in the license file is not a valid hostid

Accessing the Ansys Customer Portal

Did you like this article?

Yes
No
Give feedback about this article

Can't find what you're looking for?

Contact Support

Recently Updated

  • HOW TO - Gather Ansys Diagnostic Logs
  • ERROR - Failover Feature 'Ansys electronics_desktop' is not available
  • ERROR - Switching Network Connections Checks Out Another License
  • Specifying an Ansys License Server
  • ERROR - Cannot Borrow a License
  • HOW TO - Gather License Server Host Info
  • ERROR - Electronics Desktop opens as Twin Builder or another Desktop Configuration
  • ERROR - Request name cfd_solve_level2 does not exist in the licensing pool (-15,10032)
  • HOW TO - Reset Your Ansys Profile Folder

General Inquiries & Sales:

(800) 566-9190

Info@SimuTechGroup.com

Contact Support

  • Software
  • Services
  • Case Studies
  • Ansys Training
  • Consulting
  • Technical Support
  • About SimuTech
  • Careers
  • Privacy

© 2021 SimuTech Group

Definition by Author

0
0
Expand

Thanks for your feedback!

How can we improve this article?

We're glad you liked the article!

What specifically did you like, so we can do that more!

Thanks for your time!

What feedback do you have for us?