1. PCOIP Problem With NAT
We have a group of users accessing VDI from a different branch through MPLS link. Their access to vdi is through a NAT IP (e.g. real VDI IP is 1.1.1.1, but they are acccessing 2.2.2.2). Our network device takes care of the translation from 2.2.2.2 to 1.1.1.1 so that the connection reaches VDI when the user browses to abc.com. However, this setup does not work with PCOIP because part of the connection server setup, we have to put in 1.1.1.1:4172 as the PCOIP gateway IP. From this group of users, the route to 1.1.1.1 does not exist.
Is there a way that I can perform any of the following:
a. Configure URL instead of IP address as the PCOIP gateway
b. For a different PCOIP URL on the users VMWare View Client
Ultimately i'm trying to have them use our existing setup rather than investing in more Connection Servers. Currently, they are accessing through HTML Blast, which is limited in feature (e.g. file transfer).
2. Restrict Access Based on Source-IP
We have RSA paired with our horizon view for users accessing VDI from over the internet. At this juncture, we have a specific group of users whom wish to access VDI services. Due to some concerns, we wish to restrict access for this group of users ONLY from our branch office. Hence, they should be restricted from accessing it from their home.
This may not make much sense to some of you (even to me sometime), however the requirement is as such. These users are operating out of branch office and are using VDI to access work material. Hence, management would like to restrict them from accessing it from home due to nature of work.
Is there a feature or workaround to this?