The RDP protocol component "DATA ENCRYPTION" detected an error.

The following entry is logged in event viewer on a windows 2003 server when trying to connect using RDP from another server or XP desktop:

The RDP protocol component "DATA ENCRYPTION" detected an error in the protocol stream and has disconnected the client.

Source: TermDD , Event ID: 50

This is a known issue and can be resolved with a simple registry change. below is an image of a registry change made on a server. Unable to connect to the server using RDP, this registry change allowed the connection. The registry key is circled. Below the certificate entry in the right window pane, is the certificate entry that was originally there and was renamed - hence the double dash (--) in front of the name. The registry change was made and no reboot was required. Just tried connecting again from another server and the new certificate entry was entered automatically into the registry on the server.

The old and new entries in the registry to fix the RDP problem look the same but the data value does differ. The string is a long entry that's not shown in the image. All the way to the right the numbers/characters start to change.

This is a known issue:

http://support.microsoft.com/default.aspx?scid=kb;en-us;323497

Link to this port, add to favourites...

Remote Support Software

I found this a site that provides an online remote support solution:

Wait...before you click away. I know everyone knows the name brands of remote support software that provide you with computer remote access over the web, but this one although it doesn't have an IT household name does the job like the others. In fact, it let let's technical support and IT pros provide remote assistance software for their end-users on the cheap. No, it's not just another executable with an IP address compiled into it for downloading. They have a bit more dynamic on-demand remote support system that let's you make changes to your own configuration if you need to.

So let's say you get one of the other brands of computer remote control packages for remote tech support software that works over the web that has a static configuration and then you change ISP providers. Your out of luck. Sure you could have Dynamic DNS setup and that's good to but that's another piece of software running on your system and other id to maintain and another point of failure. Yes, point of failure. If you switch from cable, let's say, to DSL or visa versa, you have to get a new program. One can argue that you do not because of DDNS, but what if you want to provide online computer remote support software from another network. Now you have to get that same service running on the other network and the next and the next. Their system, although it works just fine with DDNS, it doesn't need it.

When you sign-up for an account you get a login to their site, not unfamiliar as many site have this, and a user page. On that user page you configure your networks settings. That's right, for many of you who have looked into software like this it's the same information you provide to the other site that have a static remote support solution. But the big difference here is that you don't wait for your pc remote support executable to be changed and of course to get charged again. It's on the fly. Change you config and instantly the same customer that you had provided on-demand pc remote support for just a while ago from another network now is connecting to the new network. You may be thinking that you need to have all your users go to their site to get remote assistance over the web from you. No, not at all. They have an executable program too that you get at no additional cost and it's dynamic too. Pretty Cool!!

I'm going to work with it some more and post back with more information.