Copyright: Installation Guide
Citation: Installation Guide


Welcome
Welcome	1 of 7

Welcome

Welcome to the Microsoft® Windows NT™ Server operating system, the multitasking operating system for client-server computing.

Windows NT Server is the high-end member of the family of Microsoft Windows™ operating systems, designed to make the most of today's computers while incorporating all the benefits of Windows - ease of use, application integration, and choice of leading applications. Windows NT Server is a powerful, reliable, and scalable operating system, ready for the demands of client-server computing and the advancing power of personal computers.

Windows NT Server provides the ideal platform to support mission-critical applications for accounting, financial analysis, customer service, databases, software development, and many more.

Windows NT Server Installation Guide is for new and experienced administrators and users of networks. This manual summarizes key networking features in Windows NT Server and presents step-by-step procedures for installing Windows NT Server and additional networking services.

This introduction provides:

A description of Windows NT Server, including its benefits

A list of what's new in this version of Windows NT Server

The Windows NT Server system requirements

A list of the conventions used in the Windows NT Server documentation set

A summary of resources available for learning about Windows NT Server


What Is Windows NT Server?
Welcome	2 of 7

What Is Windows NT Server?

Windows NT Server is designed to support complex business applications with:

Reliability. Windows NT Server provides the reliability required by management information systems (MIS) professionals and others to run line-of-business applications. The advanced microkernel design of Windows NT, along with integrated security and manageability, provides a more reliable platform than other operating systems.

Networking and workgroup support. Windows NT Server provides built-in file-sharing and print-sharing capabilities for workgroup computing, and an open network system interface that includes built-in support for IPX/SPX, TCP/IP, NetBEUI, and other transports. Windows NT Server is compatible with existing networks such as Banyan® VINES®, Novell® NetWare®, UNIX®, LAN Manager 2.x, and Microsoft Windows for Workgroups.

Interoperability. Windows NT Server also provides easy interoperability. Windows NT Server can immediately add value to your current network environment without disruption. Even though networks and interoperability are complicated, a Windows NT network is easy to use and reliable, with automatic configuration provided wherever possible and remote administration ensured for most administration tasks.

Open operating system. Windows NT Server offers flexibility in choosing computing solutions by providing integrated networking, and supports industry-standard protocols such as TCP/IP and IPX to ensure easy access to resources in a heterogeneous computing environment.

Power. Windows NT Server is a full 32-bit, preemptive multitasking operating system that enables business users to fully exploit line-of-business applications as well as the latest generations of microprocessors, including Intel® and reduced instruction set computing (RISC) systems, such as the MIPS® R4000™ and Digital Alpha AXP™, and symmetric multiprocessing systems.

A single network logon. Users can access network resources, including client-server applications, using one user account and one password per user.

Centralized management of user accounts. The administrator can work from a single computer across divisions, departments, and workgroups.

Advanced data protection features. These include disk mirroring, disk striping with parity (RAID 5), and uninterruptible power supply support.

Remote Access Service. Users can access the same resources, whether off site, traveling, or working at home. Users can dial in over asynchronous telephone lines or Integrated Services Digital Network (ISDN) lines to access the network from computers running the MS-DOS®, Windows for Workgroups, or Windows NT operating systems. RAS also supports X.25 networks.

Services for Apple® Macintosh®. This advanced feature allows Macintoshes and PCs to work together to share files, printers, and client-server applications. Macintosh users can access Windows NT Server just like any other AppleShare® server.

Support for server-based and client-server applications.

With Windows NT, you can run a host of applications on x86-based, Pentium™, and RISC-based computers, including the following:

New, powerful Win32®-based applications (32-bit Windows).

Such applications include new server applications and line-of-business applications that use server applications such as Microsoft SQL Server and Microsoft SNA Server.

Programs created for the MS-DOS and Microsoft Windows operating systems.

POSIX version 1.0-compliant programs.

On x86-based computers, you can also run OS/2® version 1.x character-based programs.

Windows NT is a complete network-independent operating system with powerful additions to support file and system security, networking capabilities, and high-end, 32-bit computing. Windows NT is designed to take full advantage of the advanced computing capabilities of x86-based and RISC-based processors to provide a platform for applications requiring sophisticated system software.

You will find these additional features in Windows NT Server:

Advanced built-in network support, including complete security features with tools for managing security and user accounts.

Administrative tools for controlling network services, auditing system events, changing hardware configuration and system performance, managing and backing up disks, and more.

The Windows NT file system (NTFS), which provides security and automatic error-correction capabilities. NTFS allows file and directory names of up to 255 characters. NTFS also offers auto-recovery in the event of system failure.

A command prompt where you can start programs and batch files, or issue all Windows NT commands and most commands for MS-DOS, OS/2 version 1.x, and POSIX version 1.0.

As a separate package, Microsoft also provides Microsoft Windows NT Workstation, the desktop edition of the Windows NT operating system for demanding mission-critical applications and for engineering, manufacturing, software development, accounting and other business computing needs. Windows NT Workstation provides the power of a workstation with the ease of use, productivity, and compatibility of a personal computer.


What’s New in Windows NT Server Version 3.5?
Welcome	3 of 7

What's New in Windows NT Server Version 3.5?

This section contains updated information for Windows NT version 3.51. Click here to see the new information.

This section describes the new features that are included in this version of Windows NT Server.

Networking and Security Management Enhancements

The ability for Windows NT computers to access NetWare file, print, and application servers via Gateway Service for NetWare. For information, see Chapter 4, "Gateway Service for NetWare."

A new version of the Microsoft implementation of the IPX/SPX protocols that are used in NetWare networks. The NWLink IPX/SPX Compatible Transport offers improved performance and new features, including multiple network support and SPX II. For information, see Chapter 3, "Networking Services Overview."

A new high-performance implementation of Microsoft TCP/IP that provides easy, powerful solutions for internetworks, including automatic configuration, powerful new name resolution capabilities, new utilities, services, and network printing support. For information, see Chapter 5, "Microsoft TCP/IP."

Easy administration of large TCP/IP networks with Dynamic Host Configuration Protocol (DHCP) service for automatic TCP/IP configuration. Windows Internet Name Service (WINS) provides dynamic mapping of network names and addresses, enabling users to operate in large scale TCP/IP networking environments with little administrative support.

Powerful additions to Remote Access Service, supporting IPX/SPX, TCP/IP, and NetBEUI using the Point-to-Point Protocol. TCP/IP is also supported using Serial Line IP standards for RAS clients. RAS servers can now support up to 256 connections. For information, see Chapter 6, "Remote Access Service."

An account lockout feature that blocks a user's access to the system after a specified number of unsuccessful logon attempts.

A Network Client Administrator utility, plus client software that can be installed on MS-DOS - based, Windows-based, and Windows for Workgroups-based computers, so that these computers can participate in a Windows NT network. For information, see Chapter 9, "Network Client Administrator," and Appendix A, "Microsoft Network Client Version 3.0 for MS-DOS."

Client-based network administration tools for Windows NT networks, so you can administer Windows NT Server from a computer running Windows 3.1 or Windows for Workgroups. For information, see Chapter 9, "Network Client Administrator."

Recovery and automatic restarting utility for troubleshooting system problems that is configured using the System option in Control Panel.

Remoteboot, for starting MS-DOS and Microsoft Windows computers over the network from a computer running Windows NT Server. For information, see Chapter 8, "Remoteboot."

Application and File System Enhancements

Support for long filenames under the FAT file system.

Ability to change fonts in Notepad, Event Viewer, Server Manager, and User Manager for Domains, plus usability improvements, such as easier scrolling with the mouse.

Full support for object linking and embedding (OLE 2.x). This includes linking, embedding, linking to embedded objects, drag and drop, in-place editing, and OLE Automation. New 32-bit Windows-based applications use this technology to provide existing new functionality.

Full support for the OpenGL™ standard for three-dimensional (3-D) graphics.

Applications created for Microsoft Windows 3.x run more reliably, because each application can now be run in its own address space.

Most command-line utilities are Unicode™-enabled.

Hardware Support

Expanded support for new hardware systems and peripherals, including support for over 2350 x86-based uniprocessor systems, over 35 x86-based multiprocessor systems, and several RISC-based systems. For a list of supported hardware, see the Hardware Compatibility List included in your Windows NT Server documentation set.

Expanded support for new graphics adapters and larger color palette sizes.

A new Control Panel option for easily configuring display resolution, font size, and refresh rate, and for installing new video display drivers. The Display option allows new settings to be previewed before committing to configuration changes.

Printing and Fonts

New plotter driver.

New PostScript® halftone extensions.

Support for Type 1 fonts.

TCP/IP printing, which allows computers on a Microsoft network to access printers connected to UNIX computers or TCP/IP printers connected directly to the network.

Setup Enhancements

Improved detection for hardware, plus the ability to select and configure network adapters if automatic detection cannot configure your settings.

Automatic upgrade from Windows NT Advanced Server 3.1, so that you can preserve security, network configuration, user accounts, and your desktop and application settings when you install this new version.

A new Windows NT-based application, WINNT32.EXE, for network setup on computers that have previous versions of Windows NT Server installed.

Automatic TCP/IP configuration for networks that implement DHCP servers.

Enhanced system repair process, and a new Repair Disk utility for updating the system configuration files saved for repair and for creating a new Emergency Repair disk.

Multimedia Drivers and Applications

This version of Windows NT includes 32-bit and 16-bit support for multimedia data types compatible with the latest releases for the Windows platform. These new features are included for multimedia in Windows NT 3.5:

Improved compatibility for 16-bit Windows 3.1 multimedia applications including new support for installable multimedia drivers and enhanced 16-bit API support

32-bit API support for Video for Windows 1.1, including Audio Compression Manager 2.0

32-bit API support for sound mixers, with support in the Volume Control application

Highest Timer Resolution now down to 1 millisecond


System Requirements
Welcome	4 of 7

System Requirements

The following table describes the system requirements for Windows NT Server.

Category	Requirement

Hardware	32-bit x86-based microprocessor (such as Intel 80386/25 or higher), Intel Pentium, or supported RISC-based microprocessor such as the MIPS R4000 and Digital Alpha AXP

VGA, or higher resolution, video display adapter

One or more hard disks, with about 90 MB minimum free hard disk space on the partition that will contain the Windows NT Server system files (110 MB free disk space required for RISC-based systems)

For x86-based computers, a high-density 3.5-inch floppy disk drive; or a high-density 5.25-inch floppy drive plus a CD-ROM drive (for computers with only a 5.25-inch drive, you can only install Windows NT over the network)

For RISC-based computers, a small computer system interface (SCSI) CD-ROM drive

One or more network adapter cards

Memory	16 MB RAM recommended minimum for x86-based systems; 16 MB minimum for RISC-based systems.

Optional components	Mouse or other pointing device

One or more SCSI CD-ROM drives (required for RISC-based computers)

Windows NT Server supports computers with up to four microprocessors. Support for additional microprocessors is available from original equipment manufacturers.


Conventions
Welcome	5 of 7

Conventions

The following conventional terms, text formats, and symbols are used throughout the printed documentation for Microsoft Windows NT.

Convention	Meaning
Bold	Indicates the actual commands, words, or characters that you type in a dialog box or at the command prompt.
Italic	Indicates a placeholder for information or parameters that you must provide. For example, if the procedure asks you to type filename, you must type the actual name of a file. Italic also indicates new terms and the titles of other books in the Microsoft Windows NT documentation set.
ALL UPPERCASE	Indicates a directory, filename, or acronym. You can use lowercase letters when you type directory names or filenames in a dialog box or at the command prompt, unless otherwise indicated for a specific application or utility.
Monospace	Represents examples of screen text or entries that you might type at the command line or in initialization files.
	Indicates a procedure.
	Indicates a procedure with only one step.
	Indicates a list of related information, not procedural steps.
Windows NT	Refers to operating system and networking functionality that is available in both Windows NT Server and Windows NT Workstation.
\WINNT or\systemroot	Refers to the Windows NT system tree. This can be \WINNT, \WINNT35, \WINDOWS, or whatever other directory name you specified when installing Windows NT.
x86	Refers to computers based on 32-bit x86-based microprocessors, such as Intel 80386 or higher, or based on Intel Pentium microprocessors.
RISC	Refers to computers built on RISC-based microprocessors such as the MIPS R4000 and Digital Alpha AXP.
	Indicates the security group membership required for the account used to log on to Windows NT in order to complete the task described.
	Indicates a special note for users of RISC-based computers.
Guidelines for mouse and keyboard actions are described in Chapter 2, "Windows NT Basics," in the Windows NT Server System Guide.


Finding Information About Windows NT Server
Welcome	6 of 7

Finding Information About Windows NT Server

This manual presents information for anyone who is installing and using Windows NT Server, including information about additional networking services that you can install.

The Windows NT Server documentation set also includes the following:

Windows NT Hardware Compatibility List

Provides a list of processors, hard drives, SCSI adapters, video adapters, pointing devices, network cards, and other hardware that have been tested to ensure compatibility with Windows NT.

Windows NT Server System Guide

Provides a description of the applications and tools provided in your Windows NT Server package. This manual presents procedures for completing common tasks such as organizing the desktop, managing files and directories, printing, using applications, administering the network, and more. A glossary at the end of the Windows NT Server System Guide defines common terms used in Windows NT.

Windows NT Server Concepts and Planning Guide

Provides information about the concepts behind Windows NT Server, such as network drivers and protocols, security, user environments, management of network files and printers, fault tolerance, and performance monitoring.

Windows NT Server Network Operations Quick Reference

Provides a summary of procedures for network management tasks using Windows NT Server.

Windows NT Server Remote Access Service

Provides background information and procedures for installing and managing Remote Access servers and clients for dial-in network access.

Windows NT Server Services for Macintosh

Provides background information and procedures for installing and using Services for Macintosh, so that PC and Apple Macintosh computers can share files and printers on the network.

Windows NT Server Services for NetWare Networks

Provides detailed information for installing and using Gateway Service for NetWare, and describes the Migration Tool for NetWare, which helps you migrate NetWare 2.x and 3.x servers to computers running Windows NT Server by transferring user and group accounts, directories, and files from NetWare to Windows NT.

Windows NT Server TCP/IP

Provides background information and procedures for using Microsoft TCP/IP as a transport protocol on the network. This includes instructions for installing and configuring Windows NT Server computers as Dynamic Host Configuration Protocol (DHCP) servers and Windows Internet Name Service (WINS) servers to support automatic configuration of Internet Protocol (IP) addresses and name resolution services, respectively, for computers on a Windows NT network.

Windows NT Server Comprehensive Index

Provides comprehensive access to topics in the Windows NT Server documentation set.

Note

Depending on your product package, these documents may be available only on the Windows NT Server compact disc.


Additional Online Information
Welcome	7 of 7

Finding Information About Windows NT Server

Additional Online Information

Other sources of information in the Windows NT Server package include:

Online demonstration

Covers the basics of Windows NT. View it by choosing the Introducing Windows NT icon in the Main program group.

Windows NT Messages database

Explains error and system information messages. This database is provided on the Windows NT Setup CD-ROM compact disc.

Online Help

Provides step-by-step instructions and reference information wherever you are working.

To get online Help

Press F1 in any window. Or, at the command prompt, type help or net help and then press ENTER.

To get an overview of online information for Windows NT

In the Main program group in Program Manager, choose the Windows NT Help icon.

Your product package also includes README text files that are copied to the \systemroot directory when you install Windows NT Server. These files contain up-to-date information about using Windows NT Server with specific hardware, printers, and networks. To see this information, choose the Read Me icon in the Main program group.


Installing Windows NT Server
Chapter 1	1 of 28

Installing Windows NT Server

This chapter describes Windows NT Setup, the program you must use to install Windows NT Server on your computer. Setup copies the appropriate files to your computer's hard disk and then configures the software you need to run applications and use the network. Topics in this chapter include the following:

What you should know before running Setup and a summary of Setup steps

How to start Setup on x86-based and RISC-based computers

Upgrading from Windows NT Advanced Server 3.1

Choosing Express or Custom Setup, and using Setup to prepare your computer for Windows NT, including creating disk partitions and formatting the partition that will contain the Windows NT files

Configuring Windows NT Server and completing Setup

Migrating settings from Microsoft Windows  and reinstalling Windows NT

Setting up the master files for network installation of Windows NT Server

If you have problems installing Windows NT Server, see SETUP.TXT on your installation disks, and see also Chapter 2, "Troubleshooting."

Caution

If you are installing Windows NT Server on a computer that will also keep a version of Windows NT Advanced Server 3.1, you must run UPDATE.EXE before running Windows NT Setup if you want to ensure that Windows NT Advanced Server 3.1 installed on your computer can still access files on your NTFS partitions and to prevent problems that can occur on FAT partitions.

You do not need to run UPDATE.EXE if you do not want to keep the older version of Windows NT Server on your computer.

If you are installing Windows NT Server on a LAN Manager server, read Chapter 4, "Upgrading a LAN Manager Server," in the Windows NT Server Upgrade Guide for LAN Manager for OS/2 for details about how to plan an upgrade.


What You Need to Know Before Running Setup
Installing Windows NT Server	2 of 28

What You Need to Know Before Running Setup

Note

This software is protected by United States copyright law. Copying is permitted only in accordance with the license agreement.

Whatever kind of computer you have, you should know the following before you start installing Windows NT Server. Ask your network administrator if you have questions. For more information on the following topics, see "Configuring Windows NT Server," later in this chapter.

The type of network adapter in your computer, the card's interrupt request (IRQ) number, base I/O address, and other settings. Windows NT Setup suggests default values for these settings. See the documentation for your network adapter card to confirm these default settings.

The computer name of your Windows NT Server computer, whether it will be a domain controller or a server, and the name of the Windows NT Server domain for which this computer will be a primary or backup domain controller. For information, see "Setting up a Primary or Backup Domain Controller," later in this chapter.

If this computer will not be a domain controller, you need to know the name of the domain or workgroup that this computer will join.

If you have a printer connected directly to your computer, the printer model and port used by the printer.

You need a high-density floppy disk of the correct size for disk drive A. This disk does not need to be formatted. Label it "Emergency Repair disk" and set it aside until Setup prompts you to insert it. For more information, see "Creating an Emergency Repair Disk," later in this chapter.

Note

If you want to preserve Windows NT Advanced Server 3.1 on the same computer where you are installing Windows NT Server 3.5, you can install the Windows NT Server 3.5 system in the same domain and use the same computername as along as this computer is not the primary domain controller. If you want to use a different computername on the same domain, the domain administrator must create another account for the new Windows NT Server 3.5 system.

If your computer already has Windows NT 3.1 installed, you can preserve your existing operating system and install Windows NT Server, provided you make certain decisions about partitioning and formatting your disk while running Setup. For information on maintaining your existing operating system, see "Preparing the Computer for Windows NT Server," later in this chapter.


Quick Start: a Summary of Windows NT Setup
Installing Windows NT Server	3 of 28

Quick Start: a Summary of Windows NT Setup

This section contains updated information for Windows NT version 3.51. Click here to see the new information.

These are the basic steps you will follow when installing Windows NT Server on your computer for the first time:

1.	Check the details in "What You Need to Know Before Running Setup," and then start Windows NT Setup.

How you start Setup depends on what kind of hardware you have and whether you are running Setup from floppy disks, a CD-ROM compact disc, or a shared network directory.

2.	Choose Custom or Express Setup. For most users, we recommend Express Setup.

3.	Specify whether this is a Windows NT upgrade or a new installation. If it is a new installation, choose the disk partition, file system, and directory for where the Windows NT Server system files will be installed on your computer.

4.	Provide identification information about your user name, computer name, and other identifiers, and specify whether this computer will have a security role in the domain.

5.	Choose the local language you want to use.

6.	For Custom Setup, choose the options you want to install. (All options are installed with Express Setup.)

7.	Set up your network adapter card and select the default network protocol.

8.	Optionally, specify the Windows NT Server domain for which this computer is primary or backup domain controller.

9.	Set up the locally installed printer, if you have one.

10.	Set up a password for the administrator's account for the local computer.

11.	For Custom Setup, set up a paging file for virtual memory and specify the installed programs on your hard disk that you want to set up to run with Windows NT Server. (These tasks are done automatically in Express Setup.)

12.	Set the local time, specify video adapter settings, and create an Emergency Repair disk.

Windows NT Setup automatically guides you through each of these steps and provides Help for any step where you need assistance before proceeding. Details about each of these steps are presented in this chapter.


Starting Setup on an x86-Based Computer
Installing Windows NT Server	4 of 28

Starting Setup on an x86-Based Computer

Important

You cannot place Windows NT Server on a drive configured with any disk compression products.

How you start Windows NT Setup for an x86-based computer depends on the source media you are using to install Windows NT Server, including:

Installing from 3.5-inch floppy disks.

Installing from a compact disc drive (for all types of supported computers that have supported CD-ROM drives).

Installing from a shared network directory.

You can also install Windows NT Server from a CD-ROM device that is supported under MS-DOS but not under Windows NT Server. Check the Hardware Compatibility List in your Windows NT Server package to see whether your CD-ROM device is supported.

If Windows NT Advanced Server 3.1 is already installed on your computer, you can also run a program called WINNT32.EXE to upgrade the operating system or install a new version, as described in "Upgrading from Windows NT Advanced Server 3.1," later in this chapter.

To install Windows NT Server from floppy disks

1.	With your computer turned off, insert the Windows NT Server Boot Disk in drive A, and then turn on your computer.

Two versions of the Setup Boot Disks are provided: one set for 5.25-inch A drives and one set for 3.5-inch A drives.

2.	When Setup asks for Setup Disk #2 and then Setup Disk #3, insert the disk in drive A.

3.	Follow the instructions on screen to complete Setup, inserting floppy disks when requested.

Note

If you start Windows NT Setup when your computer has a CD-ROM drive, Setup lets you choose whether you want to install from floppy disks or from the Windows NT Server compact disc.

If you start Windows NT Setup from a 5.25-inch drive, Setup searches for a 3.5-inch drive. If such a floppy drive cannot be found, Windows NT Setup asks you to insert the Windows NT Server compact disc. In this case, you can only run Windows NT Setup from the compact disc or from network source files, as described in "Upgrading from Windows NT Advanced Server 3.1," later in this chapter.

To install Windows NT Server from a SCSI CD-ROM drive

1.	With your computer turned off, insert the Windows NT Server Setup Boot Disk in drive A, and then turn on your computer.

2.	When Setup asks for Setup Disk #2 and then Setup Disk #3, insert the disk in drive A.

3.	When Setup asks for the Windows NT Server compact disc, insert it in the CD-ROM drive.

4.	Follow the instructions on screen to complete Setup.

If Windows NT Setup asks for Setup Disk #4, then Setup did not find the CD-ROM drive. You can continue Setup using the following procedure. For problem solving tips, see "Hardware Configuration Problems" in Chapter 2, "Troubleshooting."

Note

Before you can use the following procedure to install Windows NT Server, the network administrator must first copy the Windows NT Server master files to a shared network directory, as described in "Setting Up Master Files on a Server," later in this chapter.

To install Windows NT Server from the network, you perform the following procedure from the local x86-based computer where you want to install Windows NT Server. You can use this method to install either Windows NT Workstation or Windows NT Server. You can also use this method to install Windows NT Server on x86-based computers with SCSI or CD-ROM devices that are supported under MS-DOS but are not supported by Windows NT Server.

This method uses a program called WINNT.EXE to prepare an x86-based computer for running Windows NT Setup. This program can be used to either upgrade your existing Windows NT Server operating system or to install Windows NT Server for the first time.

To install Windows NT Server from the network or an unsupported CD-ROM device

1.	Have ready three blank, formatted, high-density floppy disks of the correct size for your computer's A drive, and have an additional disk of the same size that will be formatted during Setup.

Be sure to label the formatted disks "Setup Boot Disk," "Setup Disk #2," and "Setup Disk #3," so you can differentiate them when Windows NT Setup requests a specific disk. Label the fourth disk "Emergency Repair Disk."

2.	If you are using WINNT, use your existing MS-DOS – based network software to connect to the shared network directory that contains the Windows NT Server master files.

- Or -

If you are using WINNT or WINNT32, use File Manager to switch to the network directory that contains the master files for the new version of Windows NT Server.

- Or -

If you have an unsupported local CD-ROM device, insert the Windows NT Server compact disc in the drive, and then, while running MS-DOS, change to the CDdrive:\I386 directory on the CD-ROM drive. For example, if the CD-ROM is drive E, change to the E:\I386 directory.

3.	At the MS-DOS command prompt, type winnt and press ENTER.

- Or -

If your computer is running Windows NT Server, double-click WINNT32.EXE in the directory that contains the Windows NT Server master files.

4.	When you are asked to confirm the Windows NT Server source directory, type the path for the directory where the master files are stored (this is the same directory you switched to in step 2).

5.	When prompted, insert the blank, formatted high-density floppy disk labeled Setup Disk #3 in drive A. After some files are copied to Setup Disk #3, you will then be prompted to insert the high-density floppy disk labeled Setup Disk #2 and then the Setup Boot Disk in drive A. This process creates the three startup disks required for Setup.

After the necessary files are transferred, a message asks you to press ENTER to restart the computer.

6.	Follow the instructions on screen to complete Setup.

Make sure you keep the Setup and Emergency Repair disks that WINNT creates during installation. If you have problems with your installation, you may need these disks to repair your operating system.


Starting Setup on a RISC-Based Computer
Installing Windows NT Server	5 of 28

Starting Setup on a RISC-Based Computer

Before you can run Windows NT Setup on an ARC-compliant, RISC-based computer, you must first read the manufacturer's instructions for starting programs from CD-ROM or disk. How you start Windows NT Setup depends on the type of RISC-based computer. After Windows NT Setup starts, follow the instructions on screen.

If you already have Windows NT Advanced Server 3.1 installed on a RISC-based computer, you can also use the WINNT32.EXE program to run Windows NT Setup to upgrade your existing operating system or install a new version, as described in "Upgrading from Windows NT Advanced Server 3.1," later in this chapter. You cannot use WINNT.EXE on a RISC-based computer.

The following sample procedure for starting Windows NT Setup is typical of many (but not all) RISC-based computers:

1.	Insert the Windows NT Server compact disc in the CD-ROM drive.

2.	Restart your computer.

3.	At the ARC screen, choose Run A Program from the menu.

4.	At the prompt, type cd:\system\setupldr and press ENTER.

For some systems, you might need to supply a full device name instead of typing cd:. See your hardware documentation for details.

5.	Follow the instructions on screen.

These instructions assume that your hard disk has been initialized and has at least one partition. The system partition - the partition that has the hardware-specific files needed to load Windows NT Server - must be a FAT partition of at least 2 MB. On a RISC-based computer, the system partition is the disk partition that contains the hidden files OSLOADER.EXE and HAL.DLL in the subdirectory \OS\WINNT. If the system partition is large enough, it can also contain Windows NT Server, or you may choose to use a separate partition. If your hard disk does not include a system partition, refer to your manufacturer-supplied instructions for creating one.

If you are upgrading from Windows NT Advanced Server 3.1 on an x86-based or RISC-based computer, you can use the WINNT32 program to run Windows NT Setup, as described in the following section. You cannot use WINNT.EXE on a RISC-based computer.


Upgrading from Windows NT Advanced Server 3.1
Installing Windows NT Server	6 of 28

Upgrading from Windows NT Advanced Server 3.1

This section contains updated information for Windows NT version 3.51. Click here to see the new information.

When you start Windows NT Setup to install this new version of the Windows NT Server operating system, Setup finds any existing version of Windows NT Server or Windows NT Advanced Server 3.1 on your computer and offers you the opportunity to upgrade your existing installation.

You should first upgrade the primary domain controller (PDC) on a Windows NT Advanced Server 3.1 network to Windows NT Server 3.5 before upgrading the servers (also known as backup domain controllers or BDCs). If you upgrade a server that is not the primary domain controller first, all of the new security information installed for version 3.5 will be replaced when the server is restarted, because the server automatically replicates all information from the version 3.1 domain controller. (This problem, however, will be corrected automatically when the primary domain controller is upgraded to version 3.5.)

If you are using either WINNT or WINNT32 to upgrade from source files on a network directory, Windows NT Setup temporarily needs space on your hard disk to create the local source files for the upgrade process. The space required is about 100 MB. Windows NT Setup warns you if it cannot find sufficient free space.

If you are using the Windows NT Server compact disc or 3.5-inch floppy disks to upgrade the operating system, you need about 10 MB of free space.

Important

If Windows NT Setup warns you that it cannot proceed with the upgrade, your previous version of the Windows NT operating system will still be intact. However, it is recommended that you back up your hard disk files before running Windows NT Setup to upgrade to this new version.

Upgrading your current installation preserves the following kinds of information:

Local security accounts

Network adapter settings, protocols, and service configuration (including settings for RAS and Services for Macintosh servers)

Custom program groups, desktop settings, and other preferences set using Control Panel

Preferences set for administrative tools and accessories

Custom settings made using Registry Editor

Under the terms in your license agreement, you may be able to upgrade from Windows NT 3.1 to Windows NT Server 3.5. If you are upgrading from Windows NT 3.1, your computer cannot have a role as a domain controller in a Windows NT Server domain. If you want this computer to act as a domain controller, you need a new installation of Windows NT Server rather than an upgrade.

Note

If you upgrade from Windows NT 3.1 to Windows NT Server 3.5, Windows NT Setup will install an updated version of User Manager. After you finish the upgrade, to get the updated User Manager to appear in your program groups, you must use Windows NT Setup (in the Main program group) to delete your user profile on the computer. The next time you log on, a new profile containing program groups with the updated User Manager will be created. If you replace your Windows NT 3.1 operating system with a new installation of Windows NT Server (rather than upgrading), Windows NT Setup will install User Manager for Domains.

During the upgrade process, Setup automatically copies new files and new versions of existing files required by the system, and makes changes to system settings and program groups required for the new version. You do not have to configure network adapters, printers, and other settings as you did when you first installed Windows NT Server. The only actions you must perform during the upgrade include:

Confirming the drive and directory containing your existing Windows NT Server installation.

Providing new information for configuring Microsoft TCP/IP if this network protocol is already included in your previous Windows NT Server installation. For information about setting up a network protocol, choose the Help button in its Configuration dialog box.

Supplying a new Emergency Repair disk.

The upgrade process in Windows NT Setup is a safe operation. However, Setup may not be able to complete an upgrade if there is insufficient space on the drive containing your existing Windows NT Server installation or if other problems occur with the system.

If Setup cannot perform an upgrade, a message explains the reason so that you can quit Setup and correct the problem. After you correct the problem, start Windows NT Setup again and choose the upgrade option once more. You can retry upgrading Windows NT Server any number of times.

If Setup still cannot complete the upgrade, start Windows NT Setup again and choose to install a new version of Windows NT Server. In the rare event that you must make this choice, the new Windows NT Server installation will not preserve your custom settings or security account information.

If the Windows NT Server compact disc or network master files are available for installing Windows NT Server, you can use WINNT32.EXE to upgrade your current Windows NT installation on both x86-based and RISC-based computers.

To upgrade Windows NT Server using WINNT32

1.	While running Windows NT Advanced Server 3.1, connect to the Windows NT Server compact disc or to the shared network directory that contains the master files for the new version of Windows NT Server.

2.	In File Manager, double-click WINNT32.EXE in the directory that contains the Windows NT Server master files.

3.	In the Windows NT 3.5 Upgrade/Installation dialog box, type the path for the directory where the master files are stored (this is the same directory you switched to in step 1).

4.	Follow the instructions on screen to complete Setup.

When Windows NT Setup asks if you want to upgrade your existing installation, answer Yes, and then follow the instructions on screen.

After the necessary files are transferred, a message asks you to press Enter to restart the computer.

For complete details about setting up a shared network directory for upgrading Windows NT Server, see "Setting Up Master Files on a Server," later in this chapter.


Choosing Express vs. Custom Setup
Installing Windows NT Server	7 of 28

Choosing Express vs. Custom Setup

Early in the Setup process you must choose to use Express or Custom Setup. Express Setup is the easiest way to install Windows NT Server and is recommended for most standard installations. Express Setup asks you the minimum number of questions and installs all optional Windows NT Server components. It automatically configures your hardware settings and other components.

Custom Setup is designed for experienced users who want or need more control over how Windows NT Server is installed on their computers. With Custom Setup, you can override default values or accept recommended settings for the following:

Detection of special disk controllers. Windows NT Setup can detect SCSI adapters, CD-ROM drives, and special disk controllers for use with Windows NT. You should let Windows NT Setup detect these devices and install appropriate drivers, including those for which you have a device support disk from a manufacturer for mass storage devices. You should only skip this automatic detection when you know that detection causes Setup to fail.

The directory where the Windows NT Server files will be installed.

The video display, mouse, keyboard, and keyboard layout.

If you have a Windows NT-compatible driver from the hardware manufacturer for a video adapter card, mouse, or keyboard, follow the instructions on screen for installing from your manufacturer's disk.

The specific Windows NT Server components you want to install, and the existing applications you want to set up to run with Windows NT Server.

The virtual memory settings and local printer connections for your computer.

Any additional network adapters or other network components you want to install and configure during Windows NT Setup.

Note

