Menu
▾
▴
Re: [rdesktop-users] Light client computer made simple
|
From: Justin F. <ju...@ak...> - 2003-05-19 08:34:43
|
On Friday 16 May 2003 00:00, Casey Allen Shobe wrote: > I've got five Slackware 9-based systems configured similarly for a client. > I use kdm, and the users can choose between rdesktop or a kde login (from > which they may also run rdesktop). The server is Windows NT 4.0 Terminal isnt this going to be a problem when (as i said below) the RDP5.1 version=20 comes out as NT is RDP4 only? > Server. File server and domain controller services are provided via a > linux box running samba. > > Previously, they had a Windows 2000 domain controller/file server, and fi= ve > Windows 98 workstations. > > Now, if only there were a way to enable audio transmission, I would be se= t. > I've been thinking about moving to Citrix for the audio support. this wont happen until RDP5.1 is implemented into rdesktop. > > - Casey > > > -----Original Message----- > > From: Kenneth Hess [mailto:kh...@ah...] > > Sent: 15. ma=ED 2003 20:21 > > To: rde...@li... > > Subject: [rdesktop-users] Light client computer made simple > > > > > > All, > > > > Since several people have been interested in this solution, I > > am going to > > write it here so that it is part of the history of rdesktop. > > I originall > > published this as an article in the November 2002 issue of SysAdmin > > Magazine. There is far more detail there if you are interested. > > > > This will be the short version AND the way I did it. There > > are probably > > other ways to do this but this one works well for me. > > > > Install Linux on an old computer with at least a 500MB Hard > > Drive and 32MB > > RAM, using the following loose guidelines: Base install + > > ssh, printing, > > samba, and twm. Some newer versions have rdesktop as an rpm,...if so > > install it too as you install the computer's OS. > > > > Install rdesktop from source or rpm. If from source, do ALL of the > > following: ./configure ; make ; make install > > > > create a generic user to use as a user on the client system. > > I use 'username' > > adduser username > > > > In the home directory of "username", create a .xinitrc file > > and put in: > > /usr/local/bin/rdesktop -f servername > > twm & > > > > In /etc/hosts add: > > 192.168.0.100 servername > > > > you would be wise to give each client machine a unique name > > and put that > > in /etc/hosts as well. > > If you are using DHCP, I have a script that runs in /etc/rc.local that > > grabs the time and appends it to TSCLIENT and adds it to the > > /etc/hosts > > file on boot. Email me if you want details on this,...as > > there are some > > gotchas with it to be aware of. > > > > I also put in a .twmrc with only one entry in it for > > reconnect with the > > same command line: > > "Reconnect" f.exec "/usr/local/bin/rdesktop -f servername &" > > > > This is important if the TS is disconnected somehow,...your > > user can just > > click the mouse twice and get back to a login screen. > > > > If you want the client computer to automatically login to the client > > machine with the generic user account and automatically start a TS > > session, then do: > > > > get autologin-1.0.0-rpm (if you can't find it, email me, I have it) > > install it. > > in /etc/sysconfig/autologin (create it if it doesn't exist) > > add: > > USER=3Dusername (use the user name that you created) > > AUTOLOGIN=3Dyes > > > > Now when your client computer reboots, it will boot right up > > to a TS login > > prompt filled with the username that you have autologged in with. > > All the user has to do now is login with their passwd. > > > > If they get disconnected, the click the mouse, click > > Reconnect, and they > > are back to a login screen with their username. > > > > Simple right? > > > > One note on the TS side, fix the permissions such that the only things > > users can do is Logoff and Disconnect, or you will surely have people > > rebooting your server for you. > > > > If you want to allow them to use their local floppy and / or > > CD drives, > > you will have to share them via samba and map drives. > > > > I also once found a little utility that will hide the > > servers' floppy, CD, > > and hard drives from the users if you want. > > > > For printing, you can print to an ip printer from the TS or > > if you have a > > local printer connected to your client machine...TURN OFF > > PLUG AND PLAY in > > the BIOS, setup the printer in Linux, share from samba, and > > connect with > > the TS and print away. > > > > A little effort on the front end will save time and $$$ in the future. > > > > Also if you build this as your generic image, you can install it on > > practically any other computer and let kudzu remove and add > > your hardware > > for you. Video and Network cards are the only things that > > should change > > between client machines. > > > > Hope this helps. > > > > Feel free to email me with any questions, comments, praises, > > job offers, etc. > > > > ken > > -- > > Kenneth Hess > > AHCC > > Phone: 918.583.1004 > > Fax: 918.587.2422 > > http://www.ahcctulsa.com > > > > > > > > > > ------------------------------------------------------- > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > The only event dedicated to issues related to Linux > > enterprise solutions > > www.enterpriselinuxforum.com > > > > _______________________________________________ > > rdesktop-users mailing list > > rde...@li... > > https://lists.sourceforge.net/lists/listinfo/rdesktop-users > > ------------------------------------------------------- > This SF.net email is sponsored by: If flattening out C++ or Java > code to make your application fit in a relational database is painful, > don't do it! Check out ObjectStore. Now part of Progress Software. > http://www.objectstore.net/sourceforge > _______________________________________________ > rdesktop-users mailing list > rde...@li... > https://lists.sourceforge.net/lists/listinfo/rdesktop-users |