Netscaler gateway plugin 3.0 for mac how to#
See CTX218708 How to Configure Internal Beacon for Single FQDN on StoreFront. However, this requires the StoreFront Load Balancing Virtual Server to have a certificate that matches both the Single FQDN and the Internal Beacon. Ideally, the Internal Beacon should be a new DNS name that resolves to the StoreFront Load Balancing VIP. You can’t use the Single FQDN as the Internal Beacon.
Set the NetScaler Gateway object in StoreFront to this FQDN. Resolves to public IP, which is NAT’d to NetScaler Gateway VIP on DMZ NetScaler. External DNS name = the Single FQDN (e.g.Set the StoreFront Base URL to this address. Resolves to internal Load Balancing VIP for StoreFront. Internal DNS name = the Single FQDN (e.g.Make sure the certificates match the DNS names. If you don’t care about email-based discovery then the configuration of Single FQDN is fairly simple. Different instructions are needed for when ICA Proxy is off. This section assumes NetScaler Gateway is in ICA Proxy mode. Split DNS – different DNS resolution for internal vs external.Single FQDN is fairly new and thus has the following requirements: This assumes that external users resolve the single FQDN to NetScaler Gateway and internal users resolve the same FQDN to StoreFront Load Balancing.
Netscaler gateway plugin 3.0 for mac code#
Recently Citrix made some code changes to accept a single FQDN for both. Traditionally Receiver required separate FQDNs for StoreFront Load Balancing (internal) and NetScaler Gateway (external). Then in the StoreFront console, right-click Server Group and click Propagate Changes.ĭ – Create a single Fully Qualified Domain Name (FQDN) to access a store internally and externally.Check the box next to the NetScaler Gateway object you just created and then click OK.Note: if you want Receiver to automatically launch a VPN tunnel, then see CTX200664 How to Configure Receiver for Seamless Experience Through NetScaler Gateway.On the right, click Enable Remote Access. However, you cannot use a Load Balancing VIP when configuring Secure Ticket Authorities on your NetScaler Gateway Virtual Server. You can also enter a Load Balancing VIP here.
Use or depending on the certificates installed on the Controllers.
The Callback URL must not have client certificates set to Mandatory.The Callback URL must have a trusted and valid (matches the FQDN) certificate.For multi-datacenter, edit the HOSTS file on the StoreFront server so it resolves to NetScaler appliances in the same datacenter. The callback URL must resolve to any NetScaler Gateway VIP on the same appliance that authenticated the user.However, SmartAccess requires the Callback URL to be configured. In StoreFront 2.6 and newer, the Callback URL is optional.However, if the NetScaler Gateway URL is GSL B-enabled then you’ll need to enter the VIP of the NetScaler Gateway Virtual Server so StoreFront can differentiate one NetScaler Gateway from another. A Subnet IP address is not needed for NetScaler Gateway 10 and newer.The NetScaler Gateway FQDN must be different than the FQDN used for load balancing of StoreFront (unless you are configuring single FQDN). Enter the NetScaler Gateway Public URL.If you have multiple sites, include a geographical name. This name appears in Citrix Receiver to make it descriptive. In the Gateway Settings page, enter a display name.In the StoreFront Console, right-click NetScaler Gateway and click Add NetScaler Gateway Appliance.Make sure the Gateway vServer logon page appears. After configuring the HOSTS file, on the StoreFront server, open a browser and navigate to the DNS name.