Troubleshooting the Connector Subcomponents

This section guides you through the steps you should take to troubleshoot problems with the connector subcomponents. Before you begin, confirm the following:

• 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?

Verifying Subcomponent Installation

Verify that all of the subcomponents are installed. Subcomponent installation must be done after the connector is installed. The subcomponents installed depend upon the connectors used as follows:

• For Active Directory Connectors, no subcomponents are installed.

• For Directory Server Connectors, the Directory Server plug-in must be enabled on the 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 subcomponents are installed after the Windows NT Connector is installed.

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

To Turn on the Windows NT Audit Log

1. In the Start menu, select Programs, then Administrative Tools and User Manager.

2. In the Event Viewer, select Event Log Settings and then Event Log Wrapping.

3. Select Overwrite Events as Needed.

Verifying Server Restart After Installation

After you have installed the subcomponents, ensure that the correct post-installation steps have been taken. For example, after the Directory Server plug-in has been installed, the server must be restarted. After the Windows NT change detector and password filter have been installed on the primary domain controller, the server must be restarted.

Verifying Network Connections

If your subcomponents are still causing problems, confirm that they have established a network connection with the connector. On the machine where the connector is running, verify that the connector is listening for the subcomponent’s connection by running the following command:

# netstat -n -a

For example, the netstat command shows that the connector is listening for incoming connections on port 9999 and the subcomponent has successfully connected as follows:

# 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

However, if the subcomponent has not connected, the netstat command instead shows the following:

# 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.

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.

If the connector is not listening for incoming connections, then the output of the netstat command appears as follows:

# netstat -n -a | grep 9999
#