Re: tunneling windows terminal services via ssh - licensing error message

chad_at_bluestream.org
Date: 05/25/04


Date: 24 May 2004 18:07:10 -0700

svallarian@hotmail.com (Steven V.) wrote in message news:<2577983e.0405240919.7768326d@posting.google.com>...
> Ok, here's my setup.
>
> 1)
> My PC with latest terminal server client, running in win98
> compatibility mode.
> 2)
> using putty, ssh tunnel created between my computer and windows 2000
> server (running cygwin/sshd)
> 3)
> Port forwarded local: 3389 to remote: 10.1.2.22:3389
> 4)
> connect using terminal server client
> 127.0.0.1:3389
> 5)
> everything looks good, but after I hit connect the client sits there
> and about 5 minutes later, I get the error.
>
> "A licensing error occured while the client was attempting to connect
> (Licensing timed out). Please try connecting again."
>
> A lookup on ms site says contact sysadmin. Well of course that's me
> and it doesn't make much sense. Tried running filemon and regmon on
> both my machine and the sshd hosting machine, but didn't come up with
> much.
>
> Anybody have this problem before? Any ideas?
>
> Steven Vallarian

Hi Steve-
I know you already found the answer to this, but here's for posterity:
Going into compatibility mode breaks the program writing to the local
client's registry, which is required to use terminal server licensing.
So, setup everything to hit address 127.0.0.2 instead of just plain
localhost. No compatability mode, and everything should work just
fine.
Or, use the client I wrote to do everything! http://www.wissh.com

Thanks and good luck...
Chad Amberg
WiSSH software developer



Relevant Pages

  • RE: Printers
    ... >I want to know how i can configure a local printer in terminal server client. ... You might want to take a look at the following article for some general information on printer redirection. ...
    (microsoft.public.win2000.termserv.clients)
  • Re: tunneling windows terminal services via ssh - licensing error message
    ... > My PC with latest terminal server client, ... Going into compatibility mode breaks the program writing to the local ... setup everything to hit address 127.0.0.2 instead of just plain ...
    (comp.security.ssh)
  • Re: Because of a protocol error
    ... A Terminal Server Client Session Quits Unexpectedly ... MCSE, CCEA, Microsoft MVP - Terminal Server ... > "Because of a protocol error, ...
    (microsoft.public.windows.terminal_services)
  • Re: 1 client get licence error - all others ok
    ... Delete the locally stored license from the client. ... MCSE,CCEA, Microsoft MVP - Terminal Server ... > remote computer again of contact your server administrator." ... > terminal server client access licences for the computer. ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Permissions
    ... the message To change permission compatibility settings you must switch ... such as the registry and system ... with terminal server and what permissions it needs to run. ... Compatibility mode to Relaxed Security to see whether those applications ...
    (microsoft.public.windows.terminal_services)