Date: Fri, 25 Feb 2000 15:55:02 -0500
To: "Pete Duffin" <[EMAIL PROTECTED]>, "'Owens, Jeff'" <[EMAIL PROTECTED]>, "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
From: John Rezabek <[EMAIL PROTECTED]>
Subject: RE: ISS issue
Peter,
First are you upgrading or is this a fresh install? From version 3.1 to 3.2 the encryption strength changed from 163 to 239 bit encryption. I have seen the problem you are experiencing from folks upgrading between these versions. You can quickly verify your encryption levels by doing the following:
Before you launch the Console,
Go into the C:\Program Files\ISS\RealSecure 3.2 directory and double click on ClientTrace Log (This turns logging on)
Now launch the Console and TRY to connect to the Engine you are having problems with.
Then shutdown the console
Go into the C:\Program Files\ISS\RealSecure 3.2 directory and double click on ClientTraceLogOff (This turns logging OFF)
Then go into the C:\Program Files\ISS\RealSecure 3.2\logs and open the rscontrc file and look at the Crypt 1 and Local 1 entries for the encryption and verify if they match. I am pretty sure they will not match and they need to.
Tech Support should be able to help you resolve this issue. Let me know if you need additional info.
Thanks
John
At 08:54 AM 2/24/00 -0800, Pete Duffin wrote:
I have this same problem with the same setup and version.
I was told by support to reinstall the console using the high encryption strenth version. I also made sure the the proper key was listed first in the encryption list.
None of this worked. Any Ideas???
Pete Duffin
-----Original Message-----
From: Owens, Jeff [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 23, 2000 1:05 PM
To: '[EMAIL PROTECTED]'
Subject: FW: ISS issue
TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------
Running RealSecure Console version 3.2 on Windows NT and a Network Engine on
Solaris7.
This install was sucessful on both. On the console we exported the keys.
We then copied the CerticomNRA keys (in the ....\keys\CerticomNRA directory
on the NT box) into the \opt\ISS\RealSecure\keys\CerticomNRA directory on
the Solaris box. We stopped and started the Network Engine and then tried
to connect to the Engine from the NT Console.
The response we get is something similar to:
"Peer cryptographic provider is not compatible with the console
providers"
We have re-exported the keys and copied them over multiple times without
improvement. Is this indicative of something in particular that I may be
missing?
Thanks,
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
FishNet Security
816.421.6611
Fax: 816.421.6677
http://www.kcfishnet.com <http://www.kcfishnet.com>
John M. Rezabek Phone: 727.517.1500
Technical Product Manager Fax: 727.517.9090
ISS Internet Security Systems, Inc. Pager: 888.784.6185
NASDAQ (ISSX) 