Intergraph Smart Licensing

Network Connectivity Guide

Version 14.2 Update 1
April 2023
Copyright
Copyright © 2018-2023 Intergraph Corporation and/or its subsidiaries and affiliates. All rights reserved.
This computer program, including software, icons, graphic symbols, documentation, file formats, and audio-visual displays; may be
used only as pursuant to applicable software license agreement; contains confidential and proprietary information of Intergraph
Corporation or a Hexagon Group Company and/or third parties which is protected by patent, trademark, copyright law, trade secret law,
and international treaty, and may not be provided or otherwise made available without proper authorization from Hexagon AB and/or its
subsidiaries and affiliates.
Portions of the user interface copyright © 2018-2023 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights
Reserved.

U.S. Government Restricted Rights Legend

Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was developed
at private expense and is "restricted computer software" submitted with restricted rights in accordance with subparagraphs (a) through
(d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal Acquisition Regulations ("FAR") and
its successors, and is unpublished and all rights are reserved under the copyright laws of the United States. For units of the Department
of Defense ("DoD"): This is "commercial computer software" as defined at DFARS 252.227-7014 and the rights of the Government are
as specified at DFARS 227.7202-3.
Unpublished - rights reserved under the copyright laws of the United States.
Intergraph Corporation, Hexagon's Asset Lifecycle Intelligence Division
305 Intergraph Way
Madison, AL 35758

Documentation
Documentation shall mean, whether in electronic or printed form, User's Guides, Installation Guides, Reference Guides,
Administrator's Guides, Customization Guides, Programmer's Guides, Configuration Guides and Help Guides delivered with a
particular software product.

Other Documentation
Other Documentation shall mean, whether in electronic or printed form and delivered with software or on Smart Community,
SharePoint, box.net, or the Hexagon documentation web site, any documentation related to work processes, workflows, and best
practices that is provided by Hexagon as guidance for using a software product.

Terms of Use
a. Use of a software product and Documentation is subject to the Software License Agreement ("SLA") delivered with the software
product unless the Licensee has a valid signed license for this software product with Intergraph Corporation, Hexagon’s Asset
Lifecycle Intelligence Division ("Hexagon"), a Hexagon Group Company. If the Licensee has a valid signed license for this
software product with Hexagon, the valid signed license shall take precedence and govern the use of this software product and
Documentation. Subject to the terms contained within the applicable license agreement, Hexagon gives Licensee permission to
print a reasonable number of copies of the Documentation as defined in the applicable license agreement and delivered with the
software product for Licensee's internal, non-commercial use. The Documentation may not be printed for resale or redistribution.
b. For use of Documentation or Other Documentation where end user does not receive a SLA or does not have a valid license
agreement with Hexagon, Hexagon grants the Licensee a non-exclusive license to use the Documentation or Other
Documentation for Licensee’s internal non-commercial use. Hexagon gives Licensee permission to print a reasonable number of
copies of Other Documentation for Licensee’s internal, non-commercial use. The Other Documentation may not be printed for
resale or redistribution. This license contained in this subsection b) may be terminated at any time and for any reason by Hexagon
by giving written notice to Licensee.
Disclaimer of Warranties
Except for any express warranties as may be stated in the SLA or separate license or separate terms and conditions, Hexagon
disclaims any and all express or implied warranties including, but not limited to the implied warranties of merchantability and fitness for
a particular purpose and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or
amendment of such disclaimer. Hexagon believes the information in this publication is accurate as of its publication date.
The information and the software discussed in this document are subject to change without notice and are subject to applicable
technical product descriptions. Hexagon is not responsible for any error that may appear in this document.
The software, Documentation and Other Documentation discussed in this document are furnished under a license and may be used or
copied only in accordance with the terms of this license. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL
EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.

Intergraph Smart Licensing Network Connectivity Guide 2

Hexagon is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data. Users
should verify for themselves that the data is accurate and suitable for their project work.

