How Windows 98 Handled Network Neighborhood Browsing

In Microsoft Windows 98, Network Neighborhood served as the primary graphical interface for discovering, accessing, and managing shared resources across local area networks (LANs). Instead of relying on a centralized directory service like modern implementations of Active Directory, Windows 98 utilized the NetBIOS-based Computer Browser service alongside standard networking protocols to populate lists of available workgroups, computers, shared folders, and printers. This system balanced lightweight peer-to-peer sharing with domain compatibility, allowing home and office users to discover networked assets seamlessly through desktop navigation.

The Underlying Protocols

Network Neighborhood relied on the Server Message Block (SMB) protocol for file and printer sharing, coupled with NetBIOS for host identification and name resolution. Windows 98 could run NetBIOS over several transport protocols:

  • NetBIOS over TCP/IP (NetBT): The most common standard, using UDP ports 137 and 138 for name and datagram services, and TCP port 139 for session services.
  • NetBEUI: A non-routable, low-overhead protocol popular in small, single-segment local networks.
  • IPX/SPX (NWLink): Frequently utilized in mixed environments containing Novell NetWare servers.

The Computer Browser Service and Master Browsers

To prevent every individual machine from broadcasting continuous requests to every other machine on the wire, Windows 98 relied on the Computer Browser service. This architecture organized network discovery through designated roles:

  1. Master Browser: A designated system on the local subnet that collected announcements from all active hosts and compiled a master list called the Browse List.
  2. Backup Browsers: Systems that maintained copies of the Browse List downloaded from the Master Browser, distributing the query load across the network.
  3. Client Nodes: Ordinary workstations (such as typical Windows 98 setups) that queried the Master or Backup Browser whenever a user opened Network Neighborhood.

When a Windows 98 computer booted, it announced its presence via a broadcast packet. The Master Browser received this announcement and added the machine to the list. When a user opened Network Neighborhood, the Windows 98 client queried the local Master or Backup Browser rather than scanning the entire physical subnet, drastically reducing network traffic.

Browser Elections

If no Master Browser existed, or if the current Master Browser went offline, the network held an automated "election." Any machine could initiate an election using an election datagram.

Elections were resolved based on operating system hierarchy, software version, and uptime:

  • Windows NT Server and Primary Domain Controllers held the highest priority.
  • Windows NT Workstation followed.
  • Windows 98, Windows 95, and Windows for Workgroups sat at the bottom of the hierarchy.

A Windows 98 machine could become a Master Browser in a pure peer-to-peer environment without an NT server, but it would yield immediately if an NT-based system joined the broadcast domain.

User Navigation and Name Resolution

From the user perspective, double-clicking the Network Neighborhood icon on the desktop displayed:

  • Computers belonging to the user's immediate workgroup or domain.
  • An "Entire Network" icon, which grouped devices by external workgroups, NT domains, or NetWare directory structures.

To resolve machine names to network addresses, Windows 98 used a sequential resolution strategy:

  1. Local NetBIOS Cache: Checked recent name-to-address resolutions.
  2. WINS (Windows Internet Name Service): If configured, queried a centralized NetBIOS name server, allowing cross-subnet discovery.
  3. Broadcasts: Sent UDP broadcast queries over the local subnet.
  4. LMHOSTS / HOSTS Files: Looked up static mappings stored locally on the hard drive.
  5. DNS: Queried a configured DNS server as a final fallback.

Once a target computer was selected, the client authenticated using the local or domain credentials provided at Windows logon, rendering the host's shared drives, directories, and printers as standard Windows Explorer folders.