[THIN] Re: Alternate Addressing
- From: "Matthew Shrewsbury" <MShrewsbury@xxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Mon, 14 Nov 2005 08:06:41 -0500
It sounds like to me the *.ica file is looking for a published
application. Edit the ICA file with a text editor and see what it says.
Most likely it is trying to connect to "Published App". If so then you
have to have the ICA Browser port 1604 open in addition to the other
ports.
Matthew Shrewsbury, MCSE+Internet MCSE 2000 CCA Server+
Senior Network Administrator
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of LDS
Sent: Monday, November 14, 2005 7:46 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Alternate Addressing
I am working with our network guy configuring a the SSL VPN
functionality of our Cisco VPN Concentrator to access my Web Interface
4.0 page. I have customized the page where I have added links to static
.ica files for some legacy apps. When I connect externally I am able to
run the apps without problem from the WI portion of the page, but
running the static .ica files results in the "unable to contact
Metaframe browser" error.
Network guy says I have access through the firewall "via SSL(tcp port
443) or IPSEC (udp port 500), and that other applications ports like
Citrix are wrapped in either one of those packets".
Any suggestions? Is it an access issue or do I need to configure the
Alternate or Translated Address portions in my WI page?
Other related posts:
