Standard New VPN in NetScaler 11.0

Standard New VPN in NetScaler 11.0 -

When NetScaler Gateway the whole idea of ​​this gateway was first developed, was to act as a secure entry point into the corporate intranet via a VPN tunnel. There were only two mode of operations Clientless VPN (commonly known as CVPN known) and full VPN.

Both types of access required to the user with his / her LDAP credentials authenticate with a second factor as RSA Key or VIP token. Once successfully authenticates the user, he would be entitled to receive a full or CVPN VPN tunnel access to the Intranet Zone.

The specialized case of CVPN came into play when the user would bring in conjunction with a browser and he / she intends to access behind the gateway webservers, actually a VPN client to be installed on the client computer without , In this case, the user would be able to target its access to HTTP based connections by choosing the CVPN mode of operations only to restrict.

, since the anticipated access mode was always full VPN, the default configuration for NetScaler Gateway allows VPN access, which was indicated by:

Transparent Interception: ON

as the landscape of products changed in Citrix and NetScaler Gateway became a part of XenMobile solution as well, we have begun to custom rules in the NetScaler gateway configuration, adding that access to ensure XenMobile client (WorxHome) is limited , Against this background, we believe that a more restrictive standard a better option would be

Therefore from 11.0.F release, would our standard NetScaler Gateway VPN access configuration as follows :.

Transparent Interception: OFF

[1945003umdasbesteausunseremVerständnis], should the customer due to this update an interruption do not see in their daily work, because we already have a special rule in place for the full VPN have client-based access

for customers who are in the earlier versions of NetScaler Gateway and having to change their default configuration manually want, provided detailed information in the following document on our web site .:

https://support.citrix.com/article/ctx201129

Like all configuration changes, Citrix recommend this implemented in a production environment before being evaluated in a test environment.

Tweet