Connecting Windows 95 to Novell NetWare

When Windows 95 launched, Novell NetWare dominated local area network (LAN) environments across enterprise computing. To ensure immediate adoption in corporate environments, Windows 95 featured native, 32-bit protected-mode networking components designed to connect directly to NetWare file and print servers without relying on older DOS drivers. The primary software that made this direct connection possible was the built-in Microsoft Client for NetWare Networks, later complemented by Novell’s own NetWare Client 32.

Microsoft Client for NetWare Networks

The primary built-in solution included on the Windows 95 installation CD was the Microsoft Client for NetWare Networks. Prior to Windows 95, connecting a PC to a NetWare server required loading 16-bit real-mode DOS drivers before Windows launched, consuming critical conventional memory (the first 640 KB).

Microsoft addressed this by developing a 32-bit protected-mode network redirector (NWREDIR.VXD). When paired with Microsoft's NWLink IPX/SPX-compatible transport protocol, the Client for NetWare Networks allowed Windows 95 to interface directly with NetWare 2.x, 3.x, and 4.x servers. It operated entirely in protected mode, freeing up conventional memory for DOS programs and significantly improving network throughput and system stability.

Initially, this client connected to NetWare 4.x servers using NetWare's bindery emulation mode. Microsoft later released the "Service for NetWare Directory Services" (NDS) add-on, giving users full access to NetWare 4's hierarchical tree structure directly from Windows 95.

Novell NetWare Client 32

Although Microsoft provided an out-of-the-box client, Novell developed its own official solution: NetWare Client 32 for Windows 95.

Novell designed Client 32 to replace both legacy 16-bit clients and Microsoft’s redirector. It provided deep, native support for NetWare Directory Services (NDS), complex NetWare login scripts, integrated graphical login dialogs, NetWare Application Manager (NAM), and advanced network security features. Like Microsoft’s client, Client 32 ran entirely in 32-bit protected mode, eliminating conventional memory overhead while offering superior performance and compatibility with proprietary NetWare features.

Legacy Support: Real-Mode NetWare Drivers

For legacy environments that could not transition to 32-bit networking immediately, Windows 95 also maintained backward compatibility with Novell's 16-bit real-mode drivers:

• NETX: The monolithic shell used primarily with NetWare 2.x and 3.x.
• VLM (Virtual Loadable Modules): The modular real-mode client introduced with NetWare 4.x.

While functional, these legacy clients required loading drivers via CONFIG.SYS and AUTOEXEC.BAT, which reduced available conventional memory and bypassed Windows 95's multithreaded networking architecture. Consequently, most administrators migrated to either Microsoft Client for NetWare Networks or Novell Client 32.