Petri.com forums Home Forums Start Page Forums Frequently Asked Questions FAQ Member List Members List
Go Back   Petri IT Knowledgebase Forums > Microsoft Networking Services > Terminal Services
Petri.com is happy to award RicklesP the title of Most Valuable Member !!!
Register Calendar Calendar Search Petri IT Knowledgebase Forums Search Todays Posts Today's Posts Mark Forums Read
Notices

Client to Client Remote Desktop Issue since enabling FIPS Crypto

Client to Client Remote Desktop Issue since enabling FIPS Crypto

this thread has 1 replies and has been viewed 9545 times

Closed Thread
 
Thread Tools Search this Thread Display Modes
  #1  
Old 9th November 2006, 22:43
gdkenoyer gdkenoyer is offline
Casual
Casual
 
 Join Date: Nov 2006
  6 month star 12 month star
 Posts: 3
 Reputation: gdkenoyer is on a distinguished road (10)
Question Client to Client Remote Desktop Issue since enabling FIPS Crypto

Our policy has required me to implement FIPS Compliant System Crypto. To (re)enable remote Server management, I upgraded the workstations' RDP to v5.2.3790.1830 (from 5.1.2600.2186).

I now no longer get the "the client could no establish a connection..." error box and can connect from my WinXP SP2 workstations to my W2k3 SP1 Servers fine.

BUT I cannot use the new client to connect to any other XP WORKSTATION. I get an error box similar to the old "the client could not..." but this one has a 4th "likely cause" of:

"The remote computer might not support the required FIPS security level. Please lower the client side required security level Policy, or contact your network administrator for assistance."

The FIPs is a domain-wide policy, and the workstations are current in patches and have rebooted since the policy was imposed.

Last edited by gdkenoyer; 9th November 2006 at 22:44.. Reason: forgot to subscribe
  #2  
Old 10th November 2006, 19:30
gdkenoyer gdkenoyer is offline
Casual
Casual
 
 Join Date: Nov 2006
  6 month star 12 month star
 Posts: 3
 Reputation: gdkenoyer is on a distinguished road (10)
Default Re: Client to Client Remote Desktop Issue since enabling FIPS Crypto

This is sad, I'm replying to myself...and not even giving an answer.

Note that this is also posted over in the Microsoft Forums in the Windows Terminal Services section.

In the MS Frorum, "TP" noted that the old client was still available/useable:
Code:
When connecting to an XP Pro workstation, use the older 
5.1.2600.2180 client. It is still installed on your workstation, 
because it is part of the OS. 

Use Start-->Run-->mstsc.exe 

Or you can create a shortcut to it: 

Right-click on the Desktop-->New-->Shortcut-->mstsc.exe
However, using two clients is a pain and I'm hoping that there's a better answer.
Closed Thread


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Remote desktop sharing sakthi Windows 2000 Pro, XP Pro 7 26th September 2006 10:25
Remote Desktop Connection Issue Cogent SBS 2000 / 2003 / 2008 / 2011 2 27th April 2006 09:58
Remote Desktop to one server 2003 DC works but not other DCs permute Terminal Services 2 13th March 2006 06:43
Exchange 2003 and remote desktop Epid Terminal Services 1 25th January 2006 17:53
Multiple Remote Desktop Connections Lukas DSL, Cable, and other Broadband Issues 6 27th June 2004 12:23


All times are GMT +3. The time now is 05:44.

Steel Blue 3.5.4 vBulletin Style ©2006 vBEnhanced
Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
 

Valid XHTML 1.0!   Valid CSS!

Copyright 2005 Daniel Petri