Event ID: 12545 Could not connect to Active Directory/LDAP Server.
- 1.Failure to connect to an Active Directory/LDAP server
- 2.Failed to connect to all Active Directory/LDAP servers
- 3.Although connection with Active Directory was attempted, no response was received from Active Directory
- 4.Although connection to Active Directory was attempted via LDAP, communication using servers other than LDAPS is not allowed for Active Directory
- 5.Connection was attempted to Active Directory’s port 636, but Active Directory denied the connection
- 6.Although a request was sent to Active Directory via LDAP, there are no viewing privileges
1.Failure to connect to an Active Directory/LDAP server
Phenomenon
The following event is output to Event Viewer.
| Log Level | Message |
|---|---|
| warn | [Overview] |
Description
Failure to connect to an Active Directory/LDAP server.
Support
Check whether the following parameters in the configuration file are configured correctly.
- ldap addresses, port, user, password, and base_dn
Check whether the Active Directory/LDAP servers are operating properly.
When an LDAPS connection is enabled, check whether LDAPS is correctly configured on Active Directory.
2.Failed to connect to all Active Directory/LDAP servers
Phenomenon
The following event is output to Event Viewer.
| Log Level | Message |
|---|---|
| error | [Overview] |
Description
Failed to connect to all Active Directory/LDAP servers.
Support
Check whether the following parameters in the configuration file are configured correctly.
- ldap addresses, port, user, password, and base_dn
Check whether the Active Directory/LDAP servers are operating properly.
When an LDAPS connection is enabled, check whether LDAPS is correctly configured on Active Directory.
3.Although connection with Active Directory was attempted, no response was received from Active Directory
Phenomenon
The following event is output to Event Viewer.
| Log Level | Message |
|---|---|
| warn | [Overview] |
Description
Although connection with Active Directory was attempted, no response was received from Active Directory.
Support
Check whether the following parameters in the configuration file are configured correctly.
- ldap addresses, port, user, password, and base_dn
Check whether the Active Directory/LDAP servers are operating properly.
4.Although connection to Active Directory was attempted via LDAP, communication using servers other than LDAPS is not allowed for Active Directory
Phenomenon
The following event is output to Event Viewer.
| Log Level | Message |
|---|---|
| error | [Overview] |
Description
Although connection to Active Directory was attempted via LDAP, communication using servers other than LDAPS is not allowed for Active Directory.
Support
Take any of the following actions.
- Allow LDAP communicator on Active Directory
- Enable STARTTLS on Directory Sync
Specify start_tls for ad.ldap.server.encryption.
5.Connection was attempted to Active Directory’s port 636, but Active Directory denied the connection
Phenomenon
The following event is output to Event Viewer.
| Log Level | Message |
|---|---|
| warn | [Overview] |
Description
Connection was attempted to Active Directory’s port 636, but Active Directory denied the connection
Support
Check the following.
- Check for settings that allow Active Directory to deny connection
- When STARTTLS is enabled on Directory Sync, check whether 389 is specified as the connection port for improvement
Start STARTTLS communication with port 389, not with port 636.
6.Although a request was sent to Active Directory via LDAP, there are no viewing privileges
Phenomenon
The following event is output to Event Viewer.
| Log Level | Message |
|---|---|
| error | [Overview] |
Description
Although a request was sent to Active Directory via LDAP, there are no viewing privileges.
Support
Check whether users for connecting to Active Directory have privileges to view all users and groups that will be synchronized over Active Directory.