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

Troubleshooting

If you do not enter the correct information when you are configuring SNA Server Client on the computer that is running Windows 2000 Professional, you cannot connect to an IBM host. This section describes how to resolve commonly encountered connectivity-related problems when you are attempting to gain access to an IBM host.

Troubleshooting Commonly Encountered Problems

When SNA Server Client is installed on Windows 2000 Professional, it must be configured correctly in order to connect to an IBM host. Because connectivity involves resources on the IBM host, the computer that is running SNA Server, and the computer that is running SNA Server Client, resources must be set up correctly for all three for successful host connectivity.

If you are unable to connect to an IBM host, the first troubleshooting step is to verify with the SNA Server administrator that SNA Server is successfully connected to and communicating with the IBM host. When this has been confirmed, verify that your Windows 2000 Professional-based computer can connect to other network resources on the Windows 2000-based server on which SNA Server is installed. For example, determine whether you can map a network drive from the computer that is running Windows 2000 Professional to a drive on the server that is running Windows 2000 Server. If you are unable to do this, you must troubleshoot the problem as a network connectivity issue between the Windows 2000 Professional-based computer and the Windows 2000 Server-based computer. After you are able to gain access resources on the server that is running Windows 2000, you can proceed to troubleshoot the issue as an IBM host connectivity problem.

Figure 26.8 lists the troubleshooting steps to take when you are using SNA Server Client with Windows 2000 Professional. Each step that is listed in Figure 26.8 is discussed later in this section.

Figure 26.8 Troubleshooting Windows 2000 Professional and IBM Host Connectivity Problems

Is the Correct Transport Protocol Selected?

When you install SNA Server Client on Windows 2000 Professional, you are prompted to select a transport protocol. The transport protocol you select must match the transport protocol that is configured for SNA Server.

To verify the configuration of the transport protocol(s) on the computer that is running SNA Server

In either SNA Server Manager or the SNA Management console, right-click the name of the server you want to modify.

In the Server Properties page, click the Server Configuration tab.

Under Network Transports, verify which protocol (or protocols) is configured to be used on the computer that is running SNA Server.

To change the transport protocol on the computer that is running SNA Server Client

In SNA Server Client, select Client Configuration.

Select the Client Protocol tab, and then click the client/server transport protocol that matches the protocol that is configured for SNA Server.

Click OK.

When you install SNA Server Client, you have the option of selecting how SNA Server Client attempts to locate SNA Server. You can select either Client locates servers in an SNA Server subdomain or Client locates servers by name. When you are locating servers in an SNA Server subdomain, it is necessary that SNA Server Client be configured to use the same SNA Server subdomain that SNA Server is configured to use. When you are locating servers by name, you can type in either the IP address or the name of the server on which SNA Server is running.

To verify what the subdomain is configured on the SNA Server

In either SNA Server Manager or the SNA Management console, right-click the name of the server you want to modify.

In the Server Properties page, click the Server Configuration tab.

Under Subdomain, verify which subdomain is configured to be used for the computer that is running SNA Server.

To change the subdomain on the computer that is running SNA Server Client

In SNA Server Client, select Client Configuration.

Click the Client Mode tab, and then enter the name of the subdomain that is configured for SNA Server in the Subdomain text box.

Click OK.

If you select Client locates servers by name and are unable to connect to SNA Server after you enter the name of the computer that is running SNA Server, the problem might be the configuration of NetBIOS name resolution on your network. To test whether or not the issue is NetBIOS name resolution, type in the IP address of the computer that is running SNA Server. If you're able to connect to this server, the problem is that the NetBIOS name of the server is not being resolved to an IP address.

NOTE

---

For detailed information about NetBIOS name resolution methods, see "Windows Internet Name Service" in the Microsoft® Windows® 2000 Server Resource Kit TCP/IP Core Networking Guide.

Is the Correct Directory Service Selected?

When you use IPX/SPX as the transport protocol to connect through SNA Server, the correct directory service (Novell Directory Services [NDS] or Bindery Services) must be selected in SNA Server Client. The directory service is configured when the NetWare server is installed. If your NetWare server is configured as NDS-based, you must also provide a default tree and context for the configuration of SNA Server Client.

NOTE

---

For more information about NDS, Bindery Services, and the default tree and context, see the chapter "Interoperability with NetWare," in this book.

If you are unable to determine whether the server that is running NetWare is configured as NDS-based or Bindery Services-based, contact your NetWare administrator or consult your NetWare documentation.

To change the directory service on the computer that is running SNA Client

In SNA Server Client, select Client Configuration.

Click the NetWare tab.

Select the directory service (Bindery or Novell Directory Services) that corresponds to the directory service configuration on the NetWare server.

Click OK.

When you connect to an IBM host, it is possible that a locally administered address (LAA) has been associated with the IBM host resources for connection to a Windows 2000 Professional-based computer. On the IBM host side of the connection, LAAs usually are configured on either a Cluster Controlleror on the computer that is running SNA Server. Then an LAA also has to be configured on Windows 2000 Professional. When a specific Windows 2000 Professional-based computer, with its associated LAA, requests a resource on the IBM host, only the resources that are assigned to that LAA would be available. An LAA rather than a burned-in Universally Administered Address (UAA) on the network adapter is used so that neither the Cluster Controller nor the computer that is running SNA Server has to be reconfigured every time a network interface card card must be replaced on a workstation that is running Windows 2000 Professional.

The LAA is configured for Windows 2000 Professional through the Advanced tab of the network adapter.

To configure the LAA for the network adapter

Open Network and Dial-Up Connections in Control Panel.

Right-click the local area connection for the network adapter you want to configure with an LAA.

Click Properties.

Click Configure.

Click the Advanced tab.

Highlight Network Address in the Property box.

Select Value, and then enter the LAA in the Value text box.

Click OK.