Windows NT Setup allows you to choose a basic video display mode for running Setup. At the end of Setup, you have the opportunity to configure and test the actual video display mode to be used with Windows NT. For information, see Chapter 5, "Control Panel," in the Windows NT Server System Guide. To change the keyboard or mouse configuration after Setup is complete, choose the Windows NT Setup icon in Program Manager, as described in Chapter 12, "System Maintenance with Windows NT Setup," in the Windows NT Server System Guide.


Preparing the Computer for Windows NT Server
Installing Windows NT Server	8 of 28

Preparing the Computer for Windows NT Server

After you choose Express or Custom Setup, you must make some basic decisions to prepare your computer for Windows NT Server. First, you must decide whether to install Windows NT Server in the same directory with a previous version of Microsoft Windows, if present.

If you do not install Windows NT Server into an existing Windows directory, you must make decisions about the following:

The disk partition where you want to install Windows NT

The file system to be used on the Windows NT Server disk partition

The directory where the Windows NT Server system files will be stored

This section provides some guidelines and other information to help you make these choices.


Installing Windows NT Server with Microsoft Windows 3.x
Installing Windows NT Server	9 of 28

Preparing the Computer for Windows NT Server

Installing Windows NT Server with Microsoft Windows 3.x

When you install Windows NT Server, Setup checks to see whether a previous version of Microsoft Windows or Windows for Workgroups is installed on your computer.

If a version of Windows 3.x is already on your computer, you can install Windows NT Server in the same directory as the previous version of Windows. This allows Windows NT Server to configure the working environment based on the existing Windows environment and to support all the features of existing Windows 3.x-based applications. When Windows NT is installed, configuration settings are added automatically so that you can still start your computer using MS-DOS and run Windows.

If you choose to install Windows NT Server in your Windows directory, Setup skips the following steps for selecting a partition, file system, or directory.


Setting Up a Mass Storage Device
Installing Windows NT Server	10 of 28

Preparing the Computer for Windows NT Server

Setting Up a Mass Storage Device

For Express Setup, Windows NT Setup automatically checks for mass storage devices, including SCSI adapter cards, proprietary interfaces for CD-ROM drives, and special disk controllers (such as arrays) in your computer.

In Custom Setup, you can choose to bypass this detection. However, it is strongly recommended that you let Setup perform detection for mass storage devices unless you already know that detection causes Setup to fail.

Caution

If you skip this special detection and your computer uses a special controller or SCSI adapter for your hard disk, Windows NT Setup will not be able to configure your hard disk to use Windows NT.

During detection, Setup looks for mass storage devices and presents you with a list of all the devices it finds. If you accept the list of devices that Setup detects, Setup installs and configures the mass storage devices.

You can also choose to specify additional mass storage devices, for example, if you have a disk with device drivers from a hardware manufacturer.

You can choose to install additional SCSI adapters after Setup is complete by running Windows NT Setup from the Main program group in Program Manager. For information, see Chapter 12, "System Maintenance with Windows NT Setup," in the Windows NT Server System Guide.


Specifying the Disk Partitions
Installing Windows NT Server	11 of 28

Preparing the Computer for Windows NT Server

Specifying the Disk Partitions

A partition can be any size from 1 MB to the entire hard disk. The partition where you plan to store Windows NT Server files must be on a permanently attached hard disk and must have enough unused disk space to hold all the files. (For more information, see the section called "System Requirements" in the "Welcome" chapter.)

The system partition is the partition that has the hardware-specific files needed to load Windows NT Server. On an x86-based computer, the operating system starts from the active system partition on the first internal hard disk. This means that Windows NT Server looks for certain files in the root directory of the C drive (Disk 0) when you start your computer. This partition must be formatted with either the NTFS, HPFS, or FAT file system for Windows NT Server to start, and it cannot be a compressed partition. It must be formatted with the FAT file system if you want to run both Windows NT Server and MS-DOS.

A RISC-based computer can have several system partitions that are configurable by the manufacturer's configuration program, and each system partition must be formatted for the FAT file system. If you want to use NTFS, you need to create at least one FAT system partition of at least 2 MB plus a second partition large enough to contain all the files you want to protect with NTFS. For information about setting up more than one system partition on a RISC-based computer, see your hardware documentation.

Caution

If your hard disk contains stripe sets, volume sets, or mirrors, these elements appear on the Setup screen as "Windows NT Fault Tolerance." Be careful not to delete any of these elements. (For more information, see the Disk Administrator chapter in the Windows NT Server System Guide.) Also, do not delete partitions that contain data you want to keep.

The following are guidelines for making decisions about your hard disk partitions.

If you will use only the Windows NT Server operating system:

On a new x86-based computer, make a single partition and format it with NTFS, as described in the following section.

On an existing system that contains files you want to keep, maintain all existing partitions. You can place the Windows NT Server files on any partition with sufficient free space.

If you want to use another operating system such as MS-DOS in addition to Windows NT Server:

If you want to run both MS-DOS and Windows NT Server on the same computer, you must first install MS-DOS. Otherwise, installing MS-DOS later might overwrite the boot sector on the hard disk, making it impossible to start Windows NT Server without using the Emergency Repair process, as described in Chapter 2, "Troubleshooting."

Make sure the system partition (the C drive) is formatted with the appropriate file system. For example, if you already have MS-DOS installed and want to keep it, preserve the C partition and keep the file system as FAT. You can place the Windows NT Server files on any uncompressed partition with sufficient free space.

Important

You cannot install Windows NT Server on a compressed drive created with any compression utility.

Also, Windows NT Server considers space created on a FAT partition using the UNDELETE SENTRY feature in MS-DOS version 6.2 as used space.

To use NTFS and have access to another operating system, you must have at least two disk partitions. Format the C drive with a file system that Windows NT Server and your other operating system can use, such as FAT. Format the other partition with NTFS. You can place the Windows NT Server files on any uncompressed partition with sufficient free space.

If you are installing Windows NT Server on a computer currently configured to start either OS/2 or MS-DOS using the boot command, Windows NT Setup sets up your system so that you can run Windows NT Server or whichever of the two operating systems (MS-DOS or OS/2) you last started before running Windows NT Setup.

If you have OS/2 Boot Manager installed on your computer and want to continue to use it after Windows NT Server installation is complete, you need to reenable it. To do this, after Setup is complete, start Disk Administrator from the Administrative Tools group in Program Manager. Select the OS/2 Boot Manager partition, and then choose Mark Active from the Partition menu.


Selecting a File System for the Windows NT Partition
Installing Windows NT Server	12 of 28

Preparing the Computer for Windows NT Server

Selecting a File System for the Windows NT Partition

This section contains updated information for Windows NT version 3.51. Click here to see the new information.

Windows NT Server can use any one of three file systems: the Windows NT file system (NTFS), the file allocation table (FAT), or the high-performance file system (HPFS). You can set up Windows NT Server on a partition with an existing file system, or you can choose to use a new file system. You can format a partition for NTFS or FAT during Setup. Setup cannot format a partition for HPFS.

The following notes will help you choose how to format or convert the partition where the Windows NT Server files will be stored:

For an unformatted partition, you can choose to format it with either the NTFS or FAT file system. Choose the FAT option if you want to access files on that partition when running Windows NT, MS-DOS, or OS/2 on this computer. Choose the NTFS option if you want to take advantage of the features in NTFS.

For an existing partition, you probably want to choose the default option, which is to keep the current file systems intact, preserving all existing files on that partition. You can convert FAT or HPFS partitions to NTFS after running Setup.

You can choose to convert an existing partition to NTFS so you can use Windows NT security. This preserves existing files, but only Windows NT has access to files on that partition after conversion.

You can choose to reformat an existing partition to the NTFS or FAT file system, which erases all existing files on that partition. If you choose to reformat the partition as NTFS, only Windows NT will have access to files created on that partition.

Note

After running Setup, you can always change file systems on any partitions. However, to preserve data, you cannot convert an NTFS partition to any other file system without backing up all the files, reformatting the partition (which erases all files), and then restoring the files from the backup. You must also back up data before repartitioning a hard disk.

Also, if you choose to convert the file system on an existing partition to NTFS, the conversion does not take place until all of Setup is complete and you first start your computer with Windows NT Server. So if you quit Setup before it finishes running, the file system on that partition is not converted.

The following table summarizes the advantages and disadvantages of each of the three file systems that Windows NT can use.

Advantages and Disadvantages of Windows NT File Systems

Advantages		Disadvantages
Windows NT file system (NTFS):
Supports complete Windows NT security, so you can specify who is allowed various kinds of access to a file or directory.  Keeps a log of activities to restore the disk in the event of power failure or other problems. Supports file and directory names of up to 255 characters, and supports extended file attributes. Automatically generates correct MS-DOS filenames so that files can be shared with MS-DOS users. Allows a program designed to run under other operating systems such as MS-DOS access to NTFS files when it runs under Windows NT.		Recognized only by Windows NT. When the computer is running another operating system (such as MS-DOS or OS/2), that operating system cannot access files on an NTFS partition on the same computer.
File allocation table (FAT):
Allows access to files when your computer is running another operating system, such as MS-DOS or OS/2.  Is the most widely used file system for PCs.  Enables you to share data on the partition with MS-DOS. Supports long filenames under version 3.5.		Files are not protected by the security features of Windows NT. Cannot support extremely large files. Less robust than NTFS; for example, no automatic disk restore features.
High-performance file system (HPFS/HPFS386):
Ensures file compatibility if you want to switch between Windows NT and OS/2 on your hard disk. Supports long filenames.  Provides better error correction than does the FAT file system.		Has not been widely adopted. Files are not protected by the security features of Windows NT. MS-DOS and Windows 3.1-based applications cannot access files with long filenames or with long directory names in their paths.


Selecting a Directory for Windows NT Server Files
Installing Windows NT Server	13 of 28

Preparing the Computer for Windows NT Server

Selecting a Directory for Windows NT Server Files

After you specify the partition for Windows NT, Setup proposes the directory where it will install the Windows NT Server files. You can accept the directory name that Setup suggests or type the directory name you prefer. We recommend that you accept the proposed directory.

If you did not choose to upgrade an existing installation of Windows NT and Setup detects a version of Windows NT in the directory where you choose to place the new Windows NT Server files, it asks if you want to choose another directory. If so, Setup automatically configures your computer so that you can run both versions of Windows NT. If you install Windows NT Server into a directory that contains a previous installation of Windows NT Server or Windows NT Advanced Server 3.1, Setup overwrites the earlier version without preserving any custom settings or user accounts.

Important

If you want to replace an existing version of Windows NT and keep your system settings and security accounts, be sure to choose the option that Setup provides to upgrade the operating system. For more information, see "Upgrading from Windows NT Advanced Server 3.1," earlier in this chapter.


Configuring Windows NT Server
Installing Windows NT Server	14 of 28

Configuring Windows NT Server

After Setup copies several basic files, you will see the Windows NT logo for the first time, and all subsequent requests for information will appear in Windows NT dialog boxes. You can use standard Windows keyboard and mouse techniques for all actions during this part of Setup, as described in Chapter 2, "Windows NT Basics," in the Windows NT Server System Guide. You can also press F1 for context-sensitive Help.

For either Express or Custom Setup, you must next supply the following information:

A name and company name that Windows NT Server will use to identify you for various operations. You must type a response and verify your response for Setup to continue.

A Product Identification number, which your technical support representative can use to identify your system. It can be found either on the inside back cover of your Installation Guide or on your registration card. You must type a response and verify your response for Setup to continue. After Setup is complete, you can see this Product ID number by choosing the About Program Manager command from the Help menu in Program Manager. The Product ID dialog box might not appear if you are installing Windows NT Server from a network directory, depending on the requirements for your site.

Whether this computer will have a role as a domain controller in Windows NT Server domain security. A domain controller authenticates domain logons and maintains the security policy and master user database for a domain. (You will specify whether this is a primary domain controller or backup domain controller later in Setup.)

Important

Be sure to decide on the security role for this Windows NT Server computer before beginning Setup. You cannot change a server to a domain controller (or vice versa) without reinstalling Windows NT Server. For more information about domain controllers and their role in Windows NT security, see the Windows NT Server Concepts and Planning Guide.

A name that will identify your computer on the network. This name must be 15 characters or fewer and must not be the same as any other computer name, domain name, or workgroup name on the network. You can invent a computer name, or ask your network administrator if a specific name has been assigned for your computer. If you need to change the computer name after Setup is completed, choose the Network icon in Control Panel.

Do not use the following characters in computer names, because using these characters in a computer name can cause unexpected results when the computer is reached over the network:

Character		Name		Keystroke
		Bullet		ALT+0149
¤		Currency sign		ALT+0164
¦		Broken vertical bar		ALT+0166
§		Section sign		ALT+0167
¶		Paragraph sign		ALT+0182
If you are going to run logon scripts, do not use spaces in the computer names of the domain controllers in the network.

The local language, or locale, that you want to use. This setting affects, for example, the format Windows NT Server uses to display the date, time, and currency. If you want to change the language after Setup is complete, choose the International icon in Control Panel. For information, see Chapter 5, "Control Panel," in the Windows NT Server System Guide.

For Custom Setup, a dialog box asks you to select optional tasks to be performed, including installing optional components such as accessories and games, configuring network settings, setting up locally connected printers, and setting up applications on your hard disk to run with Windows NT Server. For information about completing this dialog box, choose the Help button.


Setting Up a Network Adapter Card
Installing Windows NT Server	15 of 28

Configuring Windows NT Server

Setting Up a Network Adapter Card

For Express Setup, Windows NT Setup automatically checks for a network adapter card in your computer and installs the first one it recognizes. Some types of network cards may not be recognized by Setup. If Express Setup cannot identify your adapter card, it asks if you want to install Microsoft Remote Access Services (for users connecting to a network over telephone lines). If you do not choose this option, Setup displays the Network Adapter Setup dialog box and asks you to select the name of the card you want to install.

Note

If this computer will not be a domain controller and you do not want to install network software, choose Cancel in the dialog box, and continue with the rest of the Setup tasks. For a domain controller, you must install the network.

Express Setup installs only one network adapter card. If you have additional adapter cards, you can install them after running Setup by choosing the Network icon in Control Panel. For information, see Chapter 5, "Control Panel," in the Windows NT Server System Guide.

Custom Setup uses the following steps to install a network adapter card:

1.	Setup asks if you want it to detect the network card in your computer.

If you choose detection, Setup continues as described in step 2. If you reject detection, Setup displays the Network Adapter Setup dialog box and asks you to select an adapter card name from a list.

2.	If you choose detection, Setup looks for a network adapter card. It stops at the first one it identifies and asks you to select one of three options:

You can accept the identified network card, in which case Setup installs the supporting network software for you.

You can choose Find Next, which causes Setup to search for another network adapter card.

You can choose Do Not Detect, which causes Setup to stop detection and display the Network Adapter Setup dialog box.

If Custom Setup cannot identify an adapter card to install or if you do not choose any of the detected cards, Setup informs you that there are no more network cards and asks you to choose Detect to try again. Or, if you choose Continue, you have the option of installing Microsoft Remote Access Services or of manually selecting an adapter card.

3.	If you accept the card that Setup detects, Setup installs and configures it and then displays a dialog box with the adapter card settings, as described in the following section.

4.	If Setup cannot completely validate adapter card settings or if potential hardware conflicts exist, Setup warns you and allows you to change the settings.

Both Express and Custom Setup detect only one network adapter card.

Configuring the Network Adapter Card and Other Options

After Setup installs a network adapter card, it may display an Adapter Card Setup dialog box, so you can select the correct interrupt request (IRQ) number, I/O base port address, memory buffer address, and other settings. For many adapter cards, the settings are configured automatically so you don't have to identify settings. We recommend that you accept the proposed settings unless you are absolutely sure they are incorrect.

Note

If you are upgrading from Windows NT Advanced Server 3.1, the Adapter Card Setup dialog box will not appear, because your old configuration settings are still correct. However, if you previously installed TCP/IP for Windows NT Advanced Server 3.1, Setup requests new TCP/IP information. For information, choose the Help button; see also Chapter 5, "Microsoft TCP/IP."

If you are an experienced user and know that you need to change adapter card settings, see the documentation for your network adapter card, or ask your network administrator for the correct values. To see a list of the default settings for each type of adapter card, see "Network Problems" in Chapter 2, "Troubleshooting."

For Custom Setup, the Network Settings dialog box appears after you configure the first card so you can install additional network cards and supporting software. If you choose to install additional network components, you might be asked to insert additional disks supplied by the component manufacturer. For information about completing the options in the Network Settings dialog box, choose the Help button. See also, "Configuring the Network" in Chapter 5, "Control Panel" in the Windows NT Server System Guide.

If Setup cannot start the network after network adapter card settings are determined, you will have a chance to go back and select different network configuration settings, or you can choose to skip network setup and set the configuration after Windows NT Setup is finished.

Selecting Network Protocols

Whether you choose Express or Custom Setup, Windows NT Setup asks you to select one or more network protocols to install. The primary network protocols you can choose are the following:

NWLink IPX/SPX Compatible Transport, which is selected by default. For many sites, this is the standard network protocol. It supports routing, and it can support NetWare client-server applications, where NetWare-aware Sockets-based applications communicate with IPX/SPX Sockets-based applications. Choose this option if your computer is connected to or communicates with a NetWare network.

TCP/IP Protocol, which is a suite of networking protocols that provide communication across interconnected networks. Choose this option if your computer is on an interconnected network with diverse hardware and operating systems, or if you want to communicate with non-Microsoft systems such as UNIX.

NetBEUI, which is usually used in small department-size local-area networks of 1 to 200 clients. It can use token ring source routing as its only method of routing. Choose this option if your network uses NetBEUI as a transport protocol. (NetBEUI is installed automatically if you install Remote Access Service and do not configure a network adapter card.)

Caution

You must select NetBEUI if your computer communicates with other computers on an existing Microsoft network that uses NetBEUI for Windows NT 3.1, Windows for Workgroups 3.11, or LAN Manager 2.x.

If you do not install NetBEUI and your network requires it, your computer will not be able to communicate with other computers on your network.

If you are unsure about which network protocol to choose, accept the default (IPX/SPX), or ask your network administrator. After Setup, you can use the Network option in Control Panel to add or remove any transports for your system.

For more information about these network protocols, see Chapter 3, "Networking Services Overview."


Setting Up a Primary or Backup Domain Controller
Installing Windows NT Server	16 of 28

Configuring Windows NT Server

Setting Up a Primary or Backup Domain Controller

After you enter your choices for the network configuration settings, Setup displays a dialog box so that you can identify the domain for this computer to serve as a backup domain controller, or create a new domain for which this computer will be the primary domain controller.

Important

Creating a domain has important security consequences that you should understand before proceeding. Before you create a domain, be sure to read Chapter 3, "How Network Security Works," in the Windows NT Server Concepts and Planning Guide.

If you are setting up a primary domain controller, Windows NT Setup also asks you to specify a password for the Administrator account. This enables you or someone you designate to log on to the computer with maximum access. The Administrator password is an important piece of information. Write this password down and store it in a safe place. You do not have to supply this password if you are setting up a backup domain controller.

If you lose the Administrator account password for your computer, there is no way to recover it. If no other Administrative accounts have been created, you will have to reinstall Windows NT Server and set a new password to log on as Administrator.

To create a domain

1.	If you want to create a new domain, in the Domain Settings dialog box, select the Controller In New Domain option.

Caution

After Setup is finished, the only way a Windows NT Server computer can join a different domain is if you reinstall Windows NT Server. You can, however, choose the Network option in Control Panel to define a new, unused domain name for a primary domain controller. For information, see the online Help for the Network Settings dialog box after Setup is finished.

2.	In the appropriate box, type the correct domain name. Domain names cannot contain spaces (blank characters).

3.	Choose the OK button.

To join a domain as a backup domain controller

1.	Select the Backup Domain Controller option.

2.	In the appropriate box, type the correct domain name. Domain names cannot contain spaces (blank characters).

3.	Choose the OK button if a computer account already exists for this computer.

If a computer account does not exist, you must enter the name and password of an administrative account to be used to authorize the creation of a new account. For example, in the appropriate box, type the name and password for the Domain Administrator account, and then choose the OK button.

If the administrative account originates in a trusted domain, type the name of that domain followed by the account name. For example, type Shipping\Chrisdr, where Chrisdr has administrative authority in this domain but belongs to the trusted domain Shipping.

Windows NT Setup asks you to specify a password for the special Administrator user account. Then, if this computer is not joining a domain, Setup asks you to specify the user name and password for a local account. This information will be requested each time you log on this computer. The user name can be up to 20 characters and can contain any uppercase or lowercase characters except the following:

"    /    \    [    ]    :    ;    |    =    ,    +    *    ?    <    >

A password can contain up to 14 characters and is case-sensitive, which means that Windows NT Server identifies the password 7PassWd as different from 7passwd.


Setting Up a Local Printer
Installing Windows NT Server	17 of 28

Configuring Windows NT Server

Setting Up a Local Printer

For both Express and Custom Setup, you can set up a printer that is connected directly to your computer. For information about setting up a printer, choose the Help button and follow the instructions.

If you don't have a printer connected to your computer, choose Cancel when the Printer Setup dialog box appears. After you install Windows NT Server, you can choose the Print Manager icon in Program Manager to set up network printers or change the printer configuration. For information about configuring and using printers, see Chapter 6, "Print Manager," in the Windows NT Server System Guide.


Setting Up Virtual Memory
Installing Windows NT Server	18 of 28

Configuring Windows NT Server

Setting Up Virtual Memory

This section contains updated information for Windows NT version 3.51. Click here to see the new information.

Windows NT Server creates a special file on your hard disk called a paging file. The paging file makes it seem as if your computer has more memory to run programs, because Windows NT Server can temporarily swap the contents of memory used by one program to the hard disk so that another program can use that memory.

For Express Setup, all virtual-memory settings are configured automatically. For Custom Setup, you can change the size of the virtual-memory paging file or the drive where the file is stored. We recommend that you accept the proposed settings unless you are an experienced Windows NT Server user. If you want to change the location or size of this file or create other paging files after Setup is complete, choose the System icon in Control Panel. For more information, see "Defining Options for the Operating System" in Chapter 5, "Control Panel," in the Windows NT Server System Guide.


Setting Up Applications to Run from Program Manager
Installing Windows NT Server	19 of 28

Configuring Windows NT Server

Setting Up Applications to Run from Program Manager

The easiest way to run programs in Windows NT Server is to choose program-item icons in Program Manager. The easiest way to create the program-item icons is to have Windows NT Setup create them for you.

If you are installing Windows NT Server in a directory containing a version of Windows 3.x, Setup automatically installs your existing Windows groups, and you do not have to make choices during this part of Setup. However, Setup does not migrate groups that have the same names as those created by Windows NT Setup, such as Main, Accessories, and others. For information, see "Migrating Windows 3.x Settings," later in this chapter.


Setting the Time and Configuring Video Display
Installing Windows NT Server	20 of 28

Configuring Windows NT Server

Setting the Time and Configuring Video Display

Windows NT Setup asks you to make choices about time settings and to specify the local time.

After you set the time and choose the OK button, the Display utility appears so that you can configure your video display. For information, see online Help and see also Chapter 5, "Control Panel," in the Windows NT Server System Guide. If you want to make changes to your video configuration after running Setup, use the Display option in Control Panel.


Completing Setup and Starting Windows NT Server
Installing Windows NT Server	21 of 28

Completing Setup and Starting Windows NT Server

Windows NT Setup asks you to create an Emergency Repair disk, and then you are ready to complete Setup and start Windows NT Server.


Creating an Emergency Repair Disk
Installing Windows NT Server	22 of 28

Completing Setup and Starting Windows NT Server

Creating an Emergency Repair Disk

Windows NT Setup gives you the opportunity to insert a blank, high-density disk in drive A to create an Emergency Repair disk. This Emergency Repair disk can be used to restore your system to its initial setup state if files become corrupt.

Repair information is saved on your hard disk even if you do not create an Emergency Repair disk.

For information about using the Emergency Repair disk to restore damaged or corrupt files and for creating an Emergency Repair disk after Setup is complete, see "System Diagnosis, Recovery, and Repair" in Chapter 2, "Troubleshooting."

Note

You may experience difficulty creating the Emergency Repair disk if your A drive is a 2.88 MB drive and your disk is formatted as 2.88 MB. If you experience problems, supply a disk formatted for 1.44 MB.


Completing Setup
Installing Windows NT Server	23 of 28

Completing Setup and Starting Windows NT Server

Completing Setup

After you follow the instructions to create the Emergency Repair disk, Setup completes the final installation steps.

To complete Setup and start Windows NT Server

1.	If this computer is a backup domain controller, Setup replicates security account information from the primary domain controller. This activity takes several minutes, depending on the size of the security database.

If you choose Cancel in the message that announces database replication, the system will instead replicate the database as soon as you restart this computer.

2.	When Setup is finished running and the message asks you to restart your computer, remove any disks from the floppy disk drives and choose the Reboot button.

3.	When the boot loader menu appears, press ENTER.

4.	When the Welcome logon message appears, press CTRL+ALT+DEL to log on.

5.	In the Welcome dialog box, type and confirm your password, and then choose the OK button.

Passwords are case-sensitive, which means that Windows NT Server identifies mypassword and MyPassWord as two different entries.

Caution

For an x86-based computer, the following files are copied to the root directory on the C drive:  BOOT.INI, BOOTSECT.DOS (if another operating system is on your computer), NTLDR, and NTDETECT.COM. Also, if you have a SCSI disk that is not visible from MS-DOS (that is, not seen by the BIOS), the NTBOOTDD.SYS file is copied. These files should never be deleted because Windows NT Server will not start without them.

For a RISC-based computer, HAL.DLL and OSLOADER.EXE are copied to the \OS\WINNT directory on your system partition. These files should never be deleted.

Notice that these files are all read-only, hidden system files. If any of these files is missing on your system, you can use the Emergency Repair disk to restore them.


Migrating Windows 3.x Settings
Installing Windows NT Server	24 of 28

Migrating Windows 3.x Settings

If you installed Windows NT Server into an existing Windows 3.x directory (including Windows for Workgroups), you have the opportunity to migrate a portion of your Windows 3.x settings when you first log on as a new user (this option is not available for the Administrator user name). If you choose to preserve Windows 3.x system and program settings, Windows NT Server migrates the following:

All program groups that do not already exist in Windows NT Server. For example, a program group named Spreadsheets would migrate while the Main program group would not.

File associations.

Settings for your Windows-based applications.

Information used for object linking and embedding.

Desktop configuration settings, with the exception of screen savers.

The location of each program group icon and each group window when the icon is opened remain the same as in Windows 3.x, unless the display resolutions differ between Windows NT Server and Windows 3.x.

Shared directories from Windows for Workgroups on the local computer and connections to other shared resources are not preserved in Windows NT Server.

When migrating from Windows 3.x to Windows NT Server, you may get Question Mark icons for your group items if you use a 64K color video driver in Windows 3.0, Windows 3.1, or Windows for Workgroups 3.1x. You can change to the correct icon for each selected program item by choosing Properties from the File menu in Program Manager and then changing the icon in the Properties dialog box.


Reinstalling Windows NT Server
Installing Windows NT Server	25 of 28

Reinstalling Windows NT Server

In most cases, you should choose the option to upgrade your existing installation when you run Windows NT Setup, instead of reinstalling the operating system. When this is not possible, reinstalling Windows NT Server is identical to first-time installation unless you are reinstalling on a computer that belongs to a domain or on a domain controller. In these cases, additional steps are required to maintain security settings.

Before reinstalling Windows NT Server on a computer that belongs to a domain, the domain administrator must delete the computer account for the computer and create a new one. For security reasons, the Windows NT Net Logon service periodically changes the passwords of computer accounts (passwords change on the domain controller and on the computer simultaneously so that they always match). If you reinstall Windows NT Server without creating a new computer account, passwords on the computer and domain controller will conflict and prevent you from logging on to the domain from that computer.

The second case, reinstalling Windows NT Server on a domain controller, requires extra steps to ensure preservation of the user accounts database.

To reinstall Windows NT Server on a domain controller

1.	Use Server Manager to temporarily promote another Window NT Server domain controller to be the primary domain controller.

This step automatically demotes the original primary domain controller to backup domain controller status.

2.	Reinstall Windows NT Server on the original primary domain controller, making it a backup domain controller.

As soon as you restart the computer, the security database on the new primary domain controller begins to replicate to this backup domain controller. This may take a few minutes, depending on the type of computer hardware and the number of user accounts.

3.	Use Server Manager to promote this computer back to primary domain controller.


Setting Up Master Files on a Server
Installing Windows NT Server	26 of 28

Setting Up Master Files on a Server

This section is written for the administrator responsible for installing Windows NT Server on multiple computers. This section assumes that you have already installed Windows NT Server on a single computer and are familiar with Windows NT commands and procedures.

You can install Windows NT Server on multiple computers by first copying the Windows NT Server master source files to a shared directory on a network computer, as described in this section. Then use WINNT.EXE (for x86-based computers only) or WINNT32.EXE to install or upgrade Windows NT Server on each computer, as described earlier in this chapter.

You can use this method to install Windows NT Workstation or Windows NT Server. You can also use this method to install Windows NT Server on x86-based computers with SCSI or CD-ROM devices that are supported under MS-DOS but are not supported by Windows NT Server. On RISC-based computers, you can use WINNT32 only to upgrade or reinstall the operating system when Windows NT is already installed.

Important

Every Windows NT Server user must have a Windows NT Server license, which is obtained by buying a retail package or a Microsoft License Pack. For more information on restrictions, see your Windows NT Server license agreement.

When you copy the Windows NT Server master files, you can set up the shared directory using any type of network, such as Microsoft LAN Manager 2.1, Novell NetWare, Banyan VINES, or others. The directory containing the Windows NT Server files must be accessible from MS-DOS to all users who will be using WINNT.EXE.

Before you can copy the master Windows NT Server files onto a network directory:

The network must be operational.

You must have read-write permission to the network directory where you want to copy the Windows NT Server files, and other users must have read access to that directory. For more information, see your network software documentation.

To copy the master Windows NT Server files onto a network computer

Share the \I386, \MIPS, and \ALPHA directories of the Windows NT Server compact disc in the CD-ROM drive connected to a network computer.

- Or -

1.	Connect to the drive where you want to install the Windows NT Server master files.

2.	Create the shared directory on the drive that will contain the Windows NT Server master files.

3.	In Program Manager, choose the Command Prompt icon, and then use the xcopy command to copy the Windows NT Server files to the shared directory you created. The correct syntax is the following:

xcopy /s <cdrom>:\<platform> <share_directory>

For example: xcopy /s f:\i386  \\winnt35.src\x86

The Setup program copies the files to the specified destination. Users can now connect to this shared directory to follow the procedures for installing Windows NT Server from the network, as described in "Starting Setup on an x86-Based Computer" and "Upgrading from Windows NT Advanced Server 3.1," earlier in this chapter.


Customizing Protocol Setup
Installing Windows NT Server	27 of 28

Setting Up Master Files on a Server

Customizing Protocol Setup

The network administrator can also customize network installation to specify which transports to install and whether to present the Protocol Setup dialog box to the user. To do this, create an XPORTS.INF file and place it in the shared directory containing the Windows NT Server master files. The XPORTS.INF file should contain entries similar to the following, where 1=true and 0=false:

[DefaultProtocols]
Set !InstallNWLink = 1
Set !InstallTCPIP = 0
Set !InstallNetBEUI = 0
Set !PromptUserForProtocols = 1

A sample XPORTS.INF file is included with the Windows NT Server system files.


Customizing Product ID Specification for Network Setup
Installing Windows NT Server	28 of 28

Setting Up Master Files on a Server

Customizing Product ID Specification for Network Setup

When a user installs from the Windows NT Server floppy disks or compact disc, Windows NT Setup asks the user to enter the Product ID. The network administrator should provide this information by default by changing a value in the INITIAL.INF file in the Windows NT Server master files.

To specify the Product ID in sources files for network installation

Edit the following line of INITIAL.INF to specify the Product ID for your site license:

ProductID=<################>

For example, you might change this value to productID=942347978924567 if that is your Product ID number.

However, if you want the Product ID dialog box to appear during network setup so that each user can enter a value for the Product ID, then make sure that DisplayPidDlg="Yes" in the INITIAL.INF file.


Alternatives to Using 5.25 Inch Setup Floppy Disks

Detecting and Correcting the Floating-Point Division Error


Performing a Setup Without Using Floppy Disks

Using a Windows NT Advanced Server 3.1 PDC with a Windows NT Server 3.51 BDC


Troubleshooting
Chapter 2	1 of 32

Troubleshooting

This chapter provides information to help you troubleshoot various problems that can arise while installing, starting, and running Windows NT Server. The chapter discusses problems in these areas:

Hardware configuration

Installation

Starting Windows NT Server or an alternate operating system

Logging on to Windows NT Server and changing the password

System diagnosis, recovery, and repair

Miscellaneous issues, such as removing an NTFS partition

For troubleshooting Microsoft TCP/IP, see Windows NT Server TCP/IP. For troubleshooting the Gateway Service for NetWare, see Windows NT Server Services for NetWare Networks. For troubleshooting for RAS, see Windows NT Server Remote Access Service. For troubleshooting for Services for Macintosh, see Windows NT Server Services for Macintosh.

