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. Change Connection Method to 'Web Browser' Go back to the Licensing Server, right click your server. You can download version 6.0 here: http://www.microsoft.com/en-us/download/details.aspx?id=21296 Download the security update to upgrade to version 6.1 here: http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=22926 Credit to this article for the explanation of how to apply the 6.1 To do it: In HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders, edit the value of SecurityProviders key by adding credssp.dll at the end (separated from its current value by comma) Then in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa add the line tspkg http://onlinetvsoftware.net/because-of/because-of-a-security-error-rdp-xp.php
Join Now Hi, I am building my first Server 2012 network, and I am some strange issues with license servers. Alongside with that, there appeared another problem with printing via Easy Print. Our sister company runs our point-of-sale system from a 2003 Server via Remote Desktop. Post navigation ← Using ASP.NET SignalR To Play an RPG External DNS and redundant internet connections → 2 thoughts on “Why Can't Legacy Thin Clients Connect to RDS on Server 2012?”
New connections to the terminal server result in: Because of a security error, the client could not connect to the terminal server Connecting to the old Windows 2003 server works fine. We put them into production in 2006, and they'd been working reliably and silently ever since. Chris Vesper Bro, do you even code? Browse other questions tagged windows-server-2008-r2 terminal-server thin-client rds or ask your own question.
Required fields are marked * Name * Email * Website Comment You may use these HTML tags and attributes:
The x509 keys change from autogenerated 4096 key-length SHA2 to 2048 key.length SHA1 certiifactes after the reboot! This allowed the older thin clients to connect. Because Of A Security Error Rdp 2008 This long thread on social.technet.microsoft.com is filled with users having a similar experience.
It is possible to enable NLA support only from the registry. Will the medium be able to last 100 years? I put the answer on ServerFault as well. When we bought that house, it had an unfinished basement and an unfinished attic room, making the cabling process very simple.
I'm still searching for a tool to handle the updates on the HP Linux-based thin clients. –ewwhite Feb 1 '13 at 23:39 The above process also helped me connecting Because Of A Security Error Rdp 2012 R2 Windows 8 uses RDP 8. The other device type, of which there are many in the environment, is the HP T5510 Thin Client. RDP 5.x clients CANNOT connect, except as follows: RDP 5.x clients CAN connect if no license server is activated.
The Answer We had to get a definitive answer, so we opened a support call with Microsoft. I then rebooted the server, and since rebooting it, I get exactly the same error trying to log on from XP Embedded thin client! Because Of A Security Error Rdp 2008 R2 set it to any version and it should pass through, if not then please post the logs so we can see whats going on. Because Of A Security Error Rdp Xp Join the community Back I agree Powerful tools you need, all for free.
To check which version of Terminal Services client you have installed go to C:\Windows\System32\ and check the properties of mstsc.exe (since updating to 6.1 on Win2k3 I have version 6.0.6001.18564). check my blog Once we were sure it was running well, we'd activate the license server and install the RDS CALS. Snap! Least Common Multiple Exporting an animation as a gif file How to label into x-axis and y-axis like this picture? Because Of A Security Error Rdp 2003
Therefore, the RDP 5.x client can no longer connect. The older thin clients were using RDP 5.x, whereas Windows XP SP3 uses RDP 6.x, and Windows 7 uses RDP 7 or RDP 8, depending on whether it's been upgraded. We also rent our point-of-sale system via Remote Desktop. this content You may get a better answer to your question by starting a new discussion.
When remote desktop is enabled an administrator has to choose one of the following options: Allow connections from computers running any version of Remote Desktop (less secure). Because Of A Security Error Rdp Windows Xp May 2, 2013Remote Desktopchris At BBL Systems, we use Remote Desktop Services extensively. Is my workplace warning for texting my boss's private phone at night justified?
However, when a RDS license server is activated, a higher level of encryption is required (2048 bits) and RDP 5.x cannot support this level of encryption. Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure). The first batch of users migrated well, but as we encountered people with older HP devices, we discovered that some simply could not connect to the Windows 2008 R2 server. Because Of A Security Error Rdp 2008r2 I'm an Information Technology manager for a Fortune 500 company.
Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? Microsoft to end Windows 7 PC sales, Firefox tackles weak encryption Spiceworks Originals A daily dose of today's top tech news, in brief. © Copyright 2006-2016 Spiceworks Inc. Can't add Controller to MVC project in Visual Stud... ► July (1) ► May (1) ► March (1) ► 2008 (8) ► October (1) ► September (1) ► June (3) ► have a peek at these guys 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
I'd be curious to know if you ever got it working. 0 | Reply - Share Hide Replies ∧GuestAdediran Oluwaseyi10 months 6 days agothank you so much for this post… You I can connect to all my other Server 2012 servers fine, no issues at all. 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 That issue has been traced back to the Linux rdesktop capabilities.
My total licenses next to that shows 10 though.