File Details |
|
| File Size | 1.9 MB |
|---|---|
| License | Freeware |
| Operating System | Windows XP |
| Date Added | October 26, 2009 |
| Total Downloads | 33,433 |
| Publisher | Microsoft Corp. |
| Homepage | Microsoft Remote Desktop Connection |
Publisher's Description
Remote Desktop Connection (Terminal Services Client 6.0) provides a way to use any new Terminal Services features introduced in Microsoft Windows Vista and Microsoft Windows Server Code Name “Longhorn” from a computer running Microsoft Windows XP with Service Pack 2 or Microsoft Windows Server 2003 with Service Pack 1.
Latest Reviews
yohimbe9 reviewed v6.0 on Dec 1, 2006
mstsc /span = awesome. Just tried it on our 2003 TS and it looks great.
Remote programs = awesome
Remote access of local hard drives = awesome.
The only reason I'm giving it a 4 is like the review below about the extra security. I understand why they put it in but now there's a bunch of extra clicks that are kinda annoying. Still, a great job.
strangerdon reviewed v6.0 on Dec 1, 2006
I don't have a Vista or Longhorn system to test this with, but using it to connect to XP, 2003 or 2000 systems is a pain. The extra layer of security is not yet compatible with the legacy systems (maybe if you installed the update - which is in the form of a KB update - on both machines). The session opens with the requirement to put in your connection credentials - which can not be authenticated by the legacy machines. Therefore, you must set the client to connect despite the lack of authentication, and then type in your credentials again.
I anticipate that with a compatible system, the connection credentials would pass through for logon as well - but that is only a guess.
On the plus side, there are more videao options and the ability to select which local drives are available to the session, which is nice.
I re-installed the RDP client for 2003 and I don't see myself using it again until I have a predominately Vista environment or XP, 2003 and 2000 are updated to handle the new athentication method.
cekicen reviewed v6.0 on Dec 1, 2006
for 32 bit color, host computer must be windows vista.
Hank.Riker reviewed v6.0 on Nov 30, 2006
I have this installed on several machines now, and it is working fine. I haven't seen any slowdown's on connecting, at least once I edited up and saved a profile for the connect. I'd like to use the authentication, but I think that's got to wait for Vista, or perhaps it's in Server 2003? Neither of which I'm running.
mjm: Have you gotten the 32bit color to work? This is the feature I'm most interested in, as I have an application I want to serve from one machine, to the machine I'm remoting from, which requires 32bit color, but I can't get it to work. The video card is an older nVidia one (5x series), and I'm wondering if that's part of the problem, or if there is any way to force 32bit.
I have updated both machines with v6, and it still drops back to 16 bit. Could it be a problem with the 1600x1280 screen size?
I'm at a loss.
The MAZZTer reviewed v6.0 on Nov 30, 2006
Clue: Consider the RDC version number matching the highest version of Windows the client supports.
Hank: Your question is a bit confusing. Does the video card SUPPORT 32 bit color? If not, then you can't get it on RDC either.
I wonder if this is why I couldn't use the XP RDC to connect to my Vista RC box? Hmm. More likely ITS blocked the port. >:(
MS needs to add port-changing into the server and client. -1 point.
mjm01010101 reviewed v6.0 on Nov 30, 2006
Worth it. Monitor spanning + 32-bit color rocks.
Stach reviewed v6.0 on Nov 30, 2006
Install v6.0 hoping that it would somehow be better than what shipped with Windows XP, however all of the multiple prompting for connecting to a machine now, coupled with MUCH slow initial connection due to the multiple connections, forced me to quickly remove this "upgraded" version.
Clue reviewed v6.0.2600.0 on Sep 4, 2004
The client is very nice (fast and small) but Microsoft has confused me about the versions of the RDP clients.
That version is for machine not running windows XP, and it (according to ms site) is the same as the one within the windows XP.
But the client version within windows XP is 5.1.2600.2180, that file has version 6.0.2600.0, And to be even more confused Microsoft has documented that if you want to control windows 2003 server from windows XP client you should update the client to the one that came with windows 2003 (version 5.2.3790.0).
Why giving the same program (as Microsoft said) different versions?
yohimbe9 reviewed v6.0 on Dec 1, 2006
mstsc /span = awesome. Just tried it on our 2003 TS and it looks great.
Remote programs = awesome
Remote access of local hard drives = awesome.
The only reason I'm giving it a 4 is like the review below about the extra security. I understand why they put it in but now there's a bunch of extra clicks that are kinda annoying. Still, a great job.
strangerdon reviewed v6.0 on Dec 1, 2006
I don't have a Vista or Longhorn system to test this with, but using it to connect to XP, 2003 or 2000 systems is a pain. The extra layer of security is not yet compatible with the legacy systems (maybe if you installed the update - which is in the form of a KB update - on both machines). The session opens with the requirement to put in your connection credentials - which can not be authenticated by the legacy machines. Therefore, you must set the client to connect despite the lack of authentication, and then type in your credentials again.
I anticipate that with a compatible system, the connection credentials would pass through for logon as well - but that is only a guess.
On the plus side, there are more videao options and the ability to select which local drives are available to the session, which is nice.
I re-installed the RDP client for 2003 and I don't see myself using it again until I have a predominately Vista environment or XP, 2003 and 2000 are updated to handle the new athentication method.
cekicen reviewed v6.0 on Dec 1, 2006
for 32 bit color, host computer must be windows vista.
Hank.Riker reviewed v6.0 on Nov 30, 2006
I have this installed on several machines now, and it is working fine. I haven't seen any slowdown's on connecting, at least once I edited up and saved a profile for the connect. I'd like to use the authentication, but I think that's got to wait for Vista, or perhaps it's in Server 2003? Neither of which I'm running.
mjm: Have you gotten the 32bit color to work? This is the feature I'm most interested in, as I have an application I want to serve from one machine, to the machine I'm remoting from, which requires 32bit color, but I can't get it to work. The video card is an older nVidia one (5x series), and I'm wondering if that's part of the problem, or if there is any way to force 32bit.
I have updated both machines with v6, and it still drops back to 16 bit. Could it be a problem with the 1600x1280 screen size?
I'm at a loss.
The MAZZTer reviewed v6.0 on Nov 30, 2006
Clue: Consider the RDC version number matching the highest version of Windows the client supports.
Hank: Your question is a bit confusing. Does the video card SUPPORT 32 bit color? If not, then you can't get it on RDC either.
I wonder if this is why I couldn't use the XP RDC to connect to my Vista RC box? Hmm. More likely ITS blocked the port. >:(
MS needs to add port-changing into the server and client. -1 point.
mjm01010101 reviewed v6.0 on Nov 30, 2006
Worth it. Monitor spanning + 32-bit color rocks.
Stach reviewed v6.0 on Nov 30, 2006
Install v6.0 hoping that it would somehow be better than what shipped with Windows XP, however all of the multiple prompting for connecting to a machine now, coupled with MUCH slow initial connection due to the multiple connections, forced me to quickly remove this "upgraded" version.
Clue reviewed v6.0.2600.0 on Sep 4, 2004
The client is very nice (fast and small) but Microsoft has confused me about the versions of the RDP clients.
That version is for machine not running windows XP, and it (according to ms site) is the same as the one within the windows XP.
But the client version within windows XP is 5.1.2600.2180, that file has version 6.0.2600.0, And to be even more confused Microsoft has documented that if you want to control windows 2003 server from windows XP client you should update the client to the one that came with windows 2003 (version 5.2.3790.0).
Why giving the same program (as Microsoft said) different versions?