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

Configuring Client Service for NetWare

When you install Client Service for NetWare on Windows 2000 Professional, the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol is automatically installed.

NOTE

---

To install Client Service you need Administrator rights to the computer running Windows 2000 Professional.

Microsoft Unattended Setup Mode can be used for large deployments of Windows 2000 Professional and Client Service for NetWare. For more information about Unattended Setup Mode, see "Customizing and Automating Installations" in this book.

To install Client Service for NetWare

Open Network and Dial-Up Connections in Control Panel.

Right-click the local area connection for which you want to install Client Service for NetWare, and then click Properties.

On the General tab, click Install.

In the Select Network Component Type dialog box, click Client, and then click Add.

In the Select Network Client dialog box, click Client Service for NetWare, and then click OK.

Table 24.2 lists the files that are installed with Client Service.

Table 24.2 Client Service Files

NOTE

---

If you are unable to install clients, services, or protocols under Network and Dial-up Connections, then it is possible that policies have been implemented for your computer. For more information about policies, see "Group Policy" in the Microsoft® Windows® 2000 Server Resource Kit Distributed Systems Guide and the Microsoft® Windows® 2000 Resource Kit Group Policy Reference (Gp.chm) on the Microsoft® Windows® 2000 Resource Kit companion CD.

Figure 24.3 shows the dialog box that is displayed during the installation process.

Figure 24.3 Select NetWare Logon Dialog Box

Preferred Server or Default Tree and Context

To be authenticated by NetWare servers through Client Service, you must specify either the correct default tree and context for the user or the correct preferred server.

If you do not want to set a preferred server in the Select NetWare Logon dialog box, select None from the Preferred Server list box. You are then connected to the first NetWare server to respond to the Get Nearest Server request. You are not logged on to this server, but you can use it to browse (viewing other servers on the network), the same as when you enter the NetWare slist command.

The NetWare bindery-based environment is server-centric. For example, when logging-on to a bindery-based server, the user needs to have a login account and security access to a specific NetWare server. However, NDS uses an object-oriented distributed hierarchical database model. For example, when logging on in an NDS environment, the user is treated as an object and can access assigned resources within the NDS environment. The user accesses resources from one or more distributed NetWare servers.

To determine whether to select Preferred Server or Default Tree and Context, determine whether the NetWare server you are authenticating from is configured as bindery-based or NDS-based. Knowing the version of the NetWare server will assist in finding out whether it is bindery-based or NDS-based. For example, Table 24.3 lists the current supported versions of NetWare in a Windows 2000 network and whether or not they support bindery or NDS.

Table 24.3 NetWare Bindery and NDS

If users need to connect to bindery-based resources, specify a preferred server. If users need to connect to NDS resources, specify the tree and context.

Setting a Preferred Server in a Bindery-Based Server Environment

In a NetWare bindery-based server environment, you must direct the computer running Client Service to the NetWare server where the Windows 2000 user and group accounts with the appropriate rights are located. Select the appropriate NetWare server as the preferred server. Your computer can then log on to the NetWare server, and then you can attach to another server.

Specifying the Tree and Context in an NDS Environment

In NDS, tree refers the NDS hierarchical directory structure, and context refers to the location of an object in the directory tree. If there is only one tree in an organization, it is easy to select and specify. The context, on the other hand, is not so obvious. To locate the necessary network resources for the particular user object, you must define the context correctly when accessing NDS servers through Client Service or Gateway Service.

For example, in Figure 24.4, Reskit, at the top of the NDS directory tree, is the actual name of the root object.

Specify the context in the Client Service for NetWare dialog box. You can type it in either the typefull name or typeless name formats.

Within the tree, the context in typefull name format for the user JDOE is ou=sales.ou=milan.ou=eu.o=reskit, and the context in the typeless name format is sales.milan.eu.reskit. Both the typefull name and the typeless name formats are valid entries in the Context field of the Client Service for NetWare dialog box.

Figure 24.4 NDS Directory Tree

Run Login Script

A NetWare login script is a list of commands that are carried out each time the user logs on to the NetWare network. Login scripts can be used to set user defaults such as drive mappings, search drive mappings, printer configurations, and other variable settings which define the user's environment configuration on the NetWare network. They enable you to create a consistent user environment.

Login scripts reside on NetWare servers and can be run when you access NetWare networks through Client Service. To use a NetWare login script to set up variables on the NetWare network each time a user connects, enable the Login Script option in the Client Service for NetWare dialog box. Enabling this option causes the NetWare login script to run when the user is authenticated to the NetWare network. The NetWare login script variables only apply to the individual user.

Bindery-based and NDS versions of NetWare enable you to use different login scripts. The bindery-based server version provides system and user login scripts that are run at the system-wide level and at the user level, respectively. The system login script sets variables for all users on a server.

