You notice that your Netskope client icon has a red dot and see "Disabled due to error" when hovering the mouse over the icon. What are two reasons…

The "Disabled due to error" status on the Netskope Client icon indicates a critical failure that prevents the client from steering traffic. This state is triggered by two primary conditions. First, if the core client service (e.g., stunnel.exe or nsservice.exe) is manually stopped or has crashed, the client cannot function and will report this error. Second, if the client's internal health checks fail—for instance, if it cannot resolve or connect to its assigned Netskope gateway—it will enter a disabled state to prevent network disruption. Both scenarios represent a fundamental inability of the client to perform its duties, thus triggering the error state.

B. The steering exceptions are incorrect.

Incorrect steering exceptions can cause connectivity issues for specific applications or domains but do not disable the entire client or trigger a core error state.

D. The client traffic is directed over iPsec.

Directing traffic over an IPSec tunnel is a standard, valid configuration for forwarding traffic to the Netskope cloud; it is a feature, not an error condition.

1. Netskope Support Portal

"Troubleshooting the Netskope Client": This document outlines common client issues. It specifies that the "Disabled" status can result from the stunnel or nsservice processes not running. The "error" qualifier is added when this is an unexpected stop or crash. (Section: Client Status and Errors).

2. Netskope Support Portal

"Netskope Client Health Checks": This documentation details the connectivity and health validation performed by the client. It explicitly states that failure to connect to the configured gateway (gateway-.goskope.com) is a failed health check that will cause the client to enter a fail-open or fail-closed state

which is reported in the UI as "Disabled due to error". (Section: Gateway Connectivity Check).