Configuring Citrix MetaFrame for Windows 2000 Terminal Services

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


7.    In most cases you will not want to be able to use port 80 for Citrix XML communications because this will conflict with regular HTTP traffic. When you select a port other than 80 you will see a warning message (Figure 8.15). Make sure you use the same port when setting up your MetaFrame server. You can check the MetaFrame server’s port information in the following registry key:


HKLMSYSTEMCurrentControlSetServicesCtxHttpTcpPort



Figure 8.14 Configure the port for XML communications.



Figure 8.15 Ensure you configure IIS and MetaFrame to communicate on the same TCP port.


TIP


Citrix and Yahoo! have formed an alliance to combine the features of corporate Yahoo! and NFuse for developing intranets and extranets. This can be an excellent option for rolling out a robust corporate site.


8. Insert the directory for your Web server’s root URL (Figure 8.16). If you are creating a different virtual server/directory for NFuse, browse to the desired installation location. Place the files in the root of the Web server to connect to
http://server IP address/ NFuse15/default.htm.


Figure 8.16 Define destination folder for sample NFuse files.

9. To have NFuse automatically install ICA Clients when a user


accesses the NFuse Web site, choose Yes from the dialogue box in Figure 8.17.


Figure 8.17 Choose Yes to allow automatic installation of ICA Clients from Web pages.

10. Setup then installs Web extensions, example files, and client files to your server (Figure 8.18).


Figure 8.18 NFuse Web server extension installation file copy.

11. NFuse installation will finish and the WWW service will be

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