Skip to main content
  • EN

Hello everyone,

I have a very annoying problem with my Netskope Steering configuration.
Domain bypass exceptions don't work.


For example, I need to access a site under development, which allows access via IP filtering. As this site is in our exceptions, we're normally supposed to be able to access it with our classic public IP, so I've added it to the exceptions.

But despite this, we arrive on the site with a netskope IP (163.x.x.x), which prevents access to the site.

I'm a bit stumped at this point...
Do you have any ideas?

Thanks!

Good morning @Saga,

 

What do the client logs show for the connection to that host? You should see a line that indicates if Netskope is steering or bypassing the traffic in the nsdebuglog.log file.  Is it all domain bypasses or just a specific one? Further, did you update the client config (or wait one hour) after creating the steering bypass?  

Hi @Saga 

Hope you are doing well. I hope the answer shared by @sshiflett  helps you. Feel free to mark a answer as a “Best Answer”

 

 

I’ve been having this issue for going on three weeks now. Domain exceptions sometimes bypass steering, but most times, they are steered to Netskope - including when accessing the Netskope Dashboard. I’ve had a case open but so far Netskope hasn’t been able to fix it. I’m curious if anyone else is having this problem.

Hi, we are in the same boat on a customer installation, we have a support ticket open #00417825

We found that an exception setted for off-prem steering is somehow applied also for on-prem traffic; we were able to reproduce the issue with an hand os remote support session and we are now waiting for a resolution.

Reply


Terms & ConditionsCookie settings