[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] Citrix MetaFrame with Qube2
- Subject: [cobalt-users] Citrix MetaFrame with Qube2
- From: "Shane Davis" <sdavis@xxxxxxxxxxx>
- Date: Thu Jun 14 07:00:02 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
This question was posted in April and I'm wondering if anyone had a response
to it or if the sender was able to get an answer. I need to get this
project done soon.
Thanks for your help-
Shane Davis
Here is the previous post-
Hello,
We have recently installed a Qube on our permanent static IP internet
connection and I am looking for a solution to the following problem.
We have a Citrix Metaframe (windows nt terminal server idea) behind our
Qube. When we remove the Qube from the Circuit (see below) we can remotely
connect to the Metaframe unit using the supplied ICA client (apparently it
uses its own protocl - ICA protocol).
When we put the Qube in the circuit and leave it completely open (no
filtering) we are unable to connect to the Metaframe.
I have read that I need port 1494 open on the Qube to allow the client to be
able to pass through, I have done this as well as port 1604 as well. (this
is when I have filtering on)
In either case, filtering and no filtering, I cannot connect the the
Metaframe unit remotely.
I have heard also I may need to recompile the kernel to allow the ICA
protocol to function - currently I am at a lose with this.
I would greatly appreciate any input - not already listed above - that
others may have experienced with this.
Emailing me directly is fine.
Circuit
Internet <----> Fibre Media Convertor <----> Cobalt Qube <---> Software
base firewall and proxy server <---> rest of network
Kind regards
Darren Twyford