Home > Connect To > This Computer Can't Connect To The Remote Computer Server 2008

This Computer Can't Connect To The Remote Computer Server 2008

Contents

Error is "Because of a security error, the client could not connect to the remote computer. non could help. Their devices worked properly before the grace period expired. Very strange. 0 Pure Capsaicin OP Scott Alan Miller Apr 18, 2010 at 10:19 UTC Niagara Technology Group (NTG) is an IT service provider. check over here

Then added the License Server entry again, then restarted the Remote Desktop Servers. Was Microsoft able to assist you? Appreciate your patience. Edited by Jaap van Zijp Thursday, April 11, 2013 3:14 PM Thursday, April 11, 2013 3:05 PM Reply | Quote 0 Sign in to vote THANK YOU!!!

This Computer Can't Connect To The Remote Computer Server 2008

One customer has a per device CAL and the other a per User CAL. Now i can lof from old client without any issue. i followed all the recommendations above, and everything checks out. config : Windows 2008 R2 SP1 (Terminal server + Terminal server Licencing) Client :MotorolaMC9190 (Windows Embedded Handheld 6.5 Classic) Wednesday, October 17, 2012 8:38 AM Reply | Quote 0 Sign in

After I disconnect a handheld and try to reconnect it gives the same security error. Using a relay agent: verify that the relay agent is configured properly Using a standard DHCP server with boot options: verify that option 67 is set to acpboot.bin PXE-E55: ProxyDHCP service Cannot Connect to Server xxx (w.x.y.z) Check the event viewer on the terminal server. This Computer Can't Connect To The Remote Computer Windows 7 I have already a few licenses in my license server installed, I also have some Win CE 6.0 thin clients set up.

Please check the OS/Firmware from the Thin Clients. Cannot Rdp To Server 2008 R2 Right click on your Licensing Server name and select properties. 3. Type exported- Certificate in the File name box, and then click Save. More hints Microsoft truncates the terminal names to 15 characters.

Covered by US Patent. This Computer Can't Connect To The Remote Computer Server 2012 Select Advanced -> 'Reactivate Server' 5. Thanks Eric. I make the process but when I reboot the machine all the registry keys return and the RDP 5.1 don't connect.

Cannot Rdp To Server 2008 R2

Unfortunately, my client cannot go out and replace 6 WYSE boxes at this time. look at this site All new RDP clients can connect. This Computer Can't Connect To The Remote Computer Server 2008 Am I missing something on the server HP has directed me to do? Rdp This Computer Can't Connect To The Remote Computer Uninstall the WinTMC client if it is present.

Go to RD Licensing Manager 2. check my blog Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We I even did a reload of RDS1 and tested connecting throughout the process and it worked up until I applied the license and then it stops. Dell Wyse OS 7.1 supports Remote Desktop Protocol 7.1. This Computer Can't Connect To The Remote Computer Server 2003

  • Wednesday, June 27, 2012 12:29 PM Reply | Quote Answers 15 Sign in to vote Ok, here's what I had to do and this fixed the issue on all 3 of
  • Activated licensing with CALs on the TS (2008 r2) and now most WYSE terminals can not connect.
  • Proposed as answer by ChesekA Friday, September 28, 2012 3:28 PM Unproposed as answer by ChesekA Friday, September 28, 2012 3:28 PM Friday, September 28, 2012 3:27 PM Reply | Quote
  • Any solution ?
  • Windows Server 2008 R2 ( Remote Desktop Server + Remote Desktop License Server on the same server) Intermec CK3 Handhelds running WM6.1 and Intermec CK31 Handhelds running WM6.0. ------------- Also I
  • So my issue is with the license and so my question is what is it with the license server running on that server that is keeping thin client from connecting.
  • I have 3 servers currently affected one of which is running Server 2008 x64.
  • Start Registry Editor.
  • On Macs that had previously connected, RDP can't connect but Cord can.

They can still connect to other 2008 servers via RDP, just not any running RDS that have the license server configured. The Installation ID may come from the motherboard serial number, the MAC address on the network cards, or the GUID from the operation system. It worked for 120 days. this content No Video Check video cable, monitor power cable and outlets.

But it still doesn't make sense. Because Of A Security Error The Client Could Not Connect To The Remote Computer Check for a different computer (e.g. Support for NLA was released with Firmware 7.1.113 found in Firmware Package 7.1.3.

Tuesday, November 13, 2012 5:32 PM Reply | Quote 0 Sign in to vote Presuming that it's going to work when I can reboot the server......

Thanks! They say it's due to a non supported client version. Recent Posts 08/11/16 Using FSRM on Windows File Server to Prevent Ransomware 03/11/16 How to Run SysPrep on Upgraded Windows 02/11/16 Auditing Windows Server: Common mistakes and how to avoid them This Computer Can't Connect To The Remote Computer 2012 R2 We did have the problem that Windows XP clients, without Service Pack 3 & Remote Desktop Protocol 7 could not log in.

It sounds like from Alessandro's message that using a 2008 server as the licensing server means the additional security check has not required and clients below version 6.0 can access the Proposed as answer by Roy van den Berg Wednesday, November 07, 2012 8:24 AM Wednesday, November 07, 2012 8:24 AM Reply | Quote 0 Sign in to vote I have tried The terminals in the tree on the primary ThinManager Server show green while the terminals on the secondary are all red Enable automatic synchronization by selecting Manage > ThinManager Server List http://optimisersonpc.com/connect-to/why-can-39-t-my-computer-connect-to-the-internet.html Reboot After doing the above steps, I was able to log in using RD Mobile.

by ITDBTC on Apr 18, 2010 at 7:20 UTC | Windows 0Spice Down Next: Redirect My Documents..PST files? HP thinconnect... Maybe so. Go to RD Licensing Manager 2.

Microsoft truncates the terminal names to 15 characters. Make sure you export your settings on the problem TS first just in case the import mucks things up. Try pinging the terminal server. I can't get it to dish out licenses + I cannot get my HP thin client to connect either.

Reactive server via the given Wizard + web browser 6. So I advise you first of all, please upgrade the Wyse thin client's firmware to the latest version, upgrated the Remote Desktop Connection's edition, and check out whether all the Wyse When the RDP session is clicked it fails to find the terminal server and comes back with the "this computer cannot connect to the remote computer". 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.

This is prevelant on all XP clients (about 25) and occurs again if the XP client is rebooted / or disconnects. Product of all divisors=cube of number. The other device type, of which there are many in the environment, is the HP T5510 Thin Client.

Back to Top