How Windows 98 Managed Network Workgroups

In Microsoft Windows 98, network identification parameters—primarily the Computer Name, Workgroup, and Computer Description—were managed through a dedicated graphical interface within the Control Panel. By relying on the legacy NetBIOS naming conventions and peer-to-peer Server Message Block (SMB) networking, Windows 98 allowed local machines to organize themselves into logical administrative units without requiring a central domain controller. This article explains how users configured these settings, the naming constraints enforced by the operating system, how the values were stored internally, and the operational behavior of Workgroups on a Windows 98 local area network.

The Network Control Panel Interface

Network identification in Windows 98 was accessed by opening the Control Panel, double-clicking Network, and navigating to the Identification tab. This tab contained three text fields:

  • Computer Name: The unique identifier for the machine on the local network.
  • Workgroup: The name of the logical group of computers sharing network resources.
  • Computer Description: An optional string that provided human-readable information about the system (e.g., "Front Desk PC"), which appeared in detailed views across the network.

NetBIOS Constraints and Naming Rules

Windows 98 relied on the NetBIOS API for local network name resolution. As a result, strict naming rules were applied to both the Computer Name and the Workgroup:

  • Length Limit: Names could be a maximum of 15 characters long. (Internally, NetBIOS uses a 16-byte structure where the 16th byte is reserved as a service suffix identifying functions like the Workstation service, Messenger service, or Master Browser).
  • Character Restrictions: Names could contain alphanumeric characters and specific symbols (such as hyphens and underscores), but could not contain spaces, periods, or special characters like \, /, :, *, ?, ", <, >, or |.
  • Uniqueness: Computer names had to be strictly unique across the entire local subnet. If a machine booted up with a duplicate NetBIOS name, Windows 98 displayed a name-conflict error and disabled networking capabilities until the conflict was resolved.

Storage in the Windows Registry

When a user entered or updated their network parameters, Windows 98 committed the values to the Windows Registry. The primary keys responsible for storing these parameters included:

  • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\VNETSUP
    • ComputerName: Contained the NetBIOS computer name.
    • Workgroup: Contained the assigned Workgroup name.
    • Comment: Contained the Computer Description.

These values were read during the boot phase by the 32-bit virtual device drivers (VxDs) that powered the Windows 98 networking stack, such as VNETSUP.386. Because network drivers were tightly integrated with the system's runtime environment, any change to the Identification tab required a full system restart to take effect.

Network Neighborhood and Browse Master Elections

The Workgroup parameter directly dictated how systems discovered one another in the Network Neighborhood desktop folder. Rather than using an authoritative directory service like Active Directory, Windows 98 Workgroups operated on a decentralized Master Browser system:

  1. Elections: Machines within the same Workgroup held an automated NetBIOS broadcast election to designate a "Master Browser" (a single PC responsible for maintaining the list of available computers and shares).
  2. List Maintenance: Servers and file-sharing clients announced their presence to the Master Browser periodically via broadcast packets.
  3. Resource Browsing: When a user opened Network Neighborhood, Windows 98 queried the Master Browser for the current Workgroup's browse list, dynamically populating the view with accessible resources.