Product: Forcepoint DLP Endpoint, Forcepoint Security Manager (FSM)

Title: Resolving "Disabled" and "Disconnected" Status on Forcepoint DLP Endpoint Clients

Overview

This article provides guidance for troubleshooting Forcepoint DLP Endpoint clients that display a "Disabled" and "Disconnected" status and are unable to receive active DLP policies.

Cause

The issue occurs when communication between the endpoint and the FSM Server is disrupted. Common causes include:

• Network connectivity issues.

• Incorrect endpoint server configuration.

• Firewall or DNS-related problems.

• Failure of the Websense Data Security Web Server service on the FSM Server.

A stopped or unresponsive Websense Data Security Web Server service is a common cause, as it prevents endpoints from communicating with the FSM.

Troubleshooting

1. Verify Connectivity

From the affected endpoint:

• Ping the FSM Server:

ping <FSM_Server_IP_or_Hostname>

• Verify the required communication port is accessible:

telnet <FSM_Server_IP> <Port_Number>

or

Test-NetConnection <FSM_Server_IP> -Port <Port_Number>

2. Validate Endpoint Configuration

1. Navigate to:

C:\Program Files\Websense\Websense Endpoint\

2. Open localconfig.xml.

3. Confirm the configured FSM Server URL is correct.

4. Test the URL in a web browser to verify it is reachable from the endpoint.

3. Verify FSM Services

On the FSM Server:

1. Open Services (services.msc).

2. Locate Websense Data Security Web Server.

3. Confirm the service is running.

Resolution

If the Websense Data Security Web Server service is stopped or unresponsive:

1. Open Services on the FSM Server.

2. Start or restart the Websense Data Security Web Server service.

3. Allow the service to initialize fully.

Verification

Confirm that the endpoint successfully reconnects and that its status changes from:

Disabled / Disconnected

to

Enabled / Connected

Verify that endpoint policies are received and DLP enforcement is functioning as expected.