I just setup my laptop with Windows 7 RC Build 7100 (64-bit).I can RDP into out servers with no problems. However, when I go to remote controla user through TerminalSerivces, their session will load for a split second and then I get this error message:""Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again."I click OK and it disconnects me. I log back in and get the same message. I have noticed that occasionally I can successfully remote control a session that has their screen locked, but as soon as they login, I get the error message and disconnected. Also, 99% of of the sessions are Wyse thin clients, not a fat client somewhere. Just in case that matters some. Any suggestions on what to do? I've read elsewhere about replacing a couple files with the Vista version to fix the issue, but I don't have access to Vista. Any help would be greatly appreciated! Thanks in advance...James

Hi jatses,You should copy only one file from Vista. That will be mstscax.dll, you can find this file in \system32.I put this file to my SkyDrive so you can download it: http://cid-db4325c58a69d361.skydrive.live.com/self.aspx/Windows%207%20TechNet%20Forum/mstscax.dll(copied from my Vista VM).Or download file from the web.After replace, register this DLL by using REGSVR32.exe command line tool (REGSVR32.exe mstscax.dll). Best regards, ukasz Foks | WSS.pl

Is this an issue with the W7 version of this file specifically, as in a flaw/bug? After some further investigation, I found out that it only happens when we try to Remote Control one of our Wyse thin clients running the Wyse OS. If I tried it on any Microsoft based OS/Connection (through the true Microsoft Remote Desktop Connection Protocol), XP embedded Wyse for example, everything worked perfectly. I'm curious if it is actually a Microsoft problem or a Wyse problem since they're using a "hacked" version of the true Microsoft RDC Protocol. I'll try this tomorrow and work and see if I can get it to work this time around. Thanks again!James

Hi jatses,You should copy only one file from Vista. That will be mstscax.dll, you can find this file in \system32.I put this file to my SkyDrive so you can download it: http://cid-db4325c58a69d361.skydrive.live.com/self.aspx/Windows%207%20TechNet%20Forum/mstscax.dll(copied from my Vista VM).Or download file from the web.After replace, register this DLL by using REGSVR32.exe command line tool (REGSVR32.exe mstscax.dll). Best regards, ukasz Foks | WSS.pl I tried this and now get the following message when trying to run the RDC application:"The Remote Desktop Services ActiveX control (mstscax.dll) does not match the version of the client shell."Any other suggestions on how to resolve this issue?Thanks,James

You get the activex control error because you actually need to replace 4 files, not just 1. You need to replace mstsc.exe, mstscax.dll & also mstsc.exe.mui & mstscax.dll.mui in the en-US folder under System32. Don't forget to register mstscax.dll

You get the activex control error because you actually need to replace 4 files, not just 1. You need to replace mstsc.exe, mstscax.dll & also mstsc.exe.mui & mstscax.dll.mui in the en-US folder under System32. Don't forget to register mstscax.dll It's quite strange: the problem is known since early Beta versions of Windows 7. Now we are with the official release plus several patches, but the problem is still there.Sure I can copy and register several Vista files to my Win7, but isn't it Microsoft's job to fix such flaws? Four months (since the first post) are long enough to do that.

This afternoon at 14h00 GMT we lost contact between our Windows 7 x32 workstations to our hosted servers running Windows Server 2008 x64. No workstations were able to connect, until another client was able to connect and close the apps open on the desktop of the Windows Server 2008. Once the windows were closed, we could reconnect from Windows 7. Opening the window again (a maximized explorer) caused a repeat of the issue. We have experienced intermittent 'batches' of downtime before which suggests the compression protocol (key?) is time-based, but never like this and never across all workstations. Its still down an hour later. Microsoft needs to address this issue. We just got locked out of production servers because of a latent bug.

Hi Lukas Thanks for your information. When I try to register the dll file, I got an error. "The module "mstscax.dll" was loaded but the call to DLLRegister Server failed with error code 0x8002801c" However the program works fine . Thanks Liz