-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathREADME
More file actions
74 lines (51 loc) · 2.24 KB
/
README
File metadata and controls
74 lines (51 loc) · 2.24 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
Original README follows.
This is a fork of
https://rdesktop.svn.sourceforge.net/svnroot/rdesktop/rdesktop/trunk
which makes it possible to control rdesktop using an agent script. The purpose
of this hack was to automate OS installations. I have done the same hack for
vncviewer, see
https://github.com/tomyl/vncviewer-agent
For more background, see
http://permalink.gmane.org/gmane.network.rdesktop.user/2687
The agent script is invoked like this:
rdesktop -G ./test.xexpect host
My agent scripts use ./xexpect as interpreter. The agent protocol that
rdesktop uses is documented in this script.
==========================================
rdesktop: A Remote Desktop Protocol client
==========================================
rdesktop is an open source client for Microsoft's RDP protocol. It is
known to work with Windows versions such as NT 4 Terminal Server,
2000, XP, 2003, 2003 R2, Vista, 2008, 7, and 2008 R2. rdesktop
currently implements the RDP version 4 and 5 protocols.
Installation
------------
rdesktop uses a GNU-style build procedure. Typically all that is necessary
to install rdesktop is the following::
% ./configure
% make
% make install
The default is to install under /usr/local. This can be changed by adding
--prefix=directory to the configure line.
Note for Subversion users
-------------------------
If you have downloaded a snapshot of rdesktop using Subversion, you
will first need to run ./bootstrap in order to generate the build
infrastructure. This is not necessary for release versions of
rdesktop.
Invocation
----------
Simply run::
% rdesktop server
where server is the name of the Terminal Services machine. (If you receive
"Connection refused", this probably means that the server does not have
Terminal Services enabled, or there is a firewall blocking access.)
You can also specify a number of options on the command line. These are listed
in the rdesktop manual page (run "man rdesktop").
Smart-card support notes
------------------------
The smart-card support module uses PCSC-lite. You should use PCSC-lite 1.2.9 or
later.
To enable smart-card support in the rdesktop just run "./configure" with the
"--enable-smartcard" option. Also you can enable smart-card debug with
additional "--with-debug-smartcard" option.