Configuring Citrix MetaFrame for Windows 2000 Terminal Services

Скачать в pdf «Configuring Citrix MetaFrame for Windows 2000 Terminal Services»


To see if the firewall is correctly set up, use the standard client and connect to the server creating an entry with the external IP address instead of the server name. If you can connect, the ports and the firewall are configured correctly. When using a Web browser to gain access using NFuse, the connection information is processed on the server rather than the client, therefore eliminating the UDP broadcasting.


When a user connects to an NFuse page you have to configure that service to use port 80 to talk with the NFuse HTTP service and that then passes the client application list to the client. When the client clicks on the application, an .ICA file is created on the fly. This .ICA file contains the IP address of the least busy server and no name resolution is needed, thus there is no need to use 1604. Once the user gets the .ICA file, the Web server has done its job and is no longer needed to make a connection.


If you have changed the ICA port on the server using the ICAport command, the Template.ICA file will need to be modified by adding the line:


ICAPortNumber=whatever port number you selected


TCP Port 1494 must be open inbound and the high ports (1025 and above) opened outbound for TCP.


As shown, the NFuse Web components can be configured to resolve application names to IP addresses, eliminating the need for the ICA Client to use the UDP-based ICA Browser. Additionally, Citrix’s Secure ICA product can provide additional security by way of encryption of ICA sessions.

Скачать в pdf «Configuring Citrix MetaFrame for Windows 2000 Terminal Services»