Network Agent can’t communicate with Filtering Service

With Forcepoint Web Security, Network Agent must be able to communicate with Filtering Service to record protocol management, bandwidth, and other logging information. In standalone Forcepoint URL Filtering environments, no policy enforcement can occur when Network Agent and Filtering Service cannot communicate.

• Did you change the IP address of Filtering Service machine or reinstall Filtering Service?

  If so, the new Filtering Service internal unique identifier (UID) or IP address is not automatically registered with Network Agent and the Forcepoint Security Manager.

  To re-establish connection to the Filtering Service:

  1. Log on to the Web module of the Security Manager.

     A status alert indicates that a Network Agent instance is unable to connect to Filtering Service.

  2. In the left navigation pane, click Settings > Network Agent, position the mouse over the Global menu item until a sub-menu is displayed, then select the IP address of the Network Agent machine.
  3. At the top of the page, under Filtering Service Definition, expand the Server IP address list, and then select the IP address of the Filtering Service machine.
  4. Click OK at the bottom of the page to cache the update. Changes are not implemented until you click Save and Deploy.
• Do you have more than 2 network interface cards (NICs) on the Network Agent machine?

  If so, see Configure Network Agent to verify your web protection software settings.

• Have you reconfigured the switch connected to the Network Agent?

  If so, refer to the Network Agent Quick Start to verify your hardware setup.

If none of these apply, see Configuring Network Agent local settings for information about associating Network Agent and Filtering Service.