Network Agent is not running

For Forcepoint Web Security and integrated Forcepoint URL Filtering deployments, Network Agent offers enable full management of protocols other than HTTP, HTTPS, and FTP, plus full bandwidth-based policy enforcement.

For standalone Forcepoint URL Filtering installations, Network Agent must be running to monitor and manage network traffic.

To troubleshoot this problem:

1. Look for low memory problems on the Network Agent machine that may be preventing the service or daemon from starting.
2. Check the status of the Network Agent service or daemon:
   • Windows: Use the Windows Services tool to see if the Websense Network Agent service has started.
   • Linux: Use the /opt/Websense/WebsenseDaemonControl command to check the status of Network Agent.
   • Appliance: Use the appliance command-line interface (CLI) to check the status of Network Agent.
3. Make sure all administrators are logged off of the Forcepoint Security Manager, then restart the Websense Policy Broker and Websense Policy Server services (see Stopping and starting web protection services).
4. Start or restart the Websense Network Agent service.
5. Wait 1 minute, and then log on to the Security Manager again. If that does not fix the problem:

• Check the Windows Event Viewer for error messages from Network Agent.
• Check the Websense.log file (in the bin directory) for error messages from Network Agent.