• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 711
  • Last Modified:

Windows Server 2003 and Wyse S10 and Data Encryption error

Hello All,

Have a windows 2003 Server with plenty of terminal licenses.
Mix of Desktops and Wyse Terminals.

Server is newley installed.

All RDP sessions from a desktop are able to connect without a problem.

If you connect via a wyse terminal.  User can log in for a little (no specific time) and then gets kicked out.  The following error shows up in even viewer.

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

Have read the solutions on here and microsofts website ("The RDP Protocol Component "DATA ENCRYPTION" Detected an Error..." error message)

I have tried the following registry edit solution.  
1. Start Registry Editor.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermService\Parameters
3. Under this registry subkey, delete the following values:
• Certificate
• X509 Certificate
• X509 Certificate ID

If you delete the above they just reappear.  If you delete just the values NO ONE can login via RPD/Terminal services.
Then have to restore registry for them to access.
 
4. Quit Registry Editor, and then restart the server.


HELP HELP.

So question is why are users via RDP on a desktop not having a problem, but wyse terminals getting kicked off and the Data Encryption error appears?  Anyone have a solution to resolve this problem.

If more details are needed let me know.
0
goldmantechology
Asked:
goldmantechology
  • 2
1 Solution
 
vmaheenCommented:
hi friend,

configure  encrypts  data transfering to "low" as this article explain and check again.
http://technet2.microsoft.com/WindowsServer/en/Library/a92d8eb9-f53d-4e86-ac9b-29fd6146977b1033.mspx

Maheen
0
 
vmaheenCommented:
thanks for points,

Did you solved the problem..

can you say some words about the soluation ?

Maheen
0
 
goldmantechologyAuthor Commented:
What actually worked was changing the encryption option to compatible.

Scott
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now