Altova License Server Pain Points – Firewall Rules

Ok, so I recently came across this gotcha I wanted to share.

I needed to install Altova License Server 3.4 to handle concurrent licenses for one of their products, XMLSpy.  This seemed straightforward enough.

Altova License Server documentation says…

The firewall team will love this!
The firewall team will love this!

Obviously, the firewall team did not love the idea of “all sub-domains,” and insisted on a specific IP addy.  At first we tried the IP for altova.com.  The TTL was something ridiculous like 2 seconds, so they gave in and let us use URL rules.  However, this still was not working. So, they looked to see what wasn’t getting through, saw lic.altova.com was being blocked and opened it for me.

That got us a bit further along…

Altova License Server - Test Network Connectivity
Altova License Server – Test Network Connectivity

Unfortunately, the need for log.altova.com and link.altova.com wasn’t clear until we were communicating with lic.altova.com.

After opening only those three sub-domains, our License Server is happily communicating with the mothership.

Hopefully armed with this info I can save you the weeks of back and forth between the network team, Altova, and the therapist that it took to get this straightened out.