Re: Internal Licensing Error

On Monday 17 Jan 2011, Muñoz Díaz, Javier wrote:
> I've been looking around a bit, but I can't find a solution for this
> problem.
>
> I have some thin clients connecting to a Windows 2003 Terminal Server.
> When a client connects for first time, the TS gives it a temporary
> license, although the server has enough free per devices licenses.
>
> I've read that the client might save a license token somewhere under
> ~/.rdesktop, but this is not working.
>
> I've also read that this feature is actually not working, so I'm a bit
> confused. Does this folder need special permissions?
>
> When the temporary license ends, I cannot connect anymore, and have to
> reinstall the os on the thin clients, in order to make them work again.
>
> I know I could use the parameter to change the hostname in the rdesktop
> command, but I don't have very clear the legal implications of doing it.
>
> I'm using rdesktop v1.6, but I could change this version without problems.
>
> I can provide more info if needed.

If you are using a thin client system, e.g. LTSP, then the client's hostname 
is probably the thin client server's hostname, which will be the same for all 
users.  You should probably manually set the client's hostname in the 
rdesktop connection, e.g.

 $ rdesktop -n CLIENTHOSTNAME server.hostname

-- 
Chris Roberts

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl