Windows 98 Default Network Protocol Setup

During a fresh setup of Microsoft Windows 98, the operating system configured a standardized set of networking components to enable local and internet connectivity. This article examines the default network protocol installed during a clean Windows 98 installation, the reasoning behind Microsoft's choice, and how it marked a shift from earlier desktop operating systems.

The Default Protocol: TCP/IP

In a clean installation of Microsoft Windows 98, TCP/IP (Transmission Control Protocol/Internet Protocol) was the default network protocol automatically installed and bound to any detected network adapter or Dial-Up Networking interface.

Whenever Windows 98 detected a Network Interface Card (NIC) during setup or via Plug and Play, it automatically installed three core components:

1. Client: Client for Microsoft Networks
2. Adapter: The specific driver for the detected hardware (or Dial-Up Adapter)
3. Protocol: TCP/IP

Shift from Windows 95

The decision to make TCP/IP the primary default represented a major transition in consumer computing. The original retail release of Windows 95 defaulted to the IPX/SPX-compatible protocol (NWLink) and NetBEUI to maintain compatibility with Novell NetWare and legacy NetBIOS local area networks.

By the release of Windows 98, the rapid expansion of the World Wide Web made TCP/IP the universal standard for networking. Windows 98 was heavily integrated with web technologies—most notably Internet Explorer 4.0 and the Active Desktop—which required TCP/IP for native functionality.

Legacy Protocol Availability

While TCP/IP was the default protocol, Windows 98 still included full support for older networking protocols. Users could manually install NetBEUI, IPX/SPX-compatible protocol, and Microsoft DLC from the Network Control Panel using the installation media, but they were no longer added automatically unless upgrading from an existing Windows installation that already used them.