Guys, i too had to go through this issue i.e. when i added a address field in the configuration file and mentioning the PUBLIC IP, i lost the internal access to XenApp but found a simple way to make it work i.e. just by adding a FQDN.

I hope this solution will definitely make you happy and save a few hundred $.

Opened ports.
External works now. Good work around, However Internal doesnt work.
Although i don’t need it in my case, please post if you find a way to make it work internal and external without netscalar

Mine works internal and external without Netscaler. You just need to make sure that your firewall is configured to forward to ports when the traffic is received on the LAN interface as well as the WAN interface.

This solution appears to half working for me. I’m currently setting up 3 proof of concept farms. One farm is working with this and two are not. The one that is working has the VDA setup on the same box as the controller. The two that aren’t have the VDA’s on seperate machines. I was wondering if you’re setup utilized different boxes for the applications and controller or if it was all on the same machine.

This tends to be down to your firewall. Your WAN interface has probably been configured to accept and route traffic to the internal IP. But you LAN interface also needs to be configured in this way. Make sense?

I was hoping you could advise. I had everything working internally, however when i added address=citrix.company.com i am now presented with an error: The connection to “Citrix” failed with status (1030).
Now neither internal or external are working, i have also tried using IP but i get the same error.
Any Thoughts?

I just attempted changing the nat and access rule on the firewall to allow IP to ensure the ports were all open. I’m getting the web interface but none of the apps with launch just keep getting that 1030 error.

we are developing 7.6 storefront. I added the external address in the address= field (I had to add this manually). The storefront site comes up both internally and externally, I see the icons but I get an error message when I launch: “Unable to Launch your application”….”Cannot connect to the Citrix Xenapp Server. The Citrix Xenapp server you have selected is not accepting connections”. If I remove the address= field, life returns internally. Our firewall admin tells me all the ports are open (80, 443, 1494, 1604 and 2598.

Kira, did you manage to get this working on 2 or more servers? The issue i have is that if i connect to the desktop which is published on server1 this works however the desktop on server 2 will not launch. In turn this means i can not have my 2 desktops in a group for load balancing.

I tried the split-DNS route and it looked promising because internally access continued to work. However, I still cannot get external access to work. Did you change your base Storefront URL in Studio to mirror your external host name or IP? I’ve opened TCP 443, 1494, 2598, 80 and UDP 1604. I’ve tried various combinations for the Address= line in the deffault.ica file and nothing seems to get external access going.

Thanks a lot, it helped me a lot on a difficult situation. To suggest something to those having issues to access resources internally after the change, you can always create an additional store for users to connect internally (keeping default ICA settings) since it actually delivers the same resources for both Stores.