Rdp Protocol Data Encryption Detected Error
Contents |
comment. "The RDP Protocol Component "DATA ENCRYPTION" Detected an Error…" error message ★★★★★★★★★★★★★★★ Microsoft Fix it blogMarch 29, 20112
Event Id 50 Termdd Server 2008 R2
Share 0 0 KB Article: http://support.microsoft.com/kb/323497 INTRODUCTION
After you install Windows event id 50 termdd windows server 2003 2000 Security Rollup Package 1 (SRP1), Terminal Services clients may not be able to connect to the Terminal termdd event id 56 Services server. You may also experience this problem when you use Remote Desktop Web Connection on a Windows XP Professional computer to connect to a Terminal Services server. When thisBecause Of An Error In Data Encryption This Session Will End Windows 7
problem occurs, event ID 50 is recorded in the system event log:
Event Type: ErrorEvent Source: TermDDEvent ID: 50Description:The RDP protocol component "DATA ENCRYPTION" detected an error in the protocol stream and has disconnected the client. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 307454 (http://support.microsoft.com/kb/307454/ ) MS01-052:Rp Data
Invalid RDP data can cause Terminal Services failure
The Terminal Services client may also receive the following error message during a connection attempt: The terminal Server has ended the connection. Tags fixit Comments (2) Cancel reply Name * Email * Website Michael Brown says: April 13, 2011 at 10:55 pm is their anything that I can do too repair it Reply Conrad says: December 19, 2011 at 4:54 pm I tried these solutions but it is not working for me. I still have problems connecting to my XP professional system from my XP Pro laptop. Reply Follow UsPopular Tagsfixit Windows Outlook Exchange Server Word Office Pages Excel PowerPoint Vista Outlook Express Internet Explorer Windows 7 ie7 WinXP Media Center IE General Windows Server Media Player Archives January 2013(5) September 2012(8) July 2012(13) May 2012(15) April 2012(4) March 2012(3) January 2012(12) December 2011(2) November 2011(8) October 2011(4) All of 2013(5) All of 2012(55) All of 2011(110) All of 2010(16) All of 2009(192) All of 2008(8) Privacy & Cookies Terms of Use Trademarks © 2016 MicrosoftWindowsWindows 10 Windows Server 2012 Windows Server 2008 Windows Server 2003 Windows 8 Windows 7 Windows Vista Windows XP Exchange ServerExchange Server 2013 Exchange Server 2010 Exchange Server 2007 Exchange Server 2003 Outlook Unified Communications/Lync SharePoint Virtualization Cloud Systems ManagementSystem Center PowerShell & Scripting Active Directory & Group Policy Mobile Networking Storage TrainingOnline Training IT/Dev Connections Webcasts VIP Library Digital Magazine Archives InfoCentersIT Innovators Mobile https://blogs.technet.microsoft.com/fixit4me/2011/03/29/the-rdp-protocol-component-data-encryption-detected-an-error-error-message/ Computing Business Now Desktop VDI All About Converged Architecture Advertisement Home > Windows > JSI Tip 5678. 'The RDP protocol component "DATA ENCRYPTION" detected an error in the protocol stream and has disconnected the client'? JSI Tip 5678. 'The RDP protocol component "DATA ENCRYPTION" detected an error in the http://windowsitpro.com/windows/jsi-tip-5678-rdp-protocol-component-data-encryption-detected-error-protocol-stream-and-has-d protocol stream and has disconnected the client'? Aug 29, 2002 Jerold Schulman | Windows IT Pro EMAIL Tweet Comments 0 Advertisement Installing the Windows 2000 Security Rollup Package 1 (SRP1) may prevent the Terminal Services clients from connecting to a Terminal Services server. The following event is recorded: Event Type: Error Event Source: TermDD Event ID: 50 Description: The RDP protocol component "DATA ENCRYPTION" detected an error in the protocol stream and has disconnected the client. A possible race condition may prevent the private certificate key on the Terminal Services server from being synchronized. To workaround this issue: 1. On the Terminal Services Server, use the Registry editor to navigate to: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermService\Parameters. 2. Delete the Certificate Value Name, a REG_BINARY data type. 3. Shutdown and restart the Terminal Services Server. The Certificate Value Name is automatically regenerated. Print reprints Favorite EMAIL Tweet Please Log In or Re
Saturday, March 07, 2009 The RDP protocol component "DATA ENCRYPTION" detected an error. The following entry is logged in event viewer http://desktopremotesupport.blogspot.com/2009/03/rdp-protocol-component-data-encryption.html on a windows 2003 server when trying to connect using RDP from http://serverfault.com/questions/366407/the-rdp-protocol-component-data-encryption-detected-an-error-in-the-protocol-s 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: 50This is a known issue and can be resolved with a simple registry change. below is an image of a registry change event id 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 event id 50 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;323497Link to this port, add to favourites... Posted by Puppet at Saturday, March 07, 2009 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: 2003 server, RDP, terminal server, Windows, XP 1 comment: Anonymous said... Great and simple explanation.Thank youILIR Thursday, August 18, 2011 6:06:00 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Search This Blog Loading... Share: Subscribe To Posts Atom Posts Comments Atom Comments Blog Archive ► 2015 (2) ► April (1) ► March (1) ► 2014 (1) ► February (1) ► 2012 (1) ► January (1) ► 2011 (2) ► December (1) ► November (1) ► 2010 (5) ►
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top The RDP protocol component “DATA ENCRYPTION” detected an error in the protocol stream and has disconnected the client up vote 0 down vote favorite I have a W 2K3 Terminal Server which most of my computers can connect to without a problem. There is one computer which always fails and says: The client could not establish a connection to the remote computer. The most likely causes for this error are: 1) Remote connections might not be enabled at the remote computer. 2) The maximum number of connections was exceeded at the remote comptuer. 3) A network error occured while establishing the connection. I checked the Event Viewer on the server and found Event 50 from TermDD aT the same time the failure happens with the message (The RDP protocol component "DATA ENCRYPTION" detected an error in the protocol stream and has disconnected the client.). I have already reviewed the KB 323497 and it does not solve my problem. EDIT*** I just found KB 257894 which explains how to lower the encryption requirements. That works as a temporary fix (I just tested it), but long term I do not want to keep my encryption requirements low! windows-server-2003 windows-xp remote-desktop rdc share|improve this question asked Mar 5 '12 at 10:23 just.another.programmer 2491417 add a comment| 1 Answer 1 active oldest votes up vote 3 down vote accepted The problem computer was only running XP SP2, which does not have RDC 6.0 and does not support FIPS. Downloaded RDC 6.0 on t