Home > Websense, Windows > Websense Troubleshooting

Websense Troubleshooting

We have a new AD at our dealership!!!  YAY!  With a new AD comes new features and better integration.  With that, I have started migrating our Websense Enterprise content filter from IP based authentication to AD user/group authentication.  During this change I learned a neat little trick that should help most when troubleshooting Websense problems.

  1. Log onto the client PC and go to a restricted site.
  2. Click on the “More information” link which should change the “Your organization’s Internet use policy restricts access to this web page at this time.” part at the top of the page to a white space.
  3. Right click on that white space and click on “view source”.
  4. At the bottom of the source code it will tell you the active policy and the method its being blocked by

Backwards ass way to get this info, but now you know!

Advertisements
  1. Matt Gilmore
    October 18, 2010 at 11:06 pm

    You will run into issues with Websense and that the source page cannot give you “port” or hidden IP information hidden within the page:

    To run TestLogServer on the Filtering Service machine:

    Open a command prompt by selecting Start > Run and typing CMD.
    A command prompt window opens.
    Navigate to the \Websense\bin folder in the Websense installation directory.
    Type TestLogServer, and then press Enter.
    Browse some Web sites.
    Data populates the command prompt window as outgoing requests are received.
    Stop TestLogServer process by pressing Ctrl + C.
    To log the data to a text file, type TestLogServer -file logfile.txt on the command line, and then press Enter.
    While data is displayed in the command prompt window, the same traffic is also written to a file called logfile.txt located in the \Websense\bin folder.
    To show the log trace from a single client machine, type TestLogServer -onlyip on the command line, and then press Enter.
    Data populates the command prompt window as outgoing requests are received from the specific client machine.

    NOTE For easy analysis, TestLogServer is generally run by combining the previous two suggestions– Receiving traffic from a single machine and logging data to a text file. For example:
    TestLogServer -file logfile.txt -onlyip This command combines logging to a text file and isolating traffic from one machine. This makes reading the data easier.

    Press Ctrl + C to stop the TestLogServer.
    Review the logfile.txt in the \Websense\bin directory. Search the specific sites visited for further analysis.
    If you configured the identity of Log Server to localhost in Websense Manager, change it back to the actual IP address of the external Log Server machine.
    To resume logging to the database, restart the Websense Log Server service.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: