RE: PIX & Citrix/nfuse access [7:18938]

2001-09-10 Thread Randall Yoo
TED] Sent: 9/7/01 4:05 PM Subject: Re: PIX & Citrix/nfuse access [7:18938] I am pretty sure that Citrix uses port 1604 also. >From: "[EMAIL PROTECTED]" >Reply-To: "[EMAIL PROTECTED]" >To: [EMAIL PROTECTED] >Subject: Re: PIX & Citrix/nfuse access [7:18938]

RE: PIX & Citrix/nfuse access [7:18938]

2001-09-10 Thread Ciaron Gogarty
Subject: Re: PIX & Citrix/nfuse access [7:18938] I am pretty sure that Citrix uses port 1604 also. >From: "[EMAIL PROTECTED]" >Reply-To: "[EMAIL PROTECTED]" >To: [EMAIL PROTECTED] >Subject: Re: PIX & Citrix/nfuse access [7:18938] >Date: Fri, 7 Sep 2

Re: PIX & Citrix/nfuse access [7:18938]

2001-09-07 Thread farhan
udp should be 1604 instead - Original Message - From: "Eric Rivard" To: Sent: Saturday, September 08, 2001 4:03 AM Subject: RE: PIX & Citrix/nfuse access [7:18938] > on the pix make 2 conduit entries for tcp traffic on port 1494 and udp > traffic on port 1494. Th

RE: PIX & Citrix/nfuse access [7:18938]

2001-09-07 Thread Eric Rivard
. -Original Message- From: Jeff Smith Sent: Fri 9/7/2001 8:05 AM To: [EMAIL PROTECTED] Cc: Subject: Re: PIX & Citrix/nfuse access [7:18938] I am pretty sure that Citrix uses port 1604 also. >From:

Re: PIX & Citrix/nfuse access [7:18938]

2001-09-07 Thread [EMAIL PROTECTED]
only for program neigborhood feature - Original Message - From: "Jeff Smith" To: Sent: Friday, September 07, 2001 7:05 PM Subject: Re: PIX & Citrix/nfuse access [7:18938] > I am pretty sure that Citrix uses port 1604 also. > > > >From: "[EMAI

RE: PIX & Citrix/nfuse access [7:18938]

2001-09-07 Thread Joshua Vince
AM To: [EMAIL PROTECTED] Subject: Re: PIX & Citrix/nfuse access [7:18938] I am pretty sure that Citrix uses port 1604 also. >From: "[EMAIL PROTECTED]" >Reply-To: "[EMAIL PROTECTED]" >To: [EMAIL PROTECTED] >Subject: Re: PIX & Citrix/nfuse access [7:18938] &g

Re: PIX & Citrix/nfuse access [7:18938]

2001-09-07 Thread Jeff Smith
I am pretty sure that Citrix uses port 1604 also. >From: "[EMAIL PROTECTED]" >Reply-To: "[EMAIL PROTECTED]" >To: [EMAIL PROTECTED] >Subject: Re: PIX & Citrix/nfuse access [7:18938] >Date: Fri, 7 Sep 2001 10:23:19 -0400 > >make a static mapping &

RE: PIX & Citrix/nfuse access [7:18938]

2001-09-07 Thread Donald Queen
Also don't forget to do the altaddr command to translate the internal ip address to external address. -Original Message- From: "Rik Guyler" Date: Fri, 7 Sep 2001 07:35:02 -0400 To: [EMAIL PROTECTED] Subject: RE: PIX & Citrix/nfuse access [7:18938] > NFuse makes

Re: PIX & Citrix/nfuse access [7:18938]

2001-09-07 Thread [EMAIL PROTECTED]
make a static mapping static (inside,outside) conduit permit tcp glbol ip add (citrix port ) 1494 i guess and 80 for web shd work fine - Original Message - From: "Matthew Tayler" To: Sent: Friday, September 07, 2001 2:18 PM Subject: PIX & Citrix/nfuse access [7:18938] > Has anybody a

RE: PIX & Citrix/nfuse access [7:18938]

2001-09-07 Thread Rik Guyler
NFuse makes the initial connection via HTTP (TCP port 80) but then opens up an ICA session back to an inside MetaFrame box. To do this, assign a public address and statically translate it to the internal address of the MetaFrame box and then open TCP port 1494 and/or (it's optional) UDP port 1604