000033367 - Cannot Create Archer Endpoint - Connection Reset in RSA SecOps 1.3

Document created by RSA Customer Support Employee on Jun 20, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000033367
Applies ToRSA Product Set: RSA SecOps
RSA Version/Condition: 1.3
IssueAfter upgrading SecOps from 1.2.x to 1.3, the Archer Endpoint could not be added due to "Connection Reset" in the connectionManager.log
Message - java.net.SocketException: Connection reset
CauseThe Cert, the Bindings, and a Registry setting for SSLv2 had to be created/enabled.
Then the Archer Endpoint was able to be created.
Resolution

1. Remove the Certificate and then re-add it.
2. Reset the Bindings in the environment, ensuring that SSL is enabled.
3. Via the Registry (Start > Run > regedit) modify or create the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server 
4. Create/Edit the value Enabled, type DWORD, value "0".
5. Reboot.
Notes: The same procedure applies to key names PCT 1.0, SSL 2.0, SSL 3.0, TLS 1.0. In newer versions of Windows (especially Server editions), some of these are disabled by default - which depends on the version.  
Reference: http://support.microsoft.com/kb/187498

Attachments

    Outcomes