Windows 98 Network Time Synchronization

During the late 1990s, Microsoft Windows 98 managed local network time synchronization quite differently from modern operating systems, lacking a native background Network Time Protocol (NTP) daemon. Instead, it relied primarily on NetBIOS-based utilities like the command-line NET TIME tool executed via logon scripts, peer-to-peer networking over Server Message Block (SMB), and third-party utility software to keep client workstations aligned with a central clock.

The NET TIME Command Line Utility

The primary native mechanism for synchronizing system clocks in Windows 98 was the NET TIME command-line utility. Inherited from MS-DOS and Windows for Workgroups, this command allowed a computer to query the time of another computer or server on the local area network (LAN) and update the local Real-Time Clock (RTC).

The syntax typically took the following form:

NET TIME \\SERVERNAME /SET /YES

The switches operated as follows:

  • \\SERVERNAME: The NetBIOS name of the target server acting as the time source (typically a Windows NT 4.0 Server or a Samba server).
  • /SET: Instructed Windows 98 to change the local system time to match the target machine.
  • /YES: Automatically confirmed the prompt, allowing the command to run silently.

Alternatively, administrators could target a workgroup or domain rather than a specific server using the /WORKGROUP:name or /DOMAIN:name parameters.

Protocol Mechanics: NetBIOS and SMB

Unlike modern Windows versions that utilize Network Time Protocol (NTP) or Simple Network Time Protocol (SNTP) over UDP port 123, Windows 98 leveraged Server Message Block (SMB) protocols operating over NetBIOS (often encapsulated in NetBEUI, IPX/SPX, or NetBIOS over TCP/IP).

When NET TIME was executed, the client established an SMB session with the designated server and requested the server's local time via an SMB remote API call. The server returned its current time, and the Windows 98 kernel updated its internal clock structure.

Automation via Logon Scripts

Because Windows 98 did not run background services in the same manner as Windows NT (lacking the Windows Time service, or W32Time, which debuted in Windows 2000), time synchronization was not continuous.

To automate the process, network administrators embedded the NET TIME command into network logon scripts configured on Windows NT domain controllers. When a user logged into the domain at startup, the batch script ran automatically, synchronizing the workstation clock once per session. For stand-alone or workgroup computers, administrators frequently placed the command in the local AUTOEXEC.BAT file or utilized the Windows Task Scheduler.

Limitations and Third-Party Solutions

Native time synchronization in Windows 98 had several notable limitations:

  • Clock Drift: System clocks on Windows 9x machines were prone to drift because time was only corrected when the batch command ran, rather than being continuously adjusted or slewed.
  • Lack of Direct Internet Time: Windows 98 could not natively query public internet NTP servers directly without connecting through an SMB host acting as an intermediary.

Due to these constraints, networks requiring high precision or continuous synchronization relied heavily on third-party SNTP/NTP clients (such as Dimension 4 or Tardis), which ran as background tray applications and polled network or internet time servers periodically via standard UDP protocols.