NDS, on the other hand, enables you to use four types of login scripts that work in sequence to set users rights at the container, profile, and user level. NDS enables you to use the following login scripts:

The NDS container login script is similar to the system login script in the NetWare bindery-based server version, but it sets global variables at the container level so that you can set variables for different organizations.

The NDS profile login script allows you to set variables for users who need common access to specific applications or to members of workgroups.

The user login script allows you to set variables for individual users.

The default login script is run when a user login script is not available.

For more information about setting up a NetWare login script, see your NetWare documentation.

NWLink IPX/SPX/NetBIOS Compatible Transport Protocol

When you install Client Service on a computer running Windows 2000 Professional, the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol is automatically installed.

Figure 24.5 shows the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol dialog box.

Figure 24.5 NWLink IPX/SPX/NetBIOS Compatible Transport Protocol Dialog Box

Internal Network Number

The internal network number is used for internal routing purposes when the computer running Windows 2000 is also hosting IPX services. When calculating the best possible route for transmitting packets to a specified computer, multiple routes with the same route metrics can present ambiguity to computer hosts. When you specify a unique internal network number, you create a virtual network inside the computer. This allows for a singular optimum path from the network to the services running on the computer.

Generally, you do not need to change the internal network number. For more information about the internal network number, see "IPX Routing" in the Internetworking Guide.

To change the internal network number

In Control Panel, double-click Network and Dial-up Connections.

Right-click a local area connection, and then click Properties.

On the General tab, click NWLink IPX/SPX/NetBIOS Compatible Transport Protocol, and then click Properties.

Type a value in the Internal Network Number box, and then click OK.

NWLink IPX/SPX/NetBIOS-Compatible Transport Protocol supports the frame types shown in Table 24.4.

Table 24.4 Supported Frame Types

Frame types define packet formats used by the different network types.

During the Auto Detect process, NWLink tries each available frame type in the list for the associated medium access type. For example, on an Ethernet network, Ethernet 802.2, Ethernet 802.3, Ethernet II, and Ethernet SNAP are tested to see which frame types NWLink can communicate with. When NWLink receives a response from a NetWare server with one of the frame types, it also receives the network number associated with the frame type for the network segment where the client resides. NWLink then rebinds using the frame types from which it received responses.

The external network number is a unique number which represents a specific network segment and associated frame type. All computers on the same network segment that use a particular frame type must have the same external network number, which must be unique for each network segment.

The IPX frame type and network number are set during the initial NetWare server configuration. The Windows 2000 Professional NWLink Auto Detect feature then detects the frame type and network number that was configured on the NetWare servers. NWLink Auto Detect is the recommended option for configuring both the network number and the frame type.

Occasionally, Auto Detect selects an inappropriate network number and frame type combination for the adapter. Because Auto Detect uses the responses it receives from computers on the same network segment, Auto Detect might select an incorrect frame type and network number if computers responded with incorrect values. This is usually caused by an incorrect manual setting on one or more computers on the network.

If the Auto Detect feature selects an inappropriate frame type and network number for a particular adapter, you can manually reset an NWLink frame type or network number for that particular adapter. The frame type and network number on Windows 2000 Professional need to match the frame type and network number configured on the NetWare server. You can specify a frame type and network number of 00000000, so that the network number of the network segment is automatically detected. To manually determine the frame type and network number set on the server, inspect the Autoexec.ncf file, or at the command prompt, type:

config

In the following excerpt from an Autoexec.ncf file, the frame type is Ethernet 802.2 and the network number is set to 17216720.

load c:EPRO port=300 int=5 FRAME=ETHERNET_802.2
bind IPX to EPRO net=17216720

To manually determine the frame type and network number set on a computer running Windows 2000, carry out the ipxroute config command at the command prompt. Figure 24.6 illustrates the resulting screen.

Figure 24.6 Frame Type Displayed in the Command-Line Interface

The network number, 17216720, and the frame type, Ethernet 802.2, in the IPXROUTE CONFIG display screen correspond to the settings in the Autoexec.ncf file.

To change the frame type and network number on your Windows 2000-based computer, you must be a member of the Administrator group.

CAUTION

---

In most cases, you do not need to change the network number and frame type, because Auto Detect usually detects the frame type and network number. If you choose an incorrect setting, the client cannot connect to NetWare servers.

To change the network number and frame type

In Control Panel, double-click Network and Dial-up Connections.

Right-click a local area connection, and then click Properties.

On the General tab, click NWLink IPX/SPX/NetBIOS Compatible Transport Protocol, and then click Properties.

In the Frame type list box, select a frame type.

In the Network number text box, type a network number, and then click OK.