Installation guide

Sun Java System Web Proxy Server  231
Appendix B: Troubleshooting
proxy server as the source IP address of all permitted requests and will not log
blocked requests at all. For instructions, see Identifying the Proxy Server for
Network Agent, page 204.
If user- and group-specific policies are not being applied to protocol requests
(i.e., all protocol requests are being filtered by the Global policy), your
integration product may not be passing user credentials to Network Agent.
You can install a Websense transparent identification agent to authenticate
protocol traffic. For information about installing transparent identification
agents, see the sections on DC Agent, eDirectory Agent, Logon Agent, and
RADIUS Agent in Installing Websense Components Separately, page 99. For
information about configuring transparent identification agents, see the User
Identification chapter in the Administrator’s Guide for Websense Enterprise
and Web Security Suite.
Windows 9x workstations are not being filtered as expected
If you are running DC Agent for user identification, your Windows 9x
workstation machine names must not contain any spaces. This situation could
prevent DC Agent from receiving a user name when an internet request is
made from that workstation. Check the machine names of any Window 9x
workstations experiencing filtering problems and remove any spaces you find.
I am using Logon Agent and some users are receiving the
Websense Global policy
There may be a number of reasons why users are not being filtered as
expected; however, if your network uses Logon Agent to identify users, and if
some of those users are receiving the Websense Global policy instead of their
usual user or group policies, a network problem may exist.
If the Logon Agent logon script fails to execute properly on a workstation, the
Websense software cannot identify the user to apply the proper policy. The
Global policy will be applied as a default.
The first step is to determine if the settings for the Windows Group Policy
Objects (GPO) are being applied correctly to these workstations. If not, then
this is a network connectivity problem and not a Websense configuration
issue.