Your Netskope Client tunnel has connected to Netskope; however, the user is not receiving any steering or client configuration updates What would cause this issue?
A.
The client is unable to establish communication to add-on-[tenant].goskope.com.
B.
The client is unable to establish communication to gateway-[tenant].goskope.com.
C.
The Netskope Client service is not running.
D.
An invalid steering exception was created in the tenant
The Netskope Client establishes a data tunnel for traffic steering, but it also requires a separate communication channel to the Netskope add-on endpoint (add-on-[tenant].goskope.com) to receive configuration updates, steering policies, and client profile changes. If this endpoint is unreachable due to a firewall rule or network policy blocking the connection, the client will continue to pass traffic through its established tunnel but will not receive any new steering or client configuration updates from the tenant. This means policy changes, steering exceptions, or client configuration modifications made in the Netskope UI will not be pushed to the affected client. This is a common troubleshooting finding in environments with strict egress filtering, and the resolution involves ensuring that the add-on endpoint is reachable from all client devices.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit