[THIN] Re: Web Interface 3.0
- From: "Russell Robertson" <russell.robertson@xxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Tue, 24 Jan 2006 16:37:15 -0000
Bruno
Yes, you need to use Citrix Secure Gateway. The purpose of CSG is to
secure the connection using SSL and HTTPS, and thus uses port 443 and
not 1494. You should find virtually every firewall has 443 open.
Russell
Russell Robertson
Skibo Technologies
The Software Centre
Aberdeen Science & Technology Park
Balgownie Drive, ABERDEEN
AB22 8GU
T: +44 (0)1224 355250
E: russell.robertson@xxxxxxxxx <mailto:russell.robertson@xxxxxxxxxx>
W: www.skibo.com <http://www.skibo.com/>
Microsoft Certified Partners
Citrix Solutions Advisers
Northern Business Star Awards Finalists 2005
________________________________
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Petitti, Bruno
Sent: 24 January 2006 15:41
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Web Interface 3.0
Hi,
Currently we are running Web Interface 3.0 with Metaframe XP. To my
understanding, all the communication between the client workstation and
Web Interface server occurs by default on port 80. Once the connection
is established, to the internal Citrix server, it is using port 1494 at
this time.
Are major issue is that when a user is offsite at a client location, the
client firewall usually has port 1494 blocked.
Is there a better solution then always asking the client to open the
port on there firewall? Or is Citrix Secure Access a better solution?
Thanks for your help in advance.
Other related posts:
