Share via

Novell NetWare Integration Troubleshooting

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Troubleshooting

What problem are you having?

  • Client Service for NetWare does not start.

  • Client Service for NetWare starts, but no servers are found.

  • Client Service for NetWare starts, but only some resources are found.

  • Cannot use the NetWare map command to connect to file or print resources.

  • The network does not start when you start your computer.

  • A computer running the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol (NWLink) cannot connect to other computers.

Client Service for NetWare does not start.

Cause:  One of the required services or protocols might be unavailable.

Solution:  Try to start Client Service for NetWare manually. If that fails, use Event Viewer to look at the system log and troubleshoot the problem.

See also:Event Viewer

Client Service for NetWare starts, but no servers are found.

Cause:  The frame type or SAP might be configured incorrectly.

Solution:  Try the following:

  • View the network adapter load line in the Autoexec.ncf file of the NetWare server to verify that you are using the correct frame type for the server. For example, suppose a network adapter load line for a server is:

    load 3C503 FRAME=ETHERNET_802.3 NAME=ETH

    In this case, the server is bound to a 3Com 503 Ethernet adapter that accepts the raw 802.3 frame format.

    To see the frame type that is set for your network adapter, start Network Connections in Control Panel. If the frame type is detected automatically and the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol (NWLink) detects any frames of type 802.2 or no frames at all, NWLink sets the frame type to 802.2. If the network adapter receives frames of type 802.2, but your NetWare network uses a different frame type, you must set the frame type manually.

    To determine which frame type your routers are using on a server running Windows Server 2003 , at a command prompt, type:

    ipxroute config

  • If you cannot see NetWare file server resources, ensure that SAP is enabled on all the router interfaces that connect the computers running Windows and the server computers running NetWare software. (A Windows remote access server, which is a server running Windows Server 2003 and the Routing and Remote Access service, is an IPX router.) You can enable SAP on an interface by using Routing and Remote Access.

See also:  Configure NWLink

Client Service for NetWare starts, but only some resources are found.

Cause:  The tree and context or SAP might be configured incorrectly.

Solution:  Try the following:

  • In a Novell Directory Services (NDS) environment, verify that you are using the correct tree and context.

  • For each IPX router, view the SAP service table and verify that all of the services that should be learned from SAP are present. If some of the services are not present, you should verify that SAP filtering is not preventing the propagation of these services. The SAP service table is not the same as running the NetWare slist command or running an NDS query for a list of all the servers in the tree.

See also:  View routing tables

Cannot use the NetWare map command to connect to file or print resources.

Cause:  You might be using the wrong command prompt, or the default environment size of the command prompt window might be too small.

Solution:  The default environment for 16-bit programs is too small to accommodate the mapping table created by the map command. Designate the 32-bit command prompt (that is, Cmd.exe) as the permanent command interpreter, and reset the default environment size allocated to the command prompt window. An environment of 4,096 bytes is large enough to accommodate the map command, the mapping table, and the command interpreter.

To make these changes to the environment, type the following line in Config.nt:

shell=%systemroot%\system32\cmd.exe /e:4096

This line sets Cmd.exe as the command interpreter for the window as long as it remains open or until you run another shell command. The line also permanently allocates 4,096 bytes of environment space to 16-bit programs you run in the window.

The network does not start when you start your computer.

Cause:  You might have duplicate computer names.

Solution:  You must specify a computer name that is not the same as the name of another computer on the network or the same as the name of a workgroup or a domain on the network.

Cause:  Routing might be configured incorrectly.

Solution:  Try the following:

  • Verify that you have NetBIOS broadcast propagation (type 20 packets) enabled on all the router interfaces between the computers. (A Windows remote access server, which is a server running Windows Server 2003 and the Routing and Remote Access service, is an IPX router.) You can enable NetBIOS broadcast propagation in Routing and Remote Access.

  • Verify that you do not have more than eight routers between the computers running Windows.

Important

  • Client Service for NetWare is not available on 64-bit versions of Windows Server 2003 and Windows XP.

  • Gateway Service for NetWare is included in Windows 2000 Server. It is not included in the Windows Server 2003 family.

  • Computers running operating systems in the Windows Server 2003 family cannot be IPX routers.