Web Interface & Non Default ICA Listener, in the Network Performance / WAN Optimization forum on BrianMadden.com

I have been using the Optimizing Citrix Technology for operation over wireless Wide Area Networks guide to try and at least help an issue we are currently experiencing with a remote office which uses satellite for an Internet connection.

First off the whole thing references using the template.ica file of the Web Interface in order to make changes. In PS4 there is no template.ica, I believe it changed to default.ica. I have put the changes there but they seem to have made no effect.

I have gone along with guide and created a new site WI site which is supposed to point to an alternate ICA Listener. Which I have created. Again the problem is that the Address=[NFuse_IPV4Address]:1495 doesn't work. So my question is two fold.

1. How do I point a WI site an alternate ICA Listener besides the one running on port 1494?
2. Is there anyway to modify things like WindowsCache size, KeyboardTimer, etc in a WI site for PS 4?

If you have any experience with getting Citrix useable over a Satellite ISP please feel free to contribute as well. I need to get this working like yesterday or were going to lose the office. It’s pretty much completely unusable at this point. So please, any help is deeply appreciated.

Are you having any congestion issues with the ICA client over the satellite link? Please advise.

Hi,

I was wondering, did you or anyone else end up with a solution to this issue? I'm currently experiencing the same pain of which I need to find a solution.

QUOTE: 1. How do I point a WI site an alternate ICA Listener besides the one running on port 1494?

I, too, have been struggling with this. I managed to create the second listener, even managed to configure WI to use that listener, although it was not very reliable. However, applications took forever to launch, and usually most other connections ended up defaulting to the second listener, too, even if they WEREN'T configured to use it.

I've given up.

BTW... You were correct to use DEFAULT.ICA, rather than TEMPLATE.ICA.

Much Belated Reply:

Having setup a Full Time ICA Listener (for status bigboard screens [with no session timeout]), you have to set the client to ICA:1494 to connect to that listener.

This may be old info, but with respect to satellite WAN connections, some years ago (when IPSec was mainstream and broadband not as prolific in rural areas), I supported users on the Cisco 3000 concentrators using the Cisco 3000 v3.01 client. I had some Sales and Sales Engineers out in the boonies who had Satellite Broadband. Some could connect, some could not. The one's who could connect had difficulty maintaining the VPN connection. At the time, the deafult MTU for the client was 1400. Here's a decent article on this: http://www.dslreports.com/tweaks/MTU

Using the ping command (from the client side), determine the optimal MTU.
ping fully qualified DNS name of your WI server on the outside -f -l packet size

You'll probably see some "destination unreachable" replys. Adjust the MTU size down by 28 until you see your four reply's. Try one more size down to see if the time (latency) gets better. Use the size that performed the best. The setting is housed in the registry here: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

Yes, I know that Windows 2000 and above was supposed to have self optimizing MTU, but I found that setting the MTU to 1300 for satellite connections worked best (BTW- When Cisco published their v3.02 client, a bullet for 1300 was integrated to change the MTU size in their tool)!

Once you determine the maxMTU, you can set it using DrTCP, MaxMTU, TweakMaster or other freely available tool. The Cisco client install had it's own tool to set the MTU size.

Hope this helps,