Hi,
We have a View Connection 4.6 server at 10.10.1.1 and a security server at 10.10.1.2. Internally, view.company.com resolves to 10.10.1.1, externally this resolves to an external IP on the firewall which is then forwarded to 10.10.1.2 server. Everything works fine for both internal and external clients.
Now, since we keep security server in the same network as connection server (we have no DMZ), the security server doesn't appear to provide us with benefits for which it was designed. We'd like to eliminate this server from the setup, leaving only one connection server to serve both internal and external clients.
To this end, we have tried this: A) setup firewall forwarding to go to connection server instead of security server, and B) set PCoIP secure gateway external URL to externalIP:4172 instead of 10.10.1.1:4172 (to match what is configured on security server). Once this is setup, external clients can connect fine, however internal clients can not connect to their desktops. They can login, authenticate, get to the point where they chose their designated desktops, and then connection fails, saying desktoop can't be connected or something to that effect (unfortunately I don't have the exact wording).
I've contacted support about this and they suggested that this is by design and that View can't work off a single server, or at least that it is not supported, and suggested we log a feature request. I'm sure this can be made to work and there are setups out there that run on a single box for testing or in production for smaller shops.
I sort of suspect internal DNS resolution still resolved view.company.com into 10.10.1.1, and new PCoIP external URL may be messing with this, but if we are to point this to external IP then we create dependency on the firewall and that's not a good solution for us.
I'd appreciate if someone can point me in the right direction.
Thanks