Errors: ldap 81/48 - Socket error 107 - Error code 2 - Handshake 3154
search cancel

Errors: ldap 81/48 - Socket error 107 - Error code 2 - Handshake 3154

book

Article ID: 202190

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On Agents (SiteMinder) CA Single Sign On Federation (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) SITEMINDER

Issue/Introduction


How to avoid the following messages in the smps.log:

  1. Error# '81' during search: 'error: Can't contact LDAP server' Search Query = '(&(uid=****)(objectclass=****)(!(myType=***)))'
  2. Failed to initialize TCP client connection. Socket error 107
  3. [sm-Server-06007] failed. Error code : 2
  4. [sm-Ldap-00770] (AuthenticateUser) DN: 'cn=***,ou=Users,o=****,c=us' . Status: Error 48 . Inappropriate authentication
  5. Bad security handshake attempt. Handshake error: 3154

 

Resolution


Here are the possible ways to investigate each error:

  1. This error might appear if the LDAP User Directory closes the connection (1).
  2. This issue happens when the Web Agent closes the connection and Policy Server has not received the info to close the connection (2). To help prevent that, consider implementing SM_ENABLE_TCP_KEEPALIVE (3).
  3. This error means the data is not found in the Session Store (4). This error message might appear if there is a mixture of persistent and non-persistent realms in the environment (5).
  4. Investigate with the LDAP vendor the reasons for this. It may be a configuration problem on the LDAP side (6).
  5. This error means that the shared secret and/or the agent name does not match with the values from the Policy Store for that given Agent. Usually, the solution is to register the Agent again (7)(8)(9)(10)(11).
     

Additional Information