Turning on the Computer Browser service

The Forcepoint Web Security installer offers the option to turn on the Computer Browser service during installation of the following components on Windows Server.

  • User Service
  • DC Agent
  • Logon Agent

If you chose not to have it started, or the installer was not successful, you must turn on the service manually.

Perform the following procedure on each machine running an affected component:

Steps

  1. Make sure that Windows Network File Sharing is enabled.
    • Windows Server 2016:
      1. Go to Start > Windows System > Control Panel.
      2. In the Control Panel, click Network and Internet, then Network and Sharing Center.
      3. Click Change advanced sharing settings in the left navigation pane, then select Turn on file and printer sharing.
      4. Click Save Changes to save and exit.
    • Windows Server 2012:
      1. On the desktop, point the mouse to the top, right corner of the screen, then go to Settings > Control Panel.
      2. In the Control Panel, click Network and Internet, then Network and Sharing Center.
      3. Click Change advanced sharing settings in the left navigation pane, then select Turn on file and printer sharing.
      4. Click Save Changes to save and exit.
    • Windows Server 2008 R2:
      1. Go to Start > Network and click Network and Sharing Center.
      2. Click Advanced Sharing Settings, then select Turn on file and print sharing.
  2. Open the Windows Services tool:
    • Windows Server 2016: Go to Start, then select All Programs > Windows Administrative Tools > Services
    • Windows Server 2012: Server Manager > Tools > Services
    • Windows Server 2008 R2: Start > Administrative Tools > Services
  3. Double-click Computer Browser to open the Properties dialog box.
  4. Set the Startup type to Manual.
  5. Click Start.
  6. Change the Startup type to Automatic. This ensures that the service is started automatically every time the machine is restarted.
  7. Click OK to save your changes and close the Services tool.
  8. Repeat these steps on each Windows Server machine that hosts an affected component.