So I am attempting to create a published app that will be exclusively used by remote users on mostly cell phones via the mobile horizon client. So far testing was going ok but have since ran into a glitch where a couple of the testers could not launch the application. After research i found an article that states there are issues with the AT&T network and Horizon View. ( ATT Wireless and VDI Horizons Proxy Issue | WirelessPhreak ) . Sure enough the two testers that are having issues have AT&T as a carrier
Has anyone dealt or heard of this?
Thank you all.
From the article you shared, there's LB which might have Source IP affinity setup, and AT&T network would provide different IP for Primary protocol (443) and Secondary protocol (4172, 8443). Which Source IP affinity could not route secondary protocol to the same UAG which established primary protocol.
Would you please try to configure the LB and UAG with the Method 3 in below article?
Thanks.
We don't use published apps but we use desktops. We've ran into this issue when the client is using pcoip. We tell our end user's to switch to Blast and they don't have any issues.
