Connecting Windows 2000 to NetWare Volumes
This article explains how Microsoft Windows 2000 connects to and manages Novell NetWare volumes, highlighting the core storage and network protocols that enable cross-platform interoperability. It details the role of the NetWare Core Protocol (NCP), the necessary Windows 2000 client services, and the transport protocols required to access NetWare file systems seamlessly.
The Primary Protocol: NetWare Core Protocol (NCP)
The native protocol that allows Microsoft Windows 2000 to interact directly with NetWare storage volumes is the NetWare Core Protocol (NCP). NCP is a client-server protocol developed by Novell that handles file system requests, directory structure browsing, security authorization, and volume management. When a Windows 2000 machine reads, writes, or maps a drive to a NetWare volume, it relies on NCP to translate those file-level commands into operations the NetWare server understands.
Client Integration: CSNW and GSNW
Windows 2000 does not natively package standalone NCP file redirectors out of the box without enabling dedicated services. To utilize NCP, Windows 2000 employs one of two integrated features:
- Client Service for NetWare (CSNW): Installed on Windows 2000 Professional or Server, CSNW provides the native NCP redirector. This allows the local workstation or server to connect directly to NetWare directory trees (Novell Directory Services or NDS) and mapped volumes.
- Gateway Service for NetWare (GSNW): Available on Windows 2000 Server, GSNW acts as a bridge. It connects to the NetWare volume via NCP and then shares that storage out to native Windows clients using Microsoft’s Server Message Block (SMB/CIFS) protocol. This allows standard Windows clients without NetWare software to access NetWare storage.
Underlying Network Transport: NWLink and TCP/IP
For NCP packets to move between Windows 2000 and the NetWare server, a compatible network transport protocol is required:
- NWLink (IPX/SPX/NetBIOS Compatible Transport Protocol): Traditionally, NCP ran over Novell’s IPX/SPX stack. Microsoft included NWLink in Windows 2000 to replicate IPX/SPX, allowing legacy NetWare 3.x and 4.x volume access.
- TCP/IP (Native IP): Starting with NetWare 5.x, Novell enabled "Pure IP" (NCP over TCP/IP). Windows 2000 machines accessing modern NetWare installations can transmit NCP packets encapsulated directly inside standard TCP/IP packets using port 524, bypassing the need for IPX/SPX entirely.
By implementing the NetWare Core Protocol through CSNW or GSNW over either NWLink or TCP/IP, Windows 2000 provides full compatibility with NetWare file systems and storage volumes.