WINDOWS 1002000 PROFESSIONAL RESOURCE KIT [Electronic resources] نسخه متنی

Determining a Client Connectivity Strategy

Networks vary in size and type depending on their function. How clients connect to the network depends upon where they are located. Some examples include:

Internal clients are physically located within the corporate infrastructure. Internal
clients can use a variety of different network media, such as asynchronous transfer mode (ATM), Ethernet,
or Token Ring.

External clients are remote from the corporate network infrastructure and
require Routing and Remote Access or virtual private networking.

Clients need to be able to connect to a variety of resources.
These resources can include file and print servers, database servers such as Microsoft® SQL Server^™, Microsoft® Exchange servers, and internal Web servers.

Overview of Client Connectivity

When you connect computers running Windows 2000 Professional to a local area network, the Windows 2000 Professional operating system detects your network adapter and creates a local area connection for you. It appears, like all other connection types, in the Network and Dial-up Connections folder, which is accessed from Control Panel. By default, a local area connection is the only type of connection that is automatically activated. Dial-up connections are not activated by the system. They require a manual configuration using the Network Connection wizard located in the Network and Dial-up Connections folder in Control Panel.

If you make changes to your network, you can modify the settings of an existing local area connection to reflect those changes. These changes can be in one of the following forms:

Protocols such as static IP address changes

Domain Name System (DNS) or Windows Internet Name Service (WINS) configurations

Services

By means of the Status dialog box, you can view connection information for a local area connection such as connection duration, speed, amount of data transmitted and received, and the diagnostic tools available for a particular connection. You can also add a status icon for the local area connection in the Windows taskbar.

If you install a new LAN device on your client, the next time you start Windows 2000 Professional, a new local area connection icon appears in the Network and Dial-up Connections folder. For portable computers, you can add a Personal Computer Memory Card International Association (PCMCIA) slot, or PC card network adapter while the computer is on, and the local area connection icon is immediately added to the folder without restarting the computer.

You can configure network components used by your local network connection with the Properties menu option. Network components are the clients, services, and protocols you use to communicate with servers on your network after you are connected to a server. The components you can configure and their functions are as follows:

Services, such as file and printer sharing.

Protocols, such as Transmission Control Protocol/Internet Protocol (TCP/IP).

Clients, such as Gateway Services for NetWare and Client Services for NetWare.

For more information about configuring local area connection properties, see Windows 2000 Professional Help.

You can configure settings for multiple LAN adapters through the Advanced Settings menu option for the local area connection in the Network and Dial-up Connections folder. Using this option, you can modify the order of adapters that are used by a connection, and the adapter's associated clients, services, and protocols.

Windows 2000 Professional Services and Protocols

TCP/IP is the standard network protocol used by Windows 2000 Professional. If a client needs to access file and print resources from NetWare or Macintosh servers, Microsoft supplies either the protocol necessary for connectivity on these networks or a compatible protocol for these environments. An example of such a compatible protocol is NWLink, which is the Microsoft implementation of Novell IPX/SPX protocol.

You can install Services for Macintosh, which includes the AppleTalk protocol on client computers that need access to Macintosh resources. Macintosh clients can also access file servers by running TCP/IP.

Windows 2000 Professional attempts network connectivity with remote servers using network protocols in the order of the local area connection specified by the user in the Advanced Settings dialog box. Install and enable only the protocols that you need. For instance, if you only need TCP/IP, but have IPX loaded as well, it generates unnecessary IPX and Service Advertising Protocol (SAP) network traffic.

TCP/IP Network Clients

Clients on a TCP/IP network can have an IP address assigned to them either statically, by the network administrator, or dynamically, by the Dynamic Host Configuration Protocol (DHCP) server.

Windows 2000 uses a new DNS service called DNS dynamic update. It is used as the namespace provider whether the client is using DHCP or static IP addresses. In previous Windows networks, WINS was used in conjunction with DHCP, allowing hosts to dynamically register their NetBIOS name and IP address in the WINS database. You still need WINS if you have any clients on your network that are running Windows NT Workstation, Windows 95, Windows 98, or Microsoft® Windows® 3.1, because these clients use the NetBIOS name resolution method. It is recommended that you upgrade all NetBIOS clients to DNS dynamic update, but plan to support both DNS and WINS for some period of time.

Using Microsoft DNS on your network offers the following advantages:

Provides interoperability with other DNS servers, such as Novell NDS and UNIX Bind.

Integrates with and is required for the support of Active Directory.

Integrates with other networking services, such as WINS and DHCP.

Allows clients to update resource records by dynamically registering their DNS names and IP addresses.

