Am still connecting to the old Kemp licensing server with new image?


9 comments

Avatar

ete wee

image is - LoadMaster-VLM-7.2.54.1.20759.RELEASE-Linux-KVM-XEN-FREE.disk

0

Avatar

Nick Smylie

The correct server for that one would be licensing.kemp.ax.  Any version above 7.2.53 will use that server.

Something is probably blocking communication to that server within your network.

0

Avatar

ete wee

thanks for the quick reply. will it be 80/443 to licensing.kemp.ax?

0

Avatar

Nick Smylie

Only 443

0

Avatar

ete wee

doesnt seem to be working.

 

configured any/any on FW, move it before the firewall by physical cable bypassing the firewall entirely. it does not work. it is not the firewall. another windows laptop configured with the same IP with kemp shutdown behind the firewall and in front bypassing the firewall, i can ping, i can telnet to 52.166.52.190 at port 443. any other ideas please?

0

Avatar

Nick Smylie

Hi,

Looking into this a bit more something is not right.  You are trying to license units that have serial numbers attached to them already.  You have 2 units that were licensed on 23 of Jun and and 18th of Aug.

Are you doing something to these units after initial licensing?  Please make sure the MAC address does not change, if that changes, the license breaks.

It may be best to start from scratch with a new image.

https://freeloadbalancer.com/

0

Avatar

ete wee

is there a limit to the number of license per email address?

0

Avatar

Nick Smylie

Hi,

No there is not.  Our records show that you keep trying to licensing a unit already licensed.  It almost look like you keep breaking the units license, unintentional of course but something is happening with it.  Every request I see that comes in says its been licensing already.  You cannot license a unit that has been given a Free license already.

0

Avatar

ete wee

thanks for checking the logs. the multi clicks was generating this error and testing to see if it goes away:

Connection to Licensing Server: (52.166.52.190 - Failed)

anyway, the error seemed to have gone away for now and have placed kemp back to behind the firewalls. Will keep a lookout.

0

Please to leave a comment.

Didn't find what you were looking for?