#Citrix register vip access how to
#Citrix register vip access update

So, at this point reserve a free address in your DMZ (For this we will use 192.168.0.50) and NAT all incoming traffic from the external IP address to your DMZ IP address. You will need to ensure that your external IP address forwards to an address in your DMZ. This way if your external IP address at home changes your external DNS names will still work as expected. Then when creating the dns records for external access rather than creating an A Record create a CNAME and point it to the Dynamic DNS record registered with your router.

#Citrix register vip access update

Register an account and set your router to automatically update the dynamic DNS record with your current external IP address. Lab Tip : If (like me) you don’t have a static IP address at home and you want to put this into your home lab then check if your router supports dynamic DNS. Please be aware that DNS replication can sometimes take a while so make sure you wait for this to happen before concluding that it’s not worked. Once done test by pinging both DNS names and ensure they resolve to the SAME IP address. Internal Range: 192.168.0.0/24 (For the rest of this blog I will use the 192.168.0.0/24 subnet as a working example)Īssuming your external IP Address is 1.2.3.4 (I know this is not real!) then you will need to point BOTH and to that IP Address.External IP: You will only have a SINGLE external IP.URL: – Used for Federated Authentication NetScaler Gateway Access.URL: – Used for regular NetScaler Gateway Access.I am a great believer of building things right from the ground up – it will have you loads of time having to go back and introduce high availability at a later date! They are not strictly required to get the federated authentication to work but will make your solution highly available and more scalable in the long run. These are additional things that I would put in place before publishing this solution to production. You will have to have these all set up before continuing with the rest of this blog series. These are required in order to get your federated authentication working correctly. This post will cover the Pre Requisites that you will need in place in order to get your solution working. This will give you a good understanding about what we are building and this in my opinion is crucial before you even start to look at the more details build. If you have not read that already then please do so here:

In my previous post, I outlined what we are trying to achieve with this and posted a couple of teaser videos about how the solution should operate once complete.

#Citrix register vip access how to

OK, so let’s get into the detail of how to build your XenDesktop, Google, Federated Authentication and NetScaler Deployment.