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?
When verifying that Google Drive traffic is being tunneled to Netskope using Chrome and the Netskope Client, you would expect to see log entries indicating that the traffic is being directed through Netskope's proxy. Specifically, Option A is correct as it shows the process ''google drive'' being tunneled to nsProxy. The log entry for Option A indicates that a TLS tunneling flow from a local address and process (Google Drive) is being directed to a host (play.googleapis.com) and then to Netskope's proxy (nsProxy). This is consistent with how Netskope tunnels specified traffic for security and policy enforcement1.
Limited Time Offer
25%
Off
Currently there are no comments in this discussion, be the first to comment!
Currently there are no comments in this discussion, be the first to comment!