Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

We've released the new version of the Remote Desktop Client corresponding to Vista. Here are some of the new features:

  • Server Authentication
  • Plug and Play redirection
  • TS Gateway support
  • Monitor Spanning
  • 32-bit color and font smoothing

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)

http://www.microsoft.com/downloads/details.aspx?FamilyId=CC148041-577F-4201-B62C-D71ADC98ADB1

 

Remote Desktop Connection (Terminal Services Client 6.0) for Windows Server 2003 x64 Edition (KB925876)

http://www.microsoft.com/downloads/details.aspx?FamilyId=43C0EAE9-6B64-428F-A9DC-F97F5A1B4493

 

Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP (KB925876)

http://www.microsoft.com/downloads/details.aspx?FamilyId=26F11F0C-0D18-4306-ABCF-D4F18C8F5DF9

 

Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP x64 Edition (KB925876)

http://www.microsoft.com/downloads/details.aspx?FamilyId=160CE316-BF2B-48D0-A035-E2ABBC55D8E8

 

Localized versions and the Multi-User Interface Pack will be released in the coming months.

Leave a Comment
  • Please add 6 and 6 and type the answer here:
  • Post
  • Found out what my logoff problem was, it was cured by editing default.rdp and adding enablecredsspsupport:i:0

    the problem was related to RSA

  • What about the domain:s: parameter - will this ever be fixed? Its causing major headaches for our multi-domain, multi-terminal server situaton across domains and trusts!

  • You guys complaining about the Windows key *not* working are the lucky ones ;-)

    I have 6.0 build 6000 and it thinks the Windows key is permanently depressed!  So if I press the letter 'e' it will invoke explorer, 'r' the run menu etc.  Really tiresome, but not 100% reproducible.

    Pressing and releasing the Windows key stops this behavior.  And no, I do not have a stuck Windows key -- I never have this issue anywhere else on my machine except in a new terminal services session.

  • Accidentally pushed this out to some client PCs via WSUS, and realized it crippled our ability to connect to a Windows 2003 terminal server.  Now manually removing update 1 at a time.  This should have been marked as experimental, not a critical update :p

  • I also have the random "windows-key is acting like its stuck" issue with RDP 6.0 from XP to XP (both sp2).

    Just slapping the windows key a few times sometimes works, but occassionally it doesn't go away at all until I disconnect/reconnect a few times.

    Weird.

  • Remove the double authentication requirement.

    To stop the RDP client prompting for credentials before showing the actual remote machine login screen, append the following two lines to your My Documents\Default.rdp file, and any other .rdp files you have saved:

    prompt for credentials:i:0

    enablecredsspsupport:i:0

  • If NLA is not supported on XP or Server 2003, why is it listed as the very first bullet point in this blog post?

    Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

    We've released the new version of the Remote Desktop Client corresponding to Vista. Here are some of the new features:

       * Network Level Authentication

  • Hi,

      I couldnot remotely connect our server suddenly its running on windows server 2003 am using XP proff.After rebooted its working can any one tell me what was the prob?

  • Hi,

      I couldnot remotely connect our server suddenly its running on windows server 2003 am using XP proff.After rebooted its working can any one tell me what was the prob?

  • Hello there,

    I have trouble with the printer redirection on the XP computers with RDC 6.0 installed.

    Anything I can do?

    Cheers

    AM

  • I was recently experiencing an issue mentioned earlier in this blog: "The client could not connect. You are already connected to the console of this computer. A new console session cannot be established."

    The client was running Win XP SP2 and the server was Win Svr 2003 Std Edn SP1. I was able to resolve this issue by installing Win XP Service Pack 3 on the client. SP3 upgrades the Remote Desktop Protocol to v6.1.

  • Today installed XP Professional SP3 from the updatecenter and getting same error signature as I reported on 8/oct/2007.

    AppName: mstsc.exe AppVer: 6.0.6001.18000 ModName: unknown

    ModVer: 0.0.0.0 Offset: 00e65c50

    Any suggestion to stop this error?

  • Recently updated to RDP 6.0. on Win XP SP2. My connection to different customer servers all work fine. But I receive error message when logging out of the session "The instruction at '0x00e..' referenced memory at '0x...'. The memory could not be 'read'. This occurs to all my connections. What should I do?

  • Is the "Windows key *not* working" has been resolved so far?

    I used RDP 6.0 on my XP SP2 and it was a huge pb. In each TS session, the keyborad shortcut did not work despite I enable this dfeature in the .rdp files! I uninstall the RDP 6.0 client to the 5.2... which worked perfectly.

    But i've just install XP SP3... and you know what? RDP client is bundled! So I've still got my pb... Hey MS gus, don't tell me you did not solved the pb with some registry tweaks!

  • When using the new 6.0 client and trying to access my terminal sever, which is running a novell client login, I have some issues. After entering the machine name to RDP to I am immediately asked for a user name and password. If I enter both to move on the TS screen pops up for a second like it is going to work and then goes away, coming back to the prompt for the IP or machine name I want to connect to. If I leave the password field blank I can then get to the log in screen on the terminal server. Is there a fix for this issue?

Page 14 of 16 (229 items) «1213141516