I've searched, and the onlly response from KEMP is to try from a computer directly connected to the internet. We don't have those...they're called security risks.
The test messages in the web GUI says that it's resolving an FQDN for a licensing server. Then it's attempting a connection to an IP address that matches what is resolved for the FQDN.
How are you making this connection? HTTPS? By FQDN or IP address?
If you have an answer, will you post it for the public to read. It will make troubleshooting easier. If we need to poke holes in content filters, we can do that. But, only if we know what the hole is supposed to look like.
In the meantime, I can't find a way for the web GUI to work without going through this licensing routine. Am I locked out of product usage until this is fixed?