Skip to main content

Slow internet access- Performance problem...

  • April 27, 2022
  • 7 replies
  • 3424 views

Forum|alt.badge.img+1

Hello ,

 

Is any one seeing performance degradation in their  internet access when  netskope  is enabled ? ( netskope client version 90.x)

 

I have opened case now as so many users reported to gather today, vs few early this week.

 

RP

This topic has been closed for replies.

7 replies

edwin_alvarez
Netskope Partner
Forum|alt.badge.img+9
  • Netskope Partner
  • May 5, 2022

Can you confirm if this problem was solved? or what steps were performed with support


Forum|alt.badge.img+1
  • Author
  • New Member
  • May 6, 2022

no still investigating, and Netskope support looking for more data. i have enabled advance debug to collect more data. let us see . we have stopped further deployment until we fix the problem.

 

fun stuff is when it is intermittent problem and can be replicated slowness to  sites like cisco.com /att business site, yahoo cnn etc.

 

RP


Forum|alt.badge.img
  • New Member
  • June 15, 2022

Were you able to find out the cause of this? We've just started to notice this too.


Forum|alt.badge.img+4

Are you both using private access as well or just CASB? Its worth checking what datacenter both the clients (and if you use private access) the publisher servers are connecting to and how close that is proximity wise.


Forum|alt.badge.img+1
  • Author
  • New Member
  • June 30, 2022

Only CASB not  Private access.  We are still troubleshooting as this is become intermittent. Support asked to upgrade client to latest one and check. do not get root cause yet . which i am waiting for.


Forum|alt.badge.img+4

Check the client config settings and see what stitcher it is connecting to and what gateway - DNS should point it to one that is relatively close to wherever you are (so if you are in California example it might point you to an IP in San Jose)


Forum|alt.badge.img
  • New Member
  • July 4, 2022

Turns out our issue was DNS related, we for some reason had in our steering configuration port 53 as a non-standard port. This was causing DNS lookup issues, was fine until one day it randomly started playing up. We must have been testing something and left it in there one day.