PlanSwift requires communication via the Internet to activate licenses. Users must Users may need to configure their networks appropriately or activation will may fail. Communication is initiated from the client software (PlanSwift) to the Internet resource via the TCP protocol. Our servers never initiate communications from the Internet resource into your internal network; both IPv4 and IPv6 are supported.
| Note |
|---|
It is not possible to license PlanSwift without an Internet connection. |
...
Access to these Internet resources may require you to modify your network (including software and hardware) firewall. Our solutions are built for enterprise systems by only requiring outbound TCP access (the firewall handles the incoming response). This minimizes security risks and should meet most IT security requirements.
PlanSwift does not provide specific instructions on how to set up or modify firewalls because there is a multitude of firewall solutions on the market and each is set up differently. We provide the following information so that clients can configure their own firewall solutions or forward this article to a qualified IT professional for implementation.The tables below include all the firewall configuration information required to run PlanSwift
During installation, Planswift adds Inbound rules to Windows Defender for TCP and UDP. This should cover most average installation environments:
...
If your environment restricts network communication or utilizes a 3rd party Firewall, you or your IT department may need to make further adjustments to allow PlanSwift to communicate with the web servers.
Domains (Recommended)
Caution
| Note |
|---|
Do not configure firewalls to a specific IP addressaddresses, use the DNS Name only. |
DNS Name | Port Numbers |
|---|---|
*.planswift.com |
80, 443 | |
*.constructconnect.com | 80, 443 |
*.swiftnet.com | 80, 443 |
*.aptrinsic.com. | 80, 443 |
Firewall Exceptions
The following executable must be added as exceptions to local and network firewalls:
PlanSwift.exe (installed to C:\Program Files (x86)\PlanSwift10)
Multiple Firewall Locations
Some organizations employ several layers of firewalls that can potentially block communication to or from a workstation or the server on which Enterprise License Server is installed, preventing licensing or features to work. The list below is not all-inclusive but should give you an idea of where to check for firewalls that could be causing issues:
Windows Server OS FirewallClient Desktop Firewall (Windows Defender)
Windows Client Desktop Server OS Firewall
Virtual Server OS Firewall
3rd Party Firewall/Filters Applications local to the Server
3rd Party Firewall/Filters Applications local to the Client
Any Physical Hardware-based Network Appliances/VPN/DMZ or Network Filters that can permit/refuse traffic or add latency to the connection
...