Limitation of Damages
IN NO EVENT WILL HEXAGON BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL INCIDENTAL, SPECIAL, OR
PUNITIVE DAMAGES, INCLUDING BUT NOT LIMITED TO, LOSS OF USE OR PRODUCTION, LOSS OF REVENUE OR PROFIT,
LOSS OF DATA, OR CLAIMS OF THIRD PARTIES, EVEN IF HEXAGON HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
UNDER NO CIRCUMSTANCES SHALL HEXAGON'S LIABILITY EXCEED THE AMOUNT THAT HEXAGON HAS BEEN PAID BY
LICENSEE UNDER THIS AGREEMENT AT THE TIME THE CLAIM IS MADE. EXCEPT WHERE PROHIBITED BY APPLICABLE
LAW, NO CLAIM, REGARDLESS OF FORM, ARISING OUT OF OR IN CONNECTION WITH THE SUBJECT MATTER OF THIS
DOCUMENT MAY BE BROUGHT BY LICENSEE MORE THAN TWO (2) YEARS AFTER THE EVENT GIVING RISE TO THE CAUSE
OF ACTION HAS OCCURRED.
IF UNDER THE LAW RULED APPLICABLE ANY PART OF THIS SECTION IS INVALID, THEN HEXAGON LIMITS ITS LIABILITY TO
THE MAXIMUM EXTENT ALLOWED BY SAID LAW.

Export Controls
To the extent prohibited by United States or other applicable laws, Intergraph Corporation, Hexagon's Lifecycle Intelligence division
("Hexagon"), and a Hexagon Group Company's commercial-off-the-shelf software products, customized software, Technical Data,
and/or third-party software, or any derivatives thereof, obtained from Hexagon, its subsidiaries, or distributors must not be exported or
re-exported, directly or indirectly (including via remote access) under the following circumstances:
a. To Cuba, Iran, North Korea, Syria, or the Crimean, "Donetsk People's Republic", "Luhansk People's Republic," or Sevastopol
regions of Ukraine, or any national of these countries or territories.
b. To any person or entity listed on any United States government denial list, including, but not limited to, the United States
Department of Commerce Denied Persons, Entities, and Unverified Lists, the United States Department of Treasury Specially
Designated Nationals List, and the United States Department of State Debarred List. Visit www.export.gov for more information or
follow this link for the screening tool: https://legacy.export.gov/csl-search https://legacy.export.gov/csl-search.
c. To any entity when Customer knows, or has reason to know, the end use of the software product, customized software, Technical
Data and/or third-party software obtained from Hexagon, its subsidiaries, or distributors is related to the design, development,
production, or use of missiles, chemical, biological, or nuclear weapons, or other un-safeguarded or sensitive nuclear uses.
d. To any entity when Customer knows, or has reason to know, that an illegal reshipment will take place.
Any questions regarding export/re-export of relevant Hexagon software product, customized software, Technical Data, and/or
third-party software obtained from Hexagon, its subsidiaries, or distributors, should be addressed to Hexagon’s Export Compliance
Department, 305 Intergraph Way, Madison, Alabama 35758 USA or at exportcompliance@intergraph.com. Customer shall hold
harmless and indemnify Hexagon and a Hexagon Group Company for any causes of action, claims, costs, expenses and/or damages
resulting to Hexagon or a Hexagon Group Company from a breach by Customer.

Trademarks
Intergraph®, the Intergraph logo®, Intergraph Smart®, SmartPlant®, SmartMarine, SmartSketch®, SmartPlant Cloud®, PDS®,
FrameWorks®, I-Route, I-Export, ISOGEN®, SPOOLGEN, SupportManager®, SupportModeler®, SAPPHIRE®, TANK, PV Elite®,
CADWorx®, CADWorx DraftPro®, GTSTRUDL®, CAESAR II® , and HxGN SDx® are trademarks or registered trademarks of Intergraph
Corporation or its affiliates, parents, subsidiaries. Hexagon and the Hexagon logo are registered trademarks of Hexagon AB or its
subsidiaries. Other brands and product names are trademarks of their respective owners. Microsoft and Windows are registered
trademarks of Microsoft Corporation. Other brands and product names are trademarks of their respective owners.

Intergraph Smart Licensing Network Connectivity Guide 3

 Preface

Contents
Preface .......................................................................................................................................................... 5

When to Use This Guide ............................................................................................................................. 6

Network Connection Settings for Smart Licensing Client ...................................................................... 7

Make exceptions or whitelist Smart Licensing aliases ............................................................................ 7
Port assignments for Smart Licensing .................................................................................................... 8

Troubleshooting Connectivity.................................................................................................................. 10
Check LAN or Wi-Fi connectivity .......................................................................................................... 10
Check proxy settings on the computer ................................................................................................. 10
Update user for proxy authentication ............................................................................................. 12
Connectivity issues with licensing ......................................................................................................... 12
Other troubleshooting tips ..................................................................................................................... 13

