One of our customers recently implemented a new firewall product (ZScaler) and now their (already activated) installations of our product stopped working. They can contact https://wyday.com from Internet Explorer without problems and didn't have to set up any explicit firewall exceptions to do so.
In logs I can see that IsGenuineEx() returns 2, i.e. NotGenuine and a subsequent call to IsActivated() returns with TA_OK. In other words the activation server cannot be contacted and the grace period has expired.My application currently treats this as a temporary but fatal error, effectively disabling itself until the license can be validated again.
They are running on physical machines with Windows 8.1 (x64). Proxy use is forced to "auto-detect" via group policy. Nothing has changed regarding desktop firewall settings.
Temporarily bypassing the proxy allows the application to successfully validate the license, so the firewall/proxy definitely appears to be the culprit here.
If there was more to whitelist besides *.wyday.com:80 I assume you would already have mentioned it somewhere on the site or at least here in the forums, wouldn't you? I've already requested logs from the firewall as well as suggested running WireShark but maybe you already have an idea?Telling them to temporarily bypass the proxy every 90 days is obviously not a viable solution.
Cheers,
Oliver
More information is needed: https://wyday.com/limelm/help/faq/#useful-reports
Use the latest version of TurboActivate (currently 4.0.9.6). Also, whitelist https communication (wyday.com over 443), as described in the FAQ: https://wyday.com/limelm/help/faq/#internet-error
Probably just the crummy firewall blocking your app from outside communication.
Wyatt wrote:> More information is needed: https://wyday.com/limelm/help/faq/#useful-reports
OK, here's what was potentially missing:* Already using TurboActivate 4.0.9.6, 32bit* Reproducible on all machines on the customer's network
The rest was already in my post:* Windows 8.1, 64bit* IsGenuineEx() returns 2, while IsActivated() returns 0 (since 90 days interval + 14 days grace period have passed)
If you need any more information, please let me know.
> Also, whitelist https communication (wyday.com over 443), as described in the FAQ: https://wyday.com/limelm/help/faq/#internet-error
Yes, already confirmed. Access to wyday.com:443 was already working in Internet Explorer but they also explicitly whitelisted it anyway. No change.
> Probably just the crummy firewall blocking your app from outside communication.
Well, our "app" is a COM-Addin DLL for MS Outlook and the outlook.exe process is able to communicate fine over https (to an externally hosted Exchange Server instance) as it is... So I don't think it could be some sort of application/process-level restriction that could be doing this... Also, no changes have been made to the Windows (Desktop) Firewall settings and everything was working fine before they switched over the proxy/firewall.
As far as I can tell, they have already whitelisted everything that I was able to dig up either on the main site or here in the forums but it appears to not be enough...
Cheers,
Oliver
Well, it sounds like you've already narrowed it down to the Firewall. My advice is to stick with the built-in firewall in Windows (it's better than commercial offerings and it doesn't cost a penny).
Or, call the company that makes that firewall and ask them how to fix their broken product. Also, make sure you're using the latest "filters" and version of the Firewall. Using outdated filters on those products is as good as using no firewall at all.
