Solved

Enabling private app discovery is not allowing VPN to connect

  • 3 May 2023
  • 2 replies
  • 56 views
A
Rank
Userlevel 2
Badge +11

Hello - We have configured steering exceptions for VPN gateway IPs, domains, and cert pinned app for the VPN processes so that Netskope will not impact vpn connections and works as expected when users connect to VPN. But after enabling private app discovery users are not able to connect to VPN gateway via VPN client and not sure what is causing problem. As part of App discovery configuration we added the company wild card domain and VPN gateway FQDN matches the domain. Did anyone face similar issue before? If yes can someone provide guidance on this issue?

 

Thanks

icon

Best answer by ark007 3 May 2023, 21:03

View original

2 replies

A
Rank
Userlevel 2
Badge +11

@nduda - Will you be able to help me on this post?

 

Thanks

A
Rank
Userlevel 2
Badge +11

Just got to know that with NPA taking precedence steering exceptions that we put for VPN will not work as the parent domain is part of private app discovery configuration.

 

There is a work around where we can try using VPN gateway IP instead of FQDN to connect via VPN client.(this also works if VPN Gateway IP is not part of private app discovery configuration)

 

Thanks

Rakesh

Reply


Terms & ConditionsCookie settings