Troubleshooting Transparent Identification

Administration > IWSVA Configuration > User Identification | User Identification

Problem: After enabling the Windows Client query option, if you still receive a high frequency of 401/407 HTTP response Windows pop-ups, it could be caused by:

It is not set up with an administrator account
Solution: Check the values entered in the LDAP settings.
The network connection failed.
Solution: Use the Test Client link and check the results that are listed below.

After enabling the Domain Controller query option, there may be problems with accessing the appropriate Domain Controller server:
Problem: The listed auto-detected Domain Controller servers have an error detail message
Solutions:
1) Try clicking the Refresh button above the listed Domain Controller servers at Administration > IWSVA Configuration > User Identification | User Identification.

2) Add servers manually that cannot be auto-detected.

3) Test the remote query by clicking the Test Remote Query button.

4) See Troubleshooting the LDAP connection.

5) Verify the account information for each Domain controller in Domain Controller list.

6) Click on the "Error Detail"link beside any listed Domain Controller server to help troubleshoot.

Only Windows Active Directory servers and the Windows clients (with a Windows domain login) are supported.
Transparent Identification won’t be able to identify users accurately if multiple users share the same IP address to access the Internet. For example if teminal session or Native Address Translation (NAT) is used.
Transparent Identification will not work when there is a downstream proxy between IWSVA and the Windows client machine.
IF ONLY THE WINDOWS QUERY OPTION IS ENABLED

Transparent Identification only queries the Windows clients with the administrator account in the main domain.

IF ONLY THE DOMAIN CONTROLLER QUERY IS ENABLED
Only interactive logon sessions using the traditional domain/user account format are supported. UPN-format logons, such as user@mydomain.com provide no IP address information and cannot be supported.
No user/IP address information can be derived from log offs or hibernation wake ups.
Information could be delayed by 30 seconds (the default polling settings) or longer if the DC server is located on a remote site with a slow connection.
If a user logs onto a machine, using a domain account, when not connected to the network, then late connects the machine to the network, no logon event is recorded so no IP address information is available.
If a running machine changes its IP address, the activity is not recorded in the Wndows event log so no IP address information can be obtained. This situation may cause inaccurate IP address/user mapping to occur.