Multiple Servers Single Farm

[PeterL]

We just added a second Citrix server to our one farm. We have published apps on both servers and they run fine internally. We also make these same apps available on our Internet site. I keep the ICA file for internal access in one location and the ICA for external access in another. I have modified the ICA's TcpBrowserAddress to our external IP for Internet access.
The problem is that the apps cant be found when run externally. Does each server whose apps are available externally require it's own public TcpBrowserAddress. Am I wrong to assume that because the 2nd server is part of the same farm as the first that these apps should run the same regardless of which server they have been published on.

 

[CitrixEngineer]

You should just need to set an alternative address on your NFuse server. As long as it points to the ICA Master browser, it should return the users' application sets from the farm.

The NFuse admin guide covers this area fairly well.

http://hqextsrvsft01.citrix.com/cgi...U=1,ST=222,N=0005,K=8912,SXI=7,Case=obj(9435)

(Or just go to knowledgebase.citrix.com and do a search on NFuse if this link doesn't work!)

Hope this helps

 

[PeterL]

Only problem with that is we are not using NFUSE. We use NAT on our firewall and forward the external IP to the internal address of our primary Citrix server.

 

[CitrixEngineer]

Make sure you have port 1494 open inbound and outbound, UDP port 1604 open outbound and TCP ports 1023 and up open outbound.

Hope this helps

 

[PeterL]

Both ports are open. App's which I have published on my main Citrix server are fine both internally and via the web. The apps which have been published on my 2nd citrix server (same farm) are only available internally. The first server is a NT 4.0 with Metaframe 1.8 The second server is a Windows 2000 Term Server with Metafram 1.8 for 2000. I cant imagine that this has anything to do with.

 

[tpulley]

I copied this from another thread.... I believe this will work for you Peter. Good luck...

I have found that in order to have users connect to published apps (across the Internet) I had to connect via a desktop (using the users logon) get the properties infomation from the Target information and Start in information fields(right click on the published icon on the terminal server desktop) cut and paste Target and Start in information into a new connection ( using the Add ICA client wizard). Use the server not the application option. In the Application field paste the Target information, and in the Working Directory field paste the Start in information. Works great for me...

If I have made this seem difficult it really isn't. Took me about 2 mins to create a published Word icon (so I could remember the field names).

 

[VincentH]

You must have one public address for each metaframe server. and use the alternate address. the router must translate each public address to the correct server. if you have one public ip, the connexion is always for metaframe that have the redirection port for 1494 and 1604.
I have i good solution for this problem. I have a socks server that run on a firewall on 1080 port. i can have all servers you want with one ip address. this socks work in reverse mode (internet to lan). this solution work fine.

 

[PeterL]

VincentH
That is exactly what my problem is. Is a Socks server just a service that I run on my Firewall?

 

[VincentH]

yes go to

http://www.inet.no/dante/

it's a free socks server for unix system. My firewall is a Linux. With this socks it's more easy for your customers, they need only one port to open (1080) and tou can add a lot of metaframe servers behind this socks.

 

[BKIRK]

Hey PeterL,

You do not have to have a public address per MetaFrame server if you can use PAT (port address translation) on your firewall and change the ICA listener ports on each of your MetaFrame servers. On the first server you could leave it at it’s current address and settings, the second server you would change the ICA listener port using the ICAPORT command (something like this ICAPORT /port:1234 which will switch the ICA listener from 1494 to 1234), you then need to set the alternate address port to match by running altaddr /set {external IP}:1234 so if you pick 1234 as the port number for your external IP address of 100.200.100.200, the command would look like this altaddr /set 100.200.100.200:1234. This also requires that you configure your firewall to forward port 1494 to the first MetaFrame server and forward port 1234 to the second MetaFrame server.

You would also need to have these lines in your .ica file for the web browser access from external users.
TCPBrowserAddress=internal ipaddress
UseAlternateAddress=1


Hope this works for you,
Brian