• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1644
  • Last Modified:

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


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.

1 Solution
Sekar ChinnakannuStaff EngineerCommented:
check proxy ip details, also how about timeout settings
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.

Dirk KotteSECommented:
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).
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

how do you login to both farms on PC i mean authentication its two way or what?
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.
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.
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.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

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.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now