Download Squad

Unfortunately the update gets about 2/3 of the way through before hanging at the "Running processes after install" step. Is anyone else encountering this?

Reply

Works for me Mike.

Reply

since i installed this, i now have to log in twice to connect to all my windows 2000 servers, and i can't find a way around it. :-(

Reply

DOUBLE LOGON PROMPTS

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=979744&SiteID=17

I can confirm that the double login occurs; but I believe I know why, as I have tested again two Windows Server 2003 systems: one requiring a "double login" and the other not.

This issue appears to occurs if you have defined the "Always prompt client for password upon connection" via the Group Policy Object Editor. This setting is located under the Computer Configuration > Administrative Templates > Windows Components > Terminal Services > Encryption and Security node.

Normally, this setting would prevent someone from automatically gaining access by launch an RDP profile (pre 6.0) with a saved password. With 6.0, Microsoft eliminated this security hole, but now they've turned the authentication process into two-step process, with the client merely collecting the credentials (prior to connection) and passing it on to the server (upon connection). This is where the problem occurs. That first login prompt is before you even connect -- after which point the above defined policy kicks, the client is not allowed use preestablished credentials, and the server interrogates you for a user name and password.

Note: you can always ignore the first login and simply click "OK", as you will be prompted to login by the target server, provided that you have left the "Server Authentication" option (on the RDP client Advanced tab) at "Always connect, even if authentication fails"

I hope Microsoft does something about this -- especially since the client always adds additional information to the login name (i.e. username becomes server\username) when one goes to connect using the saved user name from the drop-down list, thereby causing authentication to fail.

Reply

And only for those with english OS :-(

Reply

To be totally honest and to the point the "New" and "Improved" RDP client totally sucks! Why should someone have to logon to a server twice to establish RDP connection. I don't care if I have to login 100 times, an additional login does not make the client any more secure than the single sign on the previous RDP clients supported.

WHAT TOTALLY BURNS MY ASS IS THAT I CANNOT REMOVE THE NEW VERSION AND INSTALL THE OLD RDP CLIENT THAT WINDOWS XP SHIPPED WITH!!!!

Man this sucks!

Eric Hanke

Reply

What sucks is, after installing this new RDP Client, I can no longer Remote Desktop from an XP client to a Server 2003 Machine. Has anyone else been experiencing this. I see nothing in my firewall logs indicating that it is blocking this. To test, I connected using another XP machine. than updated the client and tried again. Hangs forever. Any suggestions would be great. Mike RO suks A$$

Reply

OK, I was wrong, My firewall is now blocking it. TCP packet out of state. First packet isn't syn. It seems Microsoft once again doesn't play by the rules.

Reply

If you used to log in to multiple accounts (like Administrator plus one for yourself) under the old software, and are cussing the disappearance of the login screen, do this:

Right-click your TS client icon, choose Edit, then check the box that says "always ask...." The login will reappear for you!

...MontyMan.
http://www.brancekrachy.com/manufacturer_power_tranmission.html

Reply

CORRECTION: If you are using CheckPoint NGX, within Smart Defense, You can no longer protect against malformed RDP requests. 6.0 must be causing CheckPoint to think these requests are malformed. so as I said before. woohoo microsux

Reply

If you want to uninstall the new verion, run a search for mstsc.dll.mui and mstsc.exe.mui, rename them to mstsc.dll and mstsc.exe and replace the same files in your system32 folder.

Reply

To uninstall, merely remove the KB925876 package from add-remove programs in control panel.

Reply

To easily bypass the second login, enter your username rather than domain\username. The remote host automatically assumes the default remote domain for logins. Putting in domain\username seems to cause the remote hoste to prepend the domain once again making it domain\domain\username thus causing the second login requirement.

Reply

What a hunk of poo! I had to remove the KB925876 package as mentioned above (Thanks Sahir!) to connect to any of my servers. (I run Check Point Integrity Client). Cette programme est une espèce de merde!

Reply

Yes, you can enter the server or domain name where the desired account database is, but the point is the the other versions of RDP didn't require you to tab back, change the part with the name, and then try to connect. If I am in a domain using the Windows XP version of RDP, I just use my ID and password, and the RDP tool remembers those. If I need to change it, then I can. Also, I can pre-enter the name, password and domain on the XP and older version, but NOT on this new one. It requires much more typing and correction, just to reconnect to the same server. It's ridiculous.

I removed the new one - Thanks, Sahir - which doesn't even mention that it's the RDP tool, and re-installed the old XP version, which works great for everything.

This is the previous version that I use on all my servers and desktops:
Windows XP Remote Desktop Connection software
[XPSP2 5.1.2600.2180]


-- Rob "I" --

Reply

The new one really sucks!!

How to remove it:

Add/Remove programs - uninstall KB925876

Or

for some ppl it might not be there. You can go to C:\WINDOWS\$NtUninstallKB925876$\spuninst and remove it directly from there.

Reply

Unfortunately the update gets about 2/3 of the way through before hanging at the "Running processes after install" step. Is anyone else encountering this?
Meeeeeee,on the laptop but it runs ok on desktop ??!!

Reply

Unfortunately if you have used an integrated install for XP (slipstreamed) then the unistall options are not available. There is no entry in ARP and no uninstall entries in Windows. I tried to rename the files as mentioned above and ended up using system restore just to get a functioning RDP again. It's hard to believe that MS pulls crap like this so I am still looking for an uninstall option so I can reinstall the old version.

Jeff

Reply

This update is best avoided if at all possible!

Reply

You can remove this piece of crap TS client. Go to add/remove programs. At the top, click show updates. Look for "Update for Windows XP (KB925876)", click remove - reboot. Your done.....

Reply