Supports incremental zone transfers between servers.

Supports new resource record types including the Services Locator and asynchronous
transfer mode addresses records.

Before you install TCP/IP on a system, determine whether the client will receive static or dynamic IP addresses. Identify whether the hosts on your network are using DHCP or if your IP addresses are statically assigned.

DHCP

Using the Dynamic Host Configuration Protocol (DHCP) allows a client to receive an IP address automatically. This helps avoid configuration errors caused by the need to manually type in values at each computer. Also, DHCP helps prevent address conflicts that occur when a previously assigned IP address is reused to configure a new computer on the network. In addition, the DHCP lease renewal process helps assure that where client configurations need to be updated often (such as users with mobile or portable computers who change locations frequently), these changes can be made efficiently and automatically. Finally, deploying DHCP in a network allows a much more efficient use and management of your organization's address space, because addresses that are no longer used by devices are reintroduced in the address pool and reallocated to other clients.

To enable DHCP, a client simply needs to have the Obtain an IP address automatically radio button selected in the TCP/IP Properties property sheet, which is accessible through the Local Area Connection icon. This option is enabled by default when a Windows 95, Windows 98, Windows NT, or Windows 2000 Professional client is initially installed, so if you are using DHCP, you do not need to manually set your IP configuration.

The benefits of using DHCP are as follows:

You do not have to manually change the IP settings when a client, such as a roaming user,
travels throughout the network. The client is automatically given a new IP address no matter which
subnet it reconnects to, as long as a DHCP server is accessible from each of those subnets.

There is no need to manually configure settings for DNS or WINS. The DHCP server
can give these settings to the client, as long as the DHCP server has been configured to
issue such information to DHCP clients. To enable this option on the client, simply select
the Obtain DNS server address automatically option button.

There are no conflicts caused by duplicate IP addresses.

Static Addresses

If your IP addresses are assigned statically, you have the following information available:

The IP address and subnet mask for each network adapter installed in the client.

The IP address for the default gateway.

Whether or not the client is participating in DNS or WINS.

If the client is participating in DNS, the name of the DNS domain that the client is
currently part of, and the IP addresses of the primary and backup DNS servers.

If the client is participating in WINS, the IP addresses for the primary and backup WINS servers.

Windows 2000 Professional clients can operate with NetWare servers by using Client Services for NetWare or Gateway Services for NetWare.

If there are servers on the network that use Novell NetWare operating systems, Windows clients can use Client Services for NetWare to connect directly to the server, or they can connect indirectly to a Windows 2000–based server that is running Gateway Services for NetWare.

The following steps are required to gain client access to NetWare resources:

Install Client Services for NetWare. This allows you to make direct connections to NetWare resources.
The NetBIOS NWLink protocol is installed when Client Services for NetWare is installed. This is the Microsoft
version of the IPX protocol, and supports connectivity between systems running Windows 2000 Server and systems
running NetWare 4.x and earlier.

Connect to NetWare volumes. After installing the services listed previously, you can connect to a
NetWare volume by clicking My Network Places on the desktop.

Connect to NetWare file and print resources. You can add a NetWare printer in a Windows 95 or later
client by going to the Printer folders in the Settings menu, and follow the Printer Installation wizard.
You can add NetWare printers in the wizard by typing in the name of the printer in normal Universal Naming
Convention (UNC) format.

Gateway Services for NetWare

You can install Gateway Services for NetWare on a Windows 2000–based server to enable it to act as a gateway. Clients can then connect to NetWare resources without running NWLink, using TCP/IP only. The server runs Gateway Services for NetWare and NWLink, linking the client to the NetWare server. This service is included with Windows 2000 Server.

File and Print Services for NetWare

The File and Print Services for NetWare service is a separate product and enables a Windows 2000–based server to provide file and print services directly to a NetWare server and compatible client computers. Resources connected through this service appear to NetWare clients like any NetWare server and clients can gain access to volumes, files, and printers on the server. No changes or additions to the NetWare client software are necessary.

Client Services for NetWare

The Client Services for NetWare service enables client computers to make direct connections to file and printer resources on NetWare servers running NetWare 2.x, 3.x, or 4.x. You can use Client Services for NetWare to gain access to servers running either Novell Directory Services or bindery security. This service is included with Windows 95, Windows 98, Windows NT, and Windows 2000 Professional.

For information about advanced client connectivity and remote network connection methods, see "Defining a Client Connectivity Strategy" in the Deployment Planning Guide. For additional details on TCP/IP features in Windows 2000 Professional and information about how to configure TCP/IP, see the chapter "TCP/IP in Windows 2000 Professional" in this book.