Yenka Activation and smoothwall

[kesomir]

I'm having trouble activating Yenka behind school guardian 2008.

 

using Windows XP SP3, with administrator accounts:

 

I put the code in, then select the proxy setup and enter the IP and port of the proxy, selecting http.

 

It then pops up a username and password box into which I have entered a variety of valid accounts.

 

Usually, it flashes the username and password box up again instantly, but sometimes gives the "Downloaded, but could not set the licence" error, which can be caused by incorrect login details.

 

I have whitelisted yenka.com

 

All to no avail. Can't activate. Any ideas? What am I missing?

[plexer]

What authentication settings do you have your smoothie on? ntlm?

 

Ben

[plexer]

What authentication settings do you have your smoothie on? ntlm?

 

Ben

[kesomir]

Was set to

 

NTLM Identification (Terminal Services compatibility mode)

 

Have just switched it over to

 

NTLM Authentication (Terminal Services compatibility mode)

 

to try that

 

EDIT: Which appears to work - cheers for the idea

[Sean]

I think we just by-passed smoothwall, activated on one machine, changed proxy settings back and made an image!

You could try exporting the registry either side of activating, do a compare and see if any obvious registry setting fall out, haven't tried it though and theres no garantee that it even uses the registry - could just modify an .ini somewhere...

*edit* actually I've just had a look and it seems that we ran a command to create a custom MSI that includes our license */edit*

Edited July 6, 2009 by Sean
Correcting info

[duncane]

I think we just by-passed smoothwall, activated on one machine, changed proxy settings back and made an image!

You could try exporting the registry either side of activating, do a compare and see if any obvious registry setting fall out, haven't tried it though and theres no garantee that it even uses the registry - could just modify an .ini somewhere...

*edit* actually I've just had a look and it seems that we ran a command to create a custom MSI that includes our license */edit*

 

Doesn't Yenka need to be continually connected to the net for the online files? Or does installing from the server download all the parts and serve it from there?

 

(Basically, we're in the same postion as kesomir, but before I swap from NTLM Identification to NTLM Authentication, I want to see if there's another way - largely to avoid any potential knock-on problems from switching.)

 

My admin account bypasses the proxy, so I've been able to install and activate the software. Its only when accessing the online files (the majority of the content) that there's this problem.