IO::Socket::INET errors

Created: 2012-04-20 08:09:59
Modified: 2017-05-17 16:34:23
Tags: Errors Troubleshooting UnitySync

The errors described below indicate the inability to connect to either the Source or Destination directory. The most common causes are outlined below.

Error Example 1

Fatal Error  
Could not connect to the destination server (Search)  
IO::Socket::INET: connect: Unknown error  

This error typically occurs when attempting to Join to an Active Directory (AD) Destination. When running a Join connection to a Destination AD domain, UnitySync will attempt to query the Global Catalog (GC) to find the match. Therefore, the connection’s Destination IP must be that of a Domain Controller (DC) that contains the GC. On the Destination tab, always specify the standard LDAP port (389) when writing to AD but please note that since the Join will query the GC, the UnitySync server must also have access to read from the GC’s LDAP port, 3268.

Error Example 2

Error Summary  
Error line 1: Could not connect to the source server  
Error line 2: IO::Socket::INET: connect: <Error>

There are a few possible causes of this type of error:

  • You are trying to use SSL, but SSL is not configured on the source server
  • The account running SSL does not have read access to the certificate for SSL (or there is no certificate present)
  • The UnitySync SSL library only allows server keys
  • Your certificate must be self signed and it is not
  • UnitySync is unable to connect to the LDAP port on the specified server

Test to troubleshoot a connectivity problem or inability to connect to the LDAP port:

  • Run the following from a command line on the UnitySync server
    telnet x.x.x.x port

  • If this test results in an error, verify you are accessing the correct IP and Port. If so, you must resolve the issue that is prohibiting you from connecting to the IP or Port. Check connectivity to IP, verify firewall settings, etc.

  • If the test is successful but you are still receiving the described errors, contact for further assistance.

Error Example 3

IO::Socket::INET configuration failed error: 0000000000:lib(0):func(0):reason(0)

If you get this type of connectivity error, try using an LDAP browser (like LDP) to re-test connectivity to this target. If the alternate browser also errors out, then you have an underlying connectivity error that must be addressed.

If your alternate browser successfully connects, your key may not meet security requirements for UnitySync. The UnitySync SSL library only allows server keys.

This is a security feature so that a user certificate not be used as an impostor. You may find you can authenticate successfully using LDP; this is because LDP does not have this security restriction.

Error Example 4

IO::Socket::SSL: SSL connect attempt failed because of handshake problems error:00000000:lib(0):func(0):reason(0)

We’ve seen this error when firewall rules were changed on the Source. The solution is to add the IP’s to the exception rules on the firewalls.

Additionally, this error may indicate a failure to connect over SSL from the UnitySync server to the target server. This connectivity problem could be related to certificates or it could be a hardware configuration malfunction. Your firewall, router, and cabling should be checked.

Share this article:

  1. Directify - Self Service

  2. Mimic - Replication

  3. UnitySync - Sync
  1. emPass - Sync
  1. Profiler
  2. SimpleSync