We use a HP thin client which uses RDESKTOP for its connection software. I am wondering when RDP 6.0 support for Vista will be available?
jbrown@les dot com
Logged In: NO
when RDP 6.0 support for Vista will be available?
Logged In: YES
jeah that is a big problem
Not only Vista .. Win 2003 server R2 too
".. has been forced into "FIPS mode" and now I'm unable to connect from a linux machine. .."
and some next info :
MS' site says that prior to setting fips compliant encryption rdp uses as "RC4 algorithm with a 56-bit key length"
and after you enable FIPS compliant encryption "the RDP channel is encrypted by using 3DES in Cipher Block Chaining (CBC) mode with a 128-bit key length"
maybe is it easy ??
Yes would be nice to be able to connect using NLA (Network Layer Authentication)
I think it will be more important to make RDP 6.1 support with new bulk compression.
We have seen a marked improvement of the performance of java apps running on Windows in RDP v6 sessions as opposed to v5. So we'd also like to see RDP v6 implemented too.
We also use a thin client, in this case Igel boxes.
I would also like to add my voice to the requests to add RDP 6 support. Connecting to a vista system at only 16 bit color is not pretty!
Also adding my vote for RDP 6 support for the increased security.
I'm adding my vote for RDP 6 support - ThinClients using linux cannot have sound when RDP'ing to a Windows Server 2008 and have sound support. I've tried compiling with this patch: http://article.gmane.org/gmane.network.rdesktop.devel/2808 but had no success.
That was a bit convoluted: ThinClients using linux cannot have sound when RDP'ing.
I vote for RDP 6.1 support!
here is my problem:
in Windows 2008 TS I have problems with redirected disk (-r disk:usb_dev=/mnt/usbdevice)
with \\tsclient\usb_dev I can browse folders, use copy in cmd, even open files, but when I try to copy (drag and drop to my desktop) or create new folder I get 0x8007048F error Access denied and \\tsclient share get unusable.
I suppose there are some file atributes explorer can't get through RDP
Where can I find the RDP6.0 or RDP 7 protocol document. I am involved in a project that may require us to update rdesktop to support these protocols. If the relevant document source is available somewhere then we can assess whether or not it will be worth the effort.
The RDP protocol is "specified" in http://msdn.microsoft.com/en-us/library/cc240445%28PROT.10%29.aspx and neighbour documents.
RDP is not strictly versioned, but client and server negotiates which features they support and wants to use. Features introduced with 6.0 are spread out, such as in http://msdn.microsoft.com/en-us/library/cc241682.aspx
rdesktop was written before and without these documents, so they do not map directly to each other, neither in structure or naming. And RDP really is a monster.
I am also voting vor RDP 6.1
As I said on the mailing list: stop only complaining and asking and put your money where your mouth is. You want RDP 6? Go to somewhere like rentacoder.com and pay someone to do it.
I would very much like to have this in rdesktop. We (a contractor for a
company that does work for the federal government) would/require FIPS
support in all connections to Windows Vista/7/2008 systems.
The federal government is pushing settings on all systems that require
FIPS compliance. For users of Unix/Linux system rdesktop is the preferred
way to connect to Windows systems. When the FIPS settings mandated by FDCC
are enabled rdesktop can no longer be used.
If any help or support can be done for the feature request that would be
great. Would I be able to increase this request in any manner please open
You seem to have CSS turned off.
Please don't fill out this field.
It would be interesting if ðere was a page listing what different versions of RDP require, what needs to be implemented in rdesktop, and what are ðe feature interdependencies and levels of effort.
http://www.quest.com/ has modified rdesktop to support RDP 6.0. However, they have not released it to the public. Maybe someone can convince them to do so.
Sign up for the SourceForge newsletter: