Windows 98 Novell NetWare Client Software

This article explains the built-in network client software provided with Microsoft Windows 98 to connect to Novell NetWare networks. It covers the specific software package included in the operating system, the underlying network protocols required for communication, its architectural advantages over older DOS-era solutions, and how it compared to Novell's proprietary alternative.

Microsoft Windows 98 included the Microsoft Client for NetWare Networks as its native solution for connecting to Novell NetWare environments. This software allowed Windows 98 systems to seamlessly access NetWare file and print services directly through Network Neighborhood and standard Windows Explorer interfaces.

Architecture and Protocols

The Microsoft Client for NetWare Networks operated as a 32-bit, protected-mode network component. Unlike older legacy implementations that relied on real-mode DOS drivers (such as IPX.COM or NETX.EXE) loaded via AUTOEXEC.BAT or CONFIG.SYS, the Windows 98 client ran entirely within the protected-mode subsystem. This freed up conventional memory for DOS-based applications and significantly improved system stability.

To communicate with NetWare servers, the client relied on Microsoft's NWLink IPX/SPX/NetBIOS Compatible Transport Protocol, which was also included natively in Windows 98. Once both the client and protocol were installed, users could log into NetWare servers during the initial Windows logon prompt.

Features and Capabilities

• Bindery Support: The client provided native support for NetWare 2.x, 3.x, and 4.x servers operating in bindery emulation mode.
• File and Printer Sharing: Users could map drive letters to NetWare volumes and redirect printer ports to NetWare print queues using standard 32-bit print spooling.
• Logon Scripts: It supported the execution of NetWare system and user logon scripts.

Directory Services and the Novell Alternative

While the Microsoft Client for NetWare Networks was sufficient for standard environments, it had limited support for advanced Novell Directory Services (NDS) features out of the box. To achieve native NDS tree browsing with the Microsoft client, administrators had to install an add-on called Microsoft Service for NetWare Directory Services (MSNDS).

For organizations requiring full NDS integration, NetWare/IP support, or advanced Novell utilities, Novell offered its own standalone package: the Novell Client for Windows 95/98 (often referred to as Client32). While Novell's software was the preferred choice in pure Novell enterprise shops, the Microsoft Client for NetWare Networks served as the built-in, zero-configuration solution bundled on the Windows 98 installation media.