Posted: Wed Oct 10, 2012 4:36 pm Post subject: Terminal Server RDP session failure
We currently run an app on a Terminal Server on Windows 2003. This Server is in an NT4 domain (yes I know) and can't be moved.
We have created another version of this App on a Terminal Server in a Win2003 Domain.
We use Windows CE RF devices for warehouse functions. These devices connect to Terminal Server RDP sessions to run the App. They can log into the OLD system but not the new system. Users can log into the new system with a Desktop PC but when you try and login with the RF Device it say's
“Because of a security error the client could not connect to the remote computer verify that you are logged on to the network and then try connecting again”
The RF devices have worked for 3 months but stopped yesterday on the new system.
I know that Terminal Server comes with 120 day's grace but if that's the case WHY can users still log on on a Desktop.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
Looking for more Windows Networking info?
Sign up to the WindowsNetworking.com Monthly Newsletter, written by Enterprise Security MVP Deb Shinder, containing news, the hottest tips, Networking links of the month and much more. Subscribe today and don't miss a thing! View a sample newsletter.
Become a WindowsNetworking.com member!
Discuss your Windows Networking issues with thousands of other Windows Newtorking experts. Click here to join!