Technical Library | Support

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Using Logon Agent for Transparent User Identification > Logon Agent troubleshooting
Logon Agent troubleshooting
51073 | Using Logon Agent | TRITON AP-WEB and Web Filter & Security | 12-Oct-2015
If some user requests are being managed by the Default policy because Logon Agent is not able to identify the user:
*
Make sure that Group Policy Objects (GPO) are being applied correctly to Windows clients, as described in Configure the Windows logon scripts to run.
*
If User Service is installed on a Websense appliance or a Linux server and you are using Windows Active Directory (Native Mode), make sure you have configured WINS communication (see WINS setup: User Service on Linux or appliance).
*
Verify that the client machine can communicate with the domain controller from which the logon script is being run (see Domain controller visibility).
*
Ensure that NetBIOS is enabled on the client machine (see NetBIOS).
*
Make sure that the user profile on the client machine has not become corrupt (see Windows user profile issues).

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Using Logon Agent for Transparent User Identification > Logon Agent troubleshooting
Copyright 2016 Forcepoint LLC. All rights reserved.