Although Windows 2000 supports Windows NT 4.0 BDCs, you’ll run into problems if you try to create an NT 4.0 BDC machine account. You’ll receive the error message The Machine Account for This Computer either does not exist or is inaccessible. If you try to use Srvmgr to add the computer account from an existing Windows NT 4.0-based BDC, you’ll receive the error message The Network Request is not supported.Your Win2K-based PDC will log the following error message. Source: SAM
EVENT ID: 12298
DESCRIPTION:The Account "COMPUTER$" Cannot be converted to be a domain controller account as its object class attribute in the directory is not a computer or is not derived from a computer. If this is caused by an attempt to install a pre-Windows 2000 Domain, then you should recreate the account for the domain controller with the correct object class.

To work around this problem, use Win2K’s Srvmgr tool to create the account.

Both Win.NET Server and Win2K provide an adminpak.msi Windows Installer file that contains the Microsoft Management Console (MMC) snap-ins for administering Win.NET Server and Win2K servers for deployment on a Windows XP or Win2K client machine. Although you can download the MMC framework from Microsoft's Web site for execution on Win9x clients, the adminpak.msi file won't run on Win9x systems and Microsoft has no plans to enable this support. The only option is to enable Win2K Server Terminal Services on the server and create a client session to the server.