View Single Post
Posts: 179 | Thanked: 90 times | Joined on Dec 2007
#35
Originally Posted by DigiSage View Post
Sorry, I should have been more clear. I'm a sysadmin, so I'm talking abouut getting into my Windows servers, which I can easily do using mstsc or MacOS clients. (Also, before you get the wrong idea, please know that I'm a Linux admin; Windows is unfortunately a necessary evil for me (VMware VirtualCenter))
I had to do a couple of things to get rdesktop to successfully and reliably connect with my windows 2003 servers-

On the server go to- Administrative Tools->Terminal Services Configuration. In the 'General' tab I set it at-
Security Layer-> RDP Security Layer
Encryption Level-> Client Compatible

Under the 'Logon Settings' I've set it to 'use client provided logon information' to prevent having to type the user/password twice.

On the tablet, set it to use 8bpp color depth or it'll crash on logon...

At this point it would work 'sometimes'

To get it working consistently I had to create an ssl certificate and install it, then on the same tab of the Terminal services configuration window, set terminal services to use that certificate.

That in mind, it works every time now. (I regularly connect to 5 Windows/SBS 2003 servers and 2 Windows 2000 servers this way for work...)

hope this helps,
kernelpanic

p.s.- there is something with the rdesktop maemo package where once you've crashed by not setting 8bpp, you may need to reboot the tablet to get it to successfully start.

<EDIT> I've compiled the debian etch rdesktop1.5 package for armel and installed it on my tablet. and 16bpp works. (but it's not hildonized. i.e.- once minimized you can't restore the window, hardware keys don't work so '-f' must be specified on the command line, etc...) But it looks as if most of the issues (aside from ecnryption settings) are specific to the maemo port... </EDIT>

Last edited by kernelpanic; 2008-01-29 at 18:47.
 

The Following 2 Users Say Thank You to kernelpanic For This Useful Post: