I have a customer who is using our software with TurboActivate on a corporate network.
If he activates via Wi-Fi (to bypass his proxy server), it's fine. The moment that he enables (not just connects) his Wi-Fi adapter, it prompts for a key again.
What are the circumstances in which TurboActivate would deactivate a product?
My guess is he also disables (a.k.a. stops the component from "existing") whatever normal network adapter, correct? Tell him to not do that. Using a new network connection won't cause any problems. "Disabling" (and/or removing) an existing network connection will cause problems.
Also, make sure you're using the latest version of TurboActivate (currently 3.4.6) and that the customer is using a version of your app that uses that latest version of TurboActivate.
Hey Wyatt,
I sought out some clarification; he isn't disabling his ethernet adapter, just disconnecting it to force the connection over Wi-Fi.
We are using 3.4.6 in our latest release, which he has.
What circumstances will cause TurboActivate to deactivate? I can email you directly if that is better.
disabling his ethernet adapter, just disconnecting it
Physically disconnecting the adapter? If so, then that's the problem. Don't do that. Unplugging the ethernet cable is fine, though.
Also, what operating system is he running on? TurboActivate uses different fingerprint methods for different operating systems.
