Ports and Remote URL Access Required for FARO Software
Overview
FARO® software uses a variety of remote and local resources (ports and URL/IP addresses). For FARO Software to function properly, access to the following addresses and ports are required. If you are having issues with running, installing, updating, or licensing FARO Software, ensure all hardware and software firewalls are allowing traffic to these locations.
For trouble-free use of your FARO software, a comprehensive list has been provided below.
Required! - FARO Licensing Manager and HASP Driver
The FARO Licensing Manager and HASP Driver is required by all FARO Software (except for FARO Connect). It is essential that your computer can communicate to the following URL/IP addresses and associated ports.
The FARO Licensing Manager uses port 6780 at the following URL/IP addresses (the connection is not encrypted):
- http://license.faro.com:6780
- http://13.69.27.89:6780
IPv6 Notes:
The FARO Licensing Manager uses IPv4 only. A translation of the FARO licensing system endpoint IPv4 address into IPv6 CIDR subnet is provided here:
- 0:0:0:0:0:ffff:d45:1b59/128 or, in extended format: 0000:0000:0000:0000:0000:ffff:0d45:1b59/128
HASP Driver
FARO uses the Sentinel HASP driver to provide product license keys for all FARO software, whether you use a dongle/portlock or a product license key that you type into the FARO software.
The Sentinel HASP driver uses the local communications port 1947 on your computer, example: http://localhost:1947
Software Specific
In addition to the Licensing Manager/HASP driver, some FARO software utilizes additional ports and URL/IP addresses as listed below. If a software package is not listed, it does not require any additional access.
FARO InTouch
FARO InTouch is a software distribution and management application which streamlines the downloading, installation, updating, and execution of FARO software. FARO InTouch requires access to the following URLs. An “known good” expected response is provided for each URL so access can be verified.
For more information on installation and troubleshooting, see: Download, Installation, and Troubleshooting for FARO InTouch
- Data Service URL: https://data-services.faro-cloud.com/api/health
- Expected Response:
- Expected Response:
- Files URL: https://files.faro-cloud.com/
- Expected Response:
- Expected Response:
- Setup URL: https://setups.faro-cloud.com/
- Expected Response:
- Expected Response:
- GateKeeper URL: https://gatekeeper.faro-cloud.com
- Expected Response:
- Expected Response:
FARO Zone
|
Newsfeed:
Product updates / Downloads:
Start Page:
Google Maps:
Bing Maps:
|
EagleView:
FARO Zone 3D Assets:
Help:
FARO Assist:
Sketchup / 3D warehouse:
|
SCENE
- Port 15975 is required for on-site registration with FocusS, FocusM, and FocusS Plus scanners
- Not necessary for operation, but for in-software version updates access to websharecloud.com is required
Sphere XG
Ports and endpoints that should be whitelisted to make sure all our products work correctly in your environment are listed below.
| US | EU |
|---|---|
|
|
The ports that need to be whitelisted in your firewalls for the HoloViewer, Navisworks and Revit plugins to work correctly are:
- Port 443 is used for all communication (HTTPS traffic) with our servers REST endpoints
- Port 8083 is used during the local session exchange between the browser and the desktop application on Windows and Mac after a successful login of the user
- Port 5677 and Port 5688 are used by our Navisworks & Revit plugin exe to communicate with Navisworks.exe / Revit.exe
FARO Connect
Unless otherwise stated “http” URLs use TCP port 80 and "https" URLs use TCP port 443.
SphereXG Authentication
- https://entry.holobuilder.com
- https://entry.holobuilder.eu
- https://entry.holobuilder.eu
- https://core.api.holobuilder.com
- https://core.api.holobuilder.eu
SphereXG Projects
- https://v2.project.api.holobuilder.com
- https://v2.project.api.holobuilder.eu
- https://core.api.holobuilder.com
- https://core.api.holobuilder.eu
License Activation/Refresh
- https://lc.codemeter.com
- https://geoslam.pointcab-software.com/
GeoSLAM Draw
- https://geoslam.pointcab-software.com/
As-Built
Depending on the security policies in place, reported problems in many cases be resolved by "whitelisting" (adding an exclusion rule) for the appropriate installation and data folders in the endpoint security software. Please find below a list of the default installation and data folders relevant for whitelisting. These locations may need to be adapted for customized product installation folders.
Candidate folders for security whitelist:
- %PROGRAMFILES%\FARO
- %USERPROFILE%\AppData\Roaming\FARO
- %USERPROFILE%\AppData\Local\FARO
Please note that product-specific exclusions are possible:
FARO SCENE & As-Built products default installation folder:
- %PROGRAMFILES%\FARO\FARO_PRODUCT_NAME
The As-Built for AutoCAD and As-Built for Revit add-ins may require an exclusion for Autodesk host products:
- %PROGRAMFILES%\Autodesk\AUTODESK_PRODUCT_NAME
- %USERPROFILE%\AppData\Roaming\Autodesk
- %USERPROFILE%\AppData\Local\Autodesk
Note: FARO_PRODUCT_NAME and AUTODESK_PRODUCT_NAME are placeholders, typically including specific version and language information.