I've looked in the event log on the server and didn't see any errors that correlate with the times of the attempts of the login. We thought it might be related to the activation of the license server, so we de-activated it. My new house... and RDP sessions initiated to the new terminal server disconnect immediately. his comment is here
There's a disheartening statement in that thread: "The official word from Microsoft is 2008R2 RDS does not support clients below 6.0. When we bought that house, it had an unfinished basement and an unfinished attic room, making the cabling process very simple. All Rights Reserved. The environment is a mix of several generations of HP thin clients, as well as some Axel hardware terminals.
About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up For assistance, contact your system administrator or technical support. There's also a proposed solution that involves deleting some registry values from under the "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM" registry key that some reported success with. Previous:Removable USB Flash Drive as Local Disk in Windows 7 Next:How to access VMFS Datastore from Linux / Windows Related Articles Group Policy Settings to Deploy Updates using WSUS Installing
I can log in fine from Windows 7 Pro. RDP 5.x clients CANNOT connect, except as follows: RDP 5.x clients CAN connect if no license server is activated. Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? Good place for troubleshooting hints on this - http://blogs.msdn.com/b/rds/archive/2011/01/10/how-to-resolve-the-issue-remote-desktop-disconnected-or-unable-to-connect-to-remote-desktop-terminal-server.aspx0 Ghost Chili OP Best Answer Kelly Armitage Sep 26, 2012 at 7:26 UTC Sounds like some clients
Any chances I'll have to reinstall licenses or re-configure those thin clients after removing those registry entries or reactivating licensing server? –dotz Feb 8 at 0:22 This fixed an Because Of A Security Error Rdp 2012 R2 My total licenses next to that shows 10 though. Recently found the problem: Windows XP RDP clients cannot connect to the newly deployed Remote Desktop Services terminal farm on Windows Server 2012. Snap!
Any ideas? this content Same setting is also set in the rdp protocol settings of the remote desktop session host configuration. 0 This discussion has been inactive for over a year. I'm pasting it here, slightly edited, for reference, but the credit goes to EricWy: Open Remote Desktop Licensing Manager Right-click your Licensing Server name select Properties. XP users have complained about such rdp client errors as: Because of a security error, the client could not connect to the remote computer. Verify that you are logged on to Because Of A Security Error Rdp 2003
Snap! Is that potentially the problem. Menu Skip to content Chris Vesper Programmer Posts Commercial Projects About Search for: Why Can't Legacy Thin Clients Connect to RDS on Server 2012? http://gatoisland.com/because-of/because-of-a-security-error.php We suspected that the version of RDP on the client dictated whether or not it can connect.
The tech first told us to work with the thin client vendors to solve the problem. Because Of A Security Error Rdp Windows Xp The Problem On Saturday morning a user said they were getting an error message when they tried to connect to the server: Remote Desktop disconnected because of a security error. Most of our larger customers also use Remote Desktop to run our software.
Spent a good two days now playing around with this, and can't figure out for the life of me what is going on. All of the problem units were running RDP 5.x. I tried endless things - reactivating license server, checking firewall settings, removing requirement for network level authentication, reinstalling RDS roles, and was having none of it. Because Of A Security Error Rdp 2008r2 The client cannot to the remote computer.
Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? Everything worked just fine for few months but then all of a sudden it just stopped. This long thread on social.technet.microsoft.com is filled with users having a similar experience. check over here Join Now I am the IT Manger for a company that has 5 offices and they use Remote Desktop to get between the multiple servers. I have a few computers having
Is my workplace warning for texting my boss's private phone at night justified? How are the settings regarding remote desktop configured? You may need the latest client (7?) 3 Ghost Chili OP Helpful Post _Justin_ Sep 26, 2012 at 7:56 You may be limited in the number of users who can connect simultaneously to a Remote Desktop session or Terminal Services session 2. If this was the case, why did it work during our test period, and then fail when we activated the license server?
Mass replace names in vertex groups Which requires more energy: walking 1 km or cycling 1 km at the same speed? I believe I can rule out a couple things. How to increase the population growth of the human race Does the verb 'to busy' require a reflexive pronoun? Networking I've moved recently.
My only purpose for this blog is the hope that it helps someone, someday, somewhere. They have around 50 users who access it via thin clients, Windows 7, and Windows 8. Windows 8 uses RDP 8. Not the answer you're looking for?
More info here: http://technet.microsoft.com/en-us/library/cc794832(v=ws.10).aspx If the administrator selects the latter then you can't connect via a Windows Server 2003 machine unless you update your Terminal Services client to version 6.1. How are the settings regarding remote desktop configured? You may need the latest client (7?) That was my other thought. 0 Pimiento OP Kevin_139 Sep 27, 2012 You may get a better answer to your question by starting a new discussion. There are other things you can try.
I did notice that if I go into the Remote Desktop Licensing Manager, under my server name it says "Windows server 2008: installed TS or RDS Per User CALs" and next