Configuring Clients to Have Unique Server Location Entries per Connection
Configuring Clients to Have Unique Server Location Entries per Connection Configuring Clients to Have Unique Server Location Entries per Connection
Citrix states in their article: CTX025001
CTX025001 - Configuring Clients to Have Unique Server Location Entries per Connection
This document was published at: http://support.citrix.com/kb/entry.jspa?externalID=CTX025001
Document ID: CTX025001, Created on: May 22, 2000, Updated: Apr 23, 2003
Products: ICA Win32 Program Neighborhood Client
Occasionally users need to access published applications on their local LAN as well as across a WAN. Setting the Alternate Address on the client is a global setting. This note describes how to configure the client so that it requests the alternate IP address on an individual connection basis
Checking the Use Alternate Address for Firewall box when specifying Server Location appends the Appsrv.ini in the users profile with the following entry:
UseAlternateAddress=1
to the [WFCLIENT] section. This setting is a flag that instructs the client to request an alternate IP address. If this flag is added to the [WFCLIENT] section, the client requests the alternate IP address for every defined server connection. It also requests an alternate IP address when browsing Citrix servers and published applications. This allows the client to browse across firewalls even when IP address translation is enabled on a firewall. Also, notice that the TcpBrowserAddress= is given an address within the [WFCLIENT] section.
It is also possible to configure the client so that it requests the alternate IP address on an individual connection basis. Suppose a given WinFrame client connects to Citrix servers on the Intranet. For these connections, the UseAlternateAddress flag is not needed because both client and server are behind a firewall. You may, however, want to have a TcpBrowserAddress= x.x.x.x if all servers are not on the same subnet.
Occasionally the same client also connects to Citrix servers over the Internet. These WinFrame servers are behind different firewalls that are using IP address translation. In this scenario, the client should only request alternate addresses from the servers across the Internet, not from servers on the Intranet.
To configure a client for this scenario, remove the TcpBrowserAddress=x.x.x.x and UseAlternateAddress= flags from the [WFCLIENT] section. Add the UseAlternateAddress=1 and TcpBrowserAddress=x.x.x.x flags to the relevant section in the Appsrv.ini that corresponds to the server description in Program Neighborhood.
User login
Who's new
- Cachleferah
- Weedbacuupe
- vororourn
- vDonellaCandrah
- SnnaSusi