APPENDIX A: Smart Licensing Server Whitelisting Methods............................................................... 14

Use DNS names in place of IP addresses when possible .................................................................... 14
Include DNS names in web filtering and DNS filtering policies ............................................................ 14
Add Smart Licensing server IP addresses to IP-based firewalls .......................................................... 15

Index ........................................................................................................................................................... 16

Intergraph Smart Licensing Network Connectivity Guide 4

Preface
This document provides information about information about connecting to Intergraph Smart®
Licensing. The intended audience for this document is network or IT administrators who need to
learn about settings or troubleshoot possible connection issues.

Intergraph Smart Licensing Network Connectivity Guide 5

SECTION 1

When to Use This Guide

Use this guide when you need to learn more about settings in Smart Licensing Client or need to
troubleshoot issues. For example, if you might encounter the following:

 Loading a configuration connection info file shows an error connecting to the

configuration server. This can happen during or after installing Smart Licensing Client.

 Services on the Status tab in Smart Licensing Client show an error .

Intergraph Smart Licensing Network Connectivity Guide 6

SECTION 2

Network Connection Settings for Smart

Licensing Client
The following section provides more details about connection settings for Smart Licensing Client.

Make exceptions or whitelist Smart Licensing aliases

If your company uses a network device to restrict web traffic, ensure that the following target
aliases for Smart Licensing are listed as exceptions (whitelisted):
 https://licensing.hexagonppm.com
 https://identity.hexagonppm.com
 https://ppm-licensingserver-eastus-cust.hexagonsmartlicensing.com
 https://ppm-licensingserver-euro-cust.hexagonsmartlicensing.com
 https://ppm-licensingserver-apac-cust.hexagonsmartlicensing.com
 https://ppm-licensingconfigserver-prod.hexagonsmartlicensing.com
 https://ppm-licensingtelemetry.servicebus.windows.net
 https://sadsrouter.hexagonppm.com
 https://ppm-clientsds-cust.hexagonsmartlicensing.com
 https://clientsdscust.file.core.windows.net
 https://clientsdscust2.file.core.windows.net
 https://ppm-telemetrywebapi-prod.hexagonsmartlicensing.com
 Disasterserver-cust.hexagonsmartlicensing-alt.com

 You must be able to access the URLs and websites listed above using a web browser from
the Intergraph Smart Licensing Client machines.
 You must be able to access any path or endpoint at
https://ppm-clientsds-cust.hexagonsmartlicensing.com.
 For more information on whitelisting methods, see APPENDIX A: Smart Licensing Server
Whitelisting Methods (page 14).
To view online documentation, ensure that docs.hexagonali.com and
hexagonppm.fluidtopics.net are accessible.

Intergraph Smart Licensing Network Connectivity Guide 7

 Network Connection Settings for Smart Licensing Client

Port assignments for Smart Licensing

This table lists the ports used by default for communications between Smart Licensing Client and
Smart Licensing Server in the cloud.
This port must be open for outgoing communication from Smart Licensing Client computers, as
well as from the computers where Smart Licensing Portal is accessed.

Port TCP/UDP Communication Comments

Number

443 TCP From client to Standard HTTPS port. Must be open to:
server
 https://licensing.hexagonppm.com
 https://identity.hexagonppm.com
 https://ppm-licensingserver-eastus-cust.
hexagonsmartlicensing.com
 https://ppm-licensingserver-euro-cust.h
exagonsmartlicensing.com
 https://ppm-licensingserver-apac-cust.h
exagonsmartlicensing.com
 https://ppm-licensingconfigserver-prod.h
exagonsmartlicensing.com
 https://ppm-licensingtelemetry.serviceb
us.windows.net
 https://sadsrouter.hexagonppm.com
 https://ppm-clientsds-cust.hexagonsmar
tlicensing.com
 https://clientsdscust.file.core.windows.n
et
 https://clientsdscust2.file.core.windows.
net
 https://ppm-telemetrywebapi-prod.hexa
gonsmartlicensing.com
 Disasterserver-cust.hexagonsmartlicens
ing-alt.com

Intergraph Smart Licensing Network Connectivity Guide 8

 Network Connection Settings for Smart Licensing Client

Port TCP/UDP Communication Comments

Number

8088 TCP From product to By default, this port is used for local
client communication on the Smart Licensing
Client. However, you can also use a custom
port that is set while installing Intergraph
Smart Licensing Client software. For more
information, see Install the licensing client
software in Intergraph Smart Licensing
Installation and Setup Guide.

 You must be able to access the URLs and websites listed above using a web browser from
