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.
goldmantechologyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
vmaheenCommented:
thanks for points,

Did you solved the problem..

can you say some words about the soluation ?

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

Scott
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.