_White_Background_square_1920px.png?width=256&height=96&name=FLEETWATCH%20Fleet%20Information%20Technology%20by%20S%26A%20Systems%2c%20Inc%20(06_28_2021)_White_Background_square_1920px.png)
Fleetwatch FMS · Data Tools Login (On-Premises)
What Does “Unable To Log Into Windows Active Directory. Please contact FLEETWATCH” Mean?
Data Tools couldn’t sign the user in through your agency’s Windows Active Directory. It almost always comes down to one of three things: the user name’s capitalization doesn’t match, the password is wrong, or the agency’s Active Directory server is down or can’t be reached.
On-premises systems only. This message only appears on Data Tools systems hosted on your agency’s own server. It should not appear on Fleetwatch Cloud systems. If you see it on a Cloud system, contact Fleetwatch Support.
The message appears in red above the Username and Password boxes.
Common Causes
| Cause | What to do |
| User name capitalization doesn’t match | User names can be case-sensitive. Type the user name exactly as it’s set up in Data Tools (see Check 1 below). Fleetwatch Support can check the login logs and compare what was typed with the user name set up in Data Tools. |
| Wrong password | The user signs in with their Windows (network) password. Re-enter it carefully. If they’ve forgotten it or it has expired, your agency’s IT department can reset it. |
| Active Directory server is down | If several users suddenly get this message, the agency’s on-premises Active Directory server may be down or unreachable. Contact your agency’s IT support (see Check 3 below). |
Check 1: The User’s Profile
The yellow numbers on the screenshots match the steps.
| 1 | Go to Administration >> Edit User Rights. Pick the user from the Employee list and click Select User. |
| 2 | Check the Employee Username. User names may be case-sensitive, so the user must type it exactly as it appears here, including capital letters. If needed, update it to match how the user prefers to type it. |
| 3 | Make sure Use Windows Active Directory is checked. When it’s checked, the user logs in with their Windows (network) password, and the Data Tools password boxes are grayed out. |
Check 2: The LDAP Settings
| 4 | In the System Information settings, check that the LDAP Address (your Active Directory server) and LDAP Domain are correct. Your agency’s IT department can confirm the right values. |
Check 3: Can the Server Reach Active Directory?
| 5 | On the on-premises Fleetwatch server, open Command Prompt and ping the LDAP address. Replace the example address with your LDAP Address. |
C:\> ping ad.youragency.org
Reply from 10.10.20.5: bytes=32 time=1ms TTL=127
Reply from 10.10.20.5: bytes=32 time=1ms TTL=127
Reply from 10.10.20.5: bytes=32 time=1ms TTL=127
Reply from 10.10.20.5: bytes=32 time=1ms TTL=127
Replies mean the server can reach Active Directory. Go back to Checks 1 and 2.
C:\> ping ad.youragency.org
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out, “could not find host” or “Destination host unreachable” means the server can’t reach Active Directory.
No response to the ping? Contact your agency’s IT department. Ask them to confirm the Active Directory server is running and accepting connections from the on-premises Fleetwatch server.
Checked everything and the user still can’t log in? Contact Fleetwatch Support with the user’s user name, and we can check the login logs.