We've released the new version of the Remote Desktop Client corresponding to Vista. Here are some of the new features:
More details on the features are in a Knowledge Base article.
To install the new version, go to Windows Update on the target computer and look for optional software updates, or download it from the Microsoft Download Center.
Remote Desktop Connection (Terminal Services Client 6.0) for Windows Server 2003 (KB925876)
Remote Desktop Connection (Terminal Services Client 6.0) for Windows Server 2003 x64 Edition (KB925876)
Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP (KB925876)
Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP x64 Edition (KB925876)
Localized versions and the Multi-User Interface Pack will be released in the coming months.
I've found the resaon of "Windows key *not* working" problem!
If you're experiencing trouble with Windows key cobinations you have to start the terminal services service on your client computer.
For example if you want to have alt+tab working in the remote TS session, you have to start the terminal services service on your Windows....
Tell me Guys, where is it documented?
Even with XP SP3, Network Level Authentication does not work by default from the RDP client. You have to activate CredSSP: http://support.microsoft.com/kb/951608/en
I am using Windows XP Pro with Terminal Services Client 6.0 running. I am connecting from the XP machine to a Windows Vista Ultimate machine. I have no problems connecting, but I am having problems with certain keyboard keys when accessing the remote Vista machine. When I type the 'e' key it opens a computer window. When I hit the space key it changes the fcous of the windows. When I hit the 'r' key it opens the run dialog. When I hti the 'u' key it opens the ease of access center. This only occurs when I am using remote desktop from my XP to vista machine. Anyone have any thoughts?
> I've found the reason of "Windows key *not* working" problem!
Brilliant solution and well-found, sir! I'd been hunting for a solution to this, as I'm one of those who turns off all unwanted services...
With regards to Dale's and Redowa's problem with incompatible smartcards, i believe that this is caused when the server that is hosting the card is not able to communicate with the Smart Card Issuing Certification Authority.
The only workaround that i know is to uninstall this patch which to me has no added value for Windows server 2003 or Windows XP users.
I have setup Remote Desktop web Connection on a office machine and have forward the relevant ports - configured firewall etc, but all I get when I click on connect from the Remote Desktop web Connection page is a white box - nothing else. the error message states
const L_ClientNotSupportedWarning_Text = "Remote Desktop 6.0 does not support CredSSP over TSWeb. If you cannot connect to this server because of Network Level Authentication problems, please visit Windows Update to obtain the latest update to Remote Desktop Connection."
' error messages
const L_RemoteDesktopCaption_ErrorMessage = "Remote Desktop Connection"
const L_DisconnectedCaption_ErrorMessage = "Remote Desktop Disconnected"
const L_InvalidServerName_ErrorMessage = "An invalid server name was specified."
Can anyone help me please?
i have register mstscax.dll and use in vb, i have doual monotor support. i can span the screen by uing the comman mstsc /span but i use activeX in vb to span the screen. which property is to be set that span the screen on multiple monitor
every few minutes while being connected to Server 2008 Standard by way of Remote Desktop the connection continually drops. I've tried it with other routers and other computers. It has been narrowed down to the Server 2008 O.S.
Has anyone experienced the same ordeal?
please understood me about remote desktop in simple word and how to make this software in vb ?
please understood me about this software in simple word and how to make in visual basic? who read please send me answer in this id email@example.com
I was just curious if anyone has run into this. I have noticed recently on a few machines that my connections aren't being saved. I don't have alot of info to provide, but it seems to be related to the shortcut. I am not sure if the actual shortcut was always in the Terminal Services folder in Administrative tools, but that seems to be where the problerm lies. I have noticed this issue in Vista Ult, sp1 and server 2008 ent(sp1). If I just open the console and add a few connections, then close the console and open it again, the connections I added are all gone. I've noticed this on both OS's. Even if I open the console and change it from author mode to user mode full, the same thing happens and the console defaults back to author mode. However, if I create a new console and add remote desktops(add snapin) and save this and change it from author mode to user-full everthing saves and works well. Has anyone ran into this?
Hi, I am running XP SP3 on a laptop. After an automatic Windows update, my remote data connection no longer works. Something called data execution prevention keeps shutting down the connection, even after I told it to protect everything EXCEPT rdc. Any ideas?
Installed drivers and management SW for USB eToken from Aladdin on Windows Server 2003.
Starting management SW locally and all works.
Starting management SW via RDP and USB eToken is not found by the management SW.
Any idea for a solution?
If my server is running Windows 2008, is there a way connect to the server using an old RDP version say RDP 5?
Thanks in advance...
Windows Server 2008 is largely backwards compatible with previous versions of the client. The one thing that older clients do not support is Network Level Authentication. If you want your Windows Server 2008 installation to accept connections from the RDP 5 client or earlier, you will have to configure it to not require Network Level Authentication. Other than that, previous clients should work fine.