RE: Problem Publishing Citrix with ISA 2004
- From: Julio Bretín Díaz <JBretin@xxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Mon, 31 Jan 2005 17:26:40 +0100
Steve,
The fact is that we have this service published on Internet under an url as
applications.isaserver.net and we have only a web interface that is not the
same server as the presentation server, so when a client connects to the Web
Interface from internet (port 80) ISA Server relay this to the web interface
server and after when the client connects to the presentation server by
applications.isaserver.net:1494 ISA redirects the request to the presentation
server, so we use two rules to do that.
Well the problem is that our company wants to have the same url
applications.isaserver.net for internal use, so we need to publish the service
in our internal interface. Citrix admins have configure the .ica file to
include the url applications.isaserver.net instead of an ip address.
Does anyone know how can we do that?
Thank you very much.
-----Original Message-----
From: Steve Moffat [mailto:steve@xxxxxxxxxx]
Sent: Monday, January 31, 2005 4:10 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Problem Publishing Citrix with ISA 2004
http://www.ISAserver.org
Why on earth would you be publishing your citric server internally.
S
-----Original Message-----
From: "Julio Bretín Díaz" [mailto:JBretin@xxxxxxxx]
Sent: Monday, January 31, 2005 10:52 AM
To: ISA Mailing List
Subject: [isalist] Problem Publishing Citrix with ISA 2004
http://www.ISAserver.org
Hi everybody,
I'm trying to publish a Citrix Server with ISA 2004. If I publish it defining
Internal and External networks and configure rules to access from external
network to an internal server all is ok, but if I publish the service on the
internal interface and try to access from the same internal network, it doesn't
work. In the log it seems like ISA get the connection as a Citrix client
connection instead of a server inbound connection. I use a custom ICA protocol,
but ISA gets the connection as the default ICA client protocol.
This problem doesn't happen with web server publishing.
Is there any way to force ISA 2004 to publish a port for internal use?
Is this a Bug?
Is a design limitation?
Thanks in advanced.
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com Leading Network
Software Directory: http://www.serverfiles.com
No.1 Exchange Server Resource Site: http://www.msexchange.org Windows Security
Resource Site: http://www.windowsecurity.com/ Network Security Library:
http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
isalist@xxxxxxxxxx To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=isalist
Report abuse to listadmin@xxxxxxxxxxxxx
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com
Leading Network Software Directory: http://www.serverfiles.com
No.1 Exchange Server Resource Site: http://www.msexchange.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
jbretin@xxxxxxxx
To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist
Report abuse to listadmin@xxxxxxxxxxxxx
Other related posts:
