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

Troubleshooting Windows 2000 Professional and NetWare Connectivity

The following sections describe the tools that you can use to troubleshoot connectivity problems and monitor network traffic. Troubleshooting common problems is also discussed; for example, connectivity-related problems, login scripts, client server installation and configuration, and password synchronization are some of the common problems discussed.

Windows 2000 Professional Troubleshooting Tools

Windows 2000 Professional includes several tools that allow you to determine computer settings and perform diagnostic tests to resolve communication problems in an IPX/SPX networking environment.

ipxroute config This command-line tool allows you to troubleshoot IPX connectivity problems and provides information about the current state of the stack. It displays the current IPX status, including the network number, MAC address, interface name, and frame type. At the command prompt, type:

ipxroute config

ipxroute ripout This command uses RIP to determine if there is connectivity to a specific network. At the command prompt, type:

ipxroute ripout ####

where #### is the network number (an 8-digit hexadecimal number).

Network Monitor Network Monitor, or Netmon, allows you to detect and troubleshoot problems on LANs and on WANs, including Routing and Remote Access links. By using Network Monitor you can identify network traffic patterns and network problems. For example, you can locate client-to-server connection problems, find a computer that makes a disproportionate number of work requests, capture frames (packets) directly from the network, display and filter the captured frames, and identify unauthorized users on your network.

Windows 2000 Server includes a version of Network Monitor that allows you to capture traffic coming to or going from the local computer. This version of Netmon is not available with Windows 2000 Professional.

Troubleshooting Common Problems

The majority of connectivity problems between Windows 2000 Professional and NetWare are caused by an incorrect setup.

Because connectivity involves resources on both Windows 2000 Professional and NetWare computers, resources must be set up correctly on computers running both Windows 2000 Professional and NetWare.

The following symptoms when connecting to the NetWare network are likely caused by an incorrect setup:

Access is denied to applications on NetWare servers.

Programs fail to run and display error messages.

Data throughput is slow.

Users see the error message "Server not found."

Users are denied access to network resources on NetWare servers.

Access to NetWare resources is limited.

Clients have varying access to NetWare services.

Users can connect to servers running Windows 2000 and Windows NT, but not to NetWare servers.

Users can connect to some NetWare servers but not to others.

First, verify that access to NetWare resources is correctly configured on the NetWare file servers. You need to check a variety of parameters depending on the problem and its severity. Consider the following questions when resolving connectivity problems:

Are user accounts set up correctly on the NetWare file server?

Are the appropriate groups set up?

Is group membership set up correctly?

Are the correct rights set for the required resources?

NOTE

---

Contact your NetWare administrator or consult your NetWare documentation for information on proper NetWare configuration procedures.

When you have verified that the necessary configurations and rights are set up on the NetWare file servers and the problem has still not been resolved, test the configuration on the Windows 2000 Professional computer, by using the steps in Figure 24.8.

Figure 24.8 Troubleshooting NetWare Connectivity Problems

Are NWLink and Client Service for NetWare Installed?

For a client running Windows 2000 Professional to access NetWare servers, NWLink and Client Service must be installed.

To verify NWLink and Client Service installation

Double-click Network and Dial-up Connections in Control Panel.

In Network and Dial-up Connections, right-click Local Area Connection, and then click Properties.

In the Local Area Connection Properties dialog box, verify that NWLink and Client Service for NetWare are listed.

NOTE

---

For installation instructions, see "Configuring Client Service for NetWare" earlier in this chapter.

To verify that Client Service for NetWare is running

In Control Panel, double-click Administrative Tools.

Double-click Services.

Verify that Client Service for NetWare is listed as started under the Status column.

NOTE

---

Although Client Service provides access to NetWare file, print, and directory services from Windows 2000, the correct user accounts, necessary rights for resources, appropriate group rights, and associated login scripts need to be configured on the NetWare servers.

Contact your NetWare administrator or see your NetWare documentation for more information.

Are the Correct Frame Type and Network Number Installed?

When you install Client Service and NWLink, the Auto Detect feature is enabled. For more information about Auto Detect, see "NWLink IPX/SPX/NetBIOS Compatible Transport Protocol" earlier in this chapter. In most cases, Auto Detect detects the correct frame type and network number. However, problems can occur when a network is using multiple frame types or when an incorrect frame type is set manually. If NWLink detects no network traffic, NWLink sets the frame type to 802.2.

To verify that the frame type is set to Auto Detect

In the Local Area Connection Properties dialog box, double-click NWLink IPX/SPX/NetBIOS Compatible Transport Protocol.

On the General tab, verify that Auto Detect is selected in the Frame type field.

To determine the frame type set on the NetWare server

At the NetWare server system console, type:

Config

- Or -

Remotely, using the NetWare Rconsole utility^, type:

Config

In either case, the frame type is displayed.

To determine the installed network number and frame type on the Windows 2000 Professional-based computer

At the command prompt, type:

ipxroute config

Verify that the network number and frame in the Network and Frame columns are correct for your installation.

If you have multiple network adapters, examine the Node MAC address column to determine the network number that is associated with the specified card.

To manually set the correct frame type and network number

In the Local Area Connection Properties dialog box, double-click NWLink IPX/SPX/NetBIOS Compatible Transport Protocol.

On the General tab, select the Frame type field.

Select the appropriate frame type for your network from the list box.

Type the correct network number for your network in the Network number dialog box, and then click OK.

When Client Service is configured with an incorrect bindery server or an incorrect context within the NDS tree, users have problems accessing network resources.

To reset the current preferred server or default tree and context

In Control Panel, double-click CSNW.

The preferred bindery server or default tree and context is displayed.

If the default tree and context or preferred server is incorrect, select the correct default tree and context or preferred server, and then click OK.

NOTE

---

If you do not want to set a preferred server, click None. You then connect to NetWare through the nearest available NetWare bindery-based server, but you are not logged on to this server; you can use it only for browsing.

Are the User Name and Password the Same Across the LAN Servers?

To access NetWare resources by using Client Service for NetWare, a valid set of NetWare credentials (user account and password) must be created, and appropriate NetWare permissions must be granted to the account.

Once valid NetWare credentials and permissions are created, you can synchronize Windows 2000 and NetWare user credentials. Having identical credentials in both environments allows Windows 2000 with Client Service to "pass through" authentication, at Windows 2000 logon, to NetWare Bindery or NDS Tree. Users are not prompted to specify a separate set of credentials for NetWare at logon. Users can access all available NetWare resources for which those credentials have privileges without being further prompted.

To synchronize credentials, create a user account in NetWare with the identical name and password as Windows 2000 user account.

If a user's Netware password becomes "out of sync" with the Windows 2000 password, you can reset the NetWare password to the same password used in Windows 2000.

To reset the password on a NetWare NDS tree

Press Ctrl+Alt+Del.

Click Change Password.

In the Log on to dialog box select NetWare or Compatible Network.

In the Old Password text box, type your current NetWare password.

In the New Password text box, type your new password (in this case, your password for Windows 2000 Professional).

In the Confirm New Password text box type your new password again.

To reset the password on a NetWare bindery server

At the Command Prompt, enter the logical drive letter of the NetWare server, and then type:

cd public

NOTE

---

To change your password on more than one server, connect to all the servers before proceeding to the next step.

Type setpass, followed by the name of the NetWare server for which you want to change your password. When prompted for each password, type your old password and then your new password (in this case, your password for Windows 2000 Professional) twice. A message confirms that you have successfully changed your password.

If prompted, type y, and then press Enter to change your password on other NetWare servers.

NOTE

---

If you are using Client Service and working from a command prompt, use the 32-bit version of the command prompt program, Cmd.exe, which is available on the Programs menu, not the 16-bit version, Command.com.

Are the File Sizes and Timestamps for Client Service and IPX/SPX Files Correct?

In some instances files do not copy correctly, or they become corrupted during the file copy process.

To determine if the file sizes and timestamps are correct

Examine the file sizes and timestamps for the files created when Client Service and NWLink are installed on the client that is having a problem.

For a list of files that are installed with Client Service see Table 24.2 earlier in this chapter.

Make sure that these files are identical to the files on a working Windows 2000 Professional-based client.

If the file sizes and timestamps are not identical, your files might be corrupted.

To correct a problem with file corruption

In the Local Area Connection Properties dialog box, select Client Service for NetWare, click Uninstall, and then click OK.

Check that all Client Service and NWLink files have been deleted. If any files remain, rename them in case you need them later. To rename the files, replace each file extension with .bak (for example, rename file Nwlnknb.sys to Nwlnknb.bak.)

Reinstall Client Service.

Login scripts set the user environment on NetWare servers and are used to access servers. You might experience the following problems when login scripts are activated through Client Service:

CX command The user receives the following error message when the NetWare login script attempts to change context using a relative path: "The context you want to change to does not exist."

Nwscript.exe parses the NetWare login script. The CX command changes the context to move the user's context one level up within the NDS hierarchy. Instead, the user receives an error message.

To correct this problem, use absolute paths in login scripts. For example, type:

cx .somecontainer

Capture command

Error 255 is reported in line 668 of Spool.c when the login script containing the following line is run:

#COMMAND /c CAPTURE /S=<servername> /Q=<queuename>

To correct this problem, replace this line with the following:

#CAPTURE /S=<servername> /Q=<queuename>

WARNING

---

Capture.exe is not a supported application and often fails when run from the command line. The login script processor does not actually run Capture.exe. Instead, it parses the #CAPTURE command and works in the background. Therefore, when you use the #CAPTURE command, you are running the actual Capture.exe application.

Troubleshooting Other Problems

In addition to NetWare and Windows 2000 Professional connectivity problems related to setup and login scripts, you might experience the following problems.

Extra page printing at beginning or end of print job

When installing Client Service you can select and enable Add Form Feed and Print Banner. Add Form Feed instructs the printer to eject a page at the end of each document that you print. Print Banner prints a banner page before each document. To disable Add Form Feed or Print Banner, in Control Panel, open Client Service for Netware, and then deselect the corresponding check box.

Client Service creates multiple licensed connections to NDS servers

If you have a NetWare NDS tree that includes more than one NetWare server, you might be using multiple licensed connections by connecting to one server for authentication and login, and then mapping connections through a login script to another server. This can cause you to use twice the number of Novell licensed connections as necessary.

For more information about how to correct this problem, see the Knowledge Base link on the Web Resources page at http://windows.microsoft.com/windows2000/reskit/webresources/ Use the keywords "connect to multiple servers," "CSNW," and "NDS."

NetBIOS over IPX packets do not propagate across routers

If an incomplete browse list is displayed for a NetWare directory, or you cannot browse a server across a WAN link, you might have a problem with propagating NetBIOS over IPX packets.

To facilitate the communication of a LAN-based protocol, such as NetBIOS, across an IPX internetwork, IPX routers must propagate NetBIOS over IPX broadcast packets (type 20 packets), also known as IPX WAN broadcast packets. However, many router manufacturers set router parameters not to pass type 20 packets by default. If your router is configured not to pass type 20 packets, contact your router manufacturer.

Windows 2000 Professional-based computers cannot connect to other Windows clients

By default, Windows for Workgroups, Windows 95, and Windows 98-based computers use client and server-side direct hosting for the IPX/SPX protocol. Direct hosting allows computers to communicate over IPX, bypassing the NetBIOS layer.

Windows 2000 supports server-side direct hosting but does not support client-side direct hosting. Therefore, although a Windows for Workgroups, Windows 95, and Windows 98-based client running only the IPX/SPX protocol can connect to a Windows 2000-based server, a Windows 2000 Professional- based client cannot connect to a Windows 2000-based server running only the IPX/SPX protocol. To resolve this problem, enable NetBIOS on computers running Windows 2000 Professional and Windows 2000 Server.

For instructions about how to enable NetBIOS on the Windows 2000-based client running on your computer, see the documentation provided with the operating system.