Jump to content
Updated Privacy Statement

Client proxy settings are always overwritten when Gateway VPN starts


Recommended Posts

A company is using a complex setup of client proxy for their windows clients.
The setup has different proxy.pac files for each country and department. 
This is configured using Group Policy, and works fine.

But when using Netscaler VPN, then client proxy settings are always reset by the Access Gateway Plugin to whatever is set in the Session Profile.
This happens no matter which setting is chosen in the Session Profile (
 BROWSER | NS | OFF )

We could of course use a workaround of some sort to solve this - like having a lot of Session Profiles, or having a logon script calling "gpupdate /force"...

Is there a method of making NetScaler VPN not touch the client proxy settings?
Maybe just an option to set proxy = "LEAVE AS IS" ?

  • Like 1
Link to comment
Share on other sites

Hmmm - and the setting OFF is of course NOT documented.

https://docs.netscaler.com/en-us/netscaler-gateway/current-release/vpn-user-config/configure-plugin-connections/enable-proxy-support-for-user-connections.html

:-(

also in https://developer-docs.netscaler.com/en-us/adc-nitro-api/current-release/configuration/vpn/vpnsessionaction - "* OFF - Proxy settings are not configured. " - but i guess, that means NS WILL DISABLE the proxy configuration.

 

Link to comment
Share on other sites

Hi Allan,

highly interested in your issue. In one setup I'm using NS (13.0 92.21) for SSLVPN. Session-Profile Proxy is set to OFF:image.thumb.png.f50dcfab779357a9b541f7678c1ff2a7.png

I know the customer is also deploying different pac-URLs via GPO. I'm using a non-corp device to set a testproxy config like that:
image.thumb.png.475adc2870ebd3feaafd8294ae433341.png

When I logon via Windows CSA (23.8.1.11) the proxysetting consits and there are no changes to that.

Just wondering if it's a bug in a NS-Build and or with a CSA-Build. Following for more :) 

Regards,
Julian

Link to comment
Share on other sites

Posted (edited)

I agree - you are right - the issue is not there if using only the pac-file on clients.

Let me edit the issue: Some of the users are using a direct proxy server setup, and this happens:
Before starting VPN Connection:
image.thumb.png.a948a3bc87e40d9381f18578af7224df.png

After connection:

image.thumb.png.a5c3b3006633cdcbbacb457fada00ed0.png

 

EDIT: Using NS13.1-51.15, VPX Client CSA 23.10.1.7

Edited by Allan Møller Pedersen
Versions added
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...