Default Network Protocol in Early Windows 95

When Microsoft launched Windows 95 in August 1995, it shipped with NWLink—an IPX/SPX-compatible protocol—as the default network protocol installed whenever a local network adapter was detected. This article explains why Microsoft selected NWLink over NetBEUI and TCP/IP, how these protocols functioned within the operating system, and how the rise of the Internet quickly led to TCP/IP replacing it as the universal standard.

In the original release of Windows 95 (build 950, also known as the RTM release), Microsoft configured NWLink as the primary default protocol during automated network setup. NWLink was Microsoft's 32-bit implementation of Novell's IPX/SPX (Internetwork Packet Exchange/Sequenced Packet Exchange) protocol suite.

Microsoft chose NWLink because Novell NetWare was the dominant corporate local area network (LAN) operating system in the mid-1990s. By making an IPX/SPX-compatible stack the default, Microsoft ensured that Windows 95 PCs could connect to existing enterprise networks and NetWare servers out of the box with minimal configuration from system administrators.

The Role of NetBEUI

Alongside NWLink, NetBEUI (NetBIOS Extended User Interface) was widely used in early Windows environments. NetBEUI was Microsoft's traditional protocol for small peer-to-peer networks, carrying over from LAN Manager and Windows for Workgroups 3.11.

While NetBEUI was fast, lightweight, and required zero configuration, it suffered from a major limitation: it was non-routable. It could not traverse routers to communicate across segmented networks. Because of this architectural limitation, Microsoft prioritized NWLink for general LAN installations, although NetBEUI remained an optional protocol that users could manually install for small home or office workgroups.

Why TCP/IP Was Not Default

TCP/IP was included on the original Windows 95 installation media as a 32-bit protected-mode stack, but it was not selected as the primary default for local network cards. In 1994 and early 1995 during Windows 95's development, the commercial Internet was still in its infancy, and most private corporate networks ran on NetWare or NetBEUI rather than internal IP intranets.

Furthermore, configuring TCP/IP in 1995 frequently required manual assignment of IP addresses, subnet masks, and gateways, as DHCP (Dynamic Host Configuration Protocol) was not yet universally deployed across small networks. However, if a user configured a modem connection using Windows 95’s built-in Dial-Up Networking, the operating system would install and bind TCP/IP automatically to support connections to Internet service providers.

The Transition to TCP/IP

The networking landscape shifted rapidly immediately following Windows 95's debut. The explosive growth of the World Wide Web made TCP/IP essential for everyday computing.

Recognizing this transformation, Microsoft updated its defaults in subsequent releases. With the arrival of Windows 95 OEM Service Release 2 (OSR 2) in 1996, TCP/IP was promoted to the primary default networking protocol for all adapters, fully phasing out NWLink and NetBEUI as the preferred standards of the PC industry.