We have been successfully using rdesktop 1.2.0 on two linux boxes to connect
to a Windows Terminal server runiing win2k server.
However, after migrating this box to an Active Directory domain, rdesktop is
broken and doesn't connect.
Here's the output:
$ rdesktop -h
rdesktop: A Remote Desktop Protocol client.
Version 1.2.0. Copyright (C) 1999-2003 Matt Chapman.
See http://www.rdesktop.org/ for more information.
Usage: rdesktop [options] server[:port]
-u: user name
-c: working directory
-p: password (- to prompt)
-n: client hostname
-k: keyboard layout on terminal server (us,sv,gr,etc.)
-g: desktop geometry (WxH)
-f: full-screen mode
-b: force bitmap updates
-e: disable encryption (French TS)
-m: do not send motion events
-C: use private colour map
-K: keep window manager key bindings
-T: window title
-D: hide window manager decorations
$ rdesktop terminalsever01.dontyouloveAD.com ; echo $?
ERROR: recv: Connection reset by peer
I have tried turning the encryption level on the TS to low, but this doesn't
make any difference.
Can anyone shed any light on this?
rdesktop has been very useful till now..
From: Rob Adamson <rja29@ca...> - 2003-05-19 12:12:12
On Mon, 19 May 2003, Adrian Sanders wrote:
> We have been successfully using rdesktop 1.2.0 on two linux boxes to connect
> to a Windows Terminal server runiing win2k server.
> However, after migrating this box to an Active Directory domain, rdesktop is
> broken and doesn't connect.
At a guess, the domain configuration for the servers contains something
that is forbidding connections from your client.
And, have you tried to see if you can connect using MS Terminal server
client? That would help to isolate the problem.
IT Manager, Fitzwilliam College, Cambridge