Configuring Citrix MetaFrame for Windows 2000 Terminal Services

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


When connecting to Terminal Servers over a WAN, follow the guidelines set forth earlier. For a good connection, you’ll need 30 KB of bandwidth per user. If your clients will be accessing external applications like SQL server, place the Terminal Servers near the application server, not the client. Terminal Server-to-application server traffic will be significantly higher than client-to-Terminal Server traffic.

Internet Connectivity


A connection to the Internet is highly recommended if for no other reason than to make licensing easier for you. A dial-up Internet line would serve that purpose. Users may want to surf the Internet for various reasons or you may want to allow connections to your Terminal Server via the Internet. In either case, I highly recommend a firewall to protect your LAN. For Web surfing purposes, you’ll have to open port 80. You’ll have to open port 443 as well if you wish to allow SSL-encrypted web traffic. For RDP traffic to your Terminal Servers, you’ll have to open port 3389. You may wish to create a DMZ as stated earlier for increased security.

Upgrade from Windows NT 4.0 Terminal Services Considerations


There are many considerations to keep in mind when upgrading from previous versions of Terminal Server, Citrix MetaFrame, or Citrix WinFrame. You must consider the version you are upgrading from and the type of migration you are planning. You will have to purchase Terminal Server Client Access Licenses. You must check your current applications for compatibility. All this must be done before upgrading your servers.


Here are some of the questions you should ask yourself:

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