Windows 98 Network Protocols Removed to Fix Latency

During the Windows 98 era, online gaming and dial-up or early broadband internet connections frequently suffered from high ping and packet latency caused by redundant network components. To solve this, users and competitive gamers routinely stripped down their network configurations, specifically uninstalling legacy protocols such as IPX/SPX and NetBEUI, leaving only an optimized TCP/IP stack bound to their active network adapters.

The Problem with Windows 98 Default Protocol Stacks

When a network interface card (NIC) or Dial-Up Adapter was installed in Windows 98, the operating system routinely installed and bound multiple network protocols by default. Microsoft designed the system for maximum plug-and-play compatibility across local area networks (LANs), corporate Novell NetWare environments, and the emerging World Wide Web.

However, having multiple protocols bound to a single adapter introduced significant overhead:

  • Windows 98 attempted to resolve network addresses and route packets through each installed protocol in a defined priority sequence.
  • Background broadcast traffic from local-focused protocols created contention on narrow bandwidth channels, particularly 56k dial-up modems.
  • Multiplayer games built natively for the internet (such as Quake, Half-Life, and Unreal Tournament) relied solely on TCP/IP; any secondary protocol handling incoming or outgoing frames introduced processing delays in the operating system's Winsock layer.

Protocols Commonly Uninstalled

The IPX/SPX (Internetwork Packet Exchange/Sequenced Packet Exchange) protocol was originally developed by Novell for NetWare networks and was adapted by Microsoft as NWLink. In the mid-to-late 1990s, IPX/SPX was the standard protocol for local multiplayer LAN games like Doom, Warcraft II, and Command & Conquer.

Despite its utility on local networks, leaving IPX/SPX installed on internet-facing adapters caused severe latency issues:

  • Protocol Polling Delays: If an application requested network resources without explicitly defining the protocol, Windows 98 would poll IPX/SPX alongside TCP/IP, adding milliseconds of delay to outbound network requests.
  • Binding Conflicts: When bound to a dial-up modem or broadband Ethernet adapter, IPX/SPX generated unnecessary frame packaging that interfered with smooth TCP/IP throughput.

Uninstalling IPX/SPX—or entirely unbinding it from the internet-facing adapter—was the single most common tweak recommended in competitive gaming guides to lower latency.

2. NetBEUI (NetBIOS Extended User Interface)

NetBEUI was a fast, lightweight, non-routable protocol developed by IBM and Microsoft for small local area networks. Because it was non-routable, it could not communicate over the internet.

Despite having no function on the internet, Windows 98 frequently installed NetBEUI automatically when setting up networking hardware. Because NetBEUI relied heavily on broadcast packets to locate other devices on a network segment, it introduced jitter and packet loss on low-bandwidth connections. Removing NetBEUI eliminated these background broadcasts and freed up CPU cycles on older hardware.

Additional Network Components Removed for Performance

Beyond the standalone network protocols, users optimizing for lower latency also removed or unbound two related components from their network control panel:

  • File and Printer Sharing for Microsoft Networks: When bound to an external-facing adapter, this service listened for NetBIOS traffic, generated background broadcasts, and created significant security vulnerabilities alongside packet overhead.
  • Client for Microsoft Networks: If the PC was a standalone machine not connecting to a Windows NT or SMB server domain, removing or unbinding this client from the dial-up connection stopped unnecessary authentication checks and broadcast lookups during network initialization.

The Optimal Latency Configuration

The standard remedy for high latency in Windows 98 was reducing the Network Properties dialog down to a minimalist state:

  1. Client: Windows Logon (or Family Logon to bypass network login prompts).
  2. Adapter: The specific Ethernet card or Dial-Up Adapter in use.
  3. Protocol: TCP/IP only.

By stripping the networking stack down to pure TCP/IP, the operating system handled network packets linearly without protocol translation checks, broadcast interference, or driver-level routing delays.