90s Server Tech Revisited

90s Server Tech Revisited

I built a 1990s-style network in a night: a domain, mail, files, a web server and a dial-up line. This post lists what I built and corrects three things I got wrong the first time.

The machines

  • Windows 2000 Advanced Server, as Active Directory, Exchange, file server, IIS (for the Geocities archive), SQL Server 2000 and WSUS
  • Windows 2000 Professional
  • Windows XP Home
  • Windows 98
  • Windows 3.11
  • A Linux web server running Nginx
  • A Linux dial-up server

What got done in a day

Active Directory is set up. Exchange 5.5 is installed and the hosts have email. The file server has a 50 GB drive that helped configure WSUS. IIS is installed but not fully configured, because it waits on the Geocities archive. SQL Server 2000 is present with no immediate use.

The plan for IIS is an Nginx proxy in front and a small Python and Django script that mimics a 1990s Hotmail sign-in and sign-up. It would use Active Directory and the 1990s Hotmail CSS.

Correction: who joined the domain

I first wrote that all the other servers joined the domain. That is wrong for two of them.

Windows 98 joins a domain only as a logon client. The Active Directory client add-on gives it some directory features, but it gets no computer account. Windows 3.11 for Workgroups can log on to an NT-style domain and also gets no computer account.

So Windows 98 and Windows 3.11 are not domain members in the sense that Windows 2000 and XP are. They log on. They do not join. Only the Windows 2000 and XP machines joined.

One XP machine needs a note. The earlier XP VM that I joined to the domain is a separate machine from the XP Home one in the list. XP Home cannot join a domain and XP Professional can, so the VM I joined must be Professional.

Correction: which WSUS

WSUS took a lot of work and will get its own post. Which WSUS it is matters, because the versions have different requirements.

WSUS 2.0 runs on Windows 2000 Server or on Server 2003. TechNet gives Service Pack 3 on one page and Service Pack 4 on another for the Windows 2000 case. It needs IIS 5.0 on Windows 2000, and MSDE 2000 with the MS03-031 fix. It recommends 30 GB for content, which fits the 50 GB drive I gave the file server.

WSUS 3.0 does not run on Windows 2000. So the WSUS in this build is WSUS 2.0, or its predecessor, SUS 1.0.

Windows 98 and Windows 3.11 are not WSUS clients either. Only the Windows 2000 and XP machines can take updates from it.

Exchange 5.5 and the service pack

Exchange 5.5 on Windows 2000 needs Service Pack 3 or later. If you copy this build, install the service pack before Exchange.

The rest of the stack

Windows 98 is unstable and not finished. Windows 3.11 is basic.

The Nginx server proxies the Geocities archive and other hosts scraped from the Internet Archive.

The dial-up server

The dial-up server is Ubuntu with an mgetty USB 56k modem and a Linksys PAP2T. It works and provides dial-up to the other servers. More details to come.

A PAP2T is a two-port analog telephone adapter. Modem calls over a VoIP adapter are touchy: they need the G.711 codec with fax and modem settings turned on. If you copy this part, read the Linksys documentation first.

What to take from it

Windows 2000 era software wants specific service packs, and not every old client joins a domain. Several of my first claims skipped those details. Corrected, the build holds together: a domain, mail, files, updates and a dial-up line, all on virtual machines.

Subscribe to Just another Geek

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe