However I would have still expected that in a dual stack situation that Receiver would have a mechanism to ensure that its using the same IPv4 proxy that the original session was established with on the Netscaler. Now I'm sure the simple solution is to either remove the IPv6 AAAA record or enable the IPv6 VIP on the Netscaler.
The IPv6 VIP is not enabled at the moment. We have both A (IPv4) and AAAA (IPv6) records in DNS for but only the IPv4 VIP is live on our Netscaler. From the failed IPv6 enabled Mac Receiver log above I see the following: However, I have a theory as to what could be happening.
I tried to reproduce the issue on my Windows 10 machine with IPv6/IPv4 dual stack through both my Verizon LTE and Comcast and was unable to do so. This was the first instance I've ever seen this problem on Windows. I had him disable the IPv6 stack on the machine, and he was then able to launch the app successfully. He was getting an error "secure ticket authority cannot be contacted" when attempting to launch an app through Receiver 12.4 for Windows.
UPDATE - So this weekend I had a customer on Comcast who was on a Windows 10 machine in an IPv6/IPv4 configuration. Any idea why this issue would occur on a dual-stack iPv4/iPv6 Mac client but not on a Windows client? It seems to me that the browser is doing the initial connection on iPv4 as it should but something is going wrong with Receiver when it attempts to receive a ticket from the STA. We do not have iPv6 enabled on our Netscaler VIPs, StoreFront or on our XenApp hosts. Our environment is Netscaler 10.5 61.11.nc. The user is able to login through the Netscaler portal and reach the StoreFront but when attempting to launch applications received the following error "Cannot Connect To Server: xxxxxxSTAxxxxxxxx" Setting the TCP/IP parameters on the machine to only issue a link-local iPv6 address resolved the issue. The particular user we had today was a using the latest MacOS with Receiver 12.4 and Comcast ISP. It seems that many ISPs are now implementing consumer routers that issue both iPv4 and iPv6 addresses.
is an open platform for users to share their favorite wallpapers, By downloading this wallpaper, you agree to our Terms Of Use and Privacy Policy.We're run across an issue with Receiver for Mac where users cannot connect to our XenApp 6.5 farm if they have iPv6 enabled and are configured for a IPv4 and IPv6 dual stack scenario. interest allocation this image for your beloved friends, families, organization via your social media such as facebook, google plus, twitter, pinterest, or any supplementary bookmarking sites.
Dont you arrive here to know some supplementary unique pot de fleurs pas cher idea? We really hope you can easily acknowledge it as one of your suggestion and many thanks for your times for surfing our webpage. We try to introduced in this posting previously this may be one of fantastic insinuation for any Detect Receiver Citrix options.
We consent this nice of Detect Receiver Citrix graphic could possibly be the most trending subject next we allowance it in google plus or facebook. Its submitted by presidency in the best field. Here are a number of highest rated Detect Receiver Citrix pictures on internet.