For additional information, choose the Read Me icon in the Main program group.


Hardware Configuration Problems
Troubleshooting	2 of 32

Hardware Configuration Problems

The following sections discuss common hardware problems that can prevent Windows NT Server from installing, starting, or operating properly. See also "Network Problems," later in this chapter.


General Hardware Problems
Troubleshooting	3 of 32

Hardware Configuration Problems

General Hardware Problems

Windows NT Server offers a wide range of hardware support-including support for over 2300 x86 uniprocessor systems, over 35 x86-based multiprocessor systems, as well as supporting several RISC-based systems (for details, see the Hardware Compatibility List). The following notes can help you with problems you might encounter.

Note

For information about issues with specific hardware, including specific computer types, video displays, SCSI devices, pointing devices, tape drives, sound cards, printers, and network adapter cards, see the README.WRI, NETWORK.WRI, and PRINTER.WRI files in your \systemroot directory.

Interrupt Conflicts

Devices cannot share interrupt request (IRQ) settings, memory buffer addresses, or ROM addresses. A common problem in a computer with several supported devices is conflicting interrupts, I/O ports, or memory usage. Where possible, Windows NT Server identifies conflicts. However, if one of the supported devices does not seem to work, the problem may be the particular hardware configuration. Make sure there are no conflicts among network adapters or other peripherals, or between the system board and adapters. Sometimes these settings are set with software, sometimes with jumpers or switches on the hardware (refer to your hardware documentation for specific details).

If settings for a network card can be configured through software, you can configure settings while installing Windows NT Server or later, by using the Network icon in Control Panel. For more information, see "Network Adapter Card Settings," later in this chapter.

System Error F002

If you receive System Error F002, this probably means that your hardware is faulty; for example, you may be experiencing a memory failure. If this occurs, run the manufacturer's diagnostics procedure and check to see if your memory is the proper speed for your CPU.

Using More Than 16 MB RAM with ISA Computers

When accessing memory above 16 MB, Windows NT Virtual Direct Memory Access (DMA) uses a technique called double buffering to compensate for the limitations inherent in the 24-bit DMA hardware used by 16-bit Industry-Standard Architecture (ISA) bus PCs. Double buffering usually provides performance that is within a few percent of 32-bit hardware DMA used with 32-bit bus architectures such as Extended Industry-Standard Architecture (EISA) or Micro Channel® Architecture (MCA). In general, Windows NT Server will continue to take full advantage of additional RAM in PCs with ISA, EISA, MCA, and other 32-bit bus architectures up to a maximum of 4 GB.

A few ISA-based PCs have unusually poor hardware secondary cache schemes. On these computers, increasing memory beyond 16 MB will actually degrade, rather than improve, performance. This problem is a hardware limitation of these particular computers and is not specific to Windows NT Server.

Unsupported Peripherals

Some computer systems listed on the Hardware Compatibility List may ship with peripherals not yet supported by Windows NT Server, such as FAX/modems or non-SCSI CD-ROM drives. In these cases, only the base computer configuration has passed compatibility testing.

Contact your hardware manufacturer to find out whether new drivers are available for these peripherals.

IDE/ESDI Drive Support

The Windows NT IDE/ESDI drive support is limited to two disk drives per controller. Windows NT Server supports a second Integrated Device Electronics/Enhanced Small Device Interface (IDE/ESDI) controller added to COMPAQ® computers only or built in like the Gateway 2000 VESA local bus computers. If you need to configure from two to six IDE or ESDI controllers in one system, contact you technical support representative for details on how to do so.


SCSI Drives
Troubleshooting	4 of 32

Hardware Configuration Problems

SCSI Drives

Windows NT Server supports a large number of SCSI host adapters, CD-ROM drives, tape drives, removable media systems, and scanners.

Note

For a list of issues related to specific SCSI devices, see the README.WRI file in your \systemroot directory.

The SCSI and CD-ROM support built into Windows NT Server requires that CD-ROMs provide SCSI parity to function properly. For many drives this is a configurable option or is active by default. To find specifics on how SCSI parity is configured for your drive, see the documentation for your CD-ROM. Examples of drives that do not provide or support SCSI parity are the NEC® CDR-36 and CDR-37 drives.

If you have trouble with a SCSI drive, make sure the SCSI bus is set up properly (refer to your hardware documentation for specific details):

The ends of the SCSI bus must have terminating resistor packs (also called terminators) installed. If you have only internal or only external SCSI devices, the ends of the bus are probably the SCSI adapter and the last device on the cable. If you have both internal and external SCSI devices, the adapter probably is in the middle of the bus and should not have terminators installed.

If you disconnect a device that has terminators installed (such as an external CD-ROM drive), be sure to install terminators on whatever device then becomes the last one on the bus.

One of the devices on the SCSI bus - usually the adapter - should be configured to provide termination power to the bus. For more information, see "Terminating the SCSI Bus," later in this section.

If you have a SCSI hard disk drive that uses removable media, such as a cartridge drive, make sure that media is mounted on the drive before running Setup. If no media is on the drive, errors may occur during Setup that prevent installation of Windows NT Server.

In some cases, adding or removing a SCSI adapter may prevent your system from starting correctly. This section provides information on configuring SCSI devices when running Windows NT Server.

Installing from a SCSI CD-ROM Device

If you have two CD-ROM devices connected to the same SCSI host adapter, Windows NT Setup does not necessarily use the CD-ROM drive that contains the higher SCSI ID. If using one CD-ROM drive results in Setup displaying the message "Please insert the CD-ROM into the CD-ROM drive," remove the CD and try the other CD-ROM drive. Setup chooses one CD-ROM drive and refers to it as the primary CD-ROM drive.

Adding a CD-ROM Drive After Installing Windows NT Server

If you add a CD-ROM drive after you have installed Windows NT Server, use the Devices option in Control Panel to configure device startup. For all CD-ROM drives, set the Startup value of Scsicdrm to System. If your drive does not support SCSI-2 Audio, also set the Startup value of Cdaudio to System. Cdaudio should also be set to System for some SCSI-1 CD-ROM drives, including the Denon® DRD-253; Pioneer®-DRM-600; NEC Intersect 73, 73m, 74, 84; and Hitachi® 1750s, 1650s, 3650.

For more information on starting devices, choose the Help button in the Devices dialog box.

Terminating the SCSI Bus

The SCSI bus must be properly terminated on both ends. If you are using both an external and an internal SCSI device, it is best to terminate the devices and remove the terminators on the SCSI adapter.

For the SCSI adapter to operate effectively, termination power must be provided on the SCSI bus either by the adapter or by a SCSI device connected to the bus. Some adapters provide termination power with no configuration options. Others do not provide termination power (for example, Future Domain 1660 and Trantor 128 and 130B). Still others provide termination power only if a jumper is set on the adapter (for example, Future Domain 850M).

Please consult the documentation for your SCSI adapter and SCSI device to make sure that termination power is present on the SCSI bus.


Video Display Drivers and Adapter Cards
Troubleshooting	5 of 32

Hardware Configuration Problems

Video Display Drivers and Adapter Cards

The information is this section applies only to x86-based computers. Windows NT Server supports over 45 video display adapters, including the VGA standard video cards plus some newer video cards with excellent high-end support. For a list of issues related to specific video display types, see the README.WRI file in your \systemroot directory. For information about using the Display option in Control Panel to configure your video display, see Chapter 5, "Control Panel," in the Windows NT Server System Guide.

Caution

You should be careful when installing some of the higher resolution modes to be sure that your monitor supports the resolution and vertical refresh rates. Use the Display option in Control Panel to test display modes before accepting and installing any particular configuration.

Testing the Configuration

Caution

If you install a new video card without using the Display option in Control Panel to configure it, your computer may not restart correctly. In such a case, you can either install the original card (if it is available) and revise the configuration using the Display option, or select the VGA boot option on the Boot Loader startup screen. If you use the latter method, you must manually disable the video driver that was running.

When you change your display settings, you should always use the Test button in the Display dialog box to view what the video display will look like. Several things might not be working correctly that Windows NT Server cannot detect. For example,  65536-color modes are supported for the ET4000, Cirrus, and S3 drivers. However, not all cards with these chip sets are capable of displaying in 65536-color mode. Some S3 cards, for example, actually support 32768-color modes, not 65536 colors. Adapters that support 32768 colors will show two or more shades of red, green, and blue. If this occurs, do not select this mode.

Updating to Windows NT Server 3.5 Video Drivers

It is strongly recommended that you use the latest video drivers for Windows NT Server 3.5. You can continue to use video drivers from Windows NT Advanced Server 3.1, but you will be missing the benefits of performance enhancements and the new functionality provided by the Display option in Control Panel. Also, numerous bug fixes have been made to video drivers.

If you are using a video driver that was not provided by Microsoft, you should be able to continue to use that driver, although Microsoft has not tested many of these drivers with Windows NT Server 3.5. If you have problems, please contact your product support representative and also contact the provider of the driver.

Troubleshooting Video Display Configuration

If you encounter problems, read the manual for your video display adapter again for proper settings. You may have overlooked something in the manual that pertains to Windows NT Server if you previously installed the card under Windows 3.x.

In general, Windows NT Server video drivers do not use interrupts. Many VGA cards use jumpers to enable IRQ 2 for EGA compatibility. When possible, you should disable IRQ 2.

The Display utility allows you to set the vertical refresh rate for your card. Read your monitor manual to see what settings you can use. If you are unsure, set it at the lower resolution, and then later try higher resolutions.

Minimum video memory requirements for Windows NT Server depend on the specific adapter card.

Caution

Some monitors may be physically damaged by wrong video settings. Check your monitor's manual carefully before choosing a new setting.

If after changing resolution settings and rebooting you find that your display is not operating correctly, reboot again before logging on, and use the Last Known Good feature to restore your previous video settings. For more information, see "System Diagnosis, Recovery, and Repair," later in this chapter.


Installing Windows NT Server and Using WINNT.EXE
Troubleshooting	6 of 32

Installing Windows NT Server and Using WINNT.EXE

Make sure your disk has enough space to install Windows NT Server. The recommended minimum is 90 MB for x86-based computers or 110 MB for RISC-based computers.

For x86-based computers, if Windows NT Setup seems to take an extremely long time, check your computer's CPU startup speed. This should be set to high. Computer settings that control CPU speed sometimes cause the computer to start in compatibility mode (equivalent to an 8 MHz PC) or at a low speed when the computer is started from a floppy disk. This low CPU speed will cause Windows NT Setup to run quite slowly. For information about how to set the CPU speed, see your computer hardware documentation.

The WINNT.EXE program must be run from MS-DOS on an x86-based computer. It cannot be run from Windows 3.1, OS/2, or Windows NT Server. To see usage information, change to the drive and directory that contains WINNT.EXE, and type winnt /? at the MS-DOS prompt.

If you do not have access to one or more of the Windows NT Setup boot disks, you can create new boot disks using WINNT.EXE.

To create new boot disks for Windows NT Setup

1.	Connect to the drive or directory containing the Windows NT Server installation files.

This could be a network directory containing the master files or the Windows NT Server compact disc.

2.	At the command prompt, winnt /o and press Enter, then follow the instructions on screen, inserting disks as requested.

When you install Windows NT Server using WINNT.EXE, Setup stores temporary files on your computer. Setup puts these files on the first available drive with enough space on it. It may choose a drive that is not supported by Windows NT Setup, such as a drive on a secondary IDE or ESDI controller or on an unsupported SCSI disk. If this happens, the following message appears:  "Setup is unable to locate the hard drive partition prepared by the MS-DOS portion of Setup." In this case, run WINNT.EXE again and specify a supported drive using the /t switch.

For additional troubleshooting notes for Setup, see SETUP.TXT on your installation disks.


Starting Windows NT Server on an x86-Based Computer
Troubleshooting	7 of 32

Starting Windows NT Server on an x86-Based Computer

Windows NT Server starts in the following sequence on an x86-based computer:

1.	When Windows NT Server is installed, it alters the system's boot record to look for and run a program called NTLDR.

2.	NTLDR reads BOOT.INI and builds a menu of the operating systems that you can start. (The BOOT.INI file is described following this list.)

3.	NTLDR runs NTDETECT.COM, which builds a list of the system's hardware components.

4.	You can select an operating system from the menu, or let the time-out count down to 0 to start the default operating system.

If you don't see the menu and the default operating system automatically starts, the time-out value has been set to 0 in BOOT.INI.

5.	The low-level components of Windows NT Server load, and then Windows NT Server initializes the drivers and starts the services based on information stored in the Registry.

6.	The high-level components of Windows NT Server load, and then the Welcome screen is displayed so you can log on.


Editing BOOT.INI
Troubleshooting	8 of 32

Starting Windows NT Server on an x86-Based Computer

Editing BOOT.INI

If Windows NT Server does not start, make sure that the statements in BOOT.INI (found in the root directory of your system partition) refer to the correct path for the \systemroot directory.

BOOT.INI is a system text file that has two sections:  the first specifies the default operating system to start and a time-out value specifying how long to wait before starting automatically, and the second specifies the operating systems that you can start. For example, if your system is configured to run either Windows NT Server or MS-DOS, BOOT.INI typically looks like this:

[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(1)\winnt35

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\winnt35="Windows NT Server"

c:\="MS-DOS"

You can edit the text displayed in quotes to customize the operating system choices, but you must first change the read-only, hidden, and system attributes of BOOT.INI.

To change the attributes of the BOOT.INI file

At the command prompt, type attrib -h -r -s c:\boot.ini and press Enter, and then edit the file. To restore the read-only, hidden, and system attributes when you finish editing the file, type attrib +h +r +s c:\boot.ini at the command prompt.

- Or -

1.	In File Manager, choose By File Type in the View menu, and then select the Show Hidden/System Files box in the By File Type dialog box, and choose the OK button.

2.	In the File Manager window, select the BOOT.INI file, and then choose Properties from the File menu.

3.	In the Properties dialog box, clear the Read Only, Hidden, and System Attribute box and choose the OK button.

4.	Edit the file using Notepad or another text editor. Follow the same steps to restore the hidden, read-only, and system file attributes.


Maintaining the Startup Configuration
Troubleshooting	9 of 32

Starting Windows NT Server on an x86-Based Computer

Maintaining the Startup Configuration

Once Windows NT Server starts successfully, back up your configuration directory (\systemroot\SYSTEM32\CONFIG), and maintain current backups as you change your configuration and accounts. If you have to use the Repair option in Windows NT Setup to restore the system, you can restore the configuration from your backup.

For x86-based systems, do not delete BOOT.INI, NTLDR, BOOTSECT.DOS, NTDETECT.COM, or NTBOOTDD.SYS (if Windows NT Server is installed on a SCSI disk) in the root directory of the system partition. For RISC-based systems, do not delete HAL.DLL or OSLOADER.EXE in \OS\NT. If these hidden system files are deleted, Windows NT Server will not start. Use the Emergency Repair disk to recover these files.

If you made changes to a system that previously started Windows NT Server successfully and it now doesn't start, you can return to your previous configuration by choosing the Last Known Good Configuration at system startup. If Windows NT Server still won't start, use the Repair process in Windows NT Setup to recover the system. For instructions on using the Last Known Good Configuration and the Repair program, see "System Diagnosis, Recovery, and Repair," later in this chapter.


Shutting Down Without Logging On
Troubleshooting	10 of 32

Starting Windows NT Server on an x86-Based Computer

Shutting Down Without Logging On

A Shutdown button can be displayed in the Welcome dialog box that appears after a user presses CTRL+ALT+DEL to log on. When the user chooses this button, Windows NT Server performs a complete system shut down without requiring the user to specify a username or password.

The Shutdown button appears by default on Windows NT Workstation computers. To turn off the display of the Shutdown button, you must use Registry Editor to change the value of ShutDownWithoutLogon in the Registry. A value of 1 for this parameter displays the button, and a value of 0 turns off the display of the button. This parameter is found in the following Registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\WINLOGON

For information about using Registry Editor, see "Editing Registry Values" in README.WRI.


Troubleshooting Startup Error Messages
Troubleshooting	11 of 32

Starting Windows NT Server on an x86-Based Computer

Troubleshooting Startup Error Messages

This section describes solutions to error messages that might appear when you start a Windows NT computer.

"Couldn't Find NTLDR" Error Message

This message is displayed if the file NTLDR is missing from the root of the C drive. You can copy the file to C:\ from either the Windows NT CD-ROM or floppy disks.

To copy NTLDR from the Windows NT compact disc

1.	Make the CD-ROM your current drive.

2.	At the command prompt, type copy \i386\ntldr c:\

To copy NTLDR from floppy disk

1.	Insert Windows NT Setup Disk #2 in your disk drive and make that drive the current drive.

2.	At the command prompt, type expand ntldr.$ c:\ntldr

"Error 0000001E" Error Message

Usually, this error implies a problem in the file system. Run chkdsk or another similar utility on the drive. Make sure your hardware is on the Hardware Compatibility List.

"Error 0x00000069 or 0x00000067" Error Message

This initialization error indicates that Windows NT is unable to communicate with the hard drive controller. Try the following:

Slow down the direct memory access (DMA) transfer rate on the controller.

Make sure both ends of the SCSI bus are terminated.

Make sure there are no conflicts for interrupt requests (IRQs) or memory addresses.

Make sure you are not using a faulty or unsupported driver.

Make sure NTDETECT.COM is in the root of the boot drive partition.

Make sure there are no missing Windows NT system files.

"NMI Hardware Error" Error Message

This error is caused by a hardware problem. In some cases, the computer's memory can be at fault, leading to an error that does not appear when running MS-DOS or Windows 3.x, but does appear when running Windows NT. Memory errors can occur when the access rate does not match the requirements of the system board or when the access rate varies between SIMM modules or chips on a module. Cache memory access rates that are too slow can also cause this problem.

The first steps are to make sure that contacts for all boards and memory modules are clean, that boards and memory modules are properly seated, and that the computer is free of dust. If this does not work, the computer should be taken to the dealer or hardware repair technician for complete diagnostics.


Starting an Alternate Operating System
Troubleshooting	12 of 32

Starting an Alternate Operating System

If the alternate operating system does not start, make sure that the statements in BOOT.INI (found in the root directory of your system partition) specify the correct path for that operating system.

The file BOOTSECT.DOS contains the boot record for the alternate operating system (whether or not the alternate is MS-DOS). Startup fails if the system cannot find BOOTSECT.DOS in the root directory of the system partition.

If you have OS/2 Boot Manager installed on your computer and want to continue to use it after Windows NT Server installation is complete, you need to reenable it. Start Disk Administrator from the Administrative Tools group in Program Manager. Select the OS/2 Boot Manager partition, and then select Mark Active from the Partition menu. To return to booting Windows NT Server, use FDISKPM in OS/2 to make the Windows NT Server partition available.


Logging On and Changing Passwords
Troubleshooting	13 of 32

Logging On and Changing Passwords

There are a variety of reasons why you may not be able to log on to Windows NT Server. An administrator can use Event Viewer in Administrative Tools to look at the audit trail of security events to determine why you were not able to log on, and can use User Manager to resolve problems with your account or password. The Audit policies for your account must include Failure for Logon and Logoff events for such problems to be displayed in the security log. When viewing the security log, the administrator should filter out all events except Failure Audit.

Some of the possible problems with logging on include the following:

Passwords are case-sensitive and you used the wrong case. For example, if your password is Test, you cannot type TEST to log on. Check that the CAPS LOCK key is not on.

You forgot your password. There is no way to determine your old password. An administrator can give you a new password.

Your account or your password may have expired. An administrator can reenable the account or password, or assign you a new password.

You were required to enter a new password, and you may have entered one that is less than the minimum length set for the account. Also, there may be a restriction on your account concerning the reuse of an old password.

You have reinstalled Windows NT Server but the domain administrator has not yet replaced your old computer account with a new one. Until your computer has a new account, you will be unable to log on to the domain. In this case, you can select the computer name in the Welcome dialog box to log on, instead of using the domain name.

Your account may be disabled. An administrator can reenable it.

The computer may be locked by a previous user. If that is the case, only that person or an administrator can unlock the computer.

You may be trying to log on at a time during which you are not allowed. An administrator can set times that you are permitted to log on.

If you are logging on remotely from another computer:

You may be allowed to log on only at certain computers.

You may be trying to log on to the wrong domain for your account.

The network may be down.

Note

If you know the Administrator password, you can also log on to a Windows NT computer under the Administrator account. This is especially useful if you did not create a user account during Windows NT Setup.

You can change your password any time after you log on by pressing CTRL+ALT+DEL.

To change your password

1.	After you log on, press CTRL+ALT+DEL.

2.	In the Windows NT Security dialog box, choose the Change Password button.

3.	In the Change Password dialog box, type your old password.

4.	Type the new password, type it again to confirm, and choose the OK button.

The new password will take effect the next time you log on.

To change a password from a remote domain

1.	In the Windows NT Security dialog box, choose the Change Password button.

2.	In the From list in the Change Password dialog box, select the domain where you want to change the password.

3.	Continue defining the new password as described in the previous procedure.


System Diagnosis, Recovery, and Repair
Troubleshooting	14 of 32

System Diagnosis, Recovery, and Repair

These system diagnosis, recovery, and repair methods are described in this section:

Use Windows NT Diagnostics to diagnose configuration problems.

Use the Recovery option in the Control Panel System tool to specify how Windows NT Server records and responds to severe errors.

Restore the previous working configuration using the Last Known Good Configuration, which Windows NT Server automatically preserves to ensure that you can always start Windows NT Server in spite of any changes to the system configuration that may occur during a work session.

Restore corrupt or missing system files, as well as boot variables, boot sector, and configuration information using the Repair process in Windows NT Setup. Depending on what you need to repair, you may or may not need to use the Emergency Repair disk. You can also use the Repair Disk utility (RDISK.EXE) to update your system information or create a new Emergency Repair disk.

Use a fault-tolerant boot floppy disk to recover mirrored boot or system partitions.

A list of other error detection tools available in Windows NT Server appears at the end of this section.


Using Windows NT Diagnostics for System Diagnosis
Troubleshooting	15 of 32

System Diagnosis, Recovery, and Repair

Using Windows NT Diagnostics for System Diagnosis

You can use Windows NT Diagnostics (WINMSD.EXE), the diagnostic tool for Windows NT Server, to view and print configuration information for a local or remote computer. With Windows NT Diagnostics, you can view the following:

Operating system information, such as the version number and system start options, plus process, system, and user environment variables

Hardware details such as BIOS information, video resolution, CPU type, and CPU steppings

Physical memory, paging file information, and DMA usage

The current state of each driver and service on the computer

Drives and devices installed on the computer, plus related interrupt (IRQ) and port information

Network information, including transports, configuration settings, and statistics

Printer settings, fonts settings, and system processes that are running

To run Windows NT Diagnostics

In the Administrative Tools group, double-click the Windows NT Diagnostics icon.


Using the Last Known Good Configuration
Troubleshooting	16 of 32

System Diagnosis, Recovery, and Repair

Using the Last Known Good Configuration

If you encounter difficulty starting Windows NT Server, you can choose to start Windows NT Server using the Last Known Good Configuration.

To use the Last Known Good Configuration

1.	Start your computer and press the SPACEBAR immediately when the words "OS Loader" appear.

A Configuration Recovery menu appears that lets you select one of the following:

Use Current Startup Configuration

Use Last Known Good Configuration

Restart Computer

2.	Select the Last Known Good Configuration to start Windows NT Server as it was before you made the changes that prevented it from starting. This is the configuration that last successfully started Windows NT Server.

All configuration changes are lost that were made since your system was last successfully started.


Using System Recovery in Control Panel
Troubleshooting	17 of 32

System Diagnosis, Recovery, and Repair

Using System Recovery in Control Panel

When a severe error (called a STOP error, or fatal system error) occurs on Windows NT Server 3.5, by default the system writes an event to the system log, alerts administrators, dumps system memory to a file you can use for debugging, and then automatically reboots the server.

Because Windows NT Server automatically reboots, rather than waiting for administrator intervention, fatal system errors cause less server down time than they would otherwise.

By default, Windows NT Workstation computers do none of these actions automatically when a STOP error occurs. This saves memory, because the drivers required to send an alert, write an event, and dump memory to a file are not loaded into memory. If you enable any one of these actions, these drivers (totaling a few kilobytes of memory) must be kept in memory at all times.

The dump of system memory to a log file can be valuable for debugging the cause of the STOP error. If you contact your technical support representatives about the error, they may ask for the log file. Notice that Windows NT writes the log file to the same file name (MEMORY.DMP, by default) each time a STOP error occurs; to preserve log files, you should copy them to a new filename each time a STOP error occurs.

If you want to change how Windows NT Server reacts to a STOP error, use the System option in Control Panel.

To change how Windows NT Server acts when a fatal system error occurs

1.	In Control Panel, choose the System option.

2.	In the System dialog box, choose the Recovery button.

3.	In the Recovery dialog box, select the Write An Event To The System Log check box if you want to have Windows NT Server write an event containing information about the error to the system log when a STOP error occurs.

4.	Select the Send An Administrative Alert check box if you want to have Windows NT Server send an alert to administrators when a STOP error occurs.

5.	To have Windows NT Server write the contents of system memory to a log file when a STOP error occurs, select the Write Debugging Information To check box, and type the path and file name of the log file in the text box.

To have this log file overwrite any file of the same name, select the Overwrite Any Existing File check box. If you clear this check box, then Windows NT Server will not write a log file if there is already a file by that name.

6.	Select the Automatically Reboot check box if you want to have the computer reboot automatically after a STOP error.

7.	Choose the OK button.

After you change System Recovery options, you may have to restart the server to have the new options take effect. If so, a message will appear instructing you to restart the server.


Using the Repair Process
Troubleshooting	18 of 32

System Diagnosis, Recovery, and Repair

Using the Repair Process

If your system files, boot variable, or boot sector are corrupt and you are unable to recover the previous startup configuration using the Last Known Good method, you can use the Repair process in Windows NT Setup to restore your system to its initial setup state.

To repair a Windows NT Server installation, Windows NT Setup needs either the configuration information that is saved on \systemroot\REPAIR or the Emergency Repair disk created when you installed Windows NT (or created later using the Repair utility).

If your system becomes corrupt and you cannot repair it using the Emergency Repair disk or using the information in the \REPAIR directory, you must reinstall Windows NT Server from the original installation source.

To restore Windows NT Server on an x86-based computer using the repair process in Windows NT Setup

1.	If you installed Windows NT Server using the original Setup floppy disks or CD-ROM, or using WINNT.EXE, start Setup just as you did originally. That is, insert the Setup Boot Disk in drive A and start the computer.

2.	In the text-based Setup screen that asks whether you want to install Windows NT Server or repair files, type r to indicate that you want to repair your Windows NT Server files.

3.	Windows NT Setup asks you for the Emergency Repair disk. If you do not have one, Setup presents a list of the Windows NT installations that it found on your computer and lets you select the one you want to repair.

4.	Follow the instructions on the screen, inserting the Emergency Repair disk (if you have one) in drive A and providing any other Windows NT Setup disks as requested.

5.	When the final message appears, remove the Emergency Repair disk from drive A, and then press CTRL+ALT+DEL to restart your computer.

To restore Windows NT Server on a RISC-based computer with an Emergency Repair disk

1.	Start the Windows NT Setup Program as instructed in your manufacturer-supplied documentation. (How you start Windows NT Setup depends on the type of RISC-based computer you have.)

2.	In the text-based Setup screen that asks whether you want to install Windows NT Server or repair files, type r to indicate that you want to repair your Windows NT Server files.

3.	Follow the instructions on the screen, inserting the Emergency Repair disk (if you have one) in drive A if Setup asks for it.

4.	When the final message appears, remove the Emergency Repair disk, and then press ENTER to restart your computer.

The repair process in Windows NT Setup allows you to choose what you want to repair. You can repair the following:

System files

Setup checks the Windows NT Server directory tree against the log file on the Emergency Repair disk to ensure that all system files are present and none are corrupt. If any files are missing or corrupt, Repair restores the files from the appropriate Windows NT Server Setup source. Setup also checks the Windows NT Server files on the system partition to ensure that all boot files are present and none are corrupt.

If you choose to repair the system files, Setup removes security from Windows NT system files if these files are on an NTFS partition. This option is useful if you accidentally set permissions on a system file or directory so that Windows NT cannot access the system files needed to start your system.

Default system configuration

Setup checks the Registry for errors. If any Registry files are found to be corrupt, Setup gives you the option of restoring the files from  the ones created when you installed Windows NT. Note that user accounts and file security added since you first ran Setup are lost, unless you have backed up the \systemroot\SYSTEM32\CONFIG directory or updated your system configuration using the Repair Disk utility.

Boot variables

Setup restores the boot variables for a particular installation of Windows NT on your hard disk. For this option, you must provide the Emergency Repair disk created for your computer.

Boot sector (x86-based computers only)

Setup will write a new boot sector on the system partition.

If any files are missing or corrupt, Repair restores the files from the appropriate Windows NT Setup disk or CD-ROM. If you have accidentally reformatted or changed the system partition on your x86-based computer so that Windows NT Server no longer starts, the Repair program restores your original boot configuration so that you can start Windows NT Server.

Caution

Be sure to update the system repair information in the \REPAIR directory on your hard disk and to create and maintain an up-to-date Emergency Repair disk. This way, your system repair information will account for new configuration information such as drive letter assignments, stripe sets, volume sets, mirrors, and so on. Otherwise, drives may be inaccessible in the event of a system failure.

You can use the Repair Disk utility to update your system repair information and to a create a new Emergency Repair disk.

To update your system repair information

1.	From the Control menu in Program Manager, choose the Run command, and then type rdisk in the Run dialog box.

2.	In the Repair Disk Utility window, choose the Save Repair Info button.

3.	Follow the directions on screen. For more information, see the Repair Disk Utility online Help.


Using a Fault-Tolerant Boot Floppy Disk
Troubleshooting	19 of 32

System Diagnosis, Recovery, and Repair

Using a Fault-Tolerant Boot Floppy Disk

For a boot partition configured as part of a mirror set, which is the only fault-tolerance method that can be applied to the boot or system partition, the recovery procedure depends on whether the computer is x86-based or RISC-based. Both use a floppy disk for boot protection, and both use Advanced RISC Computing (ARC) names to describe the boot process.

Notice that you should create and test such a fault-tolerant boot floppy disk in advance of any failure or you will not be able to boot off the mirror if the primary boot partition is lost. For details on creating and testing such a disk, see Chapter 7, "Managing Fault Tolerance and UPS," in the Windows NT Server Concepts and Planning Guide.

When a member of a mirrored set is orphaned, you must first break the mirror-set relationship to expose the remaining secondary partition as a separate volume. When the disk that fails is the system or boot partition, you need to do the following steps to recover Disk 0 by using the information on Disk 1.

To recover Disk 0 by using the information on Disk 1

1.	Use the Windows NT Server fault-tolerant boot floppy disk (with a BOOT.INI file specifying the ARC path pointing to Disk 1) to boot the remaining secondary partition.

2.	Open Disk Administrator, select the mirror set partition, and break the mirror.

3.	Reestablish the mirror for that partition between Disk 0 and Disk 1.

4.	Exit Disk Administrator.

Disk Administrator will force the system to reboot when needed.

5.	Boot the repaired Disk 0 using the fault-tolerant boot floppy disk to boot from Disk 1.

The mirror on Disk 1 will rebuild the files on Disk 0.

6.	Open Disk Administrator, select the two disks and break the mirror.

7.	Modify the drive-letter assignments to have the C drive on Disk 0 and the D drive on Disk 1, and then mark the C drive on Disk 0 as active.

This will enable you to avoid having to change the SCSI numbers for the disks.

8.	Exit Disk Administrator.

9.	Remove the fault-tolerant boot floppy disk and then reboot Disk 0.

Note

This procedure works best when the disk geometry (that is, the number of heads, cylinders, and sectors per track) of the drives used for the primary and secondary partitions is the same, and the drives are of the same brand and model.


Other Error Detection Tools
Troubleshooting	20 of 32

System Diagnosis, Recovery, and Repair

Other Error Detection Tools

Some other ways in which Windows NT Server reports errors and preserves your system configuration and data include the following:

If your system uses NTFS, Windows NT Server logs all file transactions, replaces bad sectors automatically, and stores copies of key information for all files on the NTFS volume.

Services and applications record events, including errors, in the event logs that you can view in Event Viewer. For more information, see the Event Viewer  chapter in the Windows NT Server System Guide.

The Alerter and Messenger services work together to provide warnings on printer, security, and user session problems, and to provide server shutdown warnings if the system uses the Uninterruptible Power Supply (UPS) service. For information, see the Control Panel  chapter in the Windows NT Server System Guide.

Performance Monitor can be configured to create an alert log for monitoring performance and generating network alerts. For information, see the Performance Monitor  chapter in the Windows NT Server System Guide.

Chkdsk examines disk space and use for the NTFS, HPFS, and FAT file systems. If errors exist on the disk, chkdsk alerts you and corrects the errors if the /f switch is used. If files are open when chkdsk is attempting to correct disk errors, chkdsk lets you choose to have it automatically check the drive and correct errors the next time the computer reboots. For more information, see the online Command Reference.

Dr. Watson for Windows NT can be used to detect, diagnose, and log application errors for use by technical support personnel. To run Dr. Watson, type start drwtsn32 at the command prompt. Press F1 for Help on setting up and using Dr. Watson.

The Windows NT Messages database on the Windows NT Server compact disc provides information on error and information messages that you can use for troubleshooting. To install this database, choose Run from the File menu in Program Manager, and then type cd_rom_drive:\WINNTMSG\SETUP and follow the instructions on screen. Double-click the Microsoft Windows NT Messages icon in the new program group to use the database.

The Windows NT Server Messages book also provides instructions for using the Windows NT Debugger (WinDbg) for remote and local Kernel debugging of Windows NT Executive STOP errors.


Network Problems
Troubleshooting	21 of 32

Network Problems

Common network problems include hardware problems with the network itself, incompatible protocols running on different devices in the network, duplicate computer names, and IRQ conflicts. There may also be physical problems with the cabling and other hardware that prevent the network from operating properly.

If network problems persist, use Event Viewer from the Administrative Tools group to review the error log information generated during startup. Details in the System error log will reveal possible interrupt conflicts or other driver problems.


Duplicate Computer Names
Troubleshooting	22 of 32

Network Problems

Duplicate Computer Names

Each computer on a network must have a unique name. If you specify a computer name that is the same as another computer on the network or the same as a workgroup or a domain, the network will not start when you run Windows NT Server.


Network Adapter Card Settings
Troubleshooting	23 of 32

Network Problems

Network Adapter Card Settings

This section contains updated information for Windows NT version 3.51. Click here to see the new information.

If your network adapter card can accept more than one type of cable, make sure that the card is configured for the cable that you are plugging into it. Refer to the documentation that came with the card for details.

When you configure the network adapter card, you must select the correct IRQ setting, I/O port base address, and memory buffer address. On older network cards, you set jumpers or switches on the card for each of these items; with newer cards, you can program them with the driver software using only the I/O port address.

If you are not sure which network card is installed in your computer or what its settings are, accept the defaults proposed by Windows NT Setup. After Setup is complete, you can use the Network option in Control Panel to install and configure network settings. For information about completing any options in the dialog boxes that appear during the network portion of Setup or when you run the Network option in Control Panel, use the Help button.

You do not have to specify settings for built-in ethernet capabilities on RISC-based computers from Acer, MIPS, and Olivetti®.

The following default settings for network cards are used by Windows NT Server during network installation.For the correct settings for your particular hardware, see the documentation for your network card and other devices such as SCSI adapters, or contact your hardware manufacturer.

Default Network Card Settings

Card Name		Default Setting
3Com®:
EtherLink® II		IRQ=3 IOBaseAddress=0x300 Transceiver=On board MemoryMapped=OFF
EtherLink II® / TP		IRQ=3 IOBaseAddress=0x300 Transceiver=On board MemoryMapped=OFF
EtherLink II/ 16		IRQ=3 IOBaseAddress=0x300 Transceiver=On board MemoryMapped=OFF
EtherLink II/ 16 TP		IRQ=3 IOBaseAddress=0x300 Transceiver=On board MemoryMapped=OFF
EtherLink/ MC		No settings required
EtherLink 16/16 TP		IRQ=5 IOBaseAddress=0x200 MemoryMappedAddress=0xd0000 MemorySize=16 Transceiver=On board Zero Wait State=OFF
EtherLink 3 ISA 509		IOBaseAddress=0x200
EtherLink 3 EISA		No settings required
EtherLink 3 MC		No settings required
AMD:
AM2100/AM1500T/ PCnet		IRQ=3 DMA channel=3 IOBaseAddress=0x300
COMPAQ:
32-bit NetFlex Controller		No settings required
32-bit DualSpeed Token-Ring Controller		No settings required
DayStar:
Digital LocalTalk®		IOBaseAddress=0x340
Digital LocalTalk MC		No settings required
Digital Equipment Corporation:
EtherWorks LC		IRQ=5 MemoryAddress=0xd0000 IO Port Address=Primary
EtherWorks Turbo		IRQ=5 MemoryBaseAddress=0xd0000 IO Port Address=Primary
EtherWorks Turbo/TP		IRQ=5 MemoryBaseAddress=0xd0000 IO Port Address=Primary
EtherWorks Turbo EISA		No settings required
DECpc™		No settings required
DigiBoard:
2Port, 4Port, 8Port, PC/4e, PC/8e, PC/8i		MemoryBaseAddress=0xd0000 IOBaseAddress=0x220 IRQ=disabled
PC/Xem		MemoryBaseAddress=0xd0000 IOBaseAddress=0x224 IRQ=disabled
C/X		MemoryBaseAddress=0xd0000 IOBaseAddress=0x228 IRQ=disabled
PCIMAC - ISA/MC ISDN andPCIMAC/4		IRQ=disabled IOBaseAddress=0x320 MemoryBaseAddress=0xd0000 SwitchType=AT&T
IBM®:
Token Ring 16/4		IO Port Address=Primary
Token Ring 16/4A		No settings required
Intel:
Ether Express 16 LAN		IRQ=3 IOBaseAddress=0x300 IOChannelReady=Late TransceiverType=Thin Net
Network Peripherals:
FDDI EISA		No settings required
FDDI MC		No settings required
Novell:
NE1000Novell/Anthem NE1500T Novell/Anthem NE2100 NE2000		IRQ=3 IOBaseAddress=0x300
NE3200		No settings required
Proteon:
P1390		IRQ=5 IO Port Address=0xa20 DMA channel=5 Cable Type=STPCard Speed=16
P1990		No settings required
SMC®/Western Digital™:
8003EP		IRQ=2 MemoryBaseAddress=0x0IO Port Address=0x200
8013EWC		IRQ=2 MemoryBaseAddress=0x0IO Port Address=0x200
8013WB		IRQ=2 MemoryBaseAddress=0x0 IO Port Address=0x200
8013EA		No settings required
SMC/WD ISA		IRQ=2 MemoryBaseAddress=0xd0000 IO Base Address=0x300
SMC/WD MC  (WD8003EA, WD8003WA, WD8013WPA, WD8013EPA)		No settings required
Ungermann-Bass®:
Ethernet NIUps (MC)		No settings required
Ethernet NIUps/EOTP (short)		No settings required
Ethernet NIUpc (long)		IRQ=5 IOBaseAddress=0x368 MemoryMappedAddress=0xd8000
Ethernet NIUpc/EOTP (short)		IRQ=5 IOBaseAddress=0x368 MemoryMappedAddress=0xd8000
Built-In Ethernet on MIPS ARC/R4000 systems from Acer, MIPS, and Olivetti		No settings required
Network Adapter Card Interrupts

The IRQ that you assign to a network adapter card should be unique; that is, it should not be used by any other device in the system. The standard assignments for IRQs in x86-based computers include the following:

IRQ	Used for		IRQ	Used For
0	Timer		8	Clock
1	Keyboard		9	-
2	(cascade)		10	-
3	COM2/COM4		11	-
4	COM1/COM3		12	-
5	LPT2		13	Math coprocessor
6	Floppy controller		14	Hard drive
7	LPT1		15	Secondary disk controller
A network card should not be assigned an IRQ that is used by an active serial or parallel port, even if no device is currently attached to the port. Most newer x86-based computers let you disable the built-in serial or parallel ports. After you disable a port, you can assign its associated IRQ to another device, such as a network card.

For example, if you use only a network printer, you can usually disable the built-in parallel printer ports for both LPT1 and LPT2. Network software does not use these interfaces when the underlying devices are redirected.

For information on disabling serial or parallel ports, see the documentation for your computer.

COM1 (IRQ 4) and COM2 (IRQ 3) are usually poor choices because most x86-based computers come with two active serial ports. For example, a typical computer with a mouse on COM1 and a modem on COM2 cannot use IRQ 3 or IRQ 4 for a network adapter card. IRQ 5 is often a safe choice, because x86-based computers usually do not have two parallel printer ports.

If you have two or more COM ports on your computer, you might find that a network adapter card (especially an EtherLink II card) will conflict with one port. Two common symptoms are that the Workstation service fails to start and that an error attributed to the network adapter card is logged in Event Viewer.

To change the interrupt used by a network adapter card

1.	In Control Panel, choose the Network option.

2.	Double-click the related entry in the Installed Adapter Cards list.

3.	In the Adapter Card Setup dialog box, change the interrupt number from 3, for example, to an available interrupt, such as 5 or 10.

Use Windows NT Diagnostics in the Administrative Tools group in Program Manager to make sure that the interrupt you choose is not being used by another device.

Assigning I/O Port Base Addresses

Most devices have unique default I/O port base addresses. In the rare case that an I/O port appears to be in conflict, it can usually be moved to another setting without harm. The following table shows some common I/O port addresses:

I/O address	Used for		I/O address	Used for
3F8	COM1		300	-
3BC	-		2F8	COM2
378	LPT1		278	LPT2
Refer to the documentation for your network adapter card and other hardware devices to find which I/O addresses are required for your system.

Assigning Memory Buffer Addresses

No two devices can share memory buffers. Use Windows NT diagnostics to make sure that the buffer address for your network adapter card is not already used by another device, such as a SCSI adapter card or hard disk controller. Check the installation guide for your computer or peripherals to verify the setting of the memory buffer address.

Some SCSI and network adapters use conflicting memory addresses, such as an Adaptec™ or Future Domain SCSI adapter and a Digital EtherWorks Turbo TP network adapter. Resolving such memory-address conflicts requires reconfiguring the hardware by changing jumpers. For information, see your hardware documentation.


Services or Subsystems Do Not Start
Troubleshooting	24 of 32

Network Problems

Services or Subsystems Do Not Start

If services or subsystems do not start properly, use the Services or Devices icons in Control Panel to check their status. You can try to start services using the Services option and start a device with the Devices option. Also, check the system log in Event Viewer for entries relating to the problem.


Interoperability with Windows for Workgroups
Troubleshooting	25 of 32

Network Problems

Interoperability with Windows for Workgroups

When setting up your network, check the following issues to ensure smooth interoperability between Windows NT and Windows for Workgroups.

Browsing will not be available if you log on to a Windows for Workgroups computer whose workgroup name is the same as the name of a Windows NT Server domain or if the user name and password are not valid for the domain. If you want to browse the domain, log on with another user name and password that are valid in the domain.

Guest accounts should remain enabled on domain controllers. Instead of removing guest accounts to restrict access to certain services, simply remove any unwanted guest account rights in User Manager for Domains.

Avoid duplicate user names on different domains. If a user name is duplicated across different domains, logging on will produce different results on the Windows NT network and the Windows for Workgroups computer.

If you seem to have password problems logging on to Windows for Workgroups, delete your passwords list (the .PWL file with your username in the Windows directory). The next time you log on, you will be asked for your password and a new list will be created. Also, choose the Network icon in Control Panel, and then choose the Startup button in the Microsoft Windows Network dialog box to be sure you have specified the correct password for the Windows NT domain.


Running Windows-Based Mainframe Connectivity Software
Troubleshooting	26 of 32

Network Problems

Running Windows-Based Mainframe Connectivity Software

Some Windows 3.1-based software for connecting to mainframe computers requires a memory-resident program to operate correctly. Such software includes Access for Windows 3270 from Eicon Technology, Extra! for Windows from Attachmate, and Rumba® from Wall Data™.

When these programs run under 16-bit Windows 3.x, they add a command to AUTOEXEC.BAT to start the memory-resident program, or they require the user to start the memory-resident program through a batch file that must be run manually before starting Windows.

To run any of these memory-resident programs with Windows NT Server, add the command for starting the program to the AUTOEXEC.NT file. To find the command used to start the memory-resident program, check AUTOEXEC.BAT or the batch file used to start the program under MS-DOS.

AUTOEXEC.NT is stored with other Windows NT Server program files, usually in the \systemroot\SYSTEM32 directory. Add the line with the command for starting the memory-resident program after the line containing REDIR.EXE in AUTOEXEC.NT. Then restart your computer before starting the connectivity application.


Miscellaneous Problems
Troubleshooting	27 of 32

Miscellaneous Problems

The following section describes miscellaneous problems you may encounter installing Windows NT Server.


Removing an NTFS Partition
Troubleshooting	28 of 32

Miscellaneous Problems

Removing an NTFS Partition

If the Windows NT Server system files are not installed on an NTFS partition, you can use the format command at the command prompt to reformat that NTFS partition to another file system. However, using format will also destroy all existing data.

To remove an NTFS partition where Windows NT Server is installed

1.	Restart your system using Windows NT Setup. With your x86-based computer turned off, insert the Windows NT Server Setup Boot Disk in drive A and turn on your computer. For a RISC-based computer, place the Windows NT Server Setup compact disc in the CD-ROM drive and start Windows NT Setup.

2.	Continue through Setup until the screen appears for creating or choosing partitions. The text on that screen begins with these instructions:

The list below shows existing partitions and spaces available for creating new partitions.Use the UP and DOWN ARROW keys to move the highlight to an item in the list.

3.	Press an arrow key to highlight the NTFS partition that contains the Windows NT Server system files, and then type d to delete it.

4.	Continue to reinstall Windows NT Server on a different partition, or reformat this partition to continue with Setup.

- Or -

If you are removing Windows NT Server from this computer, press F3 to exit the Setup program.


Performance Problems
Troubleshooting	29 of 32

Miscellaneous Problems

Performance Problems

If you experience performance problems while running Windows NT Server, make sure:

The turbo function on your computer (if present) is active.

The maximum system paging file size is adequate for your memory requirements. If its size approximates the maximum paging file size (set in the System option of Control Panel), consider increasing the maximum file size setting.

You can improve screen display rates by decreasing video resolution. If lower resolution is acceptable, use the Display option in Control Panel to decrease your resolution. Video response depends largely on computer architecture and your video adapter card.


Printing from Windows-Based and MSDOS–Based Applications
Troubleshooting	30 of 32

Miscellaneous Problems

Printing from Windows-Based and MS-DOS Based Applications

Some Windows 3.1-based applications expect the printer driver to exist on the local computer when you are printing to a network printer. Some applications may fail when the network printer is not available. To avoid these problems, install an appropriate printer driver on your computer.

Some Windows 3.1-based applications may display error messages indicating that the application is out of memory or that there are insufficient system resources to run. Many of these error messages are caused when the application designates a Windows 3.1 printer driver as the default printer driver. This can occur, for example, when you install a Windows 3.1-based application whose setup program installs a printer driver and makes the driver the system default. Windows 3.1 printer drivers are not compatible with Windows NT Server. To resolve this problem, specify a default printer using Windows NT Print Manager. If necessary, first use Print Manager to create a printer.

When printing complex documents from Windows 3.1 or MS-DOS – based applications using a slower computer, Windows NT Server may begin printing before a complete page has been processed. When this occurs, portions of a page may be printed on a series of pages. You can resolve this problem by increasing the time that Windows NT Server waits before starting to print. To increase the time that Windows NT Server waits, use Registry Editor to edit the following value in the Registry:

LPT_timeout:REG_SZ:15

The value is located in the following Registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WOW

By default, the value is 15 seconds. Because raising this value slows the speed of printing from all MS-DOS and Windows 3.1-based applications, do not raise the value higher than necessary. You may want to try a value of 60 seconds first.

For information about using Registry Editor, see "Editing Registry Values" in README.WRI.


Repairing CONFIG.NT and AUTOEXEC.NT
Troubleshooting	31 of 32

Miscellaneous Problems

Repairing CONFIG.NT and AUTOEXEC.NT

If Windows NT Server displays an error message concerning these files, or if you have problems running MS-DOS–based applications, check whether CONFIG.NT or AUTOEXEC.NT is incorrect or missing. The files are located in the \systemroot\SYSTEM32 subdirectory.

If the files are incorrect or missing, you can copy new versions from the Emergency Repair disk to the \SYSTEM32 subdirectory, as described earlier in "System Diagnosis, Recovery, and Repair."


Floppy Disk Failure When Installing an Application
Troubleshooting	32 of 32

Miscellaneous Problems

Floppy Disk Failure When Installing an Application

In a few cases, Windows NT Server may be unable to read an application's original installation disks. This occurs because Windows NT Server checks disks more stringently than does MS-DOS. If you are running MS-DOS and Windows NT Server on your computer, install the application while running MS-DOS. If you are running Windows NT Server only, create a new set of installation disks on another computer running MS-DOS, and then use the new disks to install the application.

To create a new set of application installation disks

1.	Use MS-DOS to format a new floppy for each installation disk.

2.	Use the MS-DOS xcopy command to copy the files on each installation disk to a new disk.


Introduction to Networking Services and Protocols
Chapter 3	1 of 12

Networking Services Overview

Windows NT Setup adds the basic software you need to begin working on the network immediately. However, you may want to install additional networking services on your Windows NT Server computer.

This chapter provides a brief overview of network protocols and installation and configuration information for these Windows NT protocols:

Protocol or service	Description
DLC protocol	The Data Link Control (DLC) protocol for accessing IBM mainframe computers or printers attached directly to the network.
NetBEUI protocol	NetBIOS extended user interface, the standard protocol for the NetBIOS interface, for LANs of 20 to 200 workstations.
Network Monitor Agent	Provides performance counters for the network adapter card and provides an agent that can be used by other monitoring software to analyze traffic on a LAN.
NWLink IPX/SPX Compatible protocol and Gateway Service for NetWare Networks	The transport protocols used in Novell NetWare networks, and the service that allows access to files, directories, and printers on NetWare servers.
Remote Access Service	Allows remote computers to dial in to a LAN.
Services for Macintosh	Manages file and printer sharing for Windows NT and Apple Macintosh computers.
TCP/IP and related components	A suite of Transmission Control Protocol/Internet Protocol (TCP/IP) protocols for communicating in heterogeneous interconnected network.  For Windows NT Server, you can also install Dynamic Host Configuration Protocol (DHCP) servers and Windows Internetwork Name Service (WINS) servers to support dynamic configuration and name resolution services.


Introduction to Networking Services and Protocols
Networking Services Overview	2 of 12

Introduction to Networking Services and Protocols

Network services are components that add networking capabilities to Windows NT. A network protocol is a set of rules that allows computers on a network to communicate with each other. Two computers must use the same network protocol (speak the same language) to communicate.

Protocols communicate through other layers of software that control the flow of information. How network protocols and other layers of network software work together is determined by network bindings. Windows NT automatically binds network protocols to all appropriate layers.

Note

Choosing the protocols to use in a network requires evaluating several elements of the network, such as the number and types of computers, special hardware or software used, and compatibility and integration into existing networks. If you are going to set up a local area network and do not have an experienced network administrator, you should understand all the complex elements of a local area network before attempting to install one.

Follow these guidelines in choosing the protocols to install:

If you are establishing a small, isolated network, you should probably use NetBEUI or the NWLink IPX/SPX Compatible Transport.

If you are in a large network, the network administrator will have determined the network protocol to use based on network components and your company's requirements. Install only the protocols recommended by your network administrator.


Installing Networking Services
Networking Services Overview	3 of 12

Installing Networking Services

Windows NT Setup automatically installs Computer Browser, Server, and Workstation services plus a NetBIOS interface and a driver to support your network adapter card.

You must be logged on as a member of the Administrators group for the local computer to install and configure any networking services or protocols.

To install additional networking capabilities on a Windows NT computer

1.	In Control Panel, choose the Network option to display the Network Settings dialog box.

2.	In the Network Settings dialog box, choose the Add Software button.

3.	In the Add Network Software dialog box, select the name of the new networking option in the Network Software box, and then choose the Continue button.

4.	When the Windows NT Setup dialog box prompts you for the full path to the Windows NT distribution files, provide the appropriate location, and then choose the Continue button.

5.	The supporting network software is copied to your computer. If this network option requires configuration, the appropriate dialog box appears so that you can specify settings. Specify your choices or accept the default settings proposed by Windows NT. Choose the Help button in any configuration dialog box to see online Help.

6.	When the Network Settings dialog box reappears, choose the OK button to complete installation for the new software.

The system automatically performs the steps required to integrate the new networking software with your existing configuration. For most new network software, you must restart your computer for the changes to take effect.

For more information about installing network software and configuring network bindings, see "Installing Network Software" in Chapter 5, "Control Panel," in the Windows NT Server System Guide.

Windows NT Server also includes network administrative tools that run under the Windows 3.x or Windows for Workgroups operating system. You can use these tools for complete administrative support of Windows NT and Microsoft LAN Manager for OS/2 servers from computers running MS-DOS–based versions of Windows. For information, see Chapter 9, "Network Client Administrator."


DLC
Networking Services Overview	4 of 12

DLC

The Data Link Control (DLC) protocol isn't used for general networking on Windows NT. The DLC protocol provided with Windows NT is used primarily to access IBM mainframe computers. For example, Microsoft SNA Server for Windows NT uses the DLC protocol device driver when communicating with mainframes on the token ring interface.

Windows NT DLC allows Windows NT computers to connect to IBM mainframes using 3270 emulators. You can also connect to IBM AS/400® computers using 5250 emulators. Windows NT DLC works with either token ring or ethernet media access control (MAC) drivers. The DLC protocol works with Windows NT-based programs and with MS-DOS–based and 16-bit Windows-based programs.

DLC is also used to provide connectivity to local-area printers connected directly to the network. For example, DLC can be used to print to a printer such as a Hewlett-Packard® HP® 4Si that uses an HP JetDirect® network adapter to connect directly to the network instead of to a port on a print server.

To take advantage of the DLC protocol device driver, you must create a network printer in Print Manager. You can also use Print Manager to specify the network adapter that connects the printer to the server, and you can adjust the DLC timers. For more information, see the online Help for the Add Hewlett-Packard Network Port dialog box in Print Manager.


Installing the DLC Protocol
Networking Services Overview	5 of 12

DLC

Installing the DLC Protocol

If you want to connect to and communicate with a mainframe computer, the DLC protocol must be installed and running. You can then use a terminal emulator to access a mainframe computer.

If you want to print to printers that are attached directly to the network via DLC, the DLC protocol must be installed and running on the print server for the printer. Computers sending print jobs to a print server for a DLC network printer do not need the DLC protocol - only the print server requires DLC.

You can install the DLC protocol using the Network option in Control Panel.

To install the DLC protocol on a Windows NT computer

1.	In Control Panel, choose the Network option.

2.	In the Network Settings dialog box, choose the Add Software button.

3.	In the Add Network Installation dialog box, select DLC Protocol in the Network Software box, and then choose the Continue button.

4.	Follow the instructions on screen for providing a path to the Windows NT distribution files and completing Setup.


Configuring Network Settings for DLC
Networking Services Overview	6 of 12

DLC

Configuring Network Settings for DLC

The order of the network bindings as specified in the Network Settings dialog box is significant for DLC, because an adapter is specified as a number at the DLC interface. Typically this number is 0 or 1, but Windows NT DLC can support up to 16 adapters. The number corresponds to the adapter's index in the DLC bindings section. If you have only one network adapter installed, DLC applications use 0 to refer to it.

If you have more than one network adapter, you can modify the bindings to change the order to match the index number.

To modify bindings for DLC

1.	In Control Panel, choose the Network option.

2.	In the Network Settings dialog box, choose the Bindings button.

3.	In the Show Bindings For box, choose DLC Protocol.

In the list of bindings that appears, the numbers in brackets refer to the order in which the adapters were installed. For example, in the following sample, DLC refers to the ethernet adapter as adapter #0:

DLC Protocol -> ARC Built-in Ethernet Adapter Driver ->	[01] ARC Built-in EthernetAdapterDLC Protocol -> IBM Token Ring Adapter Driver ->	[02] IBM Token Ring Adapter

4.	To change the order of an item in the list, highlight the item, and then click the up- or down-arrow button to reposition it in the list.

5.	Choose the OK button to save the modified bindings list. Then choose the Close button in the Network Settings dialog box and restart your computer.


NetBEUI
Networking Services Overview	7 of 12

NetBEUI

The NetBIOS extended user interface (NetBEUI) is a small, efficient, and fast protocol optimized for high performance in smaller LANs or LAN segments. NetBEUI is designed to support department-sized LANs that consist of 20 to 200 computers. It provides for both connectionless and connection-oriented traffic on a single network segment. NetBEUI does not support traffic across routers.

NetBEUI is self-configuring and self-tuning. NetBEUI can be installed and bound to a network adapter card automatically when Windows NT is installed.

Important

You must install the NetBEUI protocol if your computer communicates with other computers on an existing Microsoft network that uses NetBEUI with Windows NT 3.1, Windows for Workgroups 3.11, or LAN Manager 2.x. If you do not have NetBEUI installed when your network requires it, your computer will not be able to communicate with other computers on your network.


Network Monitor Agent
Networking Services Overview	8 of 12

Network Monitor Agent

The Network Monitor Agent on a Windows NT computer collects and displays statistics about the network adapter card in the computer. You can view the statistics yourself, and an administrator can arrange for the statistics to be collected by a central computer to help diagnose problems with the network.

When you install the Network Monitor Agent, counters are added to Performance Monitor for monitoring statistics from the computer's network adapter card. To use these counters, start the Network Monitor Agent with the Services option in Control Panel.

An administrator can run Microsoft Network Monitor, a component of Microsoft Systems Management Server (SMS), on a Windows NT Server computer. SMS is not included with Windows NT Workstation or Windows NT Server. The computer running SMS and Network Monitor collects statistics from computers running the Network Monitor Agent. This data helps administrators perform routine troubleshooting tasks, such as locating a server that is down or that is receiving a disproportionate number of work requests.

When your Windows NT computer runs the Network Monitor Agent, you see no indication that a central server is collecting the statistics; it has no impact on your work.

The Network Monitor Agent can also be started remotely on a Windows NT computer if the managing computer is running Server Manager on an installation of Windows NT, Windows for Workgroups, or Windows. Also, the remote computer must have a network adapter card that supports promiscuous mode, a state in which the network card passes on to the network operating system all the frames it detects on the network.

To install the Network Monitor Agent on a Windows NT computer

1.	In Control Panel, choose the Network option.

2.	In the Network Settings dialog box, choose the Add Software button.

3.	In the Add Network Software dialog box, select Network Monitor Agent in the Network Software box, and then choose the Continue button.

4.	Follow the instructions on screen for providing a path to the Windows NT distribution files and completing Setup.

To view performance counters provided by Network Monitor Agent

1.	In Performance Monitor, choose Add To Chart from the Edit menu.

2.	In the Object list of the Add To Chart dialog box, select Network Monitor Statistics.

3.	In the Counter box, select the counters that you want to chart, and then complete the other options in the dialog box, as described in online Help.


NWLink IPX/SPX Compatible Transport and Gateway Service for NetWare
Networking Services Overview	9 of 12

NWLink IPX/SPX Compatible Transport and Gateway Service for NetWare

The Microsoft NWLink IPX/SPX Compatible Transport protocol is an NDIS transport that provides communication between a Windows NT computer and another Windows NT computer or a NetWare computer. The NWLink protocol is also used by the Gateway Service for NetWare to support access to files and print queues that reside on NetWare servers. Microsoft NWLink can also support NetBIOS applications running over NWLink when the remote computer is also running NWLink or a compatible transport.

The Microsoft NWLink protocol is used to support Windows NT as an application server and to connect Windows NT computers with each other and with Windows for Workgroup computers in environments where the routers are set to handle IPX (and Novell NetBIOS) traffic. Because it supports Windows Sockets, the Microsoft NWLink protocol is ideal as an application server transport, allowing MS-DOS, Windows, and OS/2 clients to connect without modifying their current NetWare client software.

The Microsoft Client Service for NetWare, which can be installed in Windows NT Workstation computers, allows Windows NT computers to access files, directories, and printers on Novell NetWare servers. The Gateway Service for NetWare on Windows NT Server provides a file and print gateway that allows networking clients (computers running Windows NT, Windows for Workgroups, or LAN Manager 2.x) to access files on NetWare servers without having NetWare client software loaded.

For information about installing, configuring, and using the NWLink transport and Gateway Service for NetWare, see Chapter 4, "Gateway Service for NetWare."


Remote Access Service
Networking Services Overview	10 of 12

Remote Access Service

Windows NT Remote Access Service allows a user at a remote site to dial in to a Remote Access server and use the network as if the computer were directly connected to the network. Remote Access Service contains two main components:

Remote Access client, which is a computer that dials in to a remote access server to use the resource on a LAN. This component can be installed on a Windows NT Workstation computer.

Remote Access server, which is a computer that allows a remote computer to dial in to and use the resource on a LAN. This component is available only with Windows NT Server.

With Remote Access Service installed on a Windows NT computer, the RAS Phone Book program can be used to enter and maintain the names and telephone numbers of remote networks. Then you can use the Phone Book to connect to and disconnect from these remote networks.

The Remote Access Service also has the Remote Access Admin, a graphical user interface for system administrators. Through the Administrator's utility, you can do the following:

Start, stop, pause, or continue the Remote Access Service

Grant or revoke Remote Access permissions

Monitor Remote Access traffic and user accounts

For a brief overview of capabilities and installation steps, see Chapter 6, "Remote Access Service." For complete details, see Windows NT Server Remote Access Service.


Services for Macintosh
Networking Services Overview	11 of 12

Services for Macintosh

Services for Macintosh is a thoroughly integrated component of Windows NT Server, making it possible for PC and Apple Macintosh computers to share files and printers.

You can set up Services for Macintosh when you install Windows NT Server, or you can set up these components later. After Services for Macintosh is set up, an Server can also function as an AppleTalk® router. Routing capability is supported for AppleTalk Phase 2. The AppleTalk protocol is the layer of AppleTalk Phase 2 protocols that deliver data to a network destination.

With Services for Macintosh, Macintosh computers need only the Macintosh operating system software to function as computers; no additional software is required. You can, however, set up the optional user authentication module, which is software that provides a secure logon to the computer running Windows NT Server.

For a brief overview of capabilities and installation steps, see Chapter 7, "Services for Macintosh." For complete details, including guidelines for planning the network and administering Services for Macintosh, see Windows NT Server Services for Macintosh. It contains configuration instructions for the AppleTalk protocol in Chapter 5, "Configuring Services for Macintosh."


TCP/IP Protocol and Related Components
Networking Services Overview	12 of 12

TCP/IP Protocol and Related Components

This section contains updated information for Windows NT version 3.51. Click here to see the new information.

When TCP/IP is used as a transport protocol with Windows NT, Windows NT computers can communicate with other kinds of systems without additional networking software. Microsoft TCP/IP in combination with other parts of Windows NT provides a scalable solution for enterprise networks that include a mix of system types and that require simple, easy software solutions that work on many platforms.

When Microsoft TCP/IP is used as the enterprise networking protocol, Windows networking solutions can be used on an existing internetwork. Each of these solutions uses a transport-independent architecture to provide client and server support for TCP/IP and connectivity utilities. These solutions for a Microsoft network include:

Microsoft Windows NT, with enhancements for wide-area network (WAN) support, Windows Sockets support, and DHCP and WINS client software.

Microsoft Windows NT Server, including FTP Server service software plus DHCP server and WINS server software to support implementation of these new protocols.

Microsoft TCP/IP-32 for Windows for Workgroups 3.11,Microsoft's new 32-bit implementation of the industry standard TCP/IP internetworking protocols. TCP/IP-32 can be used in larger networks to provide access for Windows for Workgroups computers through TCP/IP to Windows NT, LAN Manager, and other TCP/IP systems.

Microsoft LAN Manager, including support for Windows Sockets and MS-DOS – based connectivity utilities.

The current version of TCP/IP for Windows NT also supports IP routing in systems with multiple network adapters attached to separate physical networks (multihomed systems).

For a summary of the steps for installing TCP/IP with Windows NT, see Chapter 5, "Microsoft TCP/IP." For complete information about configuring and using the various components, including setting up DHCP servers and WINS servers, see Windows NT Server TCP/IP.


Gateway Service for NetWare
Chapter 4	1 of 5

Gateway Service for NetWare

If part of your computer resources are on a Novell NetWare network, your Windows NT network will need to communicate and share resources with the NetWare network. With the Gateway Service for NetWare (Gateway Service), you can access NetWare file and print resources and share them with clients on the Microsoft network that have no NetWare connectivity software. You can also manage the NetWare network and run NetWare-aware applications from your Windows NT Server computer.

This chapter explains how to install and configure the Gateway Service for NetWare. It covers the following topics:

Preparing to install the Gateway Service

Installing the Gateway Service

Configuring the NWLink IPX/SPX Compatible Transport Protocol

Specifying a preferred NetWare server

For information on using the Gateway Service, see Windows NT Server Services for NetWare Networks.


Preparing to Install the Gateway Service
Gateway Service for NetWare	2 of 5

Preparing to Install the Gateway Service

Important

Before you install the Gateway Service, you must remove any NetWare redirectors, such as the Novell NetWare Services for Windows NT, and then restart your computer.

To remove existing NetWare redirector installations

1.	In Control Panel, choose the Network option.

2.	In the Network Settings dialog box, select the existing NetWare redirector software in the Installed Network Software box.

3.	Choose the Remove button.

4.	When Windows NT asks you to confirm your choice, choose the Yes button.

5.	In the Network Settings dialog box, choose the OK button.

6.	Restart your computer for the changes to take effect.

You are now ready to install the Gateway Service.


Installing the Gateway Service
Gateway Service for NetWare	3 of 5

Installing the Gateway Service

When you install the Gateway Service, the NetWare Link IPX/SPX Compatible Transport Protocol (NWLink) is also installed if it is not already on your computer.

You must be logged on as a member of the Administrators group for the local computer to install and configure the Gateway Service.

To install the Gateway Service for NetWare

1.	In Control Panel, choose the Network option.

2.	When the Network Settings dialog box appears, choose the Add Software button.

3.	In the Add Network Software dialog box, select Gateway Service for NetWare, and then choose the Continue button.

4.	Enter the path where the Gateway Service files are located when you are prompted by Windows NT Setup, and then choose the Continue button.

5.	In the Network Settings dialog box, choose the OK button.

6.	If the NWLink IPX/SPX Protocol Configuration dialog box appears, specify the network adapter card you want to use to communicate with the NetWare network, indicate the correct frame type for your network, and then choose the OK button.

The defaults in this dialog box do not normally need to be changed. If you need to, you can always change the settings later, as described in "Configuring the NWLink IPX/SPX Compatible Transport Protocol,” next in this chapter.

7.	To restart Windows NT so the changes take effect, choose the Yes button in the message that appears.

An option labeled GSNW is added to Control Panel when the Gateway Service is installed. The icon looks like the Network icon, except that one of the cable connectors is red.

The NetWare network is added to the first place in the network search order. For more information on the network search order, see "Setting Network Provider Search Order” in Chapter 5, "Control Panel,” in the Windows NT Server System Guide.


Configuring the NWLink IPX/SPX Compatible Transport Protocol
Gateway Service for NetWare	4 of 5

Configuring the NWLink IPX/SPX Compatible Transport Protocol

After the NetWare IPX/SPX Compatible Transport Protocol (NWLink) is installed on your computer, you can specify the network adapter card it will use and the frame type of your network. The default settings do not typically need to be changed, because they are optimized for most environments, but you can modify protocol parameters after installation if, for example, you want to bind the protocol to a different network adapter card.

To configure the NWLink protocol

1.	In Control Panel, choose the Network option.

2.	In the Installed Network Software box, select NWLink IPX/SPX Compatible Transport, and then choose the Configure button.

3.	In the Adapter box of the NWLink IPX/SPX Protocol Configuration dialog box, select the name of the adapter card to which you want to bind the transport.

4.	Select Auto Frame Type Detection (the default), or Manual Frame Type Detection if you want to manually specify the frame type or types for IPX/SPX packets on your network.

5.	If you choose Manual Frame Type Detection, the box on the left lists the frame types NWLink is using, and the box on the right lists the frame types that are available but not in use. To remove a frame type that is now in use, select it from the box on the left, and then choose the Remove button. To add a frame type, select it from the box on the right, and then choose the Add button.

6.	Choose OK to close the NWLink Configuration dialog box, and then choose OK to close the Network Settings dialog box.

7.	Windows NT prompts you to restart the computer so that the changes take effect. Choose the Yes button to restart the computer.

When you set the Frame Type to Auto Detected, NWLink checks the frames being passed to the network adapter card the protocol is bound to. If it detects any frames of type 802.2 or no frames at all, it sets the frame type to 802.2. Otherwise, it sets the frame type to whatever is being passed on the network. For NetWare 4.01 networks, the frame type is usually 802.3. For token ring networks, it is 802.5.

If your workstations and servers are on a token ring network, you can use the ipxroute command line utility to view and modify the network configuration on your computer. For more information, see "Managing IPX/SPX Routing on a Token Ring Network” in Windows NT Server Services for NetWare Networks.


Specifying a Preferred NetWare Server
Gateway Service for NetWare	5 of 5

Specifying a Preferred NetWare Server

The first time you log on after the Gateway Service is installed, you should specify the NetWare server you want your workstation to connect to by default. This server is referred to as your preferred server.

To specify a preferred server when logging on

In the Select Preferred Server for NetWare dialog box, select the name of a server on the NetWare network or select <None> from the list provided, and then choose the OK button.

- Or -

Type a server name directly in the Server box, and then choose the OK button.

If you chose <None>, the Gateway Service attempts to connect to the nearest available server each time you log on.

You can change your preferred server any time you are logged on. For information on changing the preferred server, see "Connecting to a NetWare Volume or Directory" in Windows NT Server Services for NetWare Networks.

Note

The preferred server setting affects only the account under which you are logged on when you make the setting. When other users log on, they are also prompted for a preferred server. If you later change your preferred server, other users are unaffected.


Microsoft TCP/IP
Chapter 5	1 of 7

Microsoft TCP/IP

Transmission Control Protocol/Internet Protocol (TCP/IP) is a networking protocol that provides communication across interconnected networks made up of computers with diverse hardware architectures and various operating systems. TCP/IP can be used to communicate with Windows NT computers, with devices using other Microsoft networking products, or with non-Microsoft systems, such as UNIX.

This chapter introduces Microsoft TCP/IP for Windows NT and describes how to install and configure TCP/IP components. The topics in this chapter include the following:

An overview of TCP/IP for Windows NT

A description of what is included with Microsoft TCP/IP

Instructions for installing Microsoft TCP/IP and FTP Server service

For detailed information about Microsoft TCP/IP and how it works with Windows NT and other networking products, or for details about TCP/IP services, utilities, and commands, see the Windows NT Server TCP/IP manual or the online Help that is installed with TCP/IP.

To get help on Microsoft TCP/IP networking solutions

In File Manager, double-click TCPIP.HLP in the \systemroot\SYSTEM32 directory.

To get help on TCP/IP utilities

1.	In the Program Manager Main group, double-click the Windows NT Help icon.

2.	In the Windows NT Help window, choose the Command Reference Help button.

3.	In the Commands window, choose a command name.

– Or –

In the Command Reference window, choose the Search button, and then type a command name in the box or select a command name from the list.


What Is TCP/IP for Windows NT?
Microsoft TCP/IP	2 of 7

What Is TCP/IP for Windows NT?

The TCP/IP protocol family is a standard set of networking protocols, or rules, that govern how data is passed between computers on a network. TCP/IP is used to support the Internet, the worldwide internetwork connecting universities, research labs, military installations, and corporations. (By convention, "Internet" is capitalized when referring to the worldwide internetwork.) The same protocols can be used in any private internetwork that connects several local area networks.

Microsoft TCP/IP enables enterprise networking and connectivity on Windows NT computers. Adding TCP/IP to a Windows NT configuration offers the following advantages:

A standard enterprise networking protocol that is the most complete and accepted protocol available. All modern operating systems offer TCP/IP support, and most large networks rely on TCP/IP for much of their network traffic.

A technology for connecting non-Microsoft systems. Many standard connectivity utilities are available to access and transfer data between various systems, including file transfer protocol (FTP) and terminal emulation protocol (Telnet). Several of these standard utilities are included with Windows NT.

A robust, scalable, cross-platform client-server framework. Microsoft TCP/IP offers the Windows Sockets 1.1 interface, which is ideal for developing client-server applications that can run with Windows Sockets-compliant stacks from other vendors. Many public-domain Internet tools are also written to the Windows Sockets standard. Windows Sockets applications can also take advantage of other networking protocols such as Microsoft NWLink, the Microsoft implementation of the IPX/SPX protocols used in Novell NetWare networks.

The technology necessary to connect Windows NT to the global Internet. TCP/IP, Point-to-Point Protocol (PPP), and Windows Sockets 1.1 provide the foundation needed to connect and use Internet services.


What Does Microsoft TCP/IP Include?
Microsoft TCP/IP	3 of 7

What Does Microsoft TCP/IP Include?

This section contains updated information for Windows NT version 3.51. Click here to see the new information.

Microsoft TCP/IP provides all the elements necessary to implement these protocols for networking, including:

Core TCP/IP protocols, including the Transmission Control Protocol (TCP), Internet Protocol (IP), User Datagram Protocol (UDP), Address Resolution Protocol (ARP), and Internet Control Message Protocol (ICMP). This suite of Internet protocols provide a set of standards for how computers communicate and how networks are interconnected. Support is also provided for PPP and Serial Line IP (SLIP), which are protocols used for remote access connections.

Support for application interfaces, including Windows Sockets 1.1 for network programming, remote procedure call (RPC) for communicating between systems, NetBIOS for establishing logical names and sessions on the network, and network dynamic data exchange (Network DDE) for sharing information embedded in documents across the network.

Basic TCP/IP connectivity applications, including finger, ftp, lpr, rcp, rexec, rsh, telnet, and tftp. These utilities allow Windows NT users to interact with and use resources on non-Microsoft hosts, such as UNIX workstations.

TCP/IP diagnostic tools, including arp, hostname, ipconfig, lpq, nbtstat, netstat, ping, route, and tracert. These utilities can be used to detect and resolve TCP/IP networking problems.

Services and related administrative tools, including the FTP Server service for transferring files between remote computers, Windows Internet Name Service (WINS) for dynamically registering and querying computer names on an internetwork, Dynamic Host Configuration Protocol (DHCP) service for automatically configuring TCP/IP on Windows NT computers, and TCP/IP printing for accessing printers connected to a UNIX computer or connected directly to the network via TCP/IP.

Simple Network Management Protocol (SNMP) agent. This component allows a Windows NT computer to be administered remotely using remote management tools, such as Sun Net Manager or HP Open View.

The client software for simple network protocols, including Character Generator, Daytime, Discard, Echo, and Quote of the Day. These protocols allow a Windows NT computer to respond to requests from other systems that support these protocols. When these protocols are installed, a sample QUOTES files is also installed in the \systemroot\SYSTEM32\DRIVERS\ETC directory.

Path MTU Discovery, which provides the ability to determine the datagram size for all routers between Windows NT computers and any other systems on the WAN. Microsoft TCP/IP also supports the Internet Gateway Multicast Protocol (IGMP), which is used by new workgroup software products.

Performance counters for tracking the performance of TCP/IP protocols and the FTP Server service. To view these counters, run Performance Monitor in the Administrative Tools group in Program Manager. For information about these counters, see the TCP/IP online Help.

The following diagram shows the basic elements of Microsoft TCP/IP alongside the variety of additional applications and connectivity utilities provided by Microsoft and other developers.

Microsoft TCP/IP: Core Technology and Third-Party Add-ons

In this version of Windows NT, Microsoft TCP/IP does not include graphical TCP/IP utilities, Network File System (NFS) support, or some TCP/IP servers (sometimes called daemons) such as routed and telnetd. Many such applications and utilities are available in the public domain or through third-party vendors and work with Microsoft TCP/IP.


Installing and Configuring Microsoft TCP/IP and SNMP
Microsoft TCP/IP	4 of 7

Installing and Configuring Microsoft TCP/IP and SNMP

This section explains briefly how to install TCP/IP and the SNMP service for Windows NT and how to configure the protocols on your computer. For complete details, see Chapter 2, "Installing and Configuration Microsoft TCP/IP and SNMP," in Windows NT Server TCP/IP.

The TCP/IP protocol family is not installed as part of the Windows NT product during Express Setup. You can choose to install Microsoft TCP/IP components during Custom Setup or after Windows NT Setup is finished. This section assumes that Windows NT has already been successfully installed on your computer.

Windows NT users who install Remote Access Service (RAS) for remote networking maintain all the benefits of TCP/IP networking, including access to the DHCP, WINS, and DNS access capabilities of Microsoft TCP/IP. To configure RAS to use TCP/IP as a network protocol, follow the procedures described in Chapter 6, "Remote Access Service."


Before Installing Microsoft TCP/IP
Microsoft TCP/IP	5 of 7

Installing and Configuring Microsoft TCP/IP and SNMP

Before Installing Microsoft TCP/IP

The network administrator must supply the following information before you install Microsoft TCP/IP on a Windows NT computer:

Whether you can use Dynamic Host Configuration Protocol (DHCP) to configure your computer. You can choose this option if a DHCP server is installed on your internetwork. You cannot choose this option if this computer will be a DHCP server.

Whether this computer will be a DHCP server. This option is available only for Windows NT Server.

Whether this computer will be a Windows Internet Name Service (WINS) server. This option is available only for Windows NT Server.

Whether this computer will be a WINS proxy agent.

If you cannot use DHCP for automatic configuration, you must obtain the following values from your network administrator so that you can configure TCP/IP manually:

The IP address and subnet mask for each network adapter card installed on the computer

The IP address for the default local gateway (IP router)

Whether your computer will use Domain Name System (DNS) and, if so, the IP addresses of the DNS servers on the internetwork

WINS server addresses, if WINS servers are available on your network

You need to know the following information before you install the Simple Network Management Protocol (SNMP) service on your computer:

Community names in your network

Trap destination for each community

IP addresses and computer names for SNMP management hosts


Installing TCP/IP
Microsoft TCP/IP	6 of 7

Installing and Configuring Microsoft TCP/IP and SNMP

Installing TCP/IP

You must be logged on as a member of the Administrators group to install and configure TCP/IP and any of its components.

To install Microsoft TCP/IP components on a Windows NT computer

1.	In Control Panel, choose the Network option.

2.	In the Network Settings dialog box, choose the Add Software button.

3.	In the Network Software Installation dialog box, select TCP/IP Protocols And Related Components in the Network Software list box, and then choose the Continue button.

4.	In the Windows NT TCP/IP Installation Options dialog box, check the options for the components you want to install, as described in the following list, and then choose the OK button.

Option		Usage
TCP/IP Internetworking		Includes the TCP/IP protocol, NetBIOS over TCP/IP, Windows Sockets 1.1 interface, and the TCP/IP diagnostic utilities.
Connectivity Utilities		Installs the TCP/IP utilities. Select this option to install the connectivity utilities finger, ftp, lpr, rcp, rexec, rsh, telnet, and tftp, and the diagnostic utilities arp, hostname, ipconfig, lpq, nbtstat, netstat, ping, route, and tracert.
SNMP Service		Installs the SNMP service. Select this option to allow this computer to be administered remotely using management tools, such as SUN Net Manager or HP Open View. This option also allows you to monitor statistics for TCP/IP services using Performance Monitor.
TCP/IP Network Printing Support		Allows this computer to print directly over the network using TCP/IP. Select this option if you want to print to UNIX print queues or TCP/IP printers that are connected directly to the network, or if you want UNIX computers on the network to print to Windows NT print servers.
FTP Server Service		Allows files on this computer to be shared over the network with any remote computers that support the file transfer protocol (FTP) and TCP/IP (especially non-Microsoft network computers). Select this option if you want to use TCP/IP to share files with other computers.
Simple TCP/IP Services		Provides the TCP/IP services Chargen, Daytime, Discard, Echo, and Quote. Select this option to allow this computer to respond to requests from other systems that support these protocols.
DHCP Server Service		Installs the server software to support automatic configuration and addressing for computers using TCP/IP on your internetwork. Select this option if this computer is to be a DHCP Server. If you select this option, you must manually configure the IP address, subnet mask, and default gateway for this computer. You must also provide configuration information for the systems that use this service for automatic TCP/IP configuration.
WINS Server Service		Installs the server software to support Windows Internet Name Service, a dynamic name resolution service for computers on a Windows internetwork. Select this option if this computer is to be installed as a primary or secondary WINS server. Do not select this option if this computer will be a WINS proxy agent.
Enable Automatic DHCP Configuration		Turns on automatic configuration of TCP/IP parameters for this computer. Select this option if there is a DHCP server on your internetwork to support dynamic host configuration. This is the preferred method for configuring TCP/IP on most Windows NT computers.
You can read the hint bar at the bottom of each TCP/IP dialog box for information about a selected item, or choose the Help button to get detailed online information while you are installing or configuring TCP/IP.

5.	Windows NT Setup displays a message asking for the full path to the Windows NT distribution files. Provide the appropriate location, and choose the Continue button.

All necessary files are copied to your hard disk.

6.	If you did not check the Enable Automatic DHCP Configuration option, continue with the configuration procedures, as described in the online Help for these dialog boxes.

If you checked the Enable Automatic DHCP Configuration option, your computer will be configured automatically for TCP/IP after you restart your computer.

TCP/IP must be configured in order to operate.

If you have trouble installing Microsoft TCP/IP on your computer, follow the suggestions in the error messages. You can also use diagnostic utilities such as ping to isolate network hardware problems and incompatible configurations. For information, see the topic "Troubleshooting with TCP/IP Diagnostic Utilities" in the online Help for Microsoft TCP/IP.

For information about configuring and using Microsoft TCP/IP, see the Windows NT Server TCP/IP manual.


Installing Microsoft FTP Server Service
Microsoft TCP/IP	7 of 7

Installing Microsoft FTP Server Service

The Microsoft FTP Server service allows a Windows NT computer to transfer files to and from remote computers that support the file transfer protocol (FTP) and TCP/IP protocols. The FTP Server service supports all Windows NT FTP client commands. Non-Microsoft versions of FTP clients may contain commands that are not supported.

The FTP Server service is integrated with the Windows NT security model. Users connecting to the FTP Server service are authenticated based on their Windows NT user accounts and receive access based on their user profiles. For this reason, it is recommended that the FTP Server service be installed on an NTFS partition so that the files and directories made available via FTP can be secured.

Caution

The FTP Server protocol relies on the ability to pass user passwords over the network without data encryption. A user with physical access to the network could examine user passwords during the FTP validation process.

This section assumes that you have installed Microsoft TCP/IP and any necessary devices and device drivers.

The FTP Server service is not installed automatically because of the security risks mentioned previously. You must be logged on as a member of the Administrators group to install and configure the FTP Server service.

To install the FTP Server service

1.	In Control Panel, choose the Network option.

2.	In the Network Settings dialog box, choose the Add Software button.

3.	If TCP/IP has not been installed, select TCP/IP Protocols and Related Components in the Network Software box, and then choose the Continue button.

4.	In the Windows NT TCP/IP Installation Options dialog box, select the FTP Server Service Option, and then choose the OK button.

– Or –

If TCP/IP is already installed, select FTP Server Service in the Network Software box, and then choose the Continue button.

A warning message prompts you to confirm that you are familiar with FTP Security.

5.	Choose the Yes button to continue with FTP Server installation.

A message asks you for the full path to the Windows NT distribution files. Provide the appropriate location, and choose the Continue button.

6.	After the necessary files are copied to your computer, the FTP Service dialog box appears.

Continue with the configuration procedure as described in the next section. The FTP Server service must be configured in order to operate.

Note

For disk partitions that do not use NTFS, you can apply simple read/write security by using the FTP Server option in Control Panel, as described in the online Help for this option.

For information about configuring and administering the FTP Server service, see the Windows NT Server TCP/IP manual.


Supplemental Information About TCP/IP

Changed Functionality for Command-Line Utilities


Remote Access Service
Chapter 6	1 of 5

Remote Access Service

This chapter introduces Windows NT Remote Access Service (RAS) and describes how to install RAS. The topics in this chapter include the following:

An overview of Windows RAS components

Instructions for installing RAS

For detailed information about RAS and how it works with Windows NT and other networking products, see the Windows NT Server Remote Access Service manual or RAS online Help.


Remote Access Service Overview
Remote Access Service	2 of 5

Remote Access Service Overview

RAS allows remote users to work as if they are connected directly to the network. The RAS connection is transparent to Microsoft clients and network applications.

A Windows NT RAS configuration will include the following components:

Remote access clients

Windows NT, Windows for Workgroups, MS-DOS, and LAN Manager RAS clients can all connect to a Windows NT RAS server. Clients can also be any PPP client.

Remote access protocols

Windows NT version 3.5 RAS servers support the PPP protocol, enabling any PPP client to use TCP/IP, IPX, or NetBEUI. Windows NT version 3.5 clients can also access the large installed base of SLIP remote access servers. The Microsoft RAS protocol allows any Microsoft RAS client to dial in.

WAN options

Clients can dial in using standard telephone lines and a modem or modem pool. Faster links are possible using ISDN. You can also connect RAS clients to RAS servers using X.25 or an RS-232C null modem.

Security options

Windows NT logon and domain security, support for security hosts, data encryption, and callback provide secure network access for remote clients.

RAS servers

The Windows NT Server RAS permits up to 256 remote clients to dial in. The RAS server can be configured to provide access to an entire network or restrict access to the RAS server only.

LAN protocols

IP protocol support permits accessing a TCP/IP network, such as the global Internet. IPX protocol support enables remote clients to access NetWare servers and printers. You can also use NetBIOS applications over IPX, TCP/IP, or NetBEUI. Windows Sockets applications over TCP/IP or IPX, named pipes, Remote Procedure Call (RPC), and the LAN Manager API are supported.

The following illustrates all RAS features and possible configurations. Actual implementations and configurations will vary and are discussed in the Windows NT Server Remote Access Service manual.

Overview of Windows NT Server RAS


Installing RAS
Remote Access Service	3 of 5

Installing RAS

This section describes how to install Windows NT Remote Access Service (RAS) on your computer. The default configuration settings are usually ideal. For more information on configuring RAS, see the Windows NT Server Remote Access Service manual or RAS online Help.

RAS can be installed during Custom Setup or after the initial Windows NT Setup is finished. During Express Setup, if there is not a network card in a computer, the user is given the option to install RAS. This section assumes that Windows NT has already been successfully installed on your computer.

You must be logged on as a member of the Administrators group to install and configure RAS.


Hardware Requirements for RAS
Remote Access Service	4 of 5

Hardware Requirements for RAS

Before you install RAS, all hardware should be installed and working. Depending on your network and requirements, you may need the following hardware:

Network adapter card with a certified Network Driver Interface Specification (NDIS) driver

One or more compatible modems (see the Hardware Compatibility List or the Remote Access Setup program)

Multiport adapter card, for acceptable performance with multiple remote connections

X.25 smart card, if using an X.25 network

ISDN card, if using an ISDN line

See the Hardware Compatibility List to verify the compatibility of all hardware in a Windows NT computer.


Installing Remote Access Software
Remote Access Service	5 of 5

Installing Remote Access Software

RAS installation will vary slightly depending on the network protocols you have installed. If you will use the TCP/IP or IPX protocol with RAS, you should install the protocol before you install RAS, although selecting a protocol that is not installed will cause that protocol to be installed at the conclusion of RAS Setup. For information about installing either protocol, see the appropriate chapter in this manual.

To add the Remote Access software

1.	In Control Panel, choose the Network option.

2.	In the Network Settings dialog box, choose the Add Software button.

3.	From the Network Software list, select Remote Access Service and then choose the Continue button.

When prompted for the path to the distribution files, provide the path and choose the OK button. The RAS files will be copied to your computer.

4.	In the Add Port dialog box, you will see a list of all ports available to Windows NT for RAS. If you have successfully installed a multiport adapter, ISDN card, X.25 card, or other device, you should see it in this list.

Select the port you will use for remote access and choose the OK button.

5.	Remote Access Setup will offer to automatically detect the modem connected to the selected port. Choose Cancel to manually select a modem or choose the OK button to automatically detect the modem.

A dialog box will appear announcing the modem detected. Choose the OK button.

Occasionally, when attempting to detect a modem, Remote Access Setup may present a dialog box requiring you to select your modem from a short list of possible modems. This occurs only when Remote Access Setup cannot distinguish between two or more modems.

6.	In the Configure Port dialog box, the modem detected will be highlighted.

If RAS did not detect your modem, or if you chose to manually select the modem, select the device attached to the port from the list. Only supported modems are listed. If you are adding a port after initial RAS installation, you can use the Detect button to automatically detect the modem connected to the new port.

7.	In the Port Usage box, choose how the port is to be used.

Dial Out Only means the computer will be a RAS client only. Receive Calls Only means the computer will be a RAS server only. Dial Out And Receive Calls means the computer can be a client or server, however, the computer cannot do both at the same time.

8.	To configure information specific to the type of device attached to the port, select the device and choose the Settings button. The default settings are usually ideal. Choose the OK button.

9.	In the Remote Access Setup dialog box, configure RAS network-wide settings by choosing the Network button.

You can also configure or reconfigure the ports as desired by highlighting the desired port and using the buttons along the bottom of the port box.

Consult the following table for a description of each button's use. Default settings are usually ideal.

Option		Use to
Add		Make a port available to RAS.
Remove		Make a port unavailable to RAS.
Configure		Change the Remote Access settings for the port, such as the attached device or the intended usage (dialing out only, receiving calls only, or both).
Clone		Copy the same modem setup from one port to another.
Continue		Proceed to the next step in Setup when you finish with this dialog box.
Cancel		Leave the Setup program.
Network		Configure RAS server-wide settings. Set network access to entire network or RAS computer only. Select and configure network protocols the RAS server will support. Select network protocols the computer will use for dial-out (client) connections. Set authentication and data encryption options.
Disable Automatic Restoration Of Network Connections At Logon		Clear this check box to restore your previous network connections when you log on to your computer. This box is selected by default because restoring connections over a remote link can be especially time consuming.
10.	Choose the Continue button when you are finished setting up the port and network configurations.

RAS Server Configuration dialog boxes will appear for the protocols installed on your computer; you will need to configure LAN protocols for RAS use.

Remote Access Setup configures RAS, creates a Remote Access Service program group, and then confirms that installation was successful.

11.	Choose the OK button in the confirmation dialog box, and choose the OK button in the Network Settings dialog box.

You may be prompted to confirm network protocol or other settings.

12.	You must restart your computer for the Remote Access installation and configuration take effect.

When you return to Program Manager, you will see a new group called Remote Access Service.

For more information on configuring RAS, see the Windows NT Server Remote Access Service manual or RAS online Help.


Services for Macintosh
Chapter 7	1 of 3

Services for Macintosh

Microsoft Windows NT Server Services for Macintosh is a thoroughly integrated component of Microsoft Windows NT Server, making it possible for MS-DOS, Windows, Windows for Workgroups, Windows NT, and Apple Macintosh computers to share files and printers.

When you install Windows NT Server, you can choose to set up Services for Macintosh, or you can set up Services for Macintosh later. Once Services for Macintosh is set up, a computer running Windows NT Server can also function as an AppleTalk router. Routing capability is supported for AppleTalk Phase 2.

With Services for Macintosh, Macintosh computers need only the Macintosh operating system software to function as workstations; no additional software is required. You can, however, set up the optional user authentication module, which is software that provides a secure logon to the computer running Windows NT Server.

For complete information, including guidelines for planning the network and administering Services for Macintosh, see Windows NT Server Services for Macintosh.


Setting Up from Windows NT Server
Services for Macintosh	2 of 3

Setting Up from Windows NT Server

You can set up Services for Macintosh at the same time you install Windows NT Server, or you can set it up later. Either way, you set up, or enable, Services for Macintosh using the Network icon in Control Panel and the Windows NT Server distribution disk.

If you remove Services for Macintosh and later decide to set it up again, you must use the Windows NT Server distribution disk and installation program to copy the required Services for Macintosh files to the server. Removing Services for Macintosh deletes the distribution files (except Macintosh-accessible volumes) instead of disabling them.

You must be an administrator or have administrator permissions to use the Network icon in Control Panel, which is used to set up Services for Macintosh.

When you set up Services for Macintosh, the AppleTalk Protocol, File Server for Macintosh, and the Print Server for Macintosh are started, or enabled. An explanation for each of these follows.

The AppleTalk Protocol is the layer of AppleTalk Phase 2 protocols that deliver data to its destination on the network. The AppleTalk Protocol can be configured through the Network icon in Control Panel. Configuration instructions for the AppleTalk Protocol appear in Chapter 5, "Configuring Services for Macintosh," in Windows NT Server Services for Macintosh.

File Server for Macintosh, also called MacFile, allows you to designate a directory as a Macintosh-accessible volume, ensures that Macintosh filenames are legal NTFS names, and handles permissions. When set up, File Server for Macintosh commands appear in the Windows NT Server File Manager and Server Manager under the MacFile menu. Instructions for configuring it appear in Chapter 5, "Configuring Services for Macintosh," in Windows NT Server Services for Macintosh.

Print Server for Macintosh, also called MacPrint, allows all network users to send print jobs to a spooler on the computer running Windows NT Server and continue working, rather than waiting for their print jobs to complete. Windows-based users can also review the print jobs in Print Manager. For more information, see Chapter 6, "Setting Up Printers," in Windows NT Server Services for Macintosh.

Setting up Services for Macintosh creates an icon in Control Panel, which gives you the same server administration capabilities as the MacFile menu, excluding volume management, for the local computer.

To set up Services for Macintosh

1.	In Control Panel, choose the Network option.

2.	In the Network Settings dialog box, choose the Add Software button.

3.	From the Network Software list in the Add Network Software dialog box, select Services for Macintosh, and then choose the Continue button.

4.	When the Windows NT Setup dialog box appears, type the path to the Windows NT Server distribution files and choose the Continue button:

Setup copies all Services for Macintosh files.

5.	From the Network Settings dialog box, choose the OK button.

6.	When the AppleTalk Protocol Configuration dialog box appears, you can select a zone, select a different network, or enable Apple Talk routing. Make the changes you want and then choose the OK button, or choose Cancel if you don't want to change the configuration.

7.	In the Network Settings Change dialog box, choose the Restart Now button for the changes to take effect.

For information about setting up from the network and setting up for remote administration, see Windows NT Server Services for Macintosh.


Stopping and Removing Services for Macintosh
Services for Macintosh	3 of 3

Stopping and Removing Services for Macintosh

After you have set up Services for Macintosh on a server, you can remove it at any time. For example, you might want to move your Services for Macintosh installation to another server. When you remove Services for Macintosh, all Services for Macintosh files are deleted from the server's hard disk, except some program files that are in use. (The files in use will be reworked when the system is rebooted.)

Before you remove Services for Macintosh, you should stop the services using the Devices option in Control Panel.

To stop the services

1.	In Control Panel, choose the Devices option.

2.	From the Device list in the Devices dialog box, select AppleTalk Protocol.

3.	Choose the Stop button.

4.	Choose the OK button in the Stopping dialog box to stop the AppleTalk Protocol and the Print and File Servers for Macintosh.

Now you're ready to remove Services for Macintosh.

To remove Services for Macintosh

1.	In Control Panel, choose the Network option.

2.	In the Installed Network Software box of the Network Settings dialog box, select Services for Macintosh.

3.	Choose the Remove button.

4.	Choose the Yes button to confirm that you want to remove the Services for Macintosh files from the computer running Windows NT Server.

5.	Choose the OK button.

You must restart your computer.

The AppleTalk Protocol and the File and Print Servers for Macintosh will all be deleted. Removing Services for Macintosh will also make all volumes unavailable to the Macintosh users, but it will not delete them; in other words, the volumes will revert to directories.

For information about setting up the Services for Macintosh workstation software and setting up printers, see Windows NT Server Services for Macintosh.


Remoteboot
Chapter 8	1 of 42

Remoteboot

The Remoteboot service is a Windows NT Server feature that starts MS-DOS and Microsoft Windows workstations over the network. You install and configure the Remoteboot service on the server and then customize it to be more effective for your particular network and for your users' needs.

This chapter provides the following information:

Understanding the Remoteboot service

Setting up and starting the Remoteboot service

Managing remoteboot workstations

Optimizing the Remoteboot service

Directory, and configuration file details

Supporting other protocols

For updated information about the Remoteboot service, see the \systemroot\RPL\README.TXT file. If you have a Windows NT Server disk set rather than a compact disc, the README.TXT file is on the Remoteboot Disk 1.

\systemroot\RPL is the default location of the remoteboot directory. If you chose a different location to install the remoteboot directory, substitute that location for \systemroot\RPL throughout this chapter.


Understanding the Remoteboot Service
Remoteboot 	2 of 42

Understanding the Remoteboot Service

This section describes the architecture and operation of the Windows NT Server Remoteboot service.

For complete information about Windows NT file systems, security, and network planning issues, see the Windows NT Server Concepts and Planning Guide. This information will help you take best advantage of Windows NT at your site.


The Remoteboot Process
Remoteboot 	3 of 42

Understanding the Remoteboot Service

The Remoteboot Process

When you start, or boot, a computer, the operating system is loaded into its memory. The Windows NT Remoteboot service supports MS-DOS and Microsoft Windows personal computers (also called workstations) that boot using software on the server's hard disk instead of the workstation's hard disk. Each of these workstations has a network adapter, with a Remote Initial Program Load (RPL) ROM chip, that retrieves startup and configuration software from the server when the workstation starts. The workstation does not need a hard disk. This process is known as booting remotely or the remoteboot process..


How Does Remoteboot Work?
Remoteboot 	4 of 42

Understanding the Remoteboot Service

How Does Remoteboot Work?

The Remoteboot service works by providing two kinds of resources at the server:

A boot block, which contains all the information needed to start the workstation when it boots.

The remoteboot profile, which defines the operating system environment of the workstation after it boots.

The boot block and remoteboot profile are sent across the network in frames. A frame is a chunk of data, with some extra information. Sending a frame can be thought of as mailing a package of data, with the address and instructions for its use written on it.

When a remoteboot workstation is powered up, the network adapter is initialized and broadcasts a FIND frame (a boot request). The Remoteboot service receives the FIND frame, which contains the workstation's adapter ID.

The Remoteboot service checks the remoteboot database on the server to see if a workstation record already exists with this adapter ID. If not, the Remoteboot service records this adapter ID but does not boot the workstation. To boot the workstation, the administrator must convert this adapter ID record to a workstation record using Remoteboot Manager.

If a workstation record does exist with this adapter ID, the Remoteboot service sends a FOUND frame, containing the server's adapter ID, to the RPL ROM on the workstation.

The RPL ROM accepts the first FOUND frame it receives (it may receive more than one if several servers are running the Remoteboot service), and returns the SEND.FILE.REQUEST frame to the adapter ID of the server that sent the first FOUND frame.

When the Remoteboot service receives the SEND.FILE.REQUEST frame, it uses FILE.DATA.RESPONSE frames to send a boot block to the RPL ROM. The workstation record in the remoteboot database specifies which boot block to send. When the RPL ROM receives the last FILE.DATA.RESPONSE frame, it transfers execution to the entry point of the boot block.

The RPL ROM boots the operating system specified by the boot block as appropriate for the workstation.


Why Use Remoteboot?
Remoteboot 	5 of 42

Understanding the Remoteboot Service

Why Use Remoteboot?

The Remoteboot service promotes the use of diskless workstations by eliminating the need for a hard disk on each workstation, which has several advantages:

Increased network security by using workstations that do not have disk drives that can be used to copy data and to introduce viruses

Greater control over the distribution of information and software resources

Ease of updating software centrally

Reduced cost in buying and maintaining workstations

Using the Remoteboot service has advantages for workstations with hard disks as well:

Easy upgrading of software and operating systems on many workstations

Greater flexibility in standardizing workstations while allowing custom configurations

In general, Remoteboot offers greater control to the network administrator.


Setting Up and Starting the Remoteboot Service
Remoteboot 	6 of 42

Setting Up and Starting the Remoteboot Service

Before you can use the Remoteboot service, you must install a network adapter containing an RPL ROM chip on each workstation you plan to boot remotely. These adapters are available directly from network adapter manufacturers or from independent vendors. For more information about network adapters and RPL ROMs, contact your solution provider. A list of supported network adapters is provided later in this chapter.

To set up the Remoteboot service (summary)

1.	Install Windows NT Server. There are two special considerations for the Remoteboot service:

The server's computer name must not have spaces in it.

It is strongly recommended that you install remoteboot files on a disk partition formatted with NTFS so that permissions are correctly set. Users will be able to read and write to their own files in the remoteboot directory but not write to shared or system configuration files. Also, the FAT file system does nto support more than approximately 100 remoteboot workstations.

2.	Install the Remoteboot service. Or, convert an existing Microsoft LAN Manager for OS/2 remoteboot installation to run on Windows NT Server, and then install the Remoteboot service.

Note

Windows NT Server does not support remote booting of OS/2 workstations.

3.	Install the MS-DOS and/or Microsoft Windows operating system files. If you are converting from LAN Manager remoteboot, this may not be necessary.

4.	Start the Remoteboot service.

5.	Check the installation for errors.

6.	Create profiles (these define the working environment shared by one or more workstations).

This section provides step-by-step instructions for these actions. For instructions on managing remoteboot workstations, see "Managing Remoteboot Workstations," later in this chapter.


Disk Space Requirements
Remoteboot 	7 of 42

Setting Up and Starting the Remoteboot Service

Disk Space Requirements

The first step in preparing to use the Remoteboot service is to ensure the server has enough disk space for the files needed by the remote workstations. Use the values in the following table for a guideline.

Component		Disk space required
Network Client version 2.2 for MS-DOS(LAN Manager version 2.2)		5.1 MB
MS-DOS 3.30		0.7 MB
MS-DOS 4.01		1.5 MB
MS-DOS 5.00		2.8 MB
MS-DOS 6.xx		5.9 MB
Microsoft Windows 3.1		12.4 MB
Use this table to calculate the amount of disk space you need for the remoteboot configuration on your network. For example, to install the Remoteboot service for a configuration of workstations running MS-DOS 3.30 and MS-DOS 6.22, some with Microsoft Windows 3.1, you need 24.1 MB of disk space, broken down as follows:

5.1 MB for the Network Client 2.2 for MS-DOS files

0.7 MB for the MS-DOS 3.30 files

5.9 MB for the MS-DOS 6.22 files

12.4 MB for the Windows 3.1 files

In addition, you need room for personal copies of remoteboot profiles (if needed) and for directories for each workstation, where people store their own data. The amount of space to allot per workstation is up to you.


Supported Network Adapters
Remoteboot 	8 of 42

Setting Up and Starting the Remoteboot Service

Supported Network Adapters

These specific network adapters are supported on the workstation by the Remoteboot service (for the latest list see \systemroot\RPL\README.TXT):

3Com® EtherLink®		IBM Ethernet
3Com EtherLink II®		IBM® Token Ring
3Com EtherLink Plus		Intel® EtherExpress 16
3Com EtherLink /MC		Nokia®/ICL Ethernet IIe
3Com EtherLink III		Novell® NE1000
3Com TokenLink®		Novell NE2000
3Com TokenLink III		Racal Interlan NI 5210
3Com 3Station®		Racal Interlan NI 6510
AMD Series 2100 Ethernet		Western Digital™/SMC Ethernet
HP® Ethertwist®		Western Digital/SMC EtherCard™ Plus (8000 series)
Most network adapters work best with the Remoteboot service when using their default settings. However, if you need to modify these default settings in the PROTOCOL.INI files, these files are located in \systemroot\RPL\BBLOCK\NETBEUI\adapter\PROTOCOL.INI, where adapter is the name of the particular network adapter.


Installing the Remoteboot Service on the Server
Remoteboot 	9 of 42

Setting Up and Starting the Remoteboot Service

Installing the Remoteboot Service on the Server

Have on hand the Windows NT Server compact disc or floppy disks. You will also need original product disks for any operating system that you want the remoteboot workstations to run, such as MS-DOS or Microsoft Windows disks.

The installation procedure differs depending on whether you are installing a new remoteboot directory or converting an existing LAN Manager for OS/2 remoteboot directory. Use one of the two following procedures.

To install the Remoteboot service (with a new remoteboot directory)

1.	If they are not already installed, install the DLC and NetBEUI protocols on the server. The Remoteboot service requires DLC and NetBEUI. (For details about installation, see Chapter 3, "Networking Services Overview.")

2.	In Control Panel, choose the Network icon.

3.	In the Network Settings dialog box, choose the Add Software button.

4.	In the Add Network Software dialog box, select the Remoteboot Service.

5.	In the Remoteboot Setup dialog box, type the full path and directory name where you want to install the remoteboot directory.

The default value is \systemroot\RPL. This is the directory shown in descriptions and examples throughout this book.

6.	Choose the OK button.

7.	Complete the dialog boxes that appear. For help with any dialog box, press F1.

8.	When you run the Remoteboot Manager application, use the Fix Security command to set permissions throughout the remoteboot directory and to create necessary user accounts and groups.

See the post-installation information after the next procedure.

To install the Remoteboot service (converting a LAN Manager for OS/2 remoteboot directory)

1.	Use the Windows NT Server Upgrade for LAN Manager tools to convert the LAN Manager server' user accounts and file permissions. Then the remoteboot conversion can properly assign permissions and user account properties.

2.	On the Windows NT Server computer, delete the RPLUSER global group (it is created by the Upgrade for LAN Manager tools). The Fix Security command of Remoteboot Manager will create a RPLUSER local group.

Note that users who administer the Windows NT Remoteboot service must be members of the Administrators local group. The Upgrade for LAN Manager tools convert the LAN Manager RPLADMIN group to a Windows NT RPLADMIN global group but it has no function under Windows NT.

3.	Copy the entire remoteboot directory from the OS/2 server to the Windows NT Server computer. For example, if the LAN Manager remoteboot directory is \\SERVER3\C$\LANMAN\RPL and the Windows NT remoteboot directory is C:\WINNT\RPL, type the following command at the Windows NT server computer:

xcopy /e \\server3\c$\lanman\rpl c:\winnt\rpl

Keep a copy of the RPL directory for later reference. Be especially sure to make backup copies of .any INI, .CNF, and .FIT files that were modified from their default state.

4.	If it is not already installed, install the DLC protocol on the server. The Remoteboot service requires DLC. (For details about installation, see Chapter 3, "Networking Services Overview.")

5.	In Control Panel, choose the Network icon.

6.	In the Network Settings dialog box, choose the Add Software button.

7.	In the Add Network Software dialog box, select the Remoteboot Service.

8.	In the Remoteboot Setup dialog box, make the following choices:

In the Remoteboot Directory box, type the full path and directory name of the remoteboot directory on the Windows NT Server (for example, C:\WINNT\RPL).

Select the Migrate Remoteboot Directory from LAN Manager 2.2 check box.

9.	Choose the OK button.

10.	Complete the dialog boxes that appear. For help with any dialog box, press F1.

11.	Copy the new LAN Manager client software to locations in the Windows NT Server computer's RPL directory, using the following commands:

xcopy /e d:\clients\rpl\bblock   systemroot\rpl\bblock

xcopy /e d:\clients\rpl\fits   	systemroot\rpl\fits

xcopy /e d:\clients\rpl\rplfiles   systemroot\rpl\rplfiles

where d:  is the computer's compact disc drive.

If you have a Windows NT Server disk set rather than a compact disc, see the \systemroot\RPL\README.TXT file for different instructions.

12.	Run the rplcnv conversion program after Remoteboot installation. The rplcnv program converts the RPL.MAP and RPLMGR.INI files used by the LAN Manager Remoteboot service into the SYSTEM.MDB and RPLSVC.MDB files used by the Windows NT Remoteboot service database.

This is the syntax for rplcnv:

rplcnv [path]

where path specifies an absolute path to the directory containing the RPL.MAP and RPLMGR.INI files. If this parameter is omitted, it is assumed that the files are in the current directory or in \systemroot\RPL.

13.	Examine the new .INI, .CNF, and .FIT files in the Remoteboot directory and compare them to the backup copies you made before conversion. If you had modified the OS/2 versions of these files, you may want to transfer those modifications to the Windows NT versions. Do not simply copy the OS/2 versions over the Windows NT versions, as you might overwrite new data.

14.	In step 11 you installed new configurations. If you have profiles that you want to preserve from the LAN Manager installation, modify the profiles' AUTOEXEC.BAT and CONFIG.SYS files as follows:

AUTOEXEC.BAT:  @RPLLINK is no longer needed; this file has been replaced with RPLLNK.SYS which is loaded from CONFIG.SYS.

CONFIG.SYS:  Add the following line as the first line in the file:

DEVICE=C:\BINR\RPLLNK.SYS

15.	When you run the Remoteboot Manager application, use the Fix Security command to set permissions throughout the remoteboot directory and to create necessary user accounts and groups.

Whether you install a new RPL directory or magrate from OS/2, the installation process creates the following major directories:

RPL (at the location you specify during installation and with a different name if you want). This is the remoteboot directory.

RPL\BBLOCK. This directory contains boot blocks for each workstation configuration.

RPL\FITS. This directory contains file index table (FIT) files that translate references to a file on the workstation to a true path to the file on the server. For example for a workstation using a profile shared with other worksations, the FIT file would map C:\CONFIG.SYS to \\server\RPLFILES\PROFILES\profile\CONFIG.SYS, where server is the server's name and profile is the profile for this workstation.

RPL\RPLFILES. This directory contains files specific to each workstation as well as shared files such as profiles and operating system files. This directory is shared with the name RPLFILES.

RPL\RPLFILES\BINFILES\DOSxxx. These directories contain shared MS-DOS system files.

RPL\RPLFILES\BINFILES\LANMAN.DOS. This directory contains the Microsoft Network Client version 2.2 for MS-DOS, the network software used by all remoteboot workstations.

The first time you start the Remoteboot Manager and choose the Fix Security command, it creates the RPLUSER local group and assigns permissions as appropriate throughout the RPL directory.

For a complete explanation of the remoteboot directory structure, see "Directory, File Index, and Configuration File Details," later in this chapter.


Installing MSDOS Files for Remoteboot Workstations
Remoteboot 	10 of 42

Setting Up and Starting the Remoteboot Service

Installing MS-DOS Files for Remoteboot Workstations

When a workstation boots, the remoteboot server gives it a boot block which will load some version of the MS-DOS operating system. The server can also provide a version of Microsoft Windows for the workstation. You must copy MS-DOS and Windows files to the server; they are not shipped with Windows NT Server.

Note

You must have a separate, valid, software license for each workstation, including remoteboot workstations, that runs MS-DOS and/or Microsoft Windows.

In the following procedure you install MS-DOS files on the server. For information about how to install Windows files, see "Managing Remoteboot Workstations," later in this chapter. You cannot install Windows until you have at least one MS-DOS remoteboot workstation running.

To copy MS-DOS files to the server

1.	Check that the \systemroot\RPL\RPLFILES directory is being shared on the remoteboot server. It should have the share name RPLFILES.

2.	From an MS-DOS client (running a version of MS-DOS that you want to support on the remoteboot server), connect to the remoteboot server's RPLFILES share by typing

net use v: \\server\rplfiles

where server is the name of the remoteboot server.

3.	Copy all the MS-DOS files to the \systemroot\RPL\RPLFILES\BINFILES\DOSxxx directory, where xxx is the version number (for example, DOS622), by typing:

copy c:\dos\*.*  v:\binfiles\dos622

attrib -s -h  c:\io.sys

attrib -s -h  c:\msdos.sys

copy c:\io.sys  v:\binfiles\dos622

copy c:\msdos.sys  v:\binfiles\dos622

attrib +s +h  c:\io.sys

attrib +s +h  c:\msdos.sys

As shown, you may need to remove the hidden file attribute in order to copy these files. You can do this with the MS-DOS attrib command.

Copy files only to an existing DOSxxx directory; do not create a new directory. For example, any version of MS-DOS 6.2x must be copied to the existing DOS622 directory.

4.	If you copied DOS files other than MS-DOS (such as PC-DOS), you must rename the following files. From the RPL\RPLFILES\BINFILES\DOSxxx directory on the remoteboot server, type

rename ibmdos.com msdos.sys

rename ibmbio.com io.sys


Starting and Stopping the Remoteboot Service
Remoteboot 	11 of 42

Setting Up and Starting the Remoteboot Service

Starting and Stopping the Remoteboot Service

The Remoteboot service is installed as a manual service, meaning that you must start it intentionally each time you want it to run. If you want it to start automatically each time the server starts, see the instructions in the Windows NT Server System Guide.

To start or stop the Remoteboot service

1.	In the Control Panel, choose the Services icon.

2.	In the Services dialog box, select the Remoteboot service. You may need to scroll down in the list of services to reach it.

3.	Choose the Start or Stop button.

The Pause and Continue buttons have no effect on the Remoteboot service.

4.	In the Services dialog box, choose the Close button.

You can also use the net start remoteboot command to start the Remoteboot service and net stop remoteboot to stop it.


Starting the Remoteboot Manager
Remoteboot 	12 of 42

Setting Up and Starting the Remoteboot Service

Starting Remoteboot Manager

The Remoteboot Manager is an administrative tool for controlling the remoteboot process and managing remoteboot workstations.

To start Remoteboot Manager

1.	On the Windows NT Server computer, log on to a user account that belongs to the Administrators local group.

2.	From the Network Administration program group, choose the Remoteboot Manager icon.

To administer a remoteboot server other than the local machine

1.	From the Remoteboot menu, choose Set Focus.

2.	Type the name of the remoteboot server, or choose the name from the Select Computer box.

– Or –

From the command line, type rplmgr (or rplmgr\\server, where server is the name of a Windows NT Server computer.


Checking the Remoteboot Installation
Remoteboot 	13 of 42

Setting Up and Starting the Remoteboot Service

Checking the Remoteboot Installation

After you start the Remoteboot service for the first time, check the server's event log for entries related to the Remoteboot service. Use Event Viewer in the Administrative Tools group.

You should also use the Remoteboot Manager's configuration and security checking features after installation and after you add or remove support for an operating system.

To check the remoteboot configuration

1.	From the Configure menu, choose Check Configurations.

2.	Choose the Yes button.

This checks which operating systems are available for remoteboot workstations. Remoteboot Manager offers these as choices for profiles.

To check security settings in the remoteboot directory

1.	From the Configure menu, choose Fix Security.

2.	Choose the Yes button.

This overwrites permissions throughout the \systemroot\RPL directory, creates accounts for remoteboot workstations and the RPLUSER local account (if they don't already exist), and updates the domain entry in LANMAN.INI files for remoteboot workstations to match the server's own domain/workgroup.


Managing Profiles
Remoteboot 	14 of 42

Setting Up and Starting the Remoteboot Service

Managing Profiles

When you use the Remoteboot Manager for the first time, you must decide which profiles you need. A profile is the working environment shared by one or more workstations. It consists of the operating system, the workstation and architecture type, the network adapter type, and all the other information needed to boot a workstation.

Note

Remoteboot profiles are completely different from user profiles, which are used elsewhere in Windows NT Server.

To establish and name profiles, you choose from a list of configurations. A configuration is actually a template profile; a profile is created as a copy of one of the base configurations. Generally, you can find a configuration for any profile you want to create. Once the profiles are defined, it's easy to add workstations.

Workstations use profiles in either of two ways:  sharing a profile or using a personal copy of a profile. The profile is the same in either case; the difference is in how the workstation uses it.

A profile can be shared by a group of common users who have similar workstations and will use the same startup information. (All users have the same CONFIG.SYS, LANMAN.INI, and other configurations files, and those files are read-only.) For example, you may want to have a common profile that is shared by accounting, and another profile for sales and marketing. Or, you may want to create a profile shared by all Microsoft Windows users. Keep in mind, however, that the workstation architecture must be similar enough that the workstations can share startup files. Workstations that share profiles get their environment from a \systemroot\RPL\RPLFILES\PROFILES\profile directory (where profile is the name of the profile).

Sharing profiles is not practical in all cases. For example, a workstation may need customized system configuration files (like CONFIG.SYS). In this case, the workstation should use a personal copy of a profile. Changes to the startup information affect only the single workstation. Workstations that have a personal copy of a profile get their environment from a \systemroot\RPL\RPLFILES\MACHINES\cname\profile\PRO directory (where cname is the computername and profile is the name of the profile). Users can edit any of the files in that directory, such as CONFIG.SYS.

When you upgrade operating systems and make software changes, you need to install them separately to each profile and copy of a profile.

To create a profile

1.	From the Remoteboot menu in Remoteboot Manager, choose New Profile.

2.	For the Profile Name, type a name for this profile [no more than 16 characters, with no spaces or backslashes(\)].

If the server's RPL directory is on a FAT file system, use standard MS-DOS 8.3 format (eight characters, with an optional period and three more characters).

3.	In the Configuration box, choose a configuration.

If the configuration you want is not present, you must install the appropriate operating system (see "Installing MS-DOS Files for Remoteboot Workstations") and check the configuration (from the Configure menu, choose Check Configurations).

4.	For the Description, type a comment for the profile. The description should summarize the profile for easy recognition, such as MS-DOS 6.20 VGA & 3Com 503 EtherLink II adapter.

5.	Choose the OK button.

To change a profile

1.	Select an existing profile in the Remoteboot Manager.

2.	From the Remoteboot menu, choose Properties.

3.	Change the description of the profile, then choose the OK button.

You can change only the description. To change any other settings, you must create a new profile.

To delete a profile

1.	Select an existing profile in the Remoteboot Manager.

2.	From the Remoteboot menu, choose Delete.

If a message appears telling you that workstations are still assigned to this profile, you can delete or reassign all of the workstations at one time:

In the error message dialog box, choose the OK button.

Select the profile.

From the View menu, choose Workstations in Profile.

Select all of the workstations (press CTRL and click all of the workstations).

From the Remoteboot menu, choose Delete.

– Or –

From the Remoteboot menu, choose Properties. Choose a new profile for all of the workstations, then choose the OK button.

3.	In the confirmation dialog box, choose the OK button.

Once you have profiles set up, most remoteboot administration consists of managing the individual workstations.


Managing Remoteboot Workstations
Remoteboot 	15 of 42

Managing Remoteboot Workstations

When you have installed the Remoteboot service and the MS-DOS operating system files, and you have defined some profiles, you can use the Remoteboot Manager to manage the remoteboot workstations. This section provides procedures for:

Enabling and disabling the hard disk on a workstation

Adding a workstation to the Remoteboot service

Removing a workstation from the Remoteboot service

Adding Microsoft Windows for workstations

When a user starts a remoteboot workstation, what appears as the workstation's C drive is actually the workstation's working directory in the remoteboot server's RPL\RPLFILES\MACHINES directory. If the remoteboot workstation has a hard disk, this disk appears as drive D. Floppy disk drives keep their original drive names.

Before you can use the Remoteboot service, each remoteboot workstation must have a network adapter with a RPL ROM chip installed. For a list of supported network adapters, see "Setting Up and Starting the Remoteboot Service," earlier in this chapter.

Note

Some computers must have at least a disk controller to boot remotely. Such computers (many IBM PC AT®-compatibles) cannot be truly diskless workstations even if their disk controller is removed, as their BIOS (basic input/output system) assumes that at least one disk or disk controller is present. Many new computers (even diskless ones) have disk controller circuitry on the motherboard and so are not truly diskless.


Enabling Remoteboot on a Workstation’s Hard Disk
Remoteboot 	16 of 42

Managing Remoteboot Workstations

Enabling Remoteboot on a Workstation's Hard Disk

Before a workstation with a hard disk can be booted remotely, its hard disk must be properly configured for the Remoteboot service. This does not prevent users from accessing the hard disk after the workstation is booted.

Use the Microsoft Network Client version 2.2 rplenabl utility to prepare the workstation to use the Remoteboot service. Later, if you want to boot the workstation using its hard disk, run the rpldsabl utility to disable the remoteboot configuration.

Note

Some RPL ROMs will take control of the workstation even though the hard drive is enabled, so you may not need to run the rplenabl (or rpldsabl) utility on these workstations. Try simply booting the computer, and then use rplenabl if needed.

To configure a workstation's hard disk for the Remoteboot service

1.	Insert a formatted MS-DOS floppy disk in the remoteboot server's floppy disk drive.

2.	Copy the RPLENABL.EXE and RPLDSABL.EXE programs to the floppy disk by typing

copy c:\systemroot\rpl\rplfiles\binfiles\binr\rpl??abl.exe a:

where a:  is the floppy disk drive.

3.	Start the remoteboot workstation, booting MS-DOS from the local hard disk.

4.	Put the disk with the RPLENABL.EXE program in the workstation's floppy disk drive and type

a:rplenabl

For instructions on using the rpldsabl utility, see "Deleting a Workstation," later in this chapter.


Adding a New Workstation
Remoteboot 	17 of 42

Managing Remoteboot Workstations

Adding a New Workstation

As described earlier in "Setting Up and Starting the Remoteboot Service," you created profiles for workstations. You can add a new remoteboot workstation in two ways:

Create a new remoteboot database record for the workstation and manually fill in the necessary data, including the workstation's network adapter ID number and the profile you want this workstation to use. This is only recommended when you know the network adapter ID number and you are copying an existing workstation record.

When you copy an existing workstation record, you also copy the personal configuration information. For example, if the original workstation record uses a personal copy of a profile and has a customized installation of Microsoft Windows, the profile and the Windows installation will be copied for the new workstation.

Boot the workstation remotely with no special preparation on the server. This creates an adapter record on the server, which you can then convert to a workstation record by adding the workstation's name and profile. This is easier because you don't need to know the workstation's network adapter ID number.

To create a new workstation record manually

1.	Start the Remoteboot Manager.

Remember to log on to a user account that belongs to the Administrators local group.

2.	From the Remoteboot menu, choose New Workstation.

– Or –

Select an existing workstation record. From the Remoteboot menu, choose Copy.

3.	In the Adapter ID box, type the workstation's network adapter ID number. This is a unique number supplied by the network adapter firmware. The adapter ID is twelve hexadecimal digits; the first six digits identify the adapter type. If you don't know the adapter ID, stop this procedure and go to the next procedure.

4.	In the Wksta Name box, type a name for the workstation. The name can have no more than 15 characters [with no spaces or backslashes (\)]. The Remoteboot service will create a Windows NT user account with this name, not for the user but for the workstation itself.

If the server's RPL directory is on a file access table (FAT) file system, use standard MS-DOS 8.3 format (eight characters, with an optional period and three more characters).

5.	In the Description box, type a comment that describes the workstation.

6.	In the Password box, type a password for the workstation's account (not for the user using the workstation).

7.	Choose a configuration type:

Shared if this workstation can share its profile with other workstations.

Personal if this workstation must use a personal copy of a profile so that you can customize the environment for the workstation.

8.	In the Wksta In Profile box, choose a profile for this workstation.

If none of the profiles are suitable, see "Setting Up and Starting the Remoteboot Service," earlier in this chapter, for instructions on creating profiles.

9.	In the TCP/IP Settings box, enter appropriate addresses only if the workstation will use TCP/IP and will not use DHCP for automatic address handling.

10.	Choose the Add button.

To create a new workstation entry automatically

1.	Start the Remoteboot Manager on the server.

Remember to log on to a user account that belongs to the Administrators local group.

2.	Start the remoteboot workstation. The workstation does not actually boot, but it does send a boot request to the server.

3.	In Remoteboot Manager on the server, from the View menu, choose Refresh.

4.	In Remoteboot Manager, select the adapter record that has appeared with the network adapter ID number in place of the workstation name. From the Remoteboot menu, choose Convert Adapters.

– Or –

Select more than one adapter record (hold down the CTRL key while clicking with the mouse). From the Remoteboot menu, choose Convert Adapters. You will convert each of the selected records, one at a time.

– Or –

Do not select any adapter records. From the Remoteboot menu, choose Convert Adapters. You will convert all of the adapter records to workstation records, one at a time.

5.	In the Wksta Name box, type a name for the workstation. The name can have up to 15 characters. The Remoteboot service will create a Windows NT user account with this name, not for the user but for the workstation itself.

If the server's RPL directory is on a file access table (FAT) file system, use standard MS-DOS 8.3 format (eight characters, with an optional period and three more characters).

6.	In the Description box, type a comment that describes the workstation. The box already contains a comment provided by the network adapter itself.

7.	Choose a configuration type:

Shared if this workstation can share its profile with other workstations.

Personal if this workstation must use a personal copy of a profile so that you can customize the environment for the workstation.

8.	In the Wksta In Profile box, choose a profile for this workstation.

Profiles that are unsuitable for this type of adapter (determined by the first six digits of the network adapter ID number) are marked with a red X.

If none of the profiles are suitable, see "Setting Up and Starting the Remoteboot Service," earlier in this chapter for instructions on creating profiles.

9.	In the TCP/IP Configuration box, enter appropriate addresses only if the workstation will use TCP/IP and will not use DHCP for automatic address handling.

10.	Choose the Add button.

If you are converting more than one adapter ID record, the next record appears in the dialog box.

What You See on the Workstation

When you boot the workstation, a remoteboot logon prompt appears:

Type Remoteboot username, or press enter if it is <workstation>:

This asks for the account name and password associated with the workstation itself, not for the user's own account name and password.

Once the boot is complete, the user should type a net logon command to log on with his or her own username and password.

When a workstation has completed a remote boot, the current directory is C:\, and the C drive is a virtual hard drive, parts of which are mapped to various places on the remoteboot server by the FIT file. For information about FIT files and translation pairs, see "Directory, File Index, and Configuration File Details," later in this chapter.

The C:\WKSTA directory contains workstation-specific and profile-specific configuration files (such as WIN.INI) and is different for each profile to which the workstation is joined. The C:\DATA directory will always be the same, regardless of the profile used; the user can create files and directories there.

The C:\DOS and C:\LANMAN.DOS directories provide access to MS-DOS and network utilities. The C:\BINR directory provides access to shared real-mode utilities.

Local hard disks, if present, are assigned drive letters starting with D, unlike the local boot case, where the drive letters start with C.

Note

If the server uses NTFS, a workstation assigned to a profile (rather than to a personal copy of a profile) can add or modify files only in certain directories on its virtual C drive. It cannot affect directories on the C drive that are shared with other workstations (unless you explicitly grant permission to do so on the server).

A remoteboot workstation always runs the NetBEUI protocol. To run other protocols as well, see "Supporting Other Protocols," later in this chapter.

Changing a Workstation Record

You can change any of the properties of a workstation record except the network adapter ID number.

To change a workstation record

1.	Start the Remoteboot Manager on the server.

Remember to log on to a user account that belongs to the Administrators local group.

2.	Select the workstation record.

– Or –

Select more than one record (hold down CTRL while clicking) to change properties for a group of workstations at once.

3.	From the Remoteboot menu, choose Properties.

4.	Update the information as needed.

5.	Choose the OK button.


Deleting a Workstation
Remoteboot 	18 of 42

Managing Remoteboot Workstations

Deleting a Workstation

When you no longer want to boot a workstation remotely, you can remove it from the list of workstations in the Remoteboot service.

To remove a workstation from the Remoteboot service

1.	Start the Remoteboot Manager on the server.

Remember to log on to a user account that belongs to the Administrators local group.

2.	Select the workstation record.

– Or –

Select more than one reocrd (hold down CTRL while clicking) to delete a group of workstations at once.

3.	From the Remoteboot menu, choose Delete.

4.	Verify that you want to delete this workstation record.

If Remoteboot Manager originally created an account while creating a workstation record, removing the workstation record also removes the account associated with that workstation. If the account existed before the workstation record, then the account will remain after removing the workstation record.

If the workstation has a bootable hard drive, you need to disable the remoteboot process and allow the workstation to use the hard drive again.

To disable the Remoteboot process

1.	Start the workstation, booting MS-DOS remotely or from a floppy disk.

2.	Put the disk with the RPLDSABL.EXE program in the workstation's floppy disk drive and type

a:rpldsabl

where a:  is the workstation's floppy disk drive.

(If you don't have the disk anymore, see the section "Enabling Remoteboot on a Workstation's Hard Disk" earlier in this chapter for instructions on making this disk.)

3.	Remove the disk and press CTRL+ALT+DEL.


Installing Microsoft Windows for Remoteboot Workstations
Remoteboot 	19 of 42

Managing Remoteboot Workstations

Installing Microsoft Windows for Remoteboot Workstations

You can install Microsoft Windows in similar workstation environments simply by creating a profile for Windows users and installing the Windows environment in the profile. In this way, you can add as many new workstations as you need without having to install the Microsoft Windows environment with each new addition. Keep in mind, however, that all the workstations sharing the profile must be similar enough to share the same startup information.

If the workstations are not similar, you create personal copies of profiles. If Windows is already installed for a profile, and you create a new personal copy of that profile, the Windows installation is part of the new copy and you do not have to reinstall it. If you have established a personal copy of a profile and later want to add Windows, you must add it separately for that personal copy of the profile, or delete the personal copy of the profile and create a new one from a profile that does have Windows installed.

To support Microsoft Windows for remoteboot workstations:

Install Windows files on the remoteboot server. This makes the files easily available for workstation installations.

Create a profile for Windows users. Install Windows once for all workstations using the profile.

Install Windows separately for workstations using a personal copy of a profile (if the profile did not support Windows at the time you made the personal copy). Or, delete the workstation account and recreate it, making a personal copy of a profile that does support Windows.

Installing Microsoft Windows Files on the Server

Installing Windows files on the server makes the files easily available for workstation installations.

To install Windows files on the server

1.	Create an MS-DOS profile, if one does not exist. (For details, see "Setting Up and Starting the Remoteboot Service," earlier in this chapter.)

2.	Boot a remoteboot workstation that will use Microsoft Windows, and join it to the MS-DOS profile using the Remoteboot Manager. (For details, see "Adding a New Workstation," earlier in this chapter.)

Note

If you will use the shared Windows profile method for similar workstations, assign the workstation to use a profile, not a personal copy of a profile. If you will use the personal profile user method for different workstations, assign the workstation to use a personal copy of a profile.

3.	Reboot the workstation. At the remoteboot logon prompt (the prompt that first appears when you start the workstation), supply the name and passowrd of an account that is a member of the Administrators group on the Windows NT Server computer.

4.	If the workstation does not have a floppy disk drive, use the floppy disk drive of a server on the network:

First, at the server (it doesn't have to be the remoteboot server), use the File Manager or the net share command to share the server's floppy disk drive.

Then, at the workstation, use the File Manager or the net use command to connect to the shared floppy disk drive.

5.	Put the Windows Disk 1 in the floppy disk drive.

6.	Run setup /a on the Windows 3.1 Disk 1 and install to C:\WIN.

Windows files are expanded and put into the \systemroot\RPL\RPLFILES\BINFILES\WIN directory on the remoteboot server.

Continue the installation. Depending on how you want to set up profiles, proceed to "Installing Windows for a Profile" or to "Installing Windows for a Personal Copy of a Profile."

Installing Windows for a Profile

When you install Windows for a profile, all workstations that share that profile use Windows. Also, if you later assign a personal copy of the profile to a workstation, that workstation uses Windows.

To install Windows for a profile

1.	Create a profile for Microsoft Windows users on the remoteboot server.

Give the profile a specific name that suggests the Windows version and the operating system associated with it. For example, D5WIN31 tells you that this profile is for MS-DOS 5.00 with Microsoft Windows version 3.1.

2.	In Remoteboot Manager, assign a remoteboot workstation to the new profile (not using a personal copy of the profile).

3.	Reboot the workstation.

At the remoteboot logon prompt (the prompt that first appears when you start the workstation), supply the name and passwork of an account that is a member of the Administrators group on the Windows NT Server computer.

4.	On the workstation, change to the Windows directory by typing:

cd \win

5.	On the workstation, run setup /n to install Microsoft Windows in C:\WINDOWS (do not choose to upgrade any existing Windows intallations). Choose the express installation.

If the workstation has memory trouble while running Setup, see "Configuring Memory for Windows," later in this chapter.

6.	Follow the instructions in the Setup program to modify the AUTOEXEC.BAT and CONFIG.SYS files.

Note

If Setup displays an error message saying that it cannot update your system files on drive C, choose Cancel. This creates AUTOEXEC.WIN and CONFIG.WIN files in the C:\WINDOWS directory. Copy these files to C:\AUTOEXEC.BAT and C:\CONFIG.SYS, respectively.

8.	Return to the MS-DOS prompt and copy all the files and directories in C:\WINDOWS to C:\WKSTA.PRO\WIN by typing

xcopy  /e c:\windows c:\wksta.pro\win

This makes the Windows files available to all remoteboot workstations that are joined to the profile.

If the xcopy command does not work on the workstation, you can copy the files from a command prompt on the server by typing the following command, all on one line:

xcopy  c:\systemroot\rpl\rplfiles\machines\workstation\profile\wksta\win /e
c:\systemroot\rpl\rplfiles\profiles\profile\wksta\win

where workstation is the name of the workstation and profile is the name of the profile.

9.	Reboot the remoteboot workstation and log on.

Installing Windows for a Personal Copy of a Profile

If you assign a personal copy of a profile (without Windows) to a workstation, and then later decide that you want to install Windows for that workstation, you can install Windows separately for this workstation. Or, delete the workstation account and recreate it, making a personal copy of a profile that does support Windows.

You may want to install a separate copy of Windows for a workstation if the workstation requires customized Windows configuration files.

To install Windows for a personal copy of a profile

1.	On the remoteboot server, assign the remoteboot workstation to an MS-DOS profile. Specify a personal copy of the profile.

2.	Reboot the workstation.

At the remoteboot logon prompt (the prompt that first appears when you start the workstation), supply the name and password of an account that is a member of the Administrators group on the Windows NT Server computer.

3.	On the workstation, change to the Windows directory by typing the following:

cd  \win

4.	Run setup /n to install Microsoft Windows in C:\WINDOWS (do not choose to upgrade any existing Windows installations). Choose the express installation.

If the workstation has memory trouble while running Setup, see "Configuring Memory for Windows," later in this chapter.

5.	Follow the instructions in the Setup program to modify the AUTOEXEC.BAT and CONFIG.SYS files.

Note

If Setup displays and error message saying that it cannot update your system files on drive C, choose Cancel. This creates AUTOEXEC.WIN and CONFIG.WIN files in the C:\WINDOWS directory. Copy these files to C:\AUTOEXEC.BAT and C:\CONFIG.SYS, respectively.

6.	When the Setup program is finished, reboot the workstation and log on.

Configuring Memory for Windows

Here are three tips for configuring the remoteboot workstation to use memory most efficiently while running Windows Setup or Windows itself.

Configuring EMM386.EXE

The CONFIG.SYS file contains a device line for EMM386.EXE. This line is disabled (the line starts with REM) because you must calculate the parameters. This procedure is for a 386-based (or higher) workstation running MS-DOS 5.00 or higher.

To configure EMM386 for more upper memory

1.	Find out how much conventional memory the workstation has (in decimal terms) by typing mem at the MS-DOS prompt.

2.	Convert this number to hexadecimal format and drop the rightmost digit. To convert, you can use the dectohex command in the \systemroot\RPL\RPLFILES\BINFILES\BINR directory.

3.	Edit the device=EMM386.EXE line in the CONFIG.SYS file.

Remove the REM designation at the beginning of the line. Check that the path specified for the file is the root (C:\) directory, not the C:\DOS directory.

Use the remaining four digits of the hexadecimal value for the first x= value. (The second x= value is 9FFF and should not be changed.)

For example, if conventional memory is 598016, the hexadecimal value is 92000. In this case, use x=9200-9FFF.

Disabling SMARTDRV.SYS

Windows installs a device command in the CONFIG.SYS file to use SMARTDRV.SYS. If your Windows workstation seems to be operating slowly, experiment with disabling this line. Disabling SMARTDRV.SYS may speed the process up by giving Windows memory on the workstation rather than on a disk cache.

To disable SMARTDRV.SYS

Disable the device=SMARTDRV.SYS line (precede it with REM) in the workstation's CONFIG.SYS file.


Optimizing the Remoteboot Service
Remoteboot 	20 of 42

Optimizing the Remoteboot Service

Once the Remoteboot service has been configured and customized for your network needs, Windows NT offers some additional ways to optimize the service. Most of the topics in this section deal with increasing performance. Other topics tell you how to further customize your configuration.

This chapter contains information on how to:

Use the rplcmd utility to change the remoteboot database

Create remoteboot configurations for new adapters

Use multiple network adapters

Set local swapping

Use a RAM drive on the workstation

Set hardware buffers


Using The Remoteboot Command Utility (RPLCMD.EXE)
Remoteboot 	21 of 42

Optimizing the Remoteboot Service

Using The Remoteboot Command Utility (RPLCMD.EXE)

The rplcmd utility can be used to view and update records in the remoteboot database, including those that are inaccessible through Remoteboot Manager.

This utility is for advanced administrators, not for casual use.

To use the rplcmd utility

1.	Stop the Remoteboot service. For details, see "Starting and Stopping the Remoteboot Service," earlier in this chapter.

2.	Back up the remoteboot database. For details, see "Backing Up the Remoteboot Database," later in this chapter.

3.	Restart the Remoteboot Service.

4.	At the command prompt, type

rplcmd [\\computername]

where \\computername specifies a remote computer where the Remoteboot service is running. If this parameter is omitted, rplcmd manages the Remoteboot service on the local computer.

The main rplcmd command prompt appears:

Adapter Boot Config Profile Service Vendor Wksta [Quit]

Each command has the following effect:

Adapter modifies adapter records (records of remoteboot workstations that have been started but do not yet have a workstation record assigned)

Boot modifies boot block records.

Config modifies configuration records.

Profile modifies profiles.

Service controls the Remoteboot service.

Vendor associates a vendor "name," or six-digit hexadecimal prefix, with a text comment describing the vendor.

Wksta modifies workstation records.

5.	To select a command, type the first letter in the command name and press ENTER. To return to the main menu, press CTRL+Z at any prompt and press ENTER.

Each of the main commands has further command prompts, including these common commands:

Add to add a new record.

Del to delete a record (or all records).

Enum to enumerate, or show information for, a record (or all records). You can enumerate information at different levels; level 0 gives you the least information per record.


Creating Remoteboot Configurations for New Adapters
Remoteboot 	22 of 42

Optimizing the Remoteboot Service

Creating Remoteboot Configurations for New Adapters

Windows NT provides remoteboot configurations for the most popular network adapters. If you want to use a new remoteboot-compatible network adapter that is not already supported by Windows NT, you must manually create new remoteboot configurations corresponding to the new adapter. Creating these new configurations allows the Remoteboot service and Remoteboot Manager to recognize the new adapter type.

To create a configuration for a new adapter

1.	Copy the MS-DOS device driver for the network adapter to the \systemroot\RPL\BBLOCK\NDIS directory.

2.	Create the directory \systemroot\RPL\BBLOCK\NETBUEI\adapter, where adapter is the name of the adapter. Within this directory, create these files:

DOSBB.CNF

PROTOCOL.INI

Pattern these files after existing files in a corresponding directory, but substitute the new driver names in the DOSBB.CNF file, and the correct driver information in the PROTOCOL.INI file.

3.	Use the rplcmd utility to add a boot block record for the new adapter. For details about the rplcmd utility, see "Using The Remoteboot Command Utility (RPLCMD.EXE)," earlier in this chapter.

For example, the following sequence of commands creates a sample boot block record:

C:\winnt\rpl> rplcmd

Adapter Boot Config Profile Service Vendor Wksta [Quit]: b

Add Del Enum: a

BootName=DOSX

VendorName=012345

BbcFile=BBLOCK\NETBEUI\dirname\DOSBB.CNF

        All other parameters are optional

BootComment=Name of this adapter

WindowSize=0

Note

In these examples, and in those that follow, the value 012345 represents the "vendor name" or network adapter prefix. Replace this with the first six digits of the network adapter type's adapter identification number.

If the adapter prefix for the new adapter type matches that of an existing adapter type, modify the BootName field of the boot block and workstation record field to be unique among all boot block or workstation records corresponding to that adapter prefix. For example, use DOS for IBM Token Ring and IBM Ethernet.

4.	Use the rplcmd utility to add the new configuration.

For example, the following sequence of commands creates a sample configuration:

C:\winnt\rpl> rplcmd

Adapter Boot Config Profile Service Vendor Wksta [Quit]: c

Add Del Enum: a

ConfigName=DOS622x

BootName=DOSX

DirName=DOS

FitShared=fits\dos622.FIT

FitPersonal=fits\dos622p.FIT

        All other parameters are optional

ConfigComment=DOS 6.21 <adapter name>

DirName3=

DirName4=

For BootName, enter the name of the boot block record you created in step 3.


Using Multiple Network Adapters
Remoteboot 	23 of 42

Optimizing the Remoteboot Service

Using Multiple Network Adapters

If a remoteboot workstation has multiple network adapters , you will need to modify the boot block information for the adapter that has the RPL ROM chip..

To modify the boot block information

1.	Using the Remoteboot Manager, create a new profile.

2.	Add the network adapter driver to the \systemroot\RPL\BBLOCK\NETBEUI\adapter\DOSBB.CNF boot block configuration files, where adapter is the name of the adapter that has the RPL ROM chip on the workstation.

3.	Update the \systemroot\RPL\BBLOCK\NETBEUI\adapter\PROTOCOL.INI file with sections for the new network adapter driver.


Setting Up Local Swapping
Remoteboot 	24 of 42

Optimizing the Remoteboot Service

Setting Up Local Swapping

You can increase performance on your Microsoft Windows remoteboot workstations by using the workstation's hard drive for swapping.

To set up local swapping on Windows workstations

Edit the swapfile line in the workstation's SYSTEM.INI file to point to drive D.


Using a RAM Drive on the Workstation
Remoteboot 	25 of 42

Optimizing the Remoteboot Service

Using a RAM Drive on the Workstation

You can optimize post-boot performance on your remoteboot workstations by using a RAM drive. Use of a virtual disk, such as the RAMDRIVE.SYS provided with most MS-DOS versions, can reduce network traffic by storing commonly used files and utilities locally. (If, however, the workstation does not have RAM to spare, using a virtual disk could increase swapping.)

The RAM drive should be placed first in the PATH environmental variable. Giving memory to file caches may also help performance, especially on the remoteboot server. For more information about memory management, see the documentation for the MS-DOS operating system and for the network client software.


Setting Hardware Buffers
Remoteboot 	26 of 42

Optimizing the Remoteboot Service

Setting Hardware Buffers

To achieve maximum possible usage of upper memory blocks (UMBs) for MS-DOS 5.0 or higher, set hardware buffers to be contiguous and as low as possible within the C000-F000 range.

By making sure that the address ranges (ROM and RAM) are as contiguous as possible, you will be able to create the largest single, free address range. This will provide more UMBs for MS-DOS than fragmenting the address ranges.

On PC/AT computers, refer to the hardware and software manuals that came with your adapters to determine the address ranges that can be set. Usually, this is done with jumpers on the adapter, but occasionally it must be changed with a setup program. Once you have determined the address ranges, arrange them to be as close together as possible without overlapping.

On PS/2 computers, you will need to run the reference disk and supply the ADF files (if they are not already on the disk) for all the adapters. Using the reference disk program, you can determine address ranges for each adapter, and then set them.


Directory, File Index, and Configuration File Details
Remoteboot 	27 of 42

Directory, File Index, and Configuration File Details

The following sections describe the structure of the RPL directory and the formats of remoteboot configuration files.


The RPL Directory
Remoteboot 	28 of 42

Directory, File Index, and Configuration File Details

The RPL Directory

The following illustration shows the subdirectories created in the RPL directory when you install the Remoteboot service.

Directories that are automatically installed should not be deleted (for example, do not delete C:\TMP from a remoteboot workstation). If a directory is deleted, you must recreate it and set the permissions with the Remoteboot Manager Fix Security command, or you can use Remoteboot Manager to delete the affected workstation record and recreate it (after first saving any workstation-specific files).

In the \systemroot\RPL directory, the SYSTEM.MDB and RPLSVC.MDB files contain the remoteboot database. The JET.LOG file contains information used in recovery from power failures or other catastrophic interruptions.


File Index Tables
Remoteboot 	29 of 42

Directory, File Index, and Configuration File Details

File Index Tables

File index tables (or FIT files) are ASCII files containing filename lookup tables that enable file translation. Remoteboot workstation software translates a directory name or file name typed by the workstation user into the true directory name or file name on the server. In general, the workstation translates references of the form C:\... to \\servername\RPLFILES\... (that is, to locations in the \systemroot\RPL\RPLFILES directory on the server).

File translation pairs consist of a prototype filename or prefix, followed by a space, and an actual filename or prefix, relative to the directory named on the first line [usually (RPLFILES)]. If the prototype matches a proper prefix of the name to be matched, the matched portion is replaced by the actual prefix. If there is an exact match (not just a prefix), the actual filename is substituted. If several prefixes match, the longest one is selected for substitution. A network path of the form \\any_servername\sharename may be included in the actual filename or prefix, in which case it overrides the directory listed on line one.

Examples:

If the workstation requests access to C:\WIN386.SWP (for example, to open it for writing), the workstation software will use the FIT to translate it into:

\\servername\RPLFILES\TMPFILES\(CNAME)\SWAPFILE.DAT

where (CNAME) is the workstation name.

If C:\CONFIG.SYS is requested, the following will be used because it has the longest matching prefix (C:\):

\\servername\RPLFILES\PROFILES\(PROFILE)\CONFIG.SYS

where (PROFILE) is the profile name. The line near the top of each FIT file that starts with C:\ sends all C:\ references that aren't at least partially matched by other lines to the directory \\servername\RPLFILES\PROFILES\(PROFILE).

Note that the "machine writeable files" section of each .FIT file lists the files and directories to which the user has write access.

By convention there are usually two .FIT files for each profile:  one to be used when sharing the profile and one to be used with personal copies of the profile. For example, DOS622.FIT is for workstations that share the DOS622 profile, and DOS622P.FIT is for personal copies of the DOS622 profile. The file format is the same, but the personal profile .FIT translates most references to directories specific to the workstation rather than to directories shared with other workstations.

Fields in .FIT files are separated with white space. The maximum line length is 512 characters. A comment line has a semicolon (;) as the first non-space character.

The following keywords have special meaning in a .FIT file:

(PROFILE) is the name of the profile assigned to this workstation.

(CNAME) is the name of the workstation.

(RPLFILES) is the \systemroot\RPL\RPLFILES directory, shared by the server with the sharename RPLFILES.

(BINFILES) is a directory for executable files. It is assumed to be relative to RPLFILES (\systemroot\RPL\RPLFILES\BINFILES).

(TMPFILES) is a directory for temporary and swap files. It is assumed to be relative to RPLFILES (\systemroot\RPL\RPLFILES\TMPFILES).


Boot Block Configuration Files
Remoteboot 	30 of 42

Directory, File Index, and Configuration File Details

Boot Block Configuration Files

The boot block configuration file specifies the contents of the boot block sent to the workstation by the Remoteboot service and is designated by the .CNF extension. The boot block normally includes the RPLBOOT.SYS, RPLSTART.COM, and RPLDISK.SYS files and the real-mode network drivers. The boot block also contains some workstation-specific data (a copy of the workstation record from the remoteboot database) and some profile-specific data (the .FIT file associated with the profile used).

A line in a .CNF file typically has three fields:

Type

File name (path is relative to the \systemroot\RPL directory)

Parameter(s)

All valid types are listed below, along with their expected file names and parameters.

Fields in .CNF files are separated with white space. Spaces within a field are represented with tilde (~). The maximum line length is 512 characters. A comment line has a semicolon (;) as the first non-space character.

Note

The DRV and EXE types of boot block configuration files must be specified in the reverse order they would normally occur in a CONFIG.SYS file. For example, if ABC.DRV must appear before DEF.EXE in CONFIG.SYS, then DEF.EXE must appear before ABC.DRV in the .CNF file.

RPL Type

The filename specified with the RPL type is the initialization program that runs on a workstation. There must be exactly one RPL type in a .CNF file. The initialization program is normally RPLBOOT.SYS.

BASE Type

The value specified with the BASE type is a hexadecimal segment number that identifies the base address of the boot block. There can be only one BASE type in a .CNF file. If none is specified, 00C0h is used as the default base address.

DAT Type

Files listed with the DAT type specify data files that should be stored on the boot block. The filename is relative to \systemroot\RPL.

LDR Type

The filename and parameters listed with the LDR type specify which loader to use on the workstation. The loader is the program that RPLBOOT.SYS will pass control to; there can be only one LDR keyword. The loader is normally RPLSTART.COM.

DRV Type

The filename and parameters listed with the DRV type specify the device drivers used to form the boot block. The filename field specifies the name of the device driver. The DRV type has three parameter fields:

The first field specifies parameters used by the device driver.

The second field specifies any additional memory used by the device driver (in decimal kilobytes).

The third field is M if the device driver can be moved in memory to reuse space that it doesn't need; it is ~ if the device driver cannot be moved.

If the driver can be moved after initialization and its memory requirements are less than for the original driver image, RPLBOOT.SYS moves the driver to reclaim some of the unused memory and adjusts all interrupt vectors that point into the driver's memory area. Some drivers cannot be moved because they record segment addresses that are correct during initialization but not after the driver has been moved.

EXE Type

Files listed with the EXE type specify executables (.EXE and .COM files) that are run during the boot process. The file name is the name of the executable, and the parameters field specifies arguments passed to the executable. EXE lines must be specified in reverse order-that is, the last one listed in the boot block configuration file will be the first one executed.


Supporting Other Protocols
Remoteboot 	31 of 42

Supporting Other Protocols

A remoteboot workstation always runs the NetBEUI protocol. This section describes how to install support for TCP/IP, DLC, and IPX protocols for use by remoteboot workstations.


Installing TCP/IP Support
Remoteboot 	32 of 42

Supporting Other Protocols

Installing TCP/IP Support

Before you set up workstations to use TCP/IP, you must either enable DHCP to assign addresses automatically, or you must assign IP addresses and subnet masks for each workstation that will use TCP/IP. (See the Windows NT Server TCP/IP manual for more information about TCP/IP addresses.)

When you have arranged for addresses, you can then enable TCP/IP support.

To enable TCP/IP support

1.	Edit the \systemroot\RPL\BBLOCK\NETBEUI\adapter\DOSBB.CNF file, where adapter is the name of the network adapter. Remove the semicolon (;) in column one of this line:

;DRV    BBLOCK\TCPDRV.DOS /I:C:\LANMAN.DOS ~ ~

2.	For each profile (or a copy of a profile) that will support TCP/IP, edit the following files as described:

In \systemroot\RPL\RPLFILES\PROFILES\profile\AUTOEXEC.BAT, where profile is the name of the profile, enable umb.com, nmstr, and load tcpip by removing the REM designations at the beginnings of those lines.

In \systemroot\RPL\RPLFILES\PROFILES\profile\CONFIG.SYS, where profile is the name of the profile, enable nemm.dos by removing the REM designation at the beginning of that line.

3.	Boot a workstation using one of the profiles altered in the last step.


Installing DLC Support
Remoteboot 	33 of 42

Supporting Other Protocols

Installing MS-DLC Support

To install MS-DLC support

At the workstation, type load msdlc.

– Or –

Add this command to the end of the workstation's AUTOEXEC.BAT file.


Installing IPX Support
Remoteboot 	34 of 42

Supporting Other Protocols

Installing IPX Support

When you install IPX support, you will need the Microsoft Network Client version 2.2 NetWare® Connectivity disk and the Novell NetWare SHGEN-1 and SHGEN-2 disks (or the WSGEN disk).

Note

IPX support is installed per adapter and is MS-DOS version specific. Follow the installation procedure for each adapter that will support IPX; define profiles for each version of MS-DOS that will support IPX.

To install IPX support

1.	On the server, edit the \systemroot\RPL\BBLOCK\NETBEUI\adapter\DOSBB.CNF file, where adapter is the name of the network adapter. Remove the semicolon (;) in column one of this line:

;DRV    BBLOCK\IPXNDIS.DOS ~ ~ ~

2.	Create a new profile with a name that describes IPX support (for example, DOS62IPX).

Note

IPX is MS-DOS version specific. You must create a separate profile for each version of MS-DOS that will support IPX.

3.	Assign a workstation to the new profile.

4.	Boot the workstation. At the remoteboot logon prompt (the prompt that first appears when you start the workstation), supply the name and password of an account that is a member of the Administrators group on the Windows NT Server computer.

5.	If the workstation does not have a floppy disk drive, use the floppy disk drive of a server on the network:

First, at the server (it doesn't have to be the remoteboot server), use the File Manager or the net share command to share the server's floppy disk drive.

Then, at the workstation, use the File Manager or the net use command to connect to the shared floppy disk drive.

6.	Put the Microsoft Network Client NetWare Connectivity disk in the floppy disk drive.

7.	On the workstation, run the NetWare Connectivity Setup program by typing a:nwsetup (use a different drive letter if needed).

When prompted, insert the Novell NetWare SHGEN-1 and SHGEN-2 disks (or the WSGEN disk).

8.	Reboot the workstation.

Supply the workstation password (if any).

9.	Log on to the workstation with a normal user account.

10.	To start using the IPX protocol, type nwload. Or, add this command to the end of the workstation's AUTOEXEC.BAT file.

IPX is now installed on the workstation's profile and is available for use by other workstations using this profile.


Backing Up the Remoteboot Database
Remoteboot 	35 of 42

Backing Up the Remoteboot Database

The remoteboot database holds the configuration, workstation, and profile records and other data for the Remoteboot service. You should back up the database before and after you make significant changes and save the copies. The Remoteboot service automatically backs up the database every 24 hours (counting from when you start the service).

Because the Remoteboot service makes automatic backups (overwriting the current backup copies), and for good administrative procedure, you should occasionally archive copies of the backup files.

To back up the remoteboot database

From the Configure menu of Remoteboot Manager, choose Backup Database.

The JET.LOG, RPLSVC.MDB, and SYSTEM.MDB files are backed up to the \systemroot\ RPL\BACKUP directory.

To restore a backup copy of the remoteboot database

Copy the files from \systemroot\RPL\BACKUP (or other saved versions of the files) to the RPL directory.


Troubleshooting Remoteboot
Remoteboot 	36 of 42

Troubleshooting Remoteboot

This section lists some common problems you may encounter using the Remoteboot service.


Remoteboot Service Won’t Start
Remoteboot 	37 of 42

Troubleshooting Remoteboot

Remoteboot Service Won't Start

Check the server's event log, which can provide useful diagnostic information. In the Administrative Tools group, select Event Viewer.


Remoteboot Manager Won’t Start
Remoteboot 	38 of 42

Troubleshooting Remoteboot

Remoteboot Manager Won't Start

Be sure that you are logged on using an account that is a member of the Administrators local group.


Remoteboot Service Stops
Remoteboot 	39 of 42

Troubleshooting Remoteboot

Remoteboot Service Stops

Be sure that the server's own network configuration is correct, including hardware settings for the network adapter.


Remoteboot Workstation Won’t Start
Remoteboot 	40 of 42

Troubleshooting Remoteboot

Remoteboot Workstation Won't Start

If a workstation won't boot remotely, or if you're having problems with the way the workstation is booting:

Be sure that the server is running and that the Remoteboot service is running.

The workstation must be on the same subnet as the server.

Check the Remoteboot Manager's list of adapters that have not yet been converted to workstation records. To update the list, choose Refresh from the View menu. If the workstation's adapter is in the list, convert the adapter record to a workstation record.

Check the \systemroot\RPL\FITS directory. The server must have a .FIT file for each profile that is to boot remotely.

Each workstation must have a RPL ROM chip installed on or built into its network adapter. This ROM chip may need to be enabled via jumpers or a configuration program.

Check the defaults for hardware settings in the \systemroot\RPL\BBLOCK\NETBEUI\adapter\PROTOCOL.INI file.

If the workstation has a hard disk, the hard disk may need to be prepared for the Remoteboot service using the rplenabl utility.

If the remoteboot server is a backup domain controller, wait until the account you've added has been replicated (or force synchronization to the primary domain controller using Server Manager).


No Profiles Available
Remoteboot 	41 of 42

Troubleshooting Remoteboot

No Profiles Available

You have not yet created any profiles. See "Managing Profiles" earlier in this chapter.


No Configurations Available
Remoteboot 	42 of 42

Troubleshooting Remoteboot

No Configurations Available

From the Remoteboot Manager's Configure menu, choose Check Configurations. If there still are no configurations available, you have not yet copied MS-DOS files to the server. See "Installing MS-DOS Files for Remoteboot Workstations", earlier in this chapter.


Network Client Administrator
Chapter 9	1 of 14

Network Client Administrator

This chapter provides an overview on how to use the Network Client Administrator to install the following types of software:

Network client software

Client-based network administration tools

Remote Access Service (RAS) for MS-DOS

Microsoft TCP/IP-32 for Windows for Workgroups (Microsoft's new 32-bit implementation of the industry standard TCP/IP internetworking protocols)


Overview
Network Client Administrator	2 of 14

Overview

The Windows NT Server compact disc (CD) contains the following types of installation files:

Microsoft Windows for Workgroups 3.11

Microsoft Network Client for MS-DOS 3.0

Microsoft LAN Manager for MS-DOS 2.2c

Microsoft LAN Manager for MS OS/2 2.2c

Client-based network administration tools

Microsoft RAS for MS-DOS 1.1a

Microsoft TCP/IP-32 for Windows for Workgroups 3.11

The Network Client Administrator enables you to quickly install the programs and tools contained on the Windows NT Server CD. The Network Client Administrator is automatically installed in Program Manager's Network Administration group during the Windows NT Server installation.

With the Network Client Administrator, you have the following options:

The installation files on the Windows NT Server CD can be put on a shared directory.

The Network Client Administrator can create the following directory structure on a network server, and then copy the installation files contained on the Windows NT Server CD to the network server.

It is recommended that you use this method so that you can use the Windows NT Server CD as a backup copy.

To minimize the use of hard disk space, you can delete any of the directories that you do not intend to use. However, if you intend to create network installation startup disks, do not delete \CLIENTS\MSCLIENT\NETSETUP. The files contained in this directory are used to create network installation startup disks for the Microsoft Windows for Workgroups client and Microsoft Network Client for MS-DOS.

The following table describes the location and size of the installation files.

Description		Directory		Size
Microsoft LAN Manager for MS-DOS		\CLIENTS\LANMAN		3.25 MB
Microsoft LAN Manager for MS OS/2		\CLIENTS\LANMAN.OS2		3.25 MB
Microsoft Network Client for MS-DOS		\CLIENTS\MSCLIENT		5.25 MB
Microsoft RAS for MS-DOS		\CLIENTS\RAS		2.25 MB
Client-based network administration tools		\CLIENTS\SRVTOOLS		4.00 MB
Microsoft TCP/IP-32 for Windows for Workgroups		\CLIENTS\TCP32WFW		2.00 MB
Windows Driver Library containing additional network card drivers		\CLIENTS\WDL		1.00 MB
Microsoft Windows for Workgroups		\CLIENTS\WFW		21.00 MB
Total				42.00 MB


Using the Network Client Administrator
Network Client Administrator	3 of 14

Overview

Using the Network Client Administrator

Using the Network Client Administrator, you can quickly install network client software by creating a network installation startup disk or creating an installation disk set. The method you use depends on the type of network client you intend to install.

Use the following table to determine whether you need to create a network installation startup disk or an installation disk set.

Description		Network installation startup disk		Installation disk set
Microsoft Windows for Workgroups
Microsoft TCP/IP-32 for Windows for Workgroups
Microsoft Network Client for MS-DOS
Microsoft LAN Manager for MS-DOS
Microsoft LAN Manager for MS OS/2
Microsoft RAS for MS-DOS
 denotes that you can create this type of disk.  denotes that you cannot create this type of disk.

After you have installed the network client software on the target computer, you can then install RAS for MS-DOS, TCP/IP-32 for Windows for Workgroups, or client-based network administration tools. For information on how to install RAS for MS-DOS or TCP/IP-32 for Windows for Workgroups, see "Installation Disk Set," later in this section.

Client-based network administration tools enable you to have full administrative support for Windows NT, LAN Manager for MS OS/2, or LAN Manager for UNIX servers from a Windows-based computer. For information on how to install the tools, see "Installing the Client-Based Network Administration Tools," later in this chapter.

Network Installation Startup Disk

This option enables you to create disks that automatically complete the following tasks for you during the installation process for a Windows for Workgroups client or Microsoft Network Client for MS-DOS:

Start the computer

Connect to the server containing the installation files

Initiate the installation process

For a Windows for Workgroups client, you must install the software using a network installation startup disk. You cannot create an installation disk set containing the actual Windows for Workgroups installation files.

Installation Disk Set

This option enables you to create an installation disk set containing the actual installation files for the Microsoft Network Client for MS-DOS, LAN Manager for MS-DOS client, LAN Manager for MS OS/2 client, RAS for MS-DOS, or TCP/IP-32 for Windows for Workgroups. Using the installation disk set, you can install the software manually on each computer.

Tip

You can also install RAS for MS-DOS or TCP/IP-32 for Windows for Workgroups by creating a connection to the network share containing the installation files, and then installing the software over the network.


Planning for Installation
Network Client Administrator	4 of 14

Planning for Installation

Planning your software installation consists of the following steps:

Deciding whether you need to remotely boot the target computer

Determining whether the target computer meets the minimum configuration requirements for the software you intend to install

Obtaining the documentation for the software you intend to install


Using the Remoteboot Service
Network Client Administrator	5 of 14

Planning for Installation

Using the Remoteboot Service

Before you begin, decide whether you need to use the Remoteboot service, a Windows NT Server feature that starts MS-DOS and Microsoft Windows computers over the network.

If you need the target computer to have remoteboot capabilities, please note that you cannot install the Remoteboot service with the Network Client Administrator. Instead, follow the directions in Chapter 8, "Remoteboot."


Meeting Minimum Configuration Requirements
Network Client Administrator	6 of 14

Planning for Installation

Meeting Minimum Configuration Requirements

You need to gather information about the computer's hardware configuration and operating system to determine whether the computer meets the minimum configuration requirements for the software you plan to install.

Microsoft Windows for Workgroups Client

The following table describes the minimum configuration requirements for a Microsoft Windows for Workgroups client.

Category	Minimum requirement

Microprocessor	80386SX, 80486, or higher.

Memory	4 MB of RAM.

Hard disk space	80386SX computers need 8.5 MB of free disk space.80486 computers need at least 14.5 MB of free disk space.

Network card	One supported network card installed.

Operating system	MS-DOS version 5.0 or later.

Microsoft Network Client for MS-DOS

The following table describes the minimum configuration requirements for a Microsoft Network Client for MS-DOS.

Category	Minimum requirement

Microprocessor	8088 or higher.

Memory	640K of RAM.

Hard disk space	1 MB of free disk space.

Network card	One supported network card installed.

Operating system	MS-DOS version 3.3 or later.

Optional component	Microsoft Windows version 3.1.

Microsoft LAN Manager for MS-DOS Enhanced Client

The following table describes the minimum configuration requirements for a Microsoft LAN Manager for MS-DOS Enhanced client.

Category	Minimum requirement

Microprocessor	8088 or higher.

Memory	640K of RAM and either extended or expanded memory.

Hard disk space	4 MB of free disk space.

Network card	One supported network card installed.

Operating system	MS-DOS version 3.3 or later.

Optional component	Microsoft Windows version 3.1.

Microsoft LAN Manager for MS-DOS Basic Client

The following table describes the minimum configuration requirements for a Microsoft LAN Manager for MS-DOS Basic client.

Category	Minimum requirement

Microprocessor	8088 or higher.

Memory	640K of RAM.

Hard disk space	1 MB of free disk space.

Network card	One supported network card installed.

Operating system	MS-DOS version 3.3 or later.

Optional component	Microsoft Windows version 3.1 or later.

Microsoft LAN Manager for MS OS/2 Client

The following table describes the minimum configuration requirements for a Microsoft LAN Manager for MS OS/2 client.

Category	Minimum requirement

Microprocessor	80286 or higher.

Memory	4.5 MB of RAM.

Hard disk space	5 MB of free disk space.

Network card	One supported network card installed.

Operating system	Microsoft OS/2 version 1.3 or later.

Client-Based Network Administration Tools

The following table describes the minimum configuration requirements for installing the client-based network administration tools on a Windows for Workgroups client or LAN Manager for MS-DOS client.

Category	Minimum requirement

Microprocessor	80386SX, 80486SX, 80386, 80486, or Pentium.

Memory	8 MB of extended memory.

Hard disk space	3 MB of free disk space is needed for the client-based network administration tools. An additional 2 MB of free disk space is needed for Win32s™.

Network card	One supported network card installed.

Operating system	MS-DOS version 5.0 or later.

Network client software	One of the following supported platforms installed:  Windows for Workgroups or LAN Manager for MS-DOS with Windows version 3.1.


Getting Documentation
Network Client Administrator	7 of 14

Planning for Installation

Getting Documentation

The following table describes how to obtain documentation for the software you intend to install.

Software		To obtain documentation
Microsoft Windows for Workgroups		Order the retail package version of the product.
Microsoft TCP/IP-32 for Windows for Workgroups		Refer to the online Help file for Microsoft TCP/IP-32 for Windows for Workgroups.
Microsoft Network Client for MS-DOS		Refer to Appendix A, "Microsoft Network Client for MS-DOS," in this manual.
Microsoft LAN Manager for MS-DOS, Microsoft LAN Manager for MS OS/2, and RAS for MS-DOS		Fill out and return the coupon included in this package.
Client-based network administration tools		Refer to "Installing Client-Based Network Administration Tools," later in this chapter.


Starting the Network Client Administrator
Network Client Administrator	8 of 14

Starting the Network Client Administrator

To start the Network Client Administrator

In the Network Administration group, double-click the Network Client Administrator icon to display the Network Client Administrator dialog box.


Installing the Network Client Software
Network Client Administrator	9 of 14

Installing the Network Client Software

Make sure that you have enough disks on hand to complete the installation process. The number of disks you need depends on what software you choose to install. Use the following table as a guideline.

Description		Network installation startup disk	Installation disk set
Microsoft Windows for Workgroups		1 disk
Microsoft TCP/IP-32 for Windows for Workgroups			1 disk
Microsoft Network Client for MS-DOS		1 disk	1 disk
Microsoft LAN Manager for MS-DOS			4 disks
Microsoft LAN Manager for MS OS/2			4 disks
Microsoft RAS for MS-DOS			1 disk


Creating a Network Installation Startup Disk
Network Client Administrator	10 of 14

Installing the Network Client Software

Creating a Network Installation Startup Disk

If you are creating a network installation startup disk, use the guidelines described in this section.

Note

Your Windows NT Server software license does not enable you to install the Windows for Workgroups network client software. You must purchase a valid software license prior to installing Windows for Workgroups on a computer.

Make sure that the disk has been formatted using the operating system version that is resident on the target computer. Use a high-density system disk that fits the target computer's drive A. If the computer you are using to create the installation startup disk does not have a floppy drive compatible with the target computer, it is recommended that you use the following procedure.

To copy the installation files to a new directory, and then share the files

1.	Using the Network Client Administrator, follow the directions displayed on the screen to create a network installation startup disk.

2.	Indicate that you want to copy the installation files to a new directory, and then share the files when prompted.

When prompted that the destination drive does not match the drive format of the target computer's drive A, choose the OK button to continue.

When prompted that the disk is not a formatted, high-density system disk, choose the OK button to continue.

3.	Locate a computer with a floppy drive that is compatible with the target computer's floppy drive.

4.	Insert a formatted, high-density system disk in the floppy drive, and then copy the installation files from the share you created.

Make sure that you use a disk that contains the system files necessary to start the target computer; otherwise, the computer cannot be started during the installation process. If you do not have a system disk, use the following procedures.

To create a network installation startup disk using a high-density non-system disk

1.	Using the Network Client Administrator, follow the directions displayed on the screen to create a network installation startup disk.

2.	When prompted to insert a disk, insert a formatted, high-density non-system disk in the floppy drive.

When prompted that the disk you inserted is not a formatted, high-density system disk, choose the OK button.

3.	Continue following the directions displayed on the screen.

To make the network installation startup disk a system disk

1.	Insert the installation startup disk in drive A of the target computer.

2.	At the MS-DOS command prompt, type sys a: and then press ENTER to copy the hidden MS-DOS system files (IO.SYS and MSDOS.SYS) and the MS-DOS command interpreter (COMMAND.COM) to the network installation startup disk.

You now have a network installation startup disk.


Using the Network Installation Startup Disk
Network Client Administrator	11 of 14

Installing the Network Client Software

Using the Network Installation Startup Disk

If you created a network installation startup disk for a Windows for Workgroups client or Microsoft Network Client for MS-DOS, use the following procedure to install the network client software.

To install the network client software using the network installation startup disk

1.	Insert the network installation startup disk in drive A of the target computer.

2.	Reboot the target computer, and then follow the directions displayed on the screen.

Note

When installing the network client software, the target computer's name is changed to the computer name you specified when creating the network installation startup disk. You must change the computer name or the "Duplicate name on network" error message will be displayed the next time you use the network installation startup disk.


Creating an Installation Disk Set
Network Client Administrator	12 of 14

Installing the Network Client Software

Creating an Installation Disk Set

If you are creating an installation disk set, make sure that the high-density disks have been formatted using the operating system version that is resident on the target computer.

For detailed information on how to create an installation disk set for the following programs, see online Help:  Microsoft Network Client for MS-DOS, LAN Manager for MS-DOS client, LAN Manager for MS OS/2 client, RAS for MS-DOS, or TCP/IP-32 for Windows for Workgroups.


Using the Installation Disk Set
Network Client Administrator	13 of 14

Installing the Network Client Software

Using the Installation Disk Set

If you created an installation disk set for a Microsoft Network Client for MS-DOS, LAN Manager for MS-DOS client, LAN Manager for MS OS/2 client, RAS for MS-DOS, or TCP/IP-32 for Windows for Workgroups, install the software manually on each computer according to the directions in the documentation for these products.

For information about obtaining documentation for these products, see "Getting Documentation," earlier in this chapter.


Installing the Client-Based Network Administration Tools
Network Client Administrator	14 of 14

Installing the Client-Based Network Administration Tools

Client-based network administration tools enable you to have full administrative support for Windows NT, LAN Manager for MS OS/2, or LAN Manager for UNIX servers from a Windows-based computer.

To install the client-based network administration tools

1.	Using the Network Client Administrator, complete one of the following tasks:

Indicate that you want to share the installation files in the \CLIENTS\SRVTOOLS directory.

Indicate that you want to copy the installation files from the \CLIENTS\SRVTOOLS directory to a new directory, and then share the files.

2.	From the target computer, make a connection to the new share you created.

3.	Install the tools manually on the target computer using the client-based network administration tools' setup program.

To install the tools on a Windows for Workgroups client or LAN Manager for MS-DOS client, double-click the SETUP.EXE file in the WINDOWS directory of the new share you created.

The client-based network administration tools are Win32s applications. If the Win32s application programming interface (API) is not already installed on the computer, it is installed along with the client-based network administration tools.

To install the tools on a Windows NT client, double-click the setup program in the WINNT directory of the new share you created.

The setup program does not create a program group and program item. For details on how to create a program group and program item for the client-based network administration tools, see the online Help file for Program Manager.


Microsoft Network Client Version 3.0 for MS-DOS
Appendix A	1 of 18

Microsoft Network Client Version 3.0 for MS-DOS

This appendix tell how to install and use Microsoft Network Client version 3.0 for MS-DOS. Network Client is software that you install on a computer running the MS-DOS operating system so that the computer can use resources on a network. For example, a computer with Network Client can use printers, programs, and data stored on a Windows NT Server computer.

With Network Client, your computer can use resources on Microsoft networks, which are typically arranged in the following ways:

Domains have Windows NT Server computers handling the major work of network administration. You log on to the network using a single password that controls your access to resources throughout the domain. A network administrator must create a user account for you on the Windows NT Server computers.

Workgroups do not have central administration. The participating computers typically run Windows NT, Microsoft Windows for Workgroups, or Microsoft Workgroup Add-On for MS-DOS. You log on to the network using a password for your own computer, but then you may have to supply additional passwords as you connect to resources on other computers.

Other networks may have different organizations, such as Microsoft LAN Manager networks. The Network Client can connect to resources on these networks, but you may have to ask the network administrator for specific instructions on connecting to computers running older or non-Microsoft network software.

It is possible to be a member of a workgroup and of a domain, if the network has both structures already in place. In this case, you log on to the network using your domain password, but you may have to supply your workgroup password separately when you connect to resources in your workgroup.

In addition, if the computer had Novell NetWare installed before you install Network Client, you can still connect to NetWare resources (in addition to Microsoft network resources). Contact your network administrator for help setting up your computer to use both networks. Instructions for the network administrator are in the README.TXT online document located in the directory that contains the Network Client files.


Making Installation Disks
Microsoft Network Client Version 3.0 for MS-DOS	2 of 18

Making Installation Disks

A network administrator makes installation disks using the Network Client Administrator on a Windows NT Server computer. For details, see Chapter 9, "Network Client Administrator."

There are two kinds of Network Client installation disks:

An installation disk set contains all of the Network Client software. For Network Client 3.0, this is just one disk. You install manually using only this disk.

A network installation startup disk contains basic MS-DOS and Network Client software, just enough to start a client computer and then copy the full Network Client software over the network from the Windows NT Server computer. This is usually faster than installing manually.


Setting Up and Configuring Network Client
Microsoft Network Client Version 3.0 for MS-DOS	3 of 18

Setting Up and Configuring Network Client

The Setup program for Network Client identifies the computer's hardware and software, configures Network Client to run on the computer, and copies necessary files to the computer's hard disk.

Before you set up Network Client, you need to determine the following:

The user name to be used

The user name identifies a member of the workgroup or domain. Choose a unique name in the workgroup or domain.

The name to be assigned to the computer

This unique name identifies the computer within the network. Often this name is a variation of the user name.

The name of the user's workgroup and/or domain

This name determines how your computer fits in with other computers that are already organized into groups on the network. These are not names that you make up; they already exist on the network. Ask the network administrator if you don't know what names to use.

Full redirector or basic redirector

Full redirector means that you have all Network Client functions available, including logging on to domains and using advanced network applications. You can choose the basic redirector instead, which uses less memory and disk space, if you need only standard workgroup functions like connecting to shared files and printers.

To use Microsoft Windows with Network Client, you must install the full redirector, and you must start it with the net start full command before starting Windows. Windows for Workgroups and Windows NT include their own network client capabilities, and you should not run Network Client with them.

To use the Remote Access Service (connecting to a network over a phone line), you must install the full redirector.

The manufacturer and model of the network adapter

The network adapter is the card inside the computer where you plug in the network cable. The Setup program attempts to determine the model of network adapter in the computer, but it might be incorrect. Some network adapters have further configuration options; see the network administrator or the network adapter documentation if you need to change configuration options.

The network protocol used on this network

The protocol is like a language used by computers to talk to each other. Your computer must use the same protocol as the computers to which it connects. If you don't know what protocol the computers on this network use, ask the network administrator.

There are other options that you can change with the Setup program, but these are the most important options.

To set up Network Client

1.	Depending on the type of installation disk you have:

For an installation disk set (all Network Client software is on the disk), put the disk in a floppy disk drive. If you put the disk in drive A, type a:\setup at the MS-DOS command prompt, and then press ENTER. If the floppy disk drive is a different letter, use that letter instead of a.

If the computer displays an error message about lack of memory, you may need to stop other programs that take up memory, by stopping the programs or by altering the AUTOEXEC.BAT file and restarting the computer.

For a network installation startup disk, put the disk in the A drive and restart the computer. When the computer restarts it will automatically run the Network Client installation program.

A prompt appears asking you for a username and password. Supply a username and password for an account with permission to connect to the directory on the Windows NT Server computer where Network Client files are stored. When the computer displays a message about creating a password-list file, type n and then press ENTER.

The client must make a connection to the shared directory on the Windows NT Server computer. If the computer displays an error message saying that "the specified shared directory cannot be found," check that the Windows NT Server computer is indeed sharing the directory.

If the computer displays an error message about lack of memory, modify the CONFIG.SYS file on the network installation startup disk to use extended memory. For example, EMM386.EXE and HIMEM.SYS provide extended memory for MS-DOS 5.0 and later. If you do not have extended memory, use the NetBEUI or IPX protocols because they use less memory.

The network installation startup disk was configured using default settings for the network adapter. Please verify that the default settings are correct for your network adapter and modify them if necessary. (The settings are in the A:\NET\PROTOCOL.INI file.)

2.	Follow the instructions of the Setup program.

If your network adapter does not appear in the list of supported network adapters, you may be able to use one of the following instead:

"ArcNet compatible" for an ArcNet network adapter

"NE1000 compatible" for an 8-bit Ethernet network adapter that is not on the list

"NE2000 compatible" for a 16-bit Ethernet network adapter that is not on the list

If this still doesn't work, contact the network adapter manufacturer to obtain a device driver disk compatible with Microsoft Network Client or Microsoft Workgroup Add-On for MS-DOS. When you receive the driver disk, run Setup and choose Network Adapter Not Shown On List Below, and then follow the instructions.

If you need more information about any Setup dialog box, press F1 for Help.

The Network Client Setup program determines the hardware on the computer, copies the Network Client files to the hard disk, and creates and modifies network configuration files. The Setup program creates SYSTEM.INI and PROTOCOL.INI files in the directory that contains the Network Client files. These files contain information about the computer's Network Client configuration.

Setup adds a device command to the CONFIG.SYS file to install the IFSHLP.SYS device driver.

In the AUTOEXEC.BAT file, Setup adds to the path command the directory that contains the Network Client files. Also, if you specify that you want Network Client to start each time the computer is started, Setup adds the net start command. When net start runs, it examines the SYSTEM.INI file, which contains information about the startup options you specified during Setup. Setup may add additional lines to AUTOEXEC.BAT to start programs needed for specific network protocols.

The changes Setup makes to the configuration files take effect when you restart the computer after the Setup program is finished.

If your startup information changes, you can update your configuration information by running Setup again. For example, you might change your workgroup name or network card.

To update a setting after you install Network Client

1.	Change to the directory that contains your installed Network Client files, and then type setup at the command prompt.

Do not run the SETUP.EXE program that is on the installation disk.

If the computer displays an error message about lack of memory, use the net stop rdr command to stop the Network Client software before running Setup. You may need to stop other programs that take up memory, by stopping the programs or by altering the AUTOEXEC.BAT file and restarting the computer. After running Setup, either restart the computer or, if you didn't change any settings, restart Network Client by typing net start rdr.

2.	Examine the list that the Network Client Setup program displays to find the entries that you want to change. If a setting needs to be updated, press the up arrow key until you select that setting, and then press ENTER.

3.	Follow the instructions on your screen. If you need help at any time, press F1.


Getting Help
Microsoft Network Client Version 3.0 for MS-DOS	4 of 18

Getting Help

MS-DOS users can carry out Network Client commands in two ways: by using the pop-up interface or by typing commands at the MS-DOS command prompt. For both methods, online Help is available for quick information about specific Network Client commands or features.

To get help for commands typed at the MS-DOS command prompt

Type the command name followed by /?, or type net help followed by the second word in the net command.

For example, for information about the net view command, at the MS-DOS command prompt type net view /? or type net help view.

To get a summary of all Network Client commands

At the MS-DOS command prompt, type net /? | more and press ENTER.

To get help while using the pop-up interface

Press F1 or ALT+H.


Starting Network Client and Logging On
Microsoft Network Client Version 3.0 for MS-DOS	5 of 18

Starting Network Client and Logging On

During Setup, you specify whether you want Network Client to start automatically every time the computer is started. You also specify whether a prompt appears to log on to the workgroup and/or to a domain at startup time. The default settings are to automatically start Network Client and prompt for logon each time the computer is started.

If you specify in Setup that Network Client should not start automatically, the user must start it.

To start Network Client and log on to the workgroup

1.	At the MS-DOS command prompt, type net logon and press ENTER.

2.	If Network Client hasn't started, a prompt asks whether to start the workstation service. Type y and then press ENTER.

3.	If the prompt displaying the user name is correct, press ENTER.

If you are logging on at someone else's computer, type your user name, and then press ENTER.

4.	At the prompt for a password, type your password, and then press ENTER.

If you are logging on for the first time, you can specify any password up to 14 characters long. A prompt asks you to type your password again to confirm that it is correct. This is your workgroup password.

5.	If you are logging on for the first time, and the computer is in a Window NT Server domain, a prompt for the domain password appears. Type your domain password and press ENTER.

After you type your password(s), Network Client reestablishes your persistent connections, if you have any. These are connections that you made before and specified that you want to have reestablished every time you log on to your workgroup. For more information, see the online Help for net use.

Your workgroup password authorizes access to your password list file, which is a list of the passwords for connections made that are password-protected. If you do maintain a password list file, and you do log on to a domain, the password list file will also hold your domain password. For more information about the password list file and how to change your password, see the online Help for net password.

If you have trouble starting or using Network Client, see the "Troubleshooting" section later in this appendix.


Using Network Client
Microsoft Network Client Version 3.0 for MS-DOS	6 of 18

Using Network Client

MS-DOS users can issue Network Client commands by using the pop-up interface or by typing commands at the MS-DOS command prompt.

If you use the pop-up interface, you don't have to remember the syntax for the equivalent Network Client command at the MS-DOS command prompt. The pop-up interface also allows you to view your current connections, browse for shared resources, and make new connections in an easy-to-use environment. It is a character-based utility; you must use the keyboard rather than a mouse.

Experienced MS-DOS users who are familiar with Network Client commands may prefer to type commands at the MS-DOS command prompt rather than using the pop-up interface.


Loading and Displaying the Pop-Up Interface
Microsoft Network Client Version 3.0 for MS-DOS	7 of 18

Using Network Client

Loading and Displaying the Pop-Up Interface

You can load and display the pop-up interface simultaneously or as two separate operations. Loading and displaying the pop-up interface simultaneously is easier than performing the operations separately, and it makes more efficient use of memory. You load and display the interface by typing a single command. When you finish using the interface, Network Client unloads it from memory, freeing about 29K of memory for programs. The disadvantage is that you cannot use the interface while using another program.

To load and display the pop-up interface simultaneously

1.	At the MS-DOS command prompt, type net and press ENTER.

The pop-up interface appears.

2.	When you finish using the interface, press ESC. Network Client unloads the interface from memory.

The advantage of loading and displaying the pop-up interface separately is that you can display it at any time, either from the MS-DOS command prompt or while you are using another program. One disadvantage is that you need to use separate commands to load, display, and unload the interface. Also, the pop-up interface occupies about 29K of memory, whether you are using it or not, until you explicitly unload it.

To load and display the pop-up interface separately

1.	At the MS-DOS command prompt, type net start popup and press ENTER.

Note

If the pop-up interface is loaded into memory automatically when you start the computer, skip this step.

2.	When you want to display the pop-up interface, press ctrl+ALT+N.

If during Setup you chose a key other than N to display the pop-up interface, press CTRL+ALT plus the key you specified.

When you finish using the pop-up interface, you can unload it from memory.

To unload the pop-up interface from memory

At the MS-DOS command prompt, type net stop popup and press ENTER.


Using Shared Directories
Microsoft Network Client Version 3.0 for MS-DOS	8 of 18

Using Network Client

Using Shared Directories

With Network Client, members of your workgroup can exchange information using shared directories. Shared directories are directories to which all users on a network have access. You use shared directories the same way you use the directories on your local hard disk, except that you have to connect to shared directories before you can use the files on them.

To use a file in a shared directory, you need to know the name of the computer that contains the shared directory and the name of the shared directory that contains the file you want. After you establish a connection, you treat the shared directory as if it were a disk drive on your computer.

You connect to a shared directory by assigning a drive letter to it.

To connect your computer to a shared directory

1.	Display the pop-up interface as described earlier in this appendix.

2.	In the Path field of the Disk Connection pop-up, type two backslashes, the name of the computer, and the shared directory that you want to connect to.

For example, to connect to a directory named PUBLIC on a computer named RENE, type \\rene\public in the Path field.

If you're not sure of the name of the computer or directory you want to connect to, you can browse through a list by choosing the Browse button (press ALT+B, and then press F1 for help). Browsing will show you only the computers in your workgroup.

3.	To assign a drive letter to the shared directory, choose the Drive field by pressing ALT+V, type the drive letter you want to use, and then press ENTER.

If you do not specify a drive letter for the shared directory, Network Client assigns the first available drive letter.

4.	If you want to connect your computer to the shared directory every time you log on, make sure an X appears in the Reconnect At Startup check box.

To select or clear the Reconnect At Startup check box, press ALT+R.

5.	To connect to the shared directory specified in the Path field, choose the Connect button by pressing ALT+C.

You can also connect to a shared directory by issuing the net use command at the MS-DOS command prompt. For information on the net use command and its syntax, see the online Help for net use.

For information about browsing for shared directories and disconnecting from a shared directory, press F1 in the pop-up interface, or see the online Help for the net view and net use commands.

Note

Your workgroup may include computers that share directories but do not appear in the Browse dialog box. You can try connecting to these computers, even though you cannot browse for their names.


Using Shared Printers
Microsoft Network Client Version 3.0 for MS-DOS	9 of 18

Using Network Client

Using Shared Printers

You can print files with Network Client by sending them from your computer to printers that are shared by members of your workgroup. Connecting to a shared printer allows you to use it as if it were physically connected to your computer. You connect your computer to a shared printer by assigning a parallel port (LPT) to it. You can use port LPT1, LPT2, or LPT3.

To connect your computer to a shared printer

1.	Display the pop-up interface, as described earlier in this appendix.

2.	Choose the Show Printers button by pressing ALT+S.

3.	In the Port field of the Printer Connection dialog box, type two backslashes and the number of the parallel port (LPT) that you want to assign to the shared printer, and then press TAB.

4.	In the Path field, type the name of the computer and shared printer that you want to connect to. For example, to connect to a printer named LASER that is physically connected to a computer named CLIVE, type \\clive\laser in the Path field.

5.	If you want to connect your computer to this printer every time you log on to your workgroup, make sure an X appears in the Reconnect At Startup check box.

To select or clear the Reconnect At Startup check box, press ALT+R.

6.	To connect to the shared printer specified in the Path field, choose the Connect button by pressing ALT+C.

You can also issue the net use command at the MS-DOS command prompt to connect to a shared printer. For information on the net use command and its syntax, see the online Help for net use.

For information about browsing for shared printers and disconnecting from a shared printer, press F1 in the pop-up interface, or see the online Help for the net view and net use commands.

Note

Your workgroup may include computers that share printers but do not appear in the Browse dialog box. You can try connecting to these computers, even though you cannot browse for their names.

After you connect your computer to a shared printer, you can print formatted files from the application you used to create them. You can also print unformatted text files from MS-DOS with the print command. For more information, see the online Help for the print command.

You can also display the pop-up interface to pause, resume, or delete a print job, and to view the print queue, which is the list of files that are waiting to print on a particular printer. For information, see the online Help for the pop-up interface or for the net print command.


Using Network Client with Microsoft Windows
Microsoft Network Client Version 3.0 for MS-DOS	10 of 18

Using Network Client

Using Network Client with Microsoft Windows

This section contains information about configuring Microsoft Windows so that it runs with Network Client for MS-DOS.

Note

Windows for Workgroups and Windows NT include their own network client capabilities, and you should not run Network Client with them.

To use Microsoft Windows with Network Client, you must install the full redirector, and you must start it with the net start full command before starting Windows.

To configure Windows to run with Network Client for MS-DOS

1.	Start Windows.

2.	In the Main group, choose the Windows Setup icon.

The Windows Setup window appears. It lists your current display, keyboard, mouse, and network settings.

3.	From the Options menu, choose Change System Settings.

The Change System Settings dialog box appears.

4.	Open the list for the Network setting by clicking the arrow to the right of it. Or press TAB until you select the Network setting, and then press ALT+DOWN ARROW to open the list.

5.	Click Microsoft Network (or 100% compatible), or select it by pressing the UP ARROW or DOWN ARROW key.

6.	Choose the OK button.

Setup may prompt you to insert a Windows Setup disk in drive A. If it does, insert the disk. However, if the file for the Microsoft Network device driver is in a directory on your hard disk, you can type its path in the box instead.

7.	Choose the OK button.


Troubleshooting
Microsoft Network Client Version 3.0 for MS-DOS	11 of 18

Troubleshooting

This section provides help if you encounter problems when using Network Client for MS-DOS.


Network Client Won’t Start After a Successful Setup
Microsoft Network Client Version 3.0 for MS-DOS	12 of 18

Troubleshooting

Network Client Won't Start After a Successful Setup

If Network Client won't start after you complete Setup, try the following steps to solve the problem:

Make sure that all cables and connectors are securely fastened and that the network adapter is securely in its slot.

If the network adapter came with a diagnostics program, try running the program. For more information, see the documentation that came with the network adapter.

Run the net diag command. You can use net diag to test a specific connection with another computer or you can use net diag /status to see the status of your own network adapter. For information, type net help diag at the MS-DOS command prompt.

If you are using an external transceiver, specify the correct setting. For more information, see the following section, "Specifying an External Transceiver."

Make sure the correct base memory address and interrupt request (IRQ) settings are specified for the network adapter. For more information, see "Checking and Changing Network-Adapter Settings," later in this appendix.

Make sure the device command for EMM386 in your CONFIG.SYS file excludes the memory address used by your network adapter. For more information, see "Making Sure EMM386 Doesn't Conflict with the Network Adapter," later in this appendix.

Make sure the network adapter is on the list provided in Setup. If your network adapter is not on this list, you might be able to get it to work by using a generic setting. For more information, see the Setup instructions earlier in this appendix.

Make sure the network adapter is using a different interrupt (IRQ) than the mouse. For more information about determining what interrupt to assign to the network adapter, see the documentation that came with the network adapter.

If you are using the NWLink (IPX/SPX-compatible) protocol, make sure the network adapter is set for the proper network topology type. NWLink supports Ethernet network adapters only on 802.2 topology and token ring and FDDI network adapters only on 802.3 topology.

You might need to change the network adapter's configuration settings. If you have an ISA adapter that is configured by using jumpers and switches, you might need to change their positions or settings. If you have a software-configured adapter, use the configuration program that came with the network adapter to change your settings. For more information, see the documentation that came with the network adapter.


Specifying an External Transceiver
Microsoft Network Client Version 3.0 for MS-DOS	13 of 18

Troubleshooting

Specifying an External Transceiver

This section applies to you only if your network adapter is attached to an external transceiver. An external transceiver is a small box that connects the network cable to the cable that attaches to a network adapter. Only some Ethernet network adapters use external transceivers.

To specify that you are using an external transceiver

1.	Start the Network Client Setup program, as described earlier in this appendix.

2.	Select Change Network Configuration by pressing the UP ARROW key, and then press ENTER.

A list of options for modifying network-adapter and protocol settings appears.

3.	Select Change Settings by pressing the UP ARROW key, and then press ENTER.

A list of network-adapter and protocol settings appears.

4.	Press the UP ARROW key until you have selected the Transceiver setting, and then press ENTER.

A list of values appears.

5.	From the list of values, select External, Thick, or DIX (depending on what kind of transceiver you have) by pressing the UP ARROW or DOWN ARROW key. Then press ENTER.

The new value appears on the Transceiver line in the list of network-adapter settings.

6.	Press ENTER, and then follow the instructions on the screen to complete Setup.

7.	When Setup is complete, restart the computer by pressing ENTER.

If Network Client still does not start, proceed to the following section.


Checking and Changing Network-Adapter Settings
Microsoft Network Client Version 3.0 for MS-DOS	14 of 18

Troubleshooting

Checking and Changing Network-Adapter Settings

The Network Client Setup program examines your computer's configuration and attempts to determine the network adapter's base memory address and interrupt request (IRQ) setting. If Setup incorrectly identifies these, Network Client will not start.

For information about determining the correct settings yourself, see the documentation that came with the network adapter.

After you determine the correct base memory address and interrupt setting, you can specify them by running Setup again.

To change the base memory address or interrupt setting

1.	Start the Network Client Setup program, as described earlier in this appendix.

2.	Select Change Network Configuration by pressing the UP ARROW key, and then press ENTER.

A list of options for modifying network-adapter and protocol settings appears.

3.	Select Change Settings by pressing the UP ARROW key, and then press ENTER.

A list of network-adapter and protocol settings appears.

4.	If you want to change the setting for the network adapter's interrupt, proceed to step 5. If you want to change the setting for the network adapter's base memory address, do the following:

Select the setting for the base memory address by pressing the UP ARROW key, and then press ENTER. This setting is named Memory Window, RAM Address, or something similar. You might have to press the PAGE UP or PAGE DOWN key to find this setting.

A list of values appears.

Select the base memory address you want by pressing the UP ARROW or DOWN ARROW key, and then press ENTER.

The new value appears on the base memory address line in the list of network-adapter settings.

5.	If you do not want to change the network adapter's interrupt setting, proceed to step 6. If you want to change the setting, do the following:

Select the interrupt setting by pressing the UP ARROW key, and then press ENTER. This setting is named IRQ_Level, Interrupt, or something similar. You might have to press the PAGE UP or PAGE DOWN key to find this setting.

A list of values appears.

Select the interrupt you want by pressing the UP ARROW or DOWN ARROW key, and then press ENTER.

The new value appears on the interrupt line in the list of network-adapter settings.

6.	Choose The Listed Options Are Correct by pressing ENTER. Then follow the instructions on the screen to complete Setup.

7.	When Setup is complete, restart the computer by pressing ENTER.

If Network Client still does not start, proceed to the following section.


Making Sure EMM386 Doesn’t Conflict with the Network Adapter
Microsoft Network Client Version 3.0 for MS-DOS	15 of 18

Troubleshooting

Making Sure EMM386 Doesn't Conflict with the Network Adapter

If you use the EMM386 memory manager, make sure that it does not use the same memory that the network adapter uses. If you are using a different memory manager, such as Qemm™ or 386MAX®, see the documentation that came with that memory manager.

To ensure that EMM386 doesn't conflict with the network adapter

1.	Use any text editor to open the CONFIG.SYS file.

2.	Look for the device command line for the EMM386 memory manager. It should look similar to the following:

device=c:\dos\emm386.exe

If the CONFIG.SYS file does not contain a device command for EMM386, you are not using EMM386.

3.	If the CONFIG.SYS file contains a device command for EMM386, add the following to that command line:

x=mmmm-

For mmmm, specify the base memory address of your network adapter. For nnnn, specify a value that is 32K greater than mmmm by using the following method:

If the second character in mmmm is 8, the last three characters you specify for should be FFF. For example, if the base memory address is D800, the device command line should look similar to the following:

device=c:\dos\emm386.exe x=D800-DFFF

If the second character in mmmm is 0, the last three characters you specify for should be 7FF. For example, if the base memory address is C000, the device command line should look similar to the following:

device=c:\dos\emm386.exe x=C000-C7FF

Note

This method for determining the value for is based on a network-adapter device driver that uses 32K of memory. The values for mmmm and are hexadecimal numbers. Check your network-adapter documentation to see if the network adapter uses more or less than 32K of memory. If it does, adjust the value for accordingly. For example, if the adapter uses only 16K of memory, the characters to specify for in the preceding two examples would be DBFF and C3FF, respectively.

4.	Save the CONFIG.SYS file, and then quit the text editor.

5.	Restart the computer.


Shared Resources Are Not Listed
Microsoft Network Client Version 3.0 for MS-DOS	16 of 18

Troubleshooting

Shared Resources Are Not Listed

If the names of shared resources do not appear when you use the Browse dialog box in the pop-up interface or when you type net view at the MS-DOS command prompt, try the following:

Make sure the network-adapter settings are correct. For more information, see "Specifying an External Transceiver" and "Checking and Changing Network-Adapter Settings," earlier in this appendix.

Sometimes, when a computer in your workgroup is turned off or restarted, you won't be able to see other computers on the network for a few minutes. Wait a few minutes, and then check again.

If you know the name of the shared directory or printer you want to connect to, try connecting to it by typing the path of the shared directory or printer in the Path field of the Disk Connections or Printer Connections dialog boxes. Or specify the path by using the net use command at the MS-DOS command prompt.


The Computer You Want to Connect to Is Not Listed
Microsoft Network Client Version 3.0 for MS-DOS	17 of 18

Troubleshooting

The Computer You Want to Connect to Is Not Listed

If a computer on the network does not appear when you use the Browse dialog box in the pop-up interface or when you type net view at the MS-DOS command prompt, one of the following might be the cause:

The computer might have been recently restarted. Wait a few minutes, and then try again.

If a computer is part of another workgroup (not your own), you cannot use the Browse dialog box in the pop-up interface to display it. To see a list of computers in another workgroup, you must use the net view command with the /workgroup option at the MS-DOS command prompt. For more information, type net help view at the MS-DOS command prompt.


The Mouse Doesn’t Work Correctly
Microsoft Network Client Version 3.0 for MS-DOS	18 of 18

Troubleshooting

The Mouse Doesn't Work Correctly

If the mouse worked correctly before you set up Network Client, but doesn't work afterward, the mouse might be using the same interrupt setting as the network adapter. Try assigning a different interrupt to the network adapter.

For information about determining the correct interrupt setting for the network adapter, see the documentation that came with the network adapter. For information about how to change the interrupt setting, see "Checking and Changing Network-Adapter Settings," earlier in this appendix.