the Intergraph Smart Licensing Client machines.
 You must be able to access any path or endpoint at
https://ppm-clientsds-cust.hexagonsmartlicensing.com.
 For more information on whitelisting methods, see APPENDIX A: Smart Licensing Server
Whitelisting Methods (page 14).

 The URLs that can be browsed from anywhere with Smart Licensing Portal using a web
browser are:
 licensing.hexagonppm.com
 identity.hexagonppm.com
 To view online documentation, ensure that docs.hexagonali.com and
hexagonppm.fluidtopics.net are accessible.
 Some products might not be compatible with custom port installation. For more information
see the Frequently Asked Questions (FAQs) in the Intergraph Smart Licensing Help.

Intergraph Smart Licensing Network Connectivity Guide 9

SECTION 3

Troubleshooting Connectivity
Here are some things to check when troubleshooting connectivity.

Check LAN or Wi-Fi connectivity

 Open Network and Sharing Center from Control Panel.
If the computer does not have LAN or Wi-Fi network capabilities, it will not be able
to connect to Smart Licensing cloud services.

Check proxy settings on the computer

For more information on how to install in a proxy environment using the
software or a silent install, see the Intergraph Smart Licensing Installation and Setup.
Check the proxy settings. This can be done in Internet Explorer, Chrome, or in Windows. If the
proxy settings are set but Smart Licensing Client still cannot reach the cloud services, you might
need to use a proxy.config file for Smart Licensing Client to use the correct proxy settings.
The proxy.config file is a JSON file that tells Smart Licensing Client what the proxy settings for the
environment are. The file should be placed in the Smart Application Data Service directory in the
ProgramData directory. For example, browse to <drive>:\ProgramData\Smart Application Data
Service\.
The proxy.config file has different contents based on what type of proxy settings need to be
passed to Smart Licensing Client. These types correspond to the various ways to specify a proxy
using Internet Explorer, Chrome, or Windows.

Proxy options
The following describes different proxy options.
 Autodiscovery mode - The first option is to specify that Smart Licensing Client should use
Autodiscovery mode. This is equivalent to checking the Automatically detect settings box in
the Windows proxy settings. For the proxy settings to be autodiscoverable, they must be set
up to use WPAD. A proxy.config file specifying that Smart Licensing Client should use
autodiscovery mode looks like the following:
{
"proxyType": "autodiscovery"
}
 Proxy AutoConfig (PAC) script - The next type of proxy settings that can be specified by a
proxy.config file is a Proxy AutoConfig (PAC) script, which is equivalent to checking the Use
setup script box in the Windows proxy settings and giving the PAC script URL. To specify
that Smart Licensing Client use a PAC script to get the proxy settings, the proxy.config file
looks like the following:

Intergraph Smart Licensing Network Connectivity Guide 10

 Troubleshooting Connectivity

{
"proxyType": "pacfile",
"pacFileUrl": "http://business.business/proxy.pac"
}
 Manual mode - The third type of proxy settings is a manual proxy setup. This is equivalent to
checking the Use a proxy server box under the Manual Proxy Setup section of the Windows
proxy dialog. You must specify an address and a port for the proxy server with this type of
proxy settings. To configure Smart Licensing Client to use a manual proxy with the
proxy.config file, the file should look like the following:
{
"proxyType": "Manual",
"manualProxyAddress": "10.3.1.4",
"manualProxyPort":3128
}
 No proxy - A fourth option under the proxy settings is "No Proxy". This is equivalent to having
no boxes checked under the Windows proxy dialog. It is generally not necessary to specify
that there is no proxy being used in the proxy.config file, but in rare circumstances setting this
value manually can resolve connectivity issues with ISL. The proxy.config file with no proxy
set looks like the following:
{
"proxyType":"none"
}
 Proxy Refresh Interval - The Smart Licensing Client retrieves the proxy settings regularly. By
default, this value is set to sixty minutes. If your environment requires a more frequent refresh
interval, you can configure it by specifying the Proxy Refresh Interval in the proxy.config file.
The Proxy Refresh Interval is specified in minutes, and valid values are any integer between
0 and 60. A value of 0 specifies that Smart Licensing Client should retrieve the proxy settings
on every outgoing call that it makes. The Proxy Refresh Interval can be specified
independently or in conjunction with any other proxy option.
For example, a proxy.config file that only specifies the Proxy Refresh Interval will look like
the following:
{
"proxyRefreshInterval": 45
}
To specify the Proxy Refresh Interval in conjunction with specifying a proxy, add the Proxy
Refresh Interval field to the proxy.config file, like so:
{
"proxyType": "autodiscovery",
"proxyRefreshInterval": 45
}

