Users are not authenticated through the Auth Connector.
Reports that are pulled from the portal show Unauthenticated users.
Inspecting the BCCA logs yields many similar to the following:
Ip address 0xb14720a not found in logon_map
Ip address 0xd14720a not found in logon_map
Ip address 0x6596a8c0 not found in logon_map
Ip address 0x460a150a not found in logon_map
NOTE:0x460a150a is a reverse hex encoding for the IP address of 10.21.10.70.
The reason for unauthenticated users in reports might be because Auth Connector is unable to communicate with the Authentication Data Pods. Or it receives a "not found" upon querying the logon mapping between computer IP address and user name within your Active Directory (AD) services. In other words, your AD cannot map the user name in your domain with the IP address Auth Connector is querying and returns "not found". Therefore, as the portal reporting function is not able to display user name, it displays unauthenticated userinstead.
There are many reasons why Auth Connector is unable to authenticate the users:
Trusted Root Certificate is not installed on the Auth Connector
Auth Connector traffic is routing through WSS
Source NAT is enabled
Authentication data pods are not white listed on the firewall on port 443
The failure of the computer IP-to-username mapping in AD might not be an Auth Connector issue but an AD issue:
Computer fails to log on to Active Directory domains.
Computer logs on as Windows local cache profile.
Computer is not updated with security of Microsoft Active Directory requirements.
Computer is not accepted by your AD because of some other security reasons or compatibility issue.