Related Posts

12 Comments Already

commenter
stewart Said,
May 17th, 2008 @10:48 am  

what happens if you are using terminal services and you experience congestion — performance is not acceptable. What are my options

commenter
Carolyn Said,
June 12th, 2008 @3:30 pm  

What happens if you’re using web terminal services connection? Changing settings on RDC has no impact.

commenter
Chrisjan van den heever Said,
July 9th, 2008 @4:56 am  

I implemented XP SP3, and now when i try to launch the remote desktop applicaition, i get an error The pre-release version of Remote Desktop has expired. mstsc.exe time stap is 07/10/31

commenter
Nelson Said,
July 9th, 2008 @9:05 am  

Chrisjan, it seems that you probably installed a beta version of Remote Desktop client on your computer before updating your XP machine to SP3. download Remote Desktop 6.1 from Microsoft website again,install it and see if that fixes the problem.

let us know about your solution.

commenter
robert Said,
July 18th, 2008 @10:40 am  

after updating to SP3 I no longer can remote desktop. there are no errors popping to to tell me the issue it simply does not connect

commenter
Nelson Said,
July 18th, 2008 @12:11 pm  

Robert, what version of XP are you running? have you made sure the other computer you are trying to get into is properly running and accepting RDC calls?

commenter
Tom Said,
August 21st, 2008 @8:31 am  

I have 20 WinXPSP2 PCs that connect to a Windows 2000 Terminal Server. A few users upgraded to SP3 and now they cannot connect. They get: “Remote Desktop connection has encountered a problem…”

If they click either “Send error report” or “Don’t send” RDC closes. If they just move the error window out of the way they can connect and everything is fine.

Any ideas?

commenter
Mark Said,
August 21st, 2008 @2:44 pm  

How do I tell which version of RDC I have installed on my XP system?

commenter
Nelson Said,
August 21st, 2008 @6:00 pm  

Hi Mark, to check what version of remote desktop you are using, once you open remote desktop connection right-click on the small computer icon on the upper left corner of the title bar, then click on ABOUT.

commenter
Nelson Said,
August 21st, 2008 @6:06 pm  

Hi Tom, thanks for stopping by and kind of sucks some of your users are getting that error when they upgraded to XP SP3. have you check the security setting on the remote desktop client of the users that upgraded to SP3? on the Advanced tab, there is an option ” If the actual verification does not meet minimum policy requirements” make sure “connect and don’t warn me” is selected.

let me know what’s your solution though.

commenter
Rosti Said,
August 29th, 2008 @6:51 pm  

Hi,

since the upgrade to SP3, I can no longer connect to WinServer 2000 running Terminal Services. I get an error

“Because of a protocol error, this session will be diconnected. Please try connecting to the remote computer again.”

Needless to say, no point re-trying as there is now a difference in the protocl and the two do not communicate.

Is there something I can do to the Win2000 Server (without a total upgrade to a later verion) or at the client end to regain connectivity?

Rosti.

Please Leave Your Comments Below

Please Note: All comments will be moderated