IO::Socket::INET: connect: Error

This error indicates the inability to connect to either the Source or Destination directory. The most common causes are outlined below.

1 Error on Create/Join Sync

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

If this error occurs when attempting to Join (Search) to an AD/Ex2000 destination:

When running a Join (Search) connection to a destination AD/Ex2000 domain, the Sync will attempt to query the Global Catalog to find the match. Therefore, the connection’s Destination IP must be that of a Domain Controller that contains the Global Catalog. On the destination tab, always specify the standard ldap port (i.e 389) when writing to AD. However, since the Join will query the Global Catalog, the Sync server must also have access to read from the Global Catalog’s ldap port, 3268.

Use the below test to troubleshoot ability to connect to both ldap ports.

2 Error on Test Connection or Sync

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

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

a) You are trying to use SSL, but SSL is not configured on the source server.

b) The account running SS does not have read access to the certificate for SSL. (Or there is no certificate present.)

c) The Sync is unable to connect to the ldap port on the specified server.
Use the below test to troubleshoot a connectivity problem.

To Test ability to connect to the ldap port:

Test the connectivity and availability of the ldap port by running the following from a command line on the Sync server:

telnet x.x.x.x port

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

If the test is successful, contact Support@dirwiz.com or further assistance.