Product: ImportOmatic, List Management, FindOmatic, SegmentOmatic, RecordRadar, EventOmatic, ActionOmatic, QueryOmatic, ScoreOmatic, MergeOmatic, PostOmatic
Description: This solution describes the URL that applications call when attempting to validate a license
Description: This solution describes the URL that applications call when attempting to validate a license
Environment: All
Version: All
Answer:
When an Omatic application is accessed, it needs to "phone home" to look for updates and verify licensing. If it cannot reach our servers, it will not function.
The aforementioned call home (phone home) goes out on port 443 (secure). This type of traffic (application web call) on Port 443 is often blocked by network security applications and appliances. In the event that the call to the Omatic license server is blocked, an exception will need to be made in the security component that is blocking the connection request. Some of the areas this traffic may be blocked are: proxy servers, firewalls (local to the workstation, as well as network level), virus scanners (local and network), and routers.
Omatic applications call to this URL: https://subscriptionservices.omaticsoftware.com This URL points to Windows Azure services, therefore it will not have a static IP address. Depending on the your geographical location, and the Azure server loads, the resolving IP Address may be different every time it is called. As a result, IT administrators will need to allow the traffic through by name. Like the other cloud services Microsoft publishes a list of IP addresses for its services but warns they can be changed at any time without notice: https://www.microsoft.com/en-us/download/details.aspx?id=41653
Version: All
Answer:
When an Omatic application is accessed, it needs to "phone home" to look for updates and verify licensing. If it cannot reach our servers, it will not function.
The aforementioned call home (phone home) goes out on port 443 (secure). This type of traffic (application web call) on Port 443 is often blocked by network security applications and appliances. In the event that the call to the Omatic license server is blocked, an exception will need to be made in the security component that is blocking the connection request. Some of the areas this traffic may be blocked are: proxy servers, firewalls (local to the workstation, as well as network level), virus scanners (local and network), and routers.
Omatic applications call to this URL: https://subscriptionservices.omaticsoftware.com This URL points to Windows Azure services, therefore it will not have a static IP address. Depending on the your geographical location, and the Azure server loads, the resolving IP Address may be different every time it is called. As a result, IT administrators will need to allow the traffic through by name. Like the other cloud services Microsoft publishes a list of IP addresses for its services but warns they can be changed at any time without notice: https://www.microsoft.com/en-us/download/details.aspx?id=41653
To determine if your connection to the Omatic Licensing server is being restricted follow the below steps.
1. Download the .zip file attached to this solution
2. Then extract the .zip file
3. Double click on "LicensingTester.exe"
4. Click "Test Subscription Service".
*If you see "Connection to Subscription Service successful, then your license is authenticated.
**If you see a long error stack, then whitelist this URL in your security application/appliance: https://subscriptionservices.omaticsoftware.com
In addition, configure the Windows Firewall to allow traffic on port 1433 for the SQL Server.