"over secure" customer networks

Good morning,Some advice if possible please...We're now a good few months into using LimeLM/WyUpdate in our application and for the majority of people this license/auto-update combination works really well. But for the unlucky few... Who unfortunately tend to be in the Far East thus presenting language and time barriers.We notice that they cannot activate the license; something (firewall, or whatever) stops them.*Sometimes* the TurboActivate.EXE is allowed - it works. But our code doesn't; it's blocked (so even if TurboActivate works we can't verify the license from our code).What's the difference between our code and TurboActivate?TurboActivate is code-signed; we're just getting that organised for our code.But are there any other differences? As in when we call the activation functions from within our code will a firewall/anti-virus see things differently wrt how they appear from TurboActivate? I vaguely remember something about TurboActivate "appearing like Internet Explorer" ? What are the differences (if any) between us calling the API functions to verify or license compared to getting the TurboActivate.EXE to do the work?Sorry if grasping at straws but this is confusing us!Thanks,Dr. Michael Dye,

What's the difference between our code and TurboActivate?

Nothing. It's probably a local firewall blocking your app. Is your app code-signed? If not, do that. Also, tell them to whitelist your app in whatever firewalls they're using.

TurboActivate is code-signed; we're just getting that organised for our code.

OK. Yeah, do that.

I vaguely remember something about TurboActivate "appearing like Internet Explorer" ?

It doesn't appear like Internet Explorer.

What are the differences (if any) between us calling the API functions to verify or license compared to getting the TurboActivate.EXE to do the work?

None. They both use TurboActivate.dll

Thanks for the quick reply; we've just completed the implementation of a code-signing certificate (boy, was that a fun bit of learning!) and updated the application... We'll let you know if that solves the problems.By the way that'll also be the new TurboActivate that should work with Surface Pro's too so we'll check that out by removing the VM flag...Thanks,Dr. Michael Dye.