Troubleshooting Subcomponents

To Troubleshoot Subcomponents in Your Deployment

1. Have all subcomponents been installed?

   Subcomponent installation must be done after the connector is installed:

   • For Active Directory Connectors, no subcomponents are installed.

   • For Sun Java System Directory Server Connectors, the Directory Server Plug-in must be installed on the Sun Java System Directory Server being synchronized.

   • For Windows NT Connectors, the Windows Change Detector and Password Filter subcomponents must be installed on the primary domain controller for each Windows NT domain being synchronized. These two subcomponents are installed together after the Windows NT Connector has been installed.

   ---

   Note –

   For the Windows NT SAM Change Detector subcomponent to be effective, you must turn on the NT audit log. Select Start -> Programs -> Administrative Tools -> User Manager, and then select Policies -> Audit Policies. Select Audit These Events and then both the Success and Failure boxes for User and Group Management.

   Select Event Log Settings in the Event Viewer -> Event Log Wrapping, and then select Overwrite Events as Needed.

   ---

2. Have the subcomponent post-installation steps been followed?

   After the Directory Server Plug-in has been installed at the Sun Java System Directory Server, the server must be restarted. After the NT Change Detector and Password Filter have been installed on the primary domain controller, the server must be restarted.

3. Are the subcomponents running?

   Is the Directory Server where the Plug-in was installed running? Is the Primary Domain Controller where the Change Detector and Password Filter were installed running?

4. Have the subcomponents established a network connection to the connector?

   On the machine where the connector is running, verify that the connector is listening for the subcomponent’s connection by running netstat -n -a. The following examples show the results of this command for three different scenarios. (The connector was configured to listen on port 9999.)

   1. The connector is listening for incoming connections, and the subcomponent has successfully connected, which is the expected result:

      # netstat -n -a | grep 9999 *.9999 *.* 0 0 65536 0 LISTEN 12.13.1.2.44397 12.13.1.2.9999 73620 0 73620 0 ESTABLISHED 12.13.1.2.9999 12.13.1.2.44397 73620 0 73620 0 ESTABLISHED

   2. The connector is listening for incoming connections, but the subcomponent has not connected:

      # netstat -n -a | grep 9999 *.9999 *.* 0 0 65536 0 LISTEN

      After verifying that the subcomponent is running, examine the subcomponent’s local logs for potential problems.

   3. The connector is not listening for incoming connections:

      # netstat -n -a | grep 9999 #

      Verify that the correct port number was specified. Verify that the connector is running and is in the READY state. Examine the connector’s local logs for potential problems.