Don't get confused with the java.net.SocketException: Network is unreachable, which simply means that the server is not reachable. You can test this by doing a simple ping against the IP address and/or the hostname.

Other Error Messages:

org.identityconnectors.framework.common.exceptions.ConnectorException: java.net.SocketException: Network is unreachable

Note: If your IP works though your hostname doesn't, then it's likely a DNS issue. If you have 2 servers (or as I have it, 2 VMs) within the same subnet, you can determine this by logging in as root and editing the nameserver with the IP address within the /etc/resolv.conf file. Once you've done that, try pinging the hostname again

Now, going back to the No route to host

Now, going back to the No route to host

org.identityconnectors.framework.common.exceptions.ConnectorException: java.net.NoRouteToHostException: No route to host

Knowing you can connect to the AD server, ensure the connector server service is running on the AD domain (or if you have a separate server running the connector server, test that instead)

Once that's been tested, log into the (identity system administration) sysadmin console and click on 'system configuration' on the right hand side. Within there you will see both the connector server AND the AD server. The simple visual error does not indicate which host is not reachable. Ensure within the IT resource 'host' parameter contains either the IP address or the hostname. My issue wasn't that the Active Directory IT Resource was unreachable but in fact the connector server was no reachable.

In my case I had to change the nameserver within the /etc/resolv.conf configuration file. Furthermore, I changed the host from the IP address to now the full hostname+domain (in my case it's hostname1.technicalconfessions.local)

About the author