Verified trial on a new machine is getting the same remaining days as diff machine (instead of a full trial)Solved

I am using verified trial. It appears to me that machines under the same LAN (i.e., using the same public IP) are sharing the same trial info. A newly activated machine gets the same remaining days as the first activated machine in the same LAN.

Is this expected, or am I doing something wrong?

If this is expected, is it possible to allow machines sharing the same public IP to have their own trial days?

Thanks!

, edited

TurboActivate doesn't use IP addresses at all as part of fingerprinting. At best IP addresses are interesting but useless information (they can be spoofed, re-routed, and inaccurate -- not to mention "duplicated" due to multiple devices behind a single IP).

We talk more about fingerprinting works in general: https://wyday.com/limelm/features/why/#hardware-locked-descr

>> "Is this expected, or am I doing something wrong?"

I don't know. A lot more information is needed. If you're just cloning a VM and TurboActivate sees the same computers as the same computers, then that's to be expected (and why we tell customers to disallow VM activations and instead use TurboFloat): https://wyday.com/limelm/help/vm-hypervisor-licensing/

Hi Wyatt,

I am still having the problem of new trial activations getting the same remaining days as the oldest activation (as described above). I have tried activating on a non-VM machine (never activated before) and activating inside a VM on another fresh machine. The problem persists with and without a VM. Note that I am using verified trail, and these machines are running Ubuntu 14.04 and 16.04.

From wyday dashboard, I don't see these new machines shown up as verified trials. Looks like it is either the license server decides that the machines have the same fingerprint, or my license activation code is screwing up??

Could you please shed some light on this issue? Could you check on your server to see why our recent trial activations are being determined as from the same machine?

We'll look into it next week. Are you using the latest version of TurboActivate? If not, do that first.

Thanks for the reply, Wyatt.

I am using the the latest version of TurboActivate.

Hi Wyatt,

Hope you had a great weekend.Just wonder if you have got a chance to look into this issue?

Best,

We're still digging into this.

Thanks Wyatt.Please feel free to let us know if more information is needed.

Hi Wyatt, is there any update on this issue?

We are approaching our product release and really hope to integrate TurboActivate into this release. Please feel free to let me know if there is anything that we can do to help you investigate the issue.

You help is much appreciated!

We see there's a problem and we're trying to figure out why it's happening and then deploying a fix. We should have more information later today / early tomorrow.

Good news, weve found and fixed the bug. It was a server-side problem where with certain Linux devices LimeLM incorrectly detected different devices as the same device. Weve removed all corrupted entries from our database and fixed the server-side code so that that doesnt happen anymore.

Thanks for reporting this!

Reply
Discard post