Link to home
Create AccountLog in
Avatar of StephanieFoster
StephanieFosterFlag for United States of America

asked on

XP Embedded client "Because of an error in data encryption..."

I have a 2008 Terminal Server.  I have several XP and Win 7 Prof computers within the main office as well as several outreach (connected via Cisco Routers) that never disconnect.  I have about 18 thin clients running XP Embedded that receive the following error - "Because of an error in data encryption, this session will end.  Please try connecting to the remote computer again."  This can happen once or twice in a day, or as it just happened to a staff - seven times within an hour.  It always lets them back on and it has saved where they were, but as I can attest - it is very frustrating when you are typing along and get booted.  

I have looked ont he server and the only event that looks close to the time of disconnect is 4364 under Security.  But I can't tell if it was someone that just disconnected him/herself or if it was the encryption error.  

We are a 24/7 business so there is usually always someone on the server.  Last time I tried to try a fix - I bumped everyone off.  Oops.  So i hate to just "try this".  

On the thin clients, I did make a change.  I used to have three logins, one admin (me only), supervisors (core username) and user.  I have cybersitter installed on all because we have had issues with surfing inappropriately.  I changed it so the supervisors and users used the same User login.  I did create/save the RDP for manager/user.  Manager has a login, all staff use another login - we have 200 employees, too many to have their own login since we are non-profit!    Managers have told me they have seen an increase in the error since I added them to the user side.  User and Supervisor have the same abilities on the computer.  One just had full access to the internet, the other has some restrictions, but full access to the server address...

Is there something on the client side that I can try?

Thank you
Stephanie Foster
ASKER CERTIFIED SOLUTION
Avatar of Michael Pfister
Michael Pfister
Flag of Germany image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of StephanieFoster

ASKER

I'll try that - thank you.  Can I do the above to the server when there are people logged on?  I may try it first thing in the morning (5:00ish am) when there may be just a couple people, if any on.  The only bad thing is that I am at home when I do that, so if I mess something up, it is down for about 2 1/2 hours...

Here is what I did to the terminal server - I disabled the Large Send Offload under the Broadcom advanced settings.  After I temporarily took down the server (I learn by mistakes!) I decided I'd best not do anything else until I was either the only one on or I had asked what would be the best thing to try.
Stephanie
The change on the server won't break existing connections. The only side effect will be that, depending on the RDP version your clients are using, you will get a security warning when connecting.
I tried both of the above (increasing the SSL logging on the client and server) and modified the RDP Security Layer on the server.  I've had reports today that the issue is still happening.  it is only happening to staff on these thin clients.  I'm thinking now it might have to do with the CyberSitter.  Even though I have added the ip address to the server to the "always allow" these sites it must be something there.  I'm guessing I will need to allow staff full internet access at the off site locations.  Not really what I want.  I will try that at one location and see what happens.

Thanks for your help.
After increasing the logging Level did you see any SCHANNEL events logged?
I looked but didn't see anything?  Not sure exactly where to look.  I didn't see anything that specifically said SCHANNEL.
Well, I tested at one location by turning off cybersitter.  No issues since.  While the SCHANNEL has seemed to slow them down, it didn't stop them all together like the cybersitter did.  

thank you for your assistance.
While it was not the whole fix, it did help somewhat on both sides - both client and server.