We've been seeing a huge uptick in macOS related connectivity issues
(tunnel just drops and rebuilds). I've noticed lots of log entries
like:error Unable to UDP open local Endpoint The peer closed the flow
Can anyone explain what/why netskope is doin...
We've opened a support ticket as we believe we've found a bug where
devices are not honoring the fail close option in the Client
Configuration. We have fail closed unchecked, yet we notice almost all
our systems in the UI (as well as logs) having fai...
Having NS Client deployed/installed pre-Big Sur works great. We've even
managed to update the install script to grab the local user logged in,
append our email domain and auto enroll with iDP. The challenge now is
upgrading to Big Sur relies on a use...
We've turned down numerous third party deals, including even POC's of
products that integrate with Netskope because of the API V1 requirement.
It (API v1) is overly permissive and all data can be pulled from it.
This puts a lot of focus on the integr...
We opened a support ticket not too long about UDP errors in the logs
(very much like the one you are showing). The answer we got was related
to QUIC (Quick UDP Internet Connection). Netskope is blocking and
falling back to non-QUIC. We are told this ...
You can't. I've been trying to work with Netskope for ~2 years on better
improvements with how agent interactivity is done from the desktop. They
really don't seem to understand how a product like Netskope, when
impacted, can bring a company to its k...
I consider a device that connects to our VPN as On-prem. It has (for the
most part) the same direct access to internal resources that the user
would get if in the physical office. We use on-prem detections to
disable NPA when a user connects to the V...
I've asked for this numerous times, over the past 2 years. This feature
would save massive amounts of headaches in targeting certain users
without going through all the headaches of AD/Okta groups (those also
take time to sync). It would also allow u...