This may be more than the solution calls for, but have you considered using
the web client? You haven't mentioned how much flexibility the clients have
or require in configuring their own connections, but if this is not an issue
using the web will allow you complete control of all server connection
parameters. The client just needs to know a URL. Worst case scenario you
have to do a little (very little) html programming, but if you get NFuse
even that's eliminated.
Jay Dunn
IPI GrammTech, Ltd.
210.694.4313
http://www.ipi-gt.com
Nunquam Facilis Est
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Lopez, Robert
Sent: Monday, June 11, 2001 10:13 AM
To: [EMAIL PROTECTED]
Subject: RE: NAT / citrix connectivity [7:7709]
Shrug,
You indicated that even if we use NAT, client-side changes will still have
to be made. I found one document on the citrix site that speaks of "ICA
Browsing with firewall address translation - NAT". This document provides a
straight-forward solution but requires making a change on both the client
and server side. Is there any other documentation that states the need to
configure the client as well.
My dilemma is that I've been asked to provide a solution that will allow the
citrix client to create a session to the citrix server in the new subnet -
and doing so without touching the client-side. Any help will be greatly
appreciated.
Robert
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Friday, June 08, 2001 1:52 PM
To: [EMAIL PROTECTED]
Subject: Re: NAT / citrix connectivity [7:7709]
On Fri, 8 Jun 2001, Lopez, Robert wrote:
> establish a session. This is where my problem lies...the citrix server ip
> address will change once it's in the new subnet...the client will not be
> able to connect.
>
> It was suggested that we implement NAT to allow the client to connect to
the
> citrix server. This is a quick snapshot of what we have...
I'm assuming that notifying the users and having them change the IP is not
a feasable option?
Even if you DID use NAT to translate the old IP to the new IP, client-side
changes will have to be made. (and i think the server will bave to be set
up appropriately too..I'm only familar with the client side.)
The client end will have to, going from a bad memory, change their
firewall settings to allow them to connect to the server-behind-nat.
There is an option along the lines of "use alternate IP address" or
something...its been about 4 months since I did this and havent been in
front of a citrix client in at least 2...its a well documented bit.
The /better/ solution of course would be to assign a FQDN to the IP
addresses and have the clients change to THAT, so that it is only done
once...and then you can change the IP at will.
~shrug~
...david
> NAT config on cat6509sw1r1
> ip nat inside source static 10.101.99.20 164.42.100.25
If I read this right, it appears that you are doing the translation at the
/client/ end, not the server end...that is totally wierd, to me.
But, in that case, should that not be
ip nat OUTSIDE source static
since that is the direction we need to go?
but I'm still rather confused why you are doing the NAT at the client side
instead of the server side..
....david
---
david raistrick (deep in the south georgia woods)
[EMAIL PROTECTED]
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=8125&t=7709
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
