Any suggestions? Export (0) Print
Expand All

Best practices for Client Service for NetWare

Updated: January 21, 2005

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


Best practices for Client Service for NetWare

When running Novell Directory Services (NDS) administrative utilities on Windows, you must use NetWare client software.

  • To administer a Novell NDS server from a Windows computer using NDS utilities, you need to run the client software from Novell, not Client Service for NetWare.

When changing a user's NetWare password, synchronize the password for both NetWare and Windows resources.

  • You can use the Change Password dialog box that is available by pressing CTRL+ALT+DELETE. User names and passwords should be the same for all NetWare servers.

When connecting to NetWare resources on NDS trees, confirm that you are using the proper default tree and context.

Use the 32-bit version of command prompt.

  • If you are running Client Service for NetWare and use a command prompt, you should use the 32-bit version (that is, Cmd.exe), which is available on the Programs menu, not the 16-bit version (that is,

Follow the best practices for NWLink.

  • For more information about the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol (NWLink), see Best practices for NWLink.


  • 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.

Community Additions

© 2016 Microsoft