Xrdp, installing Ubuntuwiki. From Ubuntuwiki. net Overview xrdp is a somewhat limited implementation of the server side of Microsofts RDP Remote Desktop Protocol. RDP is superior in speed to earlier remote control protocols like VNC. The current implementation of xrdp only functions properly as an rdp to vnc gateway this is a bit odd and confusing, but what you actually must do is have one or more already running VNC instances listening on the target computer xrdp listens for incoming RDP connections and patches them through to the target machines VNC servers. One thing xrdp does not currently do is provide true terminal server functionality it cannot spawn new VNC server instances under arbitrary usernames by itself, it can only connect to existing VNC server sessions. What xrdp does do is accelerate remote control sessions by performing the slower VNC control session over the localhost interface, and using the much lower bandwidth RDP protocol over the network between the client and the server. It also de facto provides a way for unmodified Windows computers to remote control the machine running xrdp, as Windows XP and higher have a built in RDP client Remote Desktop but no built in VNC client. Karmic Koala has some painful thorns it wont work in its out of the box configuration, and it has known bugs with some VNC servers. The following configuration makes both of the major useful configurations of xrdp available simultaneously a Vino backend controlling the currently logged in users desktop, and a vncserver backend controlling a simplified, no compiz, non dependent on local login session. I want two different VNC sessions available The Vino session is handy because it allows you to control whatevers actually going on with the logged in user so somebody sitting at the keyboard can see what youre doing, and so that you can interact with programs which were started running locally. But it can be a bit painful to control in some cases any desktop effects you have enabled get faithfully and slowly reproduced over the network connection, and you may have a much larger screen resolution than its convenient to reproduce at your client. Also, if nobody is locally logged in, Vino wont be running and you wont be able to connect to this session at all. The vncserver clean session is handy because it will have no desktop effects, you can specify an arbitrary, smaller desktop resolution if you like, and it doesnt depend on a user being logged in locally in order for you to access it. Installing Linux On An Xp Computer' title='Installing Linux On An Xp Computer' />Linux. Note the article, Moving from Windows to Linux includes installation alternatives. First, download the latest release to your home directory with. Overview. 1. 1 why would I want two different VNC sessions available 2 Installing necessary packages 3 Configuring the servers. Installing Linux On An Xp Computer' title='Installing Linux On An Xp Computer' />Its also convenient if you need to get work done on the target machine without disturbing another user who is sitting in front of it Installing necessary packages First, youll need to install xrdp and if you dont already have it such as with Ubuntu Netbook Remix vino. If at some point you have installed tightvncserver likely as a result of trying to follow another xrdp guide somewhere else I recommend uninstalling it now. Otherwise, youll need to do a dirty workaround later. Configuring the servers vncserver for clean session remote login The clean session setup allows you to log in remotely to a session which is completely unconnected and does not rely on the locally logged in user if there even is one. Log in as the user who will own that session, start a terminal, and start vncserver for the first time. WARNING if you want to be able to run your clean session even when there is a locally logged on user, youll need to set up the clean session under a different system user. Otherwise, quite a few applications including Firefox wont work right, because their dotfiles in your profile are already locked by the other X session. You will require a password to access your desktops. New X desktop is box 1. Creating default startup script homeme. Starting applications specified in homeme. Log file is homeme. Now, configure Vino so that you can remotely control the currently logged in session. This ones easier System Remote Desktop or vino preferences from the terminal, if you prefer, check Allow other users to view your desktop, Allow other users to control your desktop, and configure the Security settings as you like you will probably want to uncheck confirm each access to this machine and check require the user to enter this password. Finally, configure etcxrdpxrdp. VNC auth. doesnt actually use username, so no. Active Local Login. Clean Session. Obviously, you can go on and specify other sessions in the same format you might want to relay VNC sessions to OTHER machines on the LAN from your xrdp host yes, that does work so that you dont have to punch different holes in the firewall for each machine on the inside. Or you might want clean sessions available for multiple user accounts. All you need to do is follow the format here, and remember that each block must have its own ID in square brackets, a human readable name argument, and its own ip and port arguments that point to working VNC servers. Automatically starting vncserver for the clean session Last step youll need to automatically start vncserver, so that it will be available whenever the machine is up. Add this to the end of etcrc. Dont forget, it wont actually be running until you either reboot, or run that command you just appended to rc. Also note that if you like, you can set up multiple vncservers, possibly running as different users, so that youve got more than one clean session to log into you just have to make sure that you specify a different desktop number the 1 at the end of the command for each vncserver session, and add blocks in your xrdp. Testing Basic listener checks Now that youve got vino, vncserver, and xrdp installed, configured and running, make sure they work right. First, check to make sure theyre listening. Install Fix Pack Websphere Linux Server here. E vinovncxrdp. You should, at a minimum, see vino, vncserver, andor Xvnc listening on ports 5. If you dont, youll need to figure out whats not running. Assuming youve got all listeners at 5. VNC servers directly with a VNC client, or you can use an RDP client to connect to xrdp, which will give you a drop down menu to select Active Local Login or Clean Session. What if my keyboard doesnt work right If youve installed tightvncserver on your own at some point, youll either need to uninstall it audo apt get remove tightvncserver will do the trick, OR if for some reason you absolutely must have tightvncserver, you can do a quick and dirty workaround Start gconf editor as the user your tightvncserver session runs under do not run as root and browse to apps gnome settings daemon plugins keyboard. Uncheck the active checkbox, and close gconf editor. Kill and restart the tightvncserver, and your keyboard should work fine now. WARNING I dont know what if anything youre not getting when you disable that active keyboard plugin all I know is that disabling it works around the tightvncxrdp bugWhat if my clean session doesnt give me a desktop Check. Most likely, youre running twm and not your normal window manager. Comment out any line invoking twm, and add a line if you dont already have one invoking Xsession. X1. 1Xsession. Kill and restart your vncserver  1, and try logging in again it should be better this time around.