Filter
Top Products
5 Windows NT Driver Setup
46
Installing the Microsoft Loopback Adapter Driver
When you do a fresh installation of Windows NT 4.0, Microsoft recommends that you
install the Microsoft Loopback Adapter driver, and then verify that networking is
operating normally before installing any NICs. The Loopback Adapter driver enables
the computer to connect to local network resources that then allow alerter and
messenger services to start on a stand-alone system.
Failure to install the Loopback Adapter driver before installing a service pack can result
in a corrupted operating system. 3Com has tested and supports only Service Pack 6a.
To install the driver, do the following:
1
Start the Windows NT 4.0 fresh installation and proceed as usual.
2
In the Windows NT 4.0 Server Setup window, click
Select from List
.
3
In the list, locate and select
MS Loopback Adapte
r and click
OK
.
4
In the Windows NT Server Setup window, click
Next
.
5
Bind protocols (TCP/IP, NetBEUI, or IPX/SPX) to the Loopback adapter driver, and then
click
Next
.
6
Continue the installation as usual.
7
When prompted, click
Yes
to restart the computer.
8
Install the service pack.
9
When prompted, click
Yes
to restart the computer.
10
Install the 3Com Gigabit Ethernet NIC, its driver, and Advanced Server Features.
11
Bind protocols (TCP/IP, NetBEUI, or IPX/SPX) to the 3Com Gigabit Ethernet NIC driver.
12
When prompted, click
Yes
to restart the computer.
Performing a Fresh Installation of Windows NT on a
Backup Domain Controller
A fresh installation of Windows NT on a backup domain controller requires the following:
■
Installation of the NIC driver
■
Network connectivity
Because the NIC driver installation requires that the latest Microsoft service pack first
be installed, and because there is no way to install a service pack during a Windows
NT fresh installation on a backup domain controller, you must first set up two servers
as primary domain controllers, and then demote one of them to a backup domain
controller.
CAUTION:
If performed incorrectly, this procedure can destroy the primary
domain controller security database. Before you proceed, back up your system.
CAUTION:
Do not use this procedure if SQL or Microsoft Exchange are on
the primary domain controller that you wish to demote to a backup domain
controller. If these items are on the primary domain controller, you must reinstall
them after you finish this procedure.