Error with Citrix Web Interface 5.4 and XenApp 5.x servers and iPad's

Hi,

We've encountered a really strange issue with Citrix Web Interface 5.4 and XenAapp 5.  When trying to launch applications that are hosted on our XenApp 5 farm via iPad's, users receive the message "Connection Error - Could not connect to server."  They receive this message when connected to the internal network and externally.  They are, however, able to launch applications from our XenApp 6.5 farm, using the same WI servers,  without issue.

Non-iPad users can launch applications from both farms without issue.

I have checked the event logs, on the WI servers and the XenApp servers, and cannot see anything that relates to this error.

Has anyone else encountered this issue and/or know how to resolve it.

Thanks
emwlawAsked:
Who is Participating?
 
Dirk KotteConnect With a Mentor SECommented:
because the reciever on ipad can't use session reliability (TCP 2598) make sure the device can connect with the old ICA protocol (TCP 1494).
0
 
Sekar ChinnakannuStaff EngineerCommented:
check proxy ip details, also how about timeout settings
0
 
emwlawAuthor Commented:
Hi Sekarc4u

Thanks for your helpI have checked both.  The Proxy IP settings are set to use the "Users Browser Settings" and the timeouts as still set to the defaults.

Thanks
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
rishimehta01Commented:
how do you login to both farms on PC i mean authentication its two way or what?
0
 
joharderCommented:
This is likely because there is a difference in the STA name.  The STA is case sensitive, and this issue seems to rear its ugly head only for iPad connections.
0
 
emwlawAuthor Commented:
Thanks dkotte.  have checked, using wireshark, and found that ICA packets were being dropped.  I check the ICA protocol (1494) configuration in the 'Terminal Services Configuration' tool and found that it was bound to only 1 NIC on the XA5 servers.  I changed the configuration to all cards and it's now working.

Thanks again.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.