Client has just had a dead Citrix Access Gateway replaced with a NetScaler VPX 200 (NS11.0: Build 63.16.nc, Date: Oct 4 2015). The installation of the NS has been completed by their hosting partner. All hardware, software and licensing is owned by my client - all hosted in remote data centre.
Install has gone without a hitch and users are able to log in to their XenApp 6.5 portal without fail. All access to the system is using Citrix Receiver. StoreFront not installed.
Now, when the client had their Access Gateway installed, IT could access the admin page, remotely, using the https://portalFQDN/lp/adminlogonpoint
and monitor & manage the Access Gateway. Since the NetScaler has gone live, the only way to access the management page (http://10.156.X.XXX/menu/st
) is to VPN --> RDP to one of the hosted servers then browse the admin url as an internal resource.
The client would like to be able to have admin access via the same external url that is used for Citrix Receiver - just like with their old Access Gateway - https://portalFQDN/lp/adminlogonpoint
. Its the same Web Interface server being used with the NetScaler as with the Access Gateway.
The client has had the hosting company working on this but so far all they have had are: "
Please note that concerning External Admin URL, we checked the NetScaler and we need to enable a mode in order to verify that the link can be accessed externally. This will require a downtime of 30 minutes, and if any issues occurred, then we can revert back the changes directly.
" Once my client confirmed a suitable slot for down time (last night) the hosting company have come back with
We have carried out the activity at, and the downtime was minimal (few minutes). Following the below email concerning the External Admin URL, we have tried to configure it, but unfortunately it did not work out due to some technical challenges. We are still checking on the issue, and will update you as soon as possible with the options available.
Any NetScaler experts able to provide me any pointers on getting it to work?
you may add a secondary IP and a secondary name like https://admin.yourportal.com.
so these secondary IP can be NATed to the admin-interface-IP
also possible with NAT: redirect https://portalFQDN:4433 to adminIP:443