From: Rens on
Curtis Vaughan wrote:
> I've put this question on the rdesktop list, but there seems to be only
> a post every couple of days (in other words, no reply).
>
> Anyhow, I have a problem using rdesktop. I know I have read a solution
> for this problem before, but now I can't find it.
> Basically, when I try to connect to a Terminal Server (whether I use
> 1.2.x or 1.3.0) I get the error that it cannot connect. As I recall it
> had something to do with forcing the Terminal Server to think the client
> had a built in license. There was a particular option one would add to
> the rdesktop command to do this. But now I can find no such documentation.
>
> Can anyone help?
>
>
> Curtis Vaughan
>
>


Hi Curtis,

You might mean logging on as a console user. That's done by appending
the option -0 to the rdesktop command.
You're basicly telling the remote desktop client that you are logging on
to the Terminal Server for administrative purposes. This comes in handy
when some other user has logged on taking up the last license and you
need to do administrative maintenance.


--
Rens


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Ramiro Caire on
Rens wrote:
> Curtis Vaughan wrote:
>> I've put this question on the rdesktop list, but there seems to be
>> only a post every couple of days (in other words, no reply).
>>
>> Anyhow, I have a problem using rdesktop. I know I have read a
>> solution for this problem before, but now I can't find it.
>> Basically, when I try to connect to a Terminal Server (whether I use
>> 1.2.x or 1.3.0) I get the error that it cannot connect. As I recall
>> it had something to do with forcing the Terminal Server to think the
>> client had a built in license. There was a particular option one
>> would add to the rdesktop command to do this. But now I can find no
>> such documentation.
>>
>> Can anyone help?
>>
>>
>> Curtis Vaughan
>>
>>
>
>
> Hi Curtis,
>
> You might mean logging on as a console user. That's done by appending
> the option -0 to the rdesktop command.
> You're basicly telling the remote desktop client that you are logging
> on to the Terminal Server for administrative purposes. This comes in
> handy when some other user has logged on taking up the last license
> and you need to do administrative maintenance.
>
>
Hi Curtis,

if you are using gnome, i recommend you GNOME-RDP, it�s very stable and
a useful tool.
Perhaps this tool solve your problems.

cheers!
Ramiro


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Chris Roberts on
Curtis Vaughan wrote:
> Basically, when I try to connect to a Terminal Server (whether I use
> 1.2.x or 1.3.0) I get the error that it cannot connect.

Saw your email on rdesktop-users, but I didn't know of any such switch. But a
few simple thoughts:

Windows 2000 or 2003? If the latter, are the users in the "Remote Desktop
Users" group? Can you logon as "administrator" - i.e. is the problem
restricted to standard users? If Windows 2000 I seem to recall that there
was a licensing problem in early versions...?

Is your server licensed by user or device - I seem to recall that there is a
problem connecting to Server 2003 from rdesktop with device licensing.

1.3 sounds old - might be worth trying a newer version of rdesktop?

Errors in the server event log (a quick Google found
http://ts.veranoest.net/ts_logon.htm)?

Sorry I cannot be more helpful.

Chris.


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org