Intergraph Smart Licensing Network Connectivity Guide 11

 Troubleshooting Connectivity

Update user for proxy authentication

If your proxy requires authentication, you must change the Intergraph Smart Licensing Client and
Intergraph Smart Application Data Services Processor services to run as a user able to
authenticate with the proxy.
1. Open the Control Panel, and then double-click Administrative Tools.
2. In the Administrative Tools window, double-click Services.
3. Right-click Intergraph Smart Licensing Client, and then select Properties from the shortcut
menu.
4. In the Service status section, click Stop.
5. On the Log On tab, select This account, and then type the user name.
6. In the Password and Confirm password boxes, type the password for the user account that
can authenticate with the proxy, and then click Apply.
7. In the Service status section, click Start, and then click OK.
8. Repeat steps 3-7 for Intergraph Smart Application Data Services Processor.

Connectivity issues with licensing

1. Open Network and Sharing Center from the Control Panel, and make sure the computer
has LAN or Wi-Fi capabilities.
2. Check the proxy settings in Windows. Smart Licensing Client uses these settings to connect
to the Smart Licensing cloud services.
For more information, see Check proxy settings on the computer in the Intergraph Smart
Licensing Network Connectivity Guide.
3. If your company uses a network device to restrict web traffic, ensure that the target aliases are
listed as exceptions or whitelisted.
4. Ensure that you can connect to the Smart Licensing cloud resources using an internet
browser. You can do this by testing your connection to our configuration server. Access to this
resource is required to load a configuration in the Smart Licensing Client, which is a
prerequisite for pulling and returning licenses.
This can be done by visiting the URL
https://ppm-licensingconfigserver-prod.hexagonsmartlicensing.com/configserver/ping in any
major web browser.
If the request returns a JSON object, you are successfully communicating with the Smart
Licensing cloud resources. If it returns a corporate error page or "You do not have permission
to view this directory or page" error, it might be necessary to whitelist the proper URLs or ports
for your network. Your corporate IT department will have more information about how to do
this.
5. If your network is using a proxy, and you have configured Smart Licensing to use that proxy
but are still unable to load a configuration or successfully resolve any resources using the
Status tab in the Smart Licensing Client, the proxy might require authentication. For more
information, see Update user for proxy authentication in the Intergraph Smart Licensing
Network Connectivity Guide.

Intergraph Smart Licensing Network Connectivity Guide 12

 Troubleshooting Connectivity

6. If your network does not have a proxy implemented but you are still experiencing connectivity
issues, it might help to specify a proxyType of "none" in the proxy.config file. For more
information, see Check proxy settings on the computer in the Intergraph Smart Licensing
Network Connectivity Guide.
The Intergraph Smart Licensing Network Connectivity Guide is available on:
 Smart Community https://smartcommunity.hexagonppm.com, from where you download
the latest version of the document.
 Help folder of the setup location. For example, [Setup
Location]\ISL14.1-Update14\14.01.14.0157\Help.
 Smart Licensing client workstations. For example, C:\Program Files\Intergraph Smart
Licensing\Client\Help\PDFs.

Other troubleshooting tips

 Ensure that port 443 is open.
 Make sure the required DNS names are open in port 443. For a list of sites, see Port
assignments for Smart Licensing (page 8).

Intergraph Smart Licensing Network Connectivity Guide 13

APPENDIX A

APPENDIX A: Smart Licensing Server

Whitelisting Methods
Intergraph Smart Licensing Client must be able to communicate with Smart Licensing servers
hosted in the cloud and deployed to various regions around the world. These servers are
necessary for the Intergraph Smart Licensing Client to request new licenses, return licenses,
exchange data, and perform various actions that are critical to the Hexagon software.
You must configure web gateways, firewalls, and proxies to allow Smart Licensing traffic to pass
through so you can use Intergraph Smart Licensing. This section provides you with a brief
overview of the three most common methods for creating exclusion lists or whitelists (whitelisting)
for Intergraph Smart Licensing network traffic at a customer site. This information will contribute to
the successful onboarding of new Intergraph Smart Licensing customers.

Use DNS names in place of IP addresses when

possible
Currently, Smart Licensing uses dynamic IP addresses on all of our cloud-based infrastructure.
This means that the IP addresses of the Smart Licensing servers could change in certain
scenarios, such as during an outage or a disaster triggered failover. This is done as part of a
strategy that prioritizes flexibility, maximum uptime, and business continuity.
However, when configuring access to Intergraph Smart Licensing servers, we encourage the use
of DNS names in place of IP addresses, if at all possible. This is because IP addresses are finite
and sometimes previously ‘good’ IP addresses could be reused by malicious actors. Using DNS
names ensures that the whitelists do not become outdated over time due to changes in the IP
addresses of services, and ensures our ability to provide you with the best, and most robust
experience possible.

 For the current list of DNS names, see Network Connection Settings for Smart Licensing
Client (page 7).
 Hexagon does understand that using DNS names is not always possible, as some firewalls
only allow the use of IP-based restrictions or exclusions.

Include DNS names in web filtering and DNS filtering

policies
Appliance or software-based web security gateways and web proxy servers protect client
computers by employing techniques such as IP whitelisting, IP backlisting, web content filtering,
and DNS filtering. These procedures combine together to protect the system from internet-based
attacks, as well as prevent access to unauthorized internet sites.

Intergraph Smart Licensing Network Connectivity Guide 14

 APPENDIX A: Smart Licensing Server Whitelisting Methods

 Web filtering - Works by inspecting the URL in the GET request and acts directly on the
HTTP/HTTPS traffic. When you use HTTPS, web filtering checks the certificate subject/SAN
and SNI fields from the client hello to decide what action to take.
 DNS filtering - Precedes the HTTP/HTTPS connection attempts and acts on the DNS
queries. This allows you to restrict or control access based on the name of the server in the
DNS query or the name of the server that the URL is attempting to access.
If your company or site uses any of these technologies, you must add rules to ensure
that the Smart Licensing Client can access the necessary cloud-based licensing servers.

Add Smart Licensing server IP addresses to IP-based

firewalls
IP Whitelisting - allows access to a specific IP address or range of IP addresses that are trusted
from within a network or domain.
IP Blacklisting - blocks access to a specific IP address or range of IP addresses.
IP address-based rules are usually entered by adding a unique IP address or a range of IP
addresses to the configuration of the firewall. For example, 192.168.0.1 or CIDR format -
192.168.0.1/24 respectively. You can enter these rules with or without specific ports depending on
the platform.
When using IP whitelisting, you must enter the current IP addresses of the Smart Licensing
servers into your firewall configuration. You must also have the IP addresses of the backup Smart
Licensing servers to ensure your client continues to operate during a disaster triggered failover to
our backup Smart Licensing server sites.
Intergraph Smart Licensing recommends that you use DNS names instead of IP addresses, see
Use DNS names in place of IP addresses when possible (page 14) and Include DNS names in
web filtering and DNS filtering policies (page 14).

 You should control web traffic using web filtering, spam filtering, and/or DNS filtering to restrict
all access to specific addresses in addition to any hardware or software-based firewalls.
 If you are required to specify a port when configuring a proxy, gateway, or firewall, you should
use TCP port 443. Intergraph Smart Licensing Client communicates using HTTPS on TCP
port 443.
 If you use IP-based rules, you must pay constant attention to the exclusion lists to prevent
obsolete addresses from being accessed, such as when machines become compromised or
IP addresses are reused.
 Whenever you configure IP-based restrictions, please contact support to get the latest list of
IP addresses.

Intergraph Smart Licensing Network Connectivity Guide 15

Index

A
Add Smart Licensing server IP addresses to
IP-based firewalls • 15
APPENDIX A
Smart Licensing Server Whitelisting
Methods • 14

C
Check LAN or Wi-Fi connectivity • 10
Check proxy settings on the computer • 10
Connectivity issues with licensing • 12

I
Include DNS names in web filtering and DNS
filtering policies • 14

M
Make exceptions or whitelist Smart
Licensing aliases • 7

N
Network Connection Settings for Smart
Licensing Client • 7

O
Other troubleshooting tips • 13

P
Port assignments for Smart Licensing • 8
Preface • 5

T
Troubleshooting Connectivity • 10

U
Update user for proxy authentication • 12
Use DNS names in place of IP addresses
when possible • 14

W
When to Use This Guide • 6

Intergraph Smart Licensing Network Connectivity Guide 16