Copyright: Copyright 1993 Microsoft Corp.
Citation: Copyright 1993 Microsoft Corporation. All rights reserved.


 Windows NT Version 3.5 Technical Library Catalog (TLC) Contents

Prepared 01/13/95

 Knowledge Base Articles Included in TLC

THE INFORMATION IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES EITHER EXPRESSED OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FORGOING EXCLUSION OR LIMITATION MAY NOT APPLY.Copyright (c) 1994 Microsoft Corporation.  All rights reserved.


Knowledge Base Articles Included in TLC
 Windows NT Version 3.5 Technical Library Catalog (TLC) Contents

 Knowledge Base Articles Included in TLC

 How To Obtain Windows NT Version 3.5 U.S. Service Pack

 README.TXT: Windows NT Version 3.5 U.S. Service Pack

 Problems Installing Other Operating System after Windows NT

 ROM BIOS Shadowing Not an Advantage with Windows NT

 Default Drive Letters and Partitions in Windows NT

 Windows NT File Size and Partition Size Limits

 Memory Available to MS-DOS Applications with Windows NT

 Isolating General Printing Problems

 Windows NT Boots, But Looks for Wrong Boot Directory

 1024-Cylinder Limitation on SCSI and ESDI Drives

 Frequently Asked Questions about TCP/IP

 Network Interface Printers Need DLC Protocol

 Automated Setup for Windows for Workgroups and TCP/IP

 MS-DOS-Based Applications and Command Prompts

 Increasing Memory for MS-DOS-Based Applications

 Files Needed to Set Up Remote Access Service (RAS)

 Enabling TCP/IP Routing

 Tuning NWLINK Registry Parameters

 Optimizing Your Paging File (PAGEFILE.SYS)

 How To Obtain TCP/IP-32 3.11a for Windows for Workgroups

 Windows NT File System Files

 Overview of FAT, HPFS, and NTFS File Systems

 Windows NT Driver Library

 Detecting Windows NT Serial Ports

 Environment Variables in Windows NT

 Windows NT Removable Media Requirements and Limitations

 Reconstructing BOOTSECT.DOS

 Recreating the Windows NT Mail Postoffice

 How to Manually Delete Print Shares or Printers

 Migrating Windows 3.1 Program Groups to Windows NT

 README.TXT: Windows NT Version 3.1 U.S. Service Pack

 User Authentification with Windows NT

 LMHOSTS File Information and Predefined Keywords

 Problems with WFW to Windows NT Connectivity

 Information on Browser Operation

 Migrating Windows 3.1 Groups After Installation

 How To Install the Sony CDU-31A CD-ROM with Windows NT

 How to Troubleshoot TCP/IP Connectivity with Windows NT

 Network Access Validation with Windows for Workgroups

 How to Remove Windows NT Boot Sector

 Descriptions of Bug Codes for Windows NT

 Installing the Sound Blaster CD-ROM Driver for Windows NT

 Network Access Validation Algorithm and Example

 Windows NT Parallel Ports Do Not Use Interrupts

 Setup Hangs During SCSI Detection; Disabling SCSI Detection

 Implementing Scheduled Backups with Windows NT Backup

 Troubleshooting 16-Bit Windows Applications Under Windows NT

 Adding More Than Two IDE or ESDI Drives in Windows NT

 Changing Setup Media, Description of Setup Information Files

 Troubleshooting Directory Replicator Problems

 Operating the HP ScanJet IIC/P with Windows NT

 STOP Message: Trap 7F Exception Errors in Windows NT

 How To Obtain Windows NT Version 3.1 U.S. Service Pack

 Microsoft Networking Client Pack Availability

 WFW RAS to Windows NT: "Access Denied" After Password Change

 Mitsumi CD-ROM Support Information

 Creating a Setup Disk for the Updated WFW 3.11 TCP/IP Drivers

 Error Messages Caused by Incorrect Serial Port Configuration

 Using the Windows NT NetDDE Share Manager

 Windows NT Boot Process and Hard Disk Constraints

 RAS Event ID (Error Code) Information

 How Browsing a Wide Area Network Works

 How to Install ISDN on WFWG 3.11 RAS

 File Copy to Netware Server Fails in File Manager

 Supported NetWare Utilities and Applications Under Windows NT

 Using WIN32S Windows Sockets Applications with TCP/IP-32

 Creating Customized Configuration Defaults for TCP/IP-32

 DEC 205 EtherNet Card and TCP/IP-32

 Setting the Name Resolution Search Order for TCP/IP-32

 Using a Numeric Hostname with TCP/IP-32

 Err Msg: Setup Error 108 or 110 During TCP/IP-32 Installation

 Shiva Remote 3.1.0 and TCP/IP-32

 Microsoft TCP/IP-32 and Sockets Support

 Creating a Boot Disk for an NTFS Partition

 TCP/IP-32: ARP -S Switch Fails on First Entry Added to ARP Cache

 Network DDE Applications Fail with TCP/IP-32

 IBM Token Ring Adapter Problems with Base I/O Address

 Detection of Duplicate IP Addresses by Microsoft TCP/IP

 TCP/IP & NBT Configuration Parameters for Windows NT 3.5

 DHCP (Dynamic Host Configuration Protocol) Basics

 DHCP: Spanning Multiple Subnets

 Troubleshooting NET USE Across a Router Using TCP/IP-32

 Obtaining Latest Novell Client Windows Drivers and DLLs

 Using ACM/1600, ACM/400, ACM/100 with Remote Access Service

 Setup and Boot Hangs on HP NetServer Computer

 Settings for 3C509 Not Detected Correctly

 Windows NT 3.5 Drivers for Compaq Devices

 Enabling Routing of IP Packets on RAS Clients

 Disabling Printing Notification Dialog Boxes in Windows NT 3.5

 Using Rumba with TCP/IP-32

 Err Msg: Error 7361: IPX or NetBIOS Must Be Running...

 TCP/IP-32 May Fail on Token Ring Network with Source Routing

 Err Msg: Hard Drive Partition... w/Quantum 540 MB IDE Drive

 Err Msg: Mail Could Not Read the Entire Message...

 README.TXT: TCP/IP-32 3.11a for Windows for Workgroups

 Err Msg: Error 692: Hardware Failure in Port or Attached....

 System Stops Responding During Shutdown and Restart Process

 How To Configure Windows NT as a Remote IP Router

 RAS Error 652 with US-Robotics 14400 Sportster

 Losing Connections with HP JetDirect Printers


How To Obtain Windows NT Version 3.5 U.S. Service Pack

Article ID: Q121693

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT 3.5 Workstation and Server U.S. Service Pack 1

----------------------------------------------------------------------

 ** THIS U.S. SERVICE PACK 1 IS FOR WINDOWS NT VERSION 3.5 ONLY!! **

The Windows NT 3.5 Workstation and Server U.S. Service Pack 1 is a

cumulative build of all fixes to Windows NT Workstation and Windows NT

Server version 3.5.

To find out which bugs are fixed by this update, see the README.TXT file

that accompanies the Service Pack or query on the following word in the

Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

AVAILABLE FORMATS

-----------------

Service Pack 1 is available in two formats:

   35SP1.EXE   A single 1.2 Mb self-extracting archive file,

               for Intel (x86) computers.

               Softlib number: S15094

   35SP1-.EXE  A single 1.7 Mb self-extracting archive file,

               for x86, MIPS, and ALPHA computers.

               This also includes symbol files for debugging.

               Softlib number: S15095

ELECTRONIC SERVICES

-------------------

35SP1.EXE and 35SP1-.EXE are available on the following electronic

services:

   Internet: ftp.microsoft.com (198.105.232.1)

      ftp: //ftp.microsoft.com/softlib/msfiles

       -or-

      ftp: //ftp.microsoft.com/bussys/winnt/winnt-public/fixes/nt35/ussp1

   CompuServe:

      Microsoft Software Library (GO MSL)

       -or-

      WINNTDL download area (GO WINNTDL)

   GEnie: Software Library

   Microsoft OnLine: Software Library

   Microsoft Download Service (206)936-6735

NOTE: Search for 35SP1.EXE or 35SP1-.EXE to find the format you wish to

download. On CompuServe:MSL and Microsoft OnLine, you can also search for

the corresponding Softlib number.

EXPANDING THE ARCHIVE FILE

--------------------------

35SP1.EXE   To create a single 3.5-inch floppy disk upgrade, execute the

            following command with a blank, formatted 1.44 Mb disk in your

            floppy drive:

               35SP1.EXE A: (assuming A: is your 3.5-inch floppy drive)

            Alternatively, 35SP1.EXE can be expanded into a directory on

            your hard disk by copying 35SP1.EXE to the preferred directory

            and executing the command:

               35SP1.EXE

35SP1-.EXE  To expand 35SP1-.EXE into a directory on your hard disk,

            execute the following command (NOTE: The "-d" switch is

            critical):

               35SP1-.EXE -d <path>

               (where "<path>" is the directory on your hard disk)

INSTALLATION OF THE SERVICE PACK

--------------------------------

After expanding the archive file, read the README.TXT for instructions on

installing the Service Pack.

Additional reference words: prodnt 3.50 servpack sp1 bug fix

KBCategory: kbnetwork kbfile

KBSubcategory: ntdistrib


README.TXT: Windows NT Version 3.5 U.S. Service Pack

Article ID: Q123863

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

Following is the README.TXT file that accompanies the Microsoft Windows

NT 3.5 Workstation and Server U.S. Service Pack 1:

---------------------------------------------------------------------------

              Microsoft Windows NT 3.5 Workstation and Server

                            U.S. Service Pack 1

---------------------------------------------------------------------------

Contents

--------

1.0  Introduction

2.0  Installation Instructions for the Windows NT U.S. Service Pack 1

2.1  User Notes

3.0  Software Update for Windows NT 3.5 for the Pentium Floating Point

     Error

3.1  Performance Considerations

3.2  Running PENTNT.EXE

3.3  Registry Entry

4.0  Calculator Application

1.0  Introduction

-----------------

This release of Microsoft(R) Windows NT(TM) U.S. Service Pack 1 contains a

fix to the Calculator application, and also a fix to disable the floating

point unit on Intel(R) Pentium(TM) machines.

The Service Pack is easy to apply from within Windows NT and changes only

those files that were originally set up on the Windows NT Workstation or

Windows NT Server system.  Service Pack releases are cumulative: they

contain all previous fixes, as well as any new fixes made to the system.

2.0  Installation Instructions for the Windows NT U.S. Service Pack

-------------------------------------------------------------------

Installing the Service Pack from a floppy disk:

1.  Insert Service Pack Disk 1 into the floppy drive.

2.  At the Windows NT Command Prompt, change to that floppy drive (that is,

    A: or B:) and type UPDATE.

3.  Follow the instructions given on the screen.

Installing the Service Pack from a CD-ROM:

1.  Insert the Service Pack CD-ROM disk into the CD-ROM drive.

2.  At the Windows NT Command Prompt, change to that CD-ROM drive, then

    change to the i386, MIPS, or ALPHA directory (depending upon whether

    you have an Intel(TM), MIPS(R), or ALPHA AXP(TM) CPU), and type UPDATE.

3.  Follow the instructions given on the screen.

Installing the Service Pack from a network drive:

1.  At the Windows NT Command Prompt, type the command to connect to the

    network drive on which the Service Pack files reside.

2.  Change to that network drive and type UPDATE.

3.  Follow the instructions given on the screen.

2.1  User Notes

---------------

*** Emergency Repair Disk

If it is necessary to use the Windows NT Emergency Repair Disk to repair

your Windows NT system at some time after you apply the Service Pack, you

will need to re-apply the Service Pack after the repair is completed.  This

is because the Emergency Repair Disk repairs your system by restoring your

original Windows NT setup.  After the repair has completed, simply follow

the above Installation Instructions to reapply the Service Pack.

*** Adding New Components to the System

If new software or hardware components are changed or added to your system

after you have applied the Service Pack, it will be necessary to reapply

the Service Pack.  This is because the files taken from the original

Windows NT disk set may not be equivalent to the files on the Service Pack

disk set.

It is not possible to install new components directly from the Service Pack

media (such as a new keyboard or printer driver).  New components must be

installed from the original product media.

*** Installing Symbol Files from the CD-ROM

To install the symbol files corresponding to the new binaries in Service

Pack 1, do the following (assuming your CD-ROM drive is D:, your symbol

files are located in the C:\WINNT\SYMBOLS directory, and you are installing

the files for an x86 machine):

    XCOPY /S /U /D D:\SUPPORT\DEBUG\I386\SYMBOLS C:\WINNT\SYMBOLS

This will copy the Service Pack 1 .DBG files over the existing versions of

these files.  The XCOPY command shown will copy only those .DBG files that

are already installed (/U switch), and only those with a more recent time-

date stamp (/D switch).

3.0 Software Update for Windows NT 3.5 for the Pentium Floating Point Error

---------------------------------------------------------------------------

This release of Windows NT 3.5 U.S. Service Pack 1 includes a utility

(PENTNT.EXE) that, on Pentium-based systems, checks whether the processor

contains the floating point division error, reports the current status of

floating point, and allows disabling and re-enabling of hardware floating

point.

This software effectively turns off the math coprocessor by trapping the

floating point instructions.  This makes the Pentium processor behave

similarly to 486SX or 386 processors that do not have a math coprocessor.

The utility works on Pentium and x86 systems.

Additionally, the solution is implemented through registry settings so that

system policy administrators can control the use of Pentium floating point

hardware on user systems.

3.1  Performance Considerations

-------------------------------

Core operating system code (for window management, disk and file

operations, and application programming interfaces) in Windows NT does not

perform floating point calculations, and so will not be affected either by

the potential floating point hardware division errors, or by disabling

hardware floating point.  However, choosing software emulation of floating

point will result in lower performance of floating point operations.  Some

utilities and applications such as the Calculator application provided with

Windows NT, and the OpenGL rendering engine, may use floating point

hardware when present.  Most word processors, databases, email, and so on,

perform few or no floating point operations.

Math-intensive applications, including spreadsheets and technical

applications, typically perform floating point operations, and therefore

will experience some performance degradation.  The OpenGL rendering engine,

which is part of Windows NT 3.5, and other 3D and CAD applications, are

instances of this type of application.  The user of such applications will

be able to choose between the higher speed of hardware floating point, or

slower floating point software emulation libraries, which will not

encounter the Pentium floating point division error.  Many applications

contain their own floating point libraries to use in this case.  A few

applications (such as Autocad) require floating point hardware and will not

run without it.  Customers running these applications will need to replace

their Pentium processor in order to avoid the floating point division

error.  The floating point software emulation's libraries are used on

systems with 486SX or 386 processors.

3.2  Running PENTNT.EXE

-----------------------

To start the PENTNT.EXE utility, at the MS-DOS prompt type:

    PENTNT [-C|-c] [-F|-f] [-O|-o] [-?|-H|-h]

The utility will test floating point division.  If no error is found, a

message will appear recommending that you use floating point hardware.  If

a division error is detected, a message appears notifying you of the error.

You then have several choices: to disable floating point hardware only if

you are using a Pentium processor with a division error, or disable

floating point hardware always.  If you choose to disable or re-enable

floating point emulation, you must restart the computer for the changes to

take effect.

The complete PENTNT command syntax is as follows:

PENTNT [-C|-c] [-F|-f] [-O|-o] [-?|-H|-h]

where:

-C|-c      Turns on conditional emulation.  This means that floating point

           emulation will be forced on if and only if the system detects

           the Pentium floating point division error at start time.  If you

           select this parameter, you must restart the computer for the

           changes to take effect.

-F|-f      Turns on forced emulation. This means that floating point

           hardware is disabled and floating point emulation will always be

           forced on, regardless of whether the system exhibits the Pentium

           division error.  This parameter is useful for testing software

           emulators and for working around floating point hardware defects

           known to the operating system.  If you select this parameter,

           you must restart the computer for the changes to take effect.

-O|-o      Turns off forced emulation and re-enables floating point

           hardware if it is present.  If you select this parameter, you

           must restart the computer for the changes to take effect.

-?|-H|-h   Displays help for the command.

3.3  Registry Entry

-------------------

The Registry entry for the PENTNT utility is located in the Registry

subtree HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager.

The following parameter is used by the PENTNT utility:

REG_DWORD

ForceNpxEmulation = 0 | 1 | 2

Specifies if the floating point emulation is turned on or off.  If set to

0, floating point emulation is not enabled and floating point hardware is

enabled. If set to 1, conditional floating point emulation is enabled.  If

set to 2, unconditional emulation is enabled.  By default, this parameter

is set to 0.

4.0  Calculator Application

---------------------------

This release of the Windows NT 3.5 U.S. Service Pack 1 contains a new

version of the Calculator application that fixes a display error in

floating point number calculations.  This display error is unrelated to the

Pentium processor floating point division hardware.  The fixed Calculator

application (CALC.EXE) is included for all Microsoft Windows NT systems,

and works on all hardware platforms supported by Windows NT.

KBCategory: kbreadme

KBSubcategory: ntdistrib

Additional reference words: prodnt 3.50 servpack sp1 bug fix


Problems Installing Other Operating System after Windows NT

Article ID: Q92383

-------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

-------------------------------------------------------------

SUMMARY

=======

After you successfully install Windows NT version 3.1, Microsoft does

not recommend that you install other operating systems on the same

computer.

MORE INFORMATION

================

When Microsoft Windows NT is installed over a previous operating

system, it copies the contents of the boot sector to a file called

BOOTSECT.xxx in the root directory. The extension of this file is

determined by the previously installed operating system; in the case

of MS-DOS, the extension would be .DOS; in the case of OS/2 version

1.x, the extension would be .OS2. It then copies a Windows NT startup

utility called the Boot Loader into the boot sector.

When the system is restarted, this utility presents you with a choice

of which operating system to start. Once you have made your selection,

the Boot Loader locates either the Windows NT bootstrap or the

BOOTSECT.xxx file, and turns over control.

If you install another operating system or upgrade to another

operating system after installing Windows NT, that process generally

replaces the Boot Loader in the boot sector, destroying the dual boot

opportunity, and effectively preventing Windows NT from starting

(booting).

To recover from this, you can use the Emergency Repair Disk. Choose

Verify Boot Files from the main menu.

Note: MS-DOS 6.0 upgrade leaves the NT Boot Loader intact--MS-DOS 6.0

OEM Setup does not.

Additional reference words: prodnt stepup 3.10 win32 boot setup overwrites

KBCategory: kbinterop kbfasttip

KBSubCategory: ntinterop


ROM BIOS Shadowing Not an Advantage with Windows NT

Article ID: Q92766

-------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

-------------------------------------------------------------

Summary:

Some machines provide the ROM BIOS shadowing option. While this

feature provides an advantage with Microsoft MS-DOS, it is not an

advantage with Microsoft Windows NT.

ROM BIOS shadowing is the process of copying the BIOS from ROM into

RAM and using either hardware or 386 enhanced mode to remap the RAM

into the normal address space of the BIOS. Because reading RAM is much

faster than reading ROM, BIOS-intensive operations are substantially

faster. For example, MS-DOS uses the BIOS to write to the screen;

therefore, with ROM BIOS shadowing, directory listings run more

quickly.

Windows NT does not use the BIOS (except during startup); therefore,

no performance is gained by shadowing. If ROM BIOS shadowing is not

used, more RAM is available. With Windows NT, there is an advantage to

disabling the ROM BIOS shadowing option.

More Information:

This applies to other BIOS shadowing schemes as well. Typically the

CMOS settings allow the system to shadow any BIOS. This includes the

following:

   System BIOS

   Video BIOS

   Other adapters ROM BIOS (in a given select range)

Additional reference words: prodnt 3.10 win32

KBCategory: kbenv kbfasttip

KBSubCategory: ntconfig


Default Drive Letters and Partitions in Windows NT

Article ID: Q93373

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

---------------------------------------------------------------

Summary:

Windows NT tends to follow the drive lettering conventions established

years ago for the earliest hard drives. However, Windows NT has fewer

restrictions on the number of hard drives it supports. For example,

most systems do not support more than two hard drives in the BIOS,

with the remainder being supported by drivers loaded in CONFIG.SYS.

Thus, the same partitions may have different letters in a system such

as MS-DOS and Windows NT. Please note that this article discusses only

the default drive lettering; you can use sticky drive letters (Disk

Administrator) to alter this lettering.

In this article, primary partition refers to any partition that is a

recognized partition (the different FAT partition types [1, 4, and 6],

HPFS [High Performance File System] and NTFS [NT File System] [7]). A

non-extended partition refers to a partition that has a type other

than 0 (Empty) or 5 (Extended).

More Information:

This article describes the rules that Windows NT follows when

assigning drive letters. Note: Only recognized partition types (1, 4,

6, 7) are assigned drive letters.

If there is a primary partition on the first hard drive marked as

active, it gets the first drive letter (C); otherwise, the first drive

letter is assigned to the first recognized primary partition.

This process is repeated for all hard drives in the system. Please

note that if you have multiple controllers in your system, the drive

letter ordering is based on the order in which the device drivers are

loaded by Windows NT.

Once the letters have been assigned to the first primary partitions on

all drives in the system, letters are assigned to the recognized

logical disks in the extended partitions using the same scheme as

outlined above, starting with the first drive in the system.

After all of the logical disks in the extended partitions are assigned

letters, one last scan is made of the drives, and letters are assigned

to any remaining recognized primary partitions.

For drives referenced in BOOT.INI, the ordering is similar except that

the above scan is done only for drives supported in the BIOS. For

drives not supported in the BIOS, it is necessary to use the arcname

style paths. The most applicable arcname naming conventions are:

   multi()disk()rdisk()partition()\...

   scsi()disk()rdisk()partition()\...

The two are similar, except that the multi()disk() format varies the

rdisk() parameter for successive disks on one controller (with a limit

of two per controller), whereas the scsi()disk() notation uses the

disk() parameter. Note that the rdisk() parameter actually refers to

which SCSI logical unit (LUN) to use, which could be a separate disk,

but the vast majority of SCSI setups have only one LUN per SCSI ID.

The partition() portion of the arcname refers to the partition number.

Partition numbers are assigned, starting with partition(1). Note that

partition(0) refers to the entire disk. First, all non-extended

partitions (those having a partition type other than 0 or 5) are

assigned numbers (and the active bit does not play a role), and then

all logical drives in extended partitions are assigned numbers.

For example:

Assume a system with two controllers, one a WD1003 compliant

controller (IDE/ESDI/ST506) supported by the ATDISK driver, and the

other a SCSI host adapter supported by a SCSI miniport driver. There

are two drives attached to the ATDISK controller and one drive

attached to the SCSI host adapter (at SCSI ID 0).

There are two primary partitions on the first ATDISK drive, two

partitions (one extended partition with one FAT partition inside and

one primary NTFS partition) on the second ATDISK drive, and one

primary FAT partition on the SCSI drive.

   +---------------+-----------------+

1/2| Primary (FAT) | Primary (XENIX) |

   +---------------+-----------------+

   +--------------------------+----------------+

3/4|Extended (one FAT inside) | Primary (NTFS) |

   +--------------------------+----------------+

   +--------------+

5  |Primary (FAT) |

   +--------------+

The drive letters are assigned as follows:

   MS-DOS: C=1, D=3, E=5 (loaded in CONFIG.SYS); 2 and 4 do not have

   drive letters.

   Windows NT: C=1, D=4, E=5, F=3; 2 does not have a drive letter.

   NTLDR/BOOT.INI: C=1, D=4, E=3; 2 and 5 do not have drive letters.

The arcname for each of the partitions is:

   1: multi(0)disk(0)rdisk(0)partition(1)

   2: multi(0)disk(0)rdisk(0)partition(2)

   3: multi(0)disk(0)rdisk(1)partition(2)

   4: multi(0)disk(0)rdisk(1)partition(1)

   5: scsi(0)disk(0)rdisk(0)partition(1)

Additional reference words: prodnt 3.10

KBCategory: kbother kbfasttip

KBSubCategory: ntfilesys


Windows NT File Size and Partition Size Limits

Article ID: Q93496

--------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

--------------------------------------------------------------

Summary:

The following table contains the partition and file size limitations

of the various file system formats under Windows NT:

   File System   Max. Partition Size   Max. File Size

   --------------------------------------------------

      FAT              2^32                2^32

      HPFS             2^41                2^32

      NTFS             2^64                2^64

Additional reference words: prodnt 3.10

KBCategory: kbother kbfasttip

KBSubCategory: ntfilesys


Memory Available to MS-DOS Applications with Windows NT

Article ID: Q93499

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

---------------------------------------------------------------

Summary:

This article describes the amount and type of memory available to

MS-DOS-based applications running under Windows NT.

More Information:

There is approximately 620K of conventional memory available at all

times to MS-DOS-based applications. Device drivers do not impact

MS-DOS memory in the same way they did with OS/2 1.x (with the

exception of small stubs that map through to the underlying Win32/NT

subsystem).

The memory for MS-DOS applications comes from the Windows NT virtual

page pool. There is practically no limit; however, there is the

typical size-versus-speed tradeoff associated with virtual storage.

This memory is user-selectable: either EMS (LIM 4.0), XMS (provided by

MS-DOS 5 HIMEM.SYS), or DPMI version 0.9.

Additional reference words: prodnt 3.10

KBCategory: kb3rdparty kbinterop kbfasttip

KBSubCategory: ntdosap


Isolating General Printing Problems

Article ID: Q93503

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

---------------------------------------------------------------

SUMMARY

=======

This article describes some common printing problems that you may

experience when using Windows NT. These printing problems may appear

in a variety of forms; for example, print jobs may show up in Print

Manager but never make it to the printer, copying files to a printer

with the command COPY <FILENAME.EXT> LPT1 may result in the message

"File not found."

This describes possible causes of these problems, and provides some

troubleshooting methods.

MORE INFORMATION

================

Common Problems and Causes

--------------------------

The following are some common causes of printer problems:

 - Incorrect settings. Make sure the printer is set up correctly in

   the Print Manager. Check that the correct properties, printer port,

   and so on, have been specified. You can also try deleting and

   reinstalling the printer driver.

 - Bad hardware. This is always a possibility, particularly if

   printing does not work correctly under MS-DOS either. Try plugging

   in another parallel or serial port.

Isolating a Problem

-------------------

The following are recommendations for trying to isolate a printing

problem:

 - If you have access to another printer, see if you can print to it.

 - Remove all extraneous hardware, video cards, and so on to see if

   there might be a hardware conflict.

 - Try printing from another application or from the command line (for

   example, try COPY <FILENAME.EXT> LPT1).

 - If you cannot print to a network printer, copy your print job and

   application to the print server and attempt to print from the print

   server. This may help determine whether the problem is with the

   network or the server.

Additional reference words: prodnt 3.10 tshoot

KBCategory: kbprint kbfasttip

KBSubCategory: ntprint


Windows NT Boots, But Looks for Wrong Boot Directory

Article ID: Q93535

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

----------------------------------------------------------------------

SUMMARY

=======

Windows NT may boot successfully, but look for the wrong boot directory.

One possible cause of this problem is installing over an earlier

installation of Windows NT. The BOOT.INI file isn't correctly updated

during the subsequent installation; certain releases marked the BOOT.INI

read-only.

Another cause might be an unsupported partitioning scheme, such as a

MOST partition. When Windows NT encounters an unknown partition type,

the numbering of logical partitions may be off by one.

Installing Over a Prior Installation

------------------------------------

If you are going to install over a previous installation, make sure that

the BOOT.INI file is not read-only so that Setup can modify it.

NOTE: Windows NT is not an upgrade. Installing Windows NT over a previous

installation will erase any customizations you have made.

If you installed over a previous installation, make sure that the BOOT.INI

file contains references to the correct directory (for example, C:\WINNT

rather than C:\NT).

Installing With a Different Partitioning Scheme

-----------------------------------------------

If you have installed NT on a machine with a different partitioning

scheme, try changing the boot partition specified in the BOOT.INI

file.

Settings for GUI Installation

-----------------------------

The GUI installation program creates a different BOOT.INI file,

containing SCSI syntax. Before the SCSI syntax can be used, the

appropriate miniport driver must be copied from C:\NT\SYSTEM\DRIVERS

to C:\NTBOOTDD.SYS. (See below for a detailed explanation of the

SCSI syntax and for descriptions of the miniport drivers.)

NOTE: The GUI installation program copies the driver and changes these

settings automatically. When you change SCSI adapters, run the Windows NT

Setup, choose Add/Remove SCSI Adapters from the Options menu, and add the

new adapter. Do this BEFORE physically removing the old SCSI adapter or you

won't be able to start Windows NT.

   [multiboot]

   timeout = 30

   default = scsi(0)disk(0)rdisk(0)partition(1)\winnt

   [operating systems]

   scsi(0)disk(0)rdisk(0)partition(1)\winnt = "Windows NT" /NODEBUG

   c:\ = "MS-DOS"

The SCSI syntax is as follows

   scsi(w)disk(x)rdisk(y)partition(z)\winnt

where:

 - "w" is the SCSI controller number; numbering starts at 0 (only

   one SCSI controller number is supported at this time).

 - "x" is the SCSI ID number, 0 to 7. Some controllers reserve IDs 0

   and 1 for BIOS support for hard drives and ID 2 for a CD-ROM drive.

   This is not a requirement for Windows NT.

 - "y" is the SCSI Logical Unit number (up to 255 units are

   supported).

 - "z" is the partition (0 would specify the whole logical unit).

The following are some of the common miniport drivers included:

   Driver                 Controller

   ------------------------------------------------------------

   AHA154X                Adaptec 154x/164x

   AHA174X                Adaptec 174x

   SPARROW                Adaptec 151x/152x/AIC 6260/6360

   BUSLOGIC               BusLogic Family

   DPTSCSI                DPT 20xx

   FD16_700               Future Domain 16xx

   FD7000EX               Future Domain / Western Digital 7000EX

   FD8XX                  Future Domain 8xx

   NCR53C9X               NCR 53c9

   NCRC700                NCR c700

   NCRC710                NCR c710

   OLISCSI                Olivetti

   SPOCK                  IBM PS/2

   T128                   Trantor t128

   T13B                   Trantor t130b

   ULTRA14F               UltraStor 14f, 34f

   ULTRA24F               UltraStor 24f

   ULTRA124               UltraStor 124f

   WD33C93                Western Digital 33c93

Additional reference words: prodnt 3.10

KBCategory: kbsetup kbfasttip

KBSubCategory: ntsetup  ntboot


1024-Cylinder Limitation on SCSI and ESDI Drives

Article ID: Q93930

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

---------------------------------------------------------------

This article explains the 1024-cylinder limitation on Enhanced Small

Device Interface (ESDI) and Small Computer System Interface (SCSI)

drives.

ESDI uses cylinder, head, sector (CHS) addressing and has a

1024-cylinder limitation. Some controller cards can work around this

by implementing a translation scheme in the onboard controller BIOS.

Windows NT (and other protected mode operating systems) must duplicate

the code found in these BIOS chips to duplicate this behavior.

Unfortunately, there are many ways to perform this translation and to

accommodate them all Microsoft would have to incorporate all of these

schemes in the standard AT disk driver. (Microsoft has NOT included

support for all known ESDI-translation schemes.)

Some ESDI controllers implement this translation in hardware; thus, it

is totally transparent to the system. This allows the standard driver

to work unchanged. Consult your controller documentation to see if

such translation is performed by the BIOS or the hardware.

SCSI uses relative block address (RBA) addressing. Normally, you do

not have to worry about a 1024-cylinder limit with SCSI until the SCSI

drive becomes very large (that is, greater than 1 gigabyte [GB]). At

that point there may be a problem. Some SCSI cards have a jumper for

greater than 1 GB support. Refer to your hardware documentation to

determine if your card has this jumper.

Additional reference words: prodnt 1024 cylinder

KBCategory: kbfasttip kbhw

KBSubCategory: nthw


Frequently Asked Questions about TCP/IP

Article ID: Q94069

----------------------------------------------------------------------

The information in this article applies to:

 - All Microsoft TCP/IP Network Protocol Products

----------------------------------------------------------------------

This article provides answers to frequently asked questions regarding

TCP/IP.

1. Q. Does MS ship NFS (Network File System) support?

   A. No.

2. Q. How can I get NFS support on my LAN Manager 2.1 workstation?

   A. Get some third party applications like Chameleon NFS from

      Netmanage or NFS from FTP Software Inc.

3. Q. Does MS ship line printer daemon (LPD) support with LAN Manager?

   A. No.

4. Q. How can I receive LPD support?

   A. Contact third-party vendors to receive this support.

5. Q. Can you bind TCP/IP to more than one network card?

   A. No.

6. Q. Why is it that when I am running LAN Manager 2.1 and trying an

      FTP connection to an IBM VM host I am not able to connect, yet I

      am able to connect to other hosts like Sun?

   A. You probably don't have a new patch that will allow you to do

      this. In LAN Manager 2.1a, we did not set the push bit. IBM's

      FTP daemon expects a push bit to be set. To gain IBM VM host

      connectivity, you must apply this patch. The patch is located

      on: \\iceberg\hotsites!ssbus\hotfix\lm21\csd01.001

7. Q. Do we support token ring source routing over TCP/IP?

   A. Yes.

8. Q. What are WINSOCK.DLL and WSOCKETS.DLL? Which one should I use ?

   A. WIN_SOCK.DLL was originally shipped with LAN Manager when it was

      beta. We took it out of LAN Manager 2.1 before we shipped.

      Sybase did their development work using the WIN_SOCK.DLL.

      Occasionally we will get some of their customers calling us

      saying that they are not able to find the WIN_SOCK.DLL. This .DLL

      was replaced by WSOCKETS.DLL. If you who have access to their

      sockets source, all they have to do is #include <wsockets.h> and

      use sockets() instead of w_sockets(), listen() instead of

      w_listen() etc.

9. Q. What is the Winsock standard?

   A. It is an open interface for network programming under MS

      Windows. Some of the companies originally involved in writing

      the specification were JSB Corporation, FTP Software Inc., Sun

      Microsystems, and Microsoft Corp.

10.Q. Where can I get the Winsock standard?

   A. In MS it is on \\toolsvr\standards!internet\winsock. On the

      Internet it can be found by using anonymous FTP to VAX.FTP.COM

      or FTP.UU.NET. You can also use the 'archie' service on the

      Internet to find the one closest to you. You can request

      information by sending an email to: winsock@ftp.com

11.Q. Does LAN Manager support the Windows Socket standard in the sockets

      SDK?

   A. No.

12.Q. Does Windows NT support the Windows Socket standard?

   A. Yes.

13.Q. Does MS support Point to Point Protocol (PPP)?

   A. We support PPP in Windows NT Workstation 3.5 and Microsoft Windows NT

      Server 3.5

14.Q. What is the difference between a LAN Manager domain and

      a Domain Name Server (DNS) Domain ?

   A. A DNS Domain is used by machines on the Internet. It is

      typically used for distributing the host file across a network.

      However, it can also be used to distribute any form of

      information (like directory service).

15.Q. Do we support Network Information Service (NIS) or Yellow Pages as

      it used to be called, from SUN?

   A. No, but we support the DNS.

16.Q. Does the LAN Manager 2.1 stack indicate if there is a duplicate IP

      address?

   A. No. LAN Manager 2.3 may have this feature.

Additional reference words: prodtcp32 tcpip tcp ip

KBCategory: kbnetwork kbfasttip

KBSubcategory: nttcp


Network Interface Printers Need DLC Protocol

Article ID: Q96623

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

--------------------------------------------------------------------

Summary:

With Windows NT, to access a network interface printer (a printer with

its own network support [for example, Hewlett-Packard IIIsi printers

have built-in network interface cards), you must install data link

control (DLC) protocol support.

Note: To obtain network address of a printer, start the printer self

test.

More information on the DLC protocol can be found in the Microsoft LAN

Manager Resource Kit published by Technical Resource Group.

Additional reference words: prodnt 3.10  hp NICs

KBCategory: kbfasttip kbprint

KBSubCategory: ntprint


Automated Setup for Windows for Workgroups and TCP/IP

Article ID: Q98245

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft LAN Manager version 2.2

 - Microsoft TCP/IP for Windows for Workgroups

 - Microsoft Windows for Workgroups version 3.1

----------------------------------------------------------------------

SUMMARY

=======

You can automate Windows for Workgroups (WfWG) setup by using the

/h:FILENAME.SHH parameter documented on pages 3-22 to 3-30 in the Windows

for Workgroups "Resource Kit." With a few extra steps, you can use this

basic method to install the Microsoft TCP/IP protocol shipped on the WfWG

connectivity disk with LAN Manager 2.2 as the transport protocol.

MORE INFORMATION

================

In order for the TCP/IP stack to be used with automated setup, you

must edit the NETWORK.INF file on Disk #2 of the WfWG install set (on

the network share if you are installing from the network) and add several

lines taken from the OEMSETUP.INF file on the connectivity disk. Use a

text editor to add the following lines to the indicated sections.

To the [transport] Section

--------------------------

   tcpip = "MS TCP/IP",104,ndis,tcp,real,0,lanabase,tcpip,tcpip_xif

Note: The stack ID value in field 2 was changed to 104 because the

original value of 020 was recognized as a 0 in the SETUP.SHH file and

the default NetBEUI protocol was installed.

To the Protocol Install Sections

--------------------------------

[tcpip]

devdir = 1:umb.com,1:tcptsr.exe,1:tinyrfc.exe,1:emsbfr.exe

devdir = 1:tcpdrv.dos,1:nemm.dos,1:nmtsr.exe,1:tcputils.ini

netdir = 1:addname.exe,1:ping.exe,1:sockets.exe

netdir = 1:hosts,1:lmhosts,1:networks,1:protocol,1:services

netdir = 1:net.exe

windir = 1:win_sock.dll,1:wsockets.dll

load    = umb,@devdir\umb

load    = tcptsr,@devdir\tcptsr

load    = tinyrfc,@devdir\tinyrfc

load    = emsbfr,@devdir\emsbfr

device = tcpdrv.dos,@devdir\tcpdrv.dos     /i:@devdir

device = nemm.dos,@devdir\nemm.dos

sysparm=386enh,TimerCriticalSection,5000

sysparm=386enh,UniqueDosPSP,TRUE

sysparm=386enh,PSPIncrement,2

[tcpip_xif]

drivername = TCPIP$

param  = IPAddress0,"IP Address",chars,15,,0x08

param  = SubNetMask0,"Subnet Mask",chars,15,,0x08

param  = DefaultGateway0,"Default Gateway",chars,15,,0x08

param  = NBSessions,"Maximum number of sessions",int,"1,20,1",6

param  = NetFiles,"Netfiles directory",static,@netdir

param  = tcpsegmentsize,"TCP segment size",static,1450

param  = tcpwindowsize,"TCP window size",static,1450

If you are installing from disk, in order to be prompted for the

correct disk, you should add the information from the [disks] section

of SETUP.INF (Windows for Workgroups Disk #1), changing the identifier

to one that is not used by the WfWG disks. For example:

   C =. ,"Enterprise Protocols for Windows for Workgroups",diskC

You then need to change the disk identifier in the [tcpip] section shown

above. That is:

devdir = C:UMB.COM,C:TCPTSR.EXE,C:TINYRFC.EXE,C:EMSBFR.EXE).

NOTE: This is not necessary if you are installing from a network drive.

You can also modify the PRIORITY parameter in the NETWORK.INF [protman]

section of TCPIP.

You can then use the TCP/IP stack ID with the TransportID parameter in

your SETUP.SHH file (TransportID=104) and run SETUP /H:SETUP.SHH to

install WfWG automatically with this protocol stack.

You can also edit the [tcpip_xif] section to automatically set parameters

in PROTOCOL.INI that you want to use. For example, to set the netmask

parameter to 255.255.0.0:

   param  = SubNetMask0,"Subnet Mask",chars,15,"255 255 0 0",0x08

REFERENCES

==========

Windows for Workgroups "Resource Kit," pages 3-22 to 3-30.

Additional reference words: 2.20 2.2 WFW31 WIN31

KBCategory: kbnetwork kbfasttip

KBSubcategory: nttcp


MS-DOS-Based Applications and Command Prompts

Article ID: Q99279

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

--------------------------------------------------------------------

Summary:

Windows NT provides a fully-integrated command prompt that enables you

to launch both Windows-based and MS-DOS-based applications. Although

the concept of running an MS-DOS-based application in a Windows-based

environment may be familiar to you, Windows NT handles this somewhat

differently than Windows (16-bit) does.

The essential difference lies in the command prompt itself; under

Windows NT, the command prompt is a 32-bit Windows NT-based

application, not the virtual MS-DOS machine you would expect from

Windows. Under Windows NT, until you start an MS-DOS-based

application, no virtual MS-DOS machine is created. Furthermore, once

you start an MS-DOS-based application, its virtual MS-DOS machine is

used for all subsequent MS-DOS-based applications started from the

same command prompt.

As in Windows, each MS-DOS-based application can have a program

information file (PIF). If there is no PIF for a particular

application, the default PIF, _DEFAULT.PIF, is used. Because Windows

NT only uses the PIF from the first application started in any given

command prompt, you may need to take special care in the way you start

your applications. For example, if you design a PIF that allocates

some EMS memory, it is important that you start the associated

application first; otherwise, the EMS memory may never be allocated.

You may start a Windows NT command prompt and then run the MS-DOS

command, MEM, to see how much memory you have free. Because MEM is

another MS-DOS-based application, Windows NT creates a virtual MS-DOS

machine, probably using _DEFAULT.PIF. After MEM finishes, you start

the application you created the PIF for. Unfortunately, because

_DEFAULT.PIF doesn't instruct Windows NT to allocate EMS memory, your

application reports that it can find no EMS memory. Rechecking the PIF

you created does not solve the problem. You need to start another

command prompt and then make sure to start your EMS-requiring

application first, before you start any other MS-DOS-based

applications.

There is one more difference to be aware of: each PIF contains a

pointer to AUTOEXEC and CONFIG files. Usually these default to the

Windows NT versions, AUTOEXEC.NT and CONFIG.NT. If you want to change

environment variables for your MS-DOS-based applications, you need to

point their PIFs to different files or modify the default ones. (To

see these files and their locations, run PIF Editor and choose Windows

NT.)

Additional reference words: prodnt 3.10 wow

KBCategory: kb3rdparty kbinterop kbfasttip

KBSubCategory: ntdosap


Increasing Memory for MS-DOS-Based Applications

Article ID: Q99363

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

--------------------------------------------------------------------

Summary:

You can increase available conventional memory (largest executable

program size) for your MS-DOS-based applications by modifying their

default AUTOEXEC files and removing the lines that load DOSX and RDR,

the MS-DOS extender and network redirector drivers. However, this is

not recommended, as it disables support for many functions, including:

EMS memory; DPMI services; named pipes; NetBIOS; LAN Manager APIs; and

the DLC protocol. If you have an MS-DOS-based application that

requires none of these services, and you need extra memory, do the

following:

1. In the System32 subdirectory, make a copy of the AUTOEXEC.NT file.

2. In the new AUTOEXEC file, insert REM commands before the lines

   loading DOSX and RDR.

3. Start PIF Editor and create a PIF for your MS-DOS-based

   application.

4. From the main PIF Editor window, choose Windows NT.

5. In the Autoexec Filename field, enter the name of your new AUTOEXEC

   file.

6. Save the PIF and exit PIF Editor.

Note: If you want to start your program from a Windows NT command

prompt, make sure you run it before any other MS-DOS-based programs.

If you start other MS-DOS-based applications from the same command

prompt prior to running the one that needs the extra conventional

memory, the PIF you created will not be used.

Additional reference words: prodnt 3.10

KBCategory: kb3rdparty kbinterop kbfasttip

KBSubCategory: ntdosap


Files Needed to Set Up Remote Access Service (RAS)

Article ID: Q99373

--------------------------------------------------------------------

The information in this article applies to:

   Microsoft Windows NT operating system version 3.1

--------------------------------------------------------------------

Summary:

The files listed below are those needed to install Remote Access

Service (RAS) for Windows NT. This list may be useful if you are

having difficulty installing RAS on a computer that no longer has

access to the media from which Windows NT was originally installed.

For example, if you installed Windows NT on a laptop computer from a

shared CD-ROM on the network, Windows NT will not allow you to install

RAS from floppies. In this example, you can simply copy all the files

listed below to your laptop's hard drive and set up RAS from there.

   RASADMIN EXE             210432

   RASADMIN HLP             184702

   RASAPI32 DLL              16896

   RASCAUTH DLL              23552

   RASPHONE EXE             172032

   RASPHONE HLP             223878

   RASMAN   EXE              13312

   RASMSG   DLL              12800

   RASMXS   DLL              32768

   RASSER   DLL              18944

   RASTEST  EXE              36352

   RASHUB   SYS              61440

   ASYNCMAC SYS              72704

   MODEM    INF              51470

   PAD      INF               1660

   SWITCH   INF                223

   RASADMIN DLL              26624

   RASGTWY  DLL              48640

   RASSAUTH DLL              46592

   RASSRV   EXE              30208

   RASREAD  TXT                481

   RASCFG   DLL              57344

   RASFIL32 DLL              13312

   RASSETUP HLP              11904

   OEMNSVRA INF             109077

Note: OEMNSVRA.INF is the RAS setup information file. You can view it

in any text editor.

Additional reference words: prodnt 3.10

KBCategory: kbfasttip kbnetwork

KBSubCategory: NTNETSERV NTRAS


Enabling TCP/IP Routing

Article ID: Q99686

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

--------------------------------------------------------------------

WARNING: Using Registry Editor incorrectly can cause

    serious, system-wide problems that may require you to

    reinstall Windows NT to correct them. Microsoft cannot

    guarantee that any problems resulting from the use of

    Registry Editor can be solved. Use this tool at your own

    risk.

Summary:

This article describes how to enable TCP/IP routing in Windows NT and

how to configure static routing tables using ROUTE.EXE.

How to Enable TCP/IP Routing

============================

Routing between subnets is disabled by default for the TCP/IP protocol

in Windows NT. To enable routing, following these steps:

1. Start Registry Editor (REGEDT32.EXE) and go to the following

   subkey:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip

      \Parameters

2. From the Edit menu, choose Add Value.

3. Enter the following values:

      Value Name: IpEnableRouter

      Data Type: REG_DWORD

      Value: 1

4. Exit Registry Editor and restart Windows NT.

Configuring Static Routing Tables

=================================

If two subnets are separated by more than one Windows NT machine or by

a router, Windows NT can route between the subnets if you manually

configure the routing tables. Static configurable routing is

supported, but neither routing information protocol (RIP) or OSPF are

supported.

The ROUTE.EXE command manually configures network routing tables.

ROUTE has the following syntax:

   route [-fs] [command [destination][gateway]]

Switches

--------

   -f Clears routing tables

   -s Packets for which no destinations are found are routed to the

      smart gateway.

Commands

--------

   add      Adds a route

   delete   Deletes a path

   print    Prints a route

   change   Changes an existing route

All symbolic names used for gateway and destination are looked up in

the database files NETWORKS and HOSTS.

Additional reference words: prodnt 3.10

KBCategory: kbfasttip kbnetwork

KBSubCategory: NTNETSERV NTTCP


Tuning NWLINK Registry Parameters

Article ID: Q99745

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

--------------------------------------------------------------------

NWLink is an implementation of the IPX/SPX protocols popular in Novell

NetWare networks. An additional module, NWNBLink, provides support for

the Novell implementation of the NetBIOS protocol. This article is

divided into the following sections:

 - NWNBLink Parameters (Microsoft Extensions to Novell NetBIOS)

 - NWNBLink Parameters (Novell NetBIOS or Microsoft Extensions)

 - IPX/SPX Parameters (Network Interface Cards/Token Ring)

 - IPX/SPX Parameters (Global)

CAUTION: Although you can modify all the parameters listed here in

Registry Editor, the default values should rarely need to be changed.

Any changes you make to these parameters can easily affect the

performance of NWLink.

Note: All parameters are listed in the following format:

   <name> : <data type> : <default value> (valid range, units)

In Registry Editor, if no value is present, assume the default is

being used. If you cannot find the parameter, you need to manually add

it (choose Add Value from the Edit menu).

NWNBLink Parameters (Microsoft Extensions to Novell NetBIOS)

============================================================

Registry path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

               \NWNBLink\Parameters

The Microsoft Extensions to Novell NetBIOS are provided to enhance the

performance of the traditional Novell NetBIOS protocol. NWNBLink can

automatically detect whether or not it is talking to a Novell NetBIOS

implementation that does not understand these extensions; if it is

being misunderstood, NWNBLink falls back to the standard Novell

NetBIOS protocol currently in use in Novell networks. Significant

performance gains can be realized if the extensions are used (for

example, if the NetBIOS conversation occurs between two Windows NT

computers).

AckDelayTime : REG_DWORD : 250 (50-65535, milliseconds)

-------------------------------------------------------

Determines the value of the delayed acknowledgment timer.

AckWindow : REG_DWORD : 2 (0-65535, frames)

-------------------------------------------

Specifies the number of frames to receive before sending an

acknowledgment. AckWindow is used as a clocking mechanism on networks

in which the sender is networked on a fast LAN, but the receiver is

networked on the other side using a slower link. By automatically

forcing acknowledgments, the sender can keep sending frames

continually. If both the sender and receiver are located on a fast

link, you can set AckWindow to 0 to turn off sending an acknowledgment

to the sender. Alternatively, NWNBLink can be set to dynamically

determine whether to use the AckWindow parameter based on the setting

of AckWindowThreshold.

AckWindowThreshold : REG_DWORD : 500 (0-65535, milliseconds)

------------------------------------------------------------

Specifies the threshold value for the round trip time that defines

when AckWindow is ignored. The round trip time is an estimate of how

long it takes for a frame to be sent and received from a workstation.

NWNBLink determines this estimate and uses it as a basis for

determining whether it is necessary to send automatic acknowledgments.

If AckWindowThreshold is set to 0,  NWNBLink relies on the AckWindow

entry.

EnablePiggyBackAck : REG_DWORD : 1 (0 - False or 1 - True)

----------------------------------------------------------

Allows the receiver to piggyback acknowledgments. Piggybacking

acknowledgments can occur when the receiver has detected the end of a

NetBIOS message. When the sender and receiver are not participating in

two-way NetBIOS traffic, you should set EnablePiggyBackAck to false.

An example of one-way traffic is a stock update application, where a

server constantly sends NetBIOS messages to clients, but the client

does not need to respond.

If EnablePiggyBackAck is true but there is no back traffic, NWNBLink

will wait the number of milliseconds determined by AckDelayTime before

sending the acknowledgment, then it will turn off support for

piggybacking acknowledgments. If the workstation at some point starts

sending as well as receiving data, NWNBLink will turn support back on

for piggybacking acknowledgments.

Extensions : REG_DWORD : 1 (0 - false or 1 - true)

--------------------------------------------------

Specifies whether to use NWNBLink extensions discussed in this

section.

RcvWindowMax : REG_DWORD : 4 (1-49152, frames)

----------------------------------------------

Specifies the maximum number of frames the receiver can receive at one

time. The value specified by RcvWindowMax is sent to the sender during

session initialization to give the sender an upper bound on the number

of frames that can be sent at one time. (Related parameters:

AckDelayTime, AckWindow, AckWindowThreshold, EnablePiggyBackAck, and

RcvWindowMax.)

NWNBLink Parameters (Novell NetBIOS or Microsoft Extensions)

============================================================

Registry path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

               \NWNBLink\Parameters

The following parameters can be used to configure Novell NetBIOS or

Microsoft extensions.

BroadcastTimeout : REG_DWORD : 1 (1-65535, half-seconds)

--------------------------------------------------------

Specifies the time between sending find-name requests. This value is

not affected if Internet is set to 1. (Related parameter:

BroadcastCount.)

BroadcastCount : REG_DWORD : 3 (1-65535, times)

-----------------------------------------------

Specifies the number of times to send a broadcast. This value is not

affected if Internet is set to 1. (Related parameter:

BroadcastTimeout.)

ConnectionCount : REG_DWORD : 5 (1-65535, times)

------------------------------------------------

Specifies the number of times to send a connection probe. A connection

probe is sent by the initiator of a session if a connection could not

be made to the remote computer. (Related parameter:

ConnectionTimeout.)

ConnectionTimeout : REG_DWORD : 2 (1-65535, half-seconds)

---------------------------------------------------------

Specifies the time between sending connection probes when initiating a

session.

InitialRetransmissionTime : REG_DWORD : 500 (1-65535, milliseconds)

-------------------------------------------------------------------

Specifies the initial value for the retransmission time. (Related

parameter: RetransmitMax.)

Internet : REG_DWORD : 1 (0 - False or 1 - True)

------------------------------------------------

Specifies whether to change the packet type from 0x04 to 0x14 (Novell

WAN broadcast).

KeepAliveCount : REG_DWORD : 8 (1-65535, times)

-----------------------------------------------

Specifies the number of times to send a session-alive frame before

timing out if there is no response. (Related parameter:

KeepAliveTimeout.)

KeepAliveTimeout : REG_DWORD : 60 (1-65535, half-seconds)

---------------------------------------------------------

Specifies the time between sending session-alive frames. (Related

parameter: KeepAliveCount.)

RetransmitMax : REG_DWORD : 8 (1-65535, times)

----------------------------------------------

Specifies the maximum number of times the sender should retransmit

before assuming that something is wrong with the link. (Related

parameter: InitialRetransmissionTime.)

IPX/SPX Parameters (Network Interface Cards)

============================================

Registry path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

               \NWLink\NetConfig\Driver01

These parameters are specific for each binding of NWLink to each

network adapter. Currently, only one card is supported.

AdapterName : REG_DWORD : <Adapter name>

----------------------------------------

Specifies the name of the adapter NWLink will use. This parameter is

set when you choose a network adapter to bind NWLink using the Network

icon in Control Panel.

BindSap : REG_DWORD : 8137 (hex)

--------------------------------

Specifies the Ethertype if the frame format is Ethernet II. The

Ethertype field is only relevant if Ethernet II frames are to be sent

or received. You can choose the frame type using the Network icon in

Control Panel. For more information, see the PktType parameter.

EnableFuncaddr : REG_DWORD : 1 (0 - False or 1 - True)

------------------------------------------------------

When true, this parameter specifies that the IPX functional address is

enabled if the adapter is a Token Ring card. If false, the IPX

functional address is not added. The IPX functional address is

C00000800000 (hex). Novell has been phasing out the use of this

address, but it is still used in some places. It is up to the

application to take advantage of the IPX functional address. In most

instances, the broadcast address (FFFFFFFFFFFF hex) is used.

MaxPktSize : REG_DWORD : 0 (0-65535)

------------------------------------

Specifies the maximum frame size the network adapter should be allowed

to transmit. If this number is 0, NWLink will get this information

from the adapter driver. This parameter allows the administrator to

make the maximum transmit size smaller than the driver allows. A

scenario in which you might want to change this entry is in an

environment in which the network adapter on one side of a conversation

is on a link that has a larger frame size than the link on the other

side. For example, if the sending station is linked to a 16 MBPS Token

Ring and the receiving station is linked to an Ethernet network.

NetworkNumber : REG_DWORD : 0 (network number in hex)

-----------------------------------------------------

Specifies the network number to be used for this adapter. If it is 0,

NWLink gets the network number from the network as it is running. This

parameter is set using the Network icon in Control Panel. IPX network

numbers are 4 bytes (8 hex characters) long. An example of an IPX

network number is AABBDDFF. You should not have to enter a specific

value because NWLink will determine it for you. Make sure to get the

network number for your IPX subnet from the network administrator if

you want to enter a specific number.

PktType : REG_DWORD : 1 (0-4)

-----------------------------

NWLink supports Ethernet, Token Ring, FDDI, and Arcnet topologies. The

PktType parameter specifies the packet form to use. The valid values

are:

   0 (Ethernet II)

   1 (Ethernet 802.3)

   2 (802.2)

   3 (SNAP)

   4 (Arcnet)

If your adapter is an Ethernet adapter, choose between 0 and 3. If the

adapter is Token Ring or FDDI, choose option 2 or 3. If you are using

an Arcnet adapter, choose option 4. If the adapter is a Token Ring or

FDDI adapter, values 0 and 1 will work the same as value 2. (Related

parameter: BindSap.)

RipAgeTime : REG_DWORD : 5 (1-65535, minutes)

---------------------------------------------

IPX maintains a routing information protocol (RIP) cache in order to

locate machines on a remote network. The RipAgeTime entry informs IPX

how many minutes to wait before requesting a RIP update for an entry.

This timer is reset when a RIP announcement is received for an entry

that is in the RIP cache.

RipUsageTime : REG_DWORD : 15 (1-65535, minutes)

------------------------------------------------

IPX maintains a RIP cache in order to locate machines on a remote

network. The RipUsageTime entry informs IPX how many minutes to wait

before an entry in the RIP cache will be deleted from the cache. This

timer is reset when a packet is sent to the remote machine.

SourceRouteBcast : REG_DWORD : 0 (0 or 1)

-----------------------------------------

Specifies the source route to be used when transmitting a packet to

the broadcast MAC address (FFFFFFFFFFF hex). If this value is 0, the

packet is transmitted to the single-route broadcast (0xC2, 0x70). If

the value is 1, the packet is transmitted to the all-routes broadcast

(0x82, 0x70). (Related parameters: SourceRouteDef, SourceRouting, and

SourceRouteMCast.)

SourceRouteDef : REG_DWORD : 0 (0 or 1)

---------------------------------------

Specifies the source route to be used when transmitting a package to a

unique MAC address that is not in the source routing table. If the MAC

address is in the source routing table, the route in the table will be

used. If this value is 0, the packet is transmitted to the single-

route broadcast (0xC2, 0x70). If the value is 1, the packet is

transmitted to the all-routes broadcast (0x82, 0x70). (Related

parameters: SourceRouteBcast, SourceRouting, and SourceRouteMCast.)

SourceRouting : REG_DWORD : 0 (0 - False or 1 - True)

-----------------------------------------------------

Specifies whether to use source routing. This parameter is only used

if the adapter is Token Ring. If there are no source routing bridges

on the Token Ring, disable this entry to disable all of the source

routing logic. (Related parameters: SourceRouteBcast, SourceRouteDef,

and SourceRouteMCast.)

SourceRouteMcast : REG_DWORD : 0 (0 - False or 1 - True)

--------------------------------------------------------

Specifies the source route to be used when transmitting a packet to a

multi-cast MAC address (C000xxxxxxxx). If false, the packet is

transmitted to the single-route broadcast (0xC2, 0x70). If true, the

packet is transmitted to the all-routes broadcast (0x82, 0x70).

(Related parameters: SourceRouteBcast, SourceRouteDef, and

SourceRouting.)

IPX/SPX Parameters (Global)

===========================

Registry path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

               \NWLink\Parameters

The following parameters are global for the entire NWLink transport.

ConnectionCount : REG_DWORD : 10 (1-65535, times)

-------------------------------------------------

Specifies the number of times the probe is sent when SPX is trying to

connect to a remote node. If no response is received after the probes

are sent, an error occurs. (Related parameter: ConnectionTimeout.)

ConnectionTimeout : REG_DWORD : 2 (1 to 65535, half-seconds)

------------------------------------------------------------

Specifies the time between connection probes when SPX is trying to

connect to a remote node. (Related parameter: ConnectionCount.)

KeepAliveTimeout : REG_DWORD : 12 (1-65535, half-seconds)

---------------------------------------------------------

Specifies the amount of time the local side should wait before sending

a probe to the remote side to verify that the SPX connection is still

alive. (Related parameter: KeepAliveCount.)

KeepAliveCount : REG_DWORD : 8 (1-65535, times)

-----------------------------------------------

Specifies how many times to send a keep-alive probe before timing out

if there is no response. (Related parameter: KeepAliveTimeout.)

RipCount : REG_DWORD : 5 (1-65535, times)

-----------------------------------------

When the RIP protocol layer is trying to find a route on the network,

this parameter specifies how many times to send a request before

giving up. (Related parameter: RipTimeout.)

RipTimeout : REG_DWORD : 1 (1-65535, half-seconds)

--------------------------------------------------

Specifies the timeout between RIP request packets being sent out when

the RIP protocol layer is trying to find a route on the network.

(Related parameter: RipCount.)

WindowSize : REG_DWORD : 4 (1-10, SPX packets)

----------------------------------------------

Specifies the window to use in the SPX packets. SPX uses the

Allocation field of the SPX packet to tell the remote node how many

receives are available for receiving data. The WindowSize entry

specifies what value to put in the SPX Allocation field.

Additional reference words: prodnt 3.10

KBCategory: kbinterop kbfasttip

KBSubCategory: ntinterop


Optimizing Your Paging File (PAGEFILE.SYS)

Article ID: Q99768

------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

------------------------------------------------------------------

Windows NT uses a paging file for virtual memory called PAGEFILE.SYS.

This file is created during Windows NT Setup and is always located in

the root directory. No matter what your system configuration is,

Windows NT will create and use a paging file.

The paging file is not necessarily a single file; it can be a group of

files stored in various locations, across hard disks and partitions.

The files are collectively referred to as "the paging file." When

thinking about the size of the paging file, the sum of all the files

that make up the paging file is the only value you need to keep in

mind.

The following two guidelines should be met when optimizing the paging

file:

1. In general, you should set the size of the paging file to the same

   size as your system RAM plus 12 MB. There is a minimum size

   requirement of 22 MB for the operating system. If system RAM plus

   12 MB is less than 22 MB, increase the size of the paging file

   until your system RAM plus paging file is at least 22 MB.

   NOTE: 22 MB is just what the operating system requires for itself.

   For reasonable application performance, a 40 MB total is

   recommended.

   These sizes are recommended because Windows NT requires "backing

   storage" for everything it keeps in RAM. If Windows NT requires

   more space in RAM, it must be able to swap out code and data to

   either the paging file or the original executable file. If Windows

   NT cannot do this, out of memory errors will be generated.

   If you set your paging file to system RAM plus 12 MB and you still

   get low memory warnings, try increasing the size of the paging

   file. If you need more disk space and you are not getting memory

   warnings or memory-related problems, you can try to decrease the

   size of the paging file.

   Also, if you have enough surplus RAM to support the operating

   system and application memory requirements, the need for a large

   paging file is lessened. If you have, for example, 64 MB of RAM,

   you may be able to safely reduce your paging file to a very small

   size.

2. If you have multiple hard disks, splitting up the paging file is a

   good idea, as it will speed up the access time. If you have two

   hard disks, and you split the paging file, both hard disks can be

   accessing information simultaneously, greatly increasing the

   throughput. However, if you have two hard disks, and one hard disk

   is faster than the other, it may be more effective to store the

   paging file on only the faster hard disk. Some experimentation may

   be necessary to arrive at the best configuration for your system.

   Note: There is no point in splitting up the paging file between

   multiple partitions as it does not increase the ability of the hard

   disk to access the paging file. This may be a good idea, however,

   if your logical drives aren't large enough for the entire paging

   file.

Additional reference words: prodnt 3.10

KBCategory: kbother kbfasttip

KBSubcategory: ntgeneral


How To Obtain TCP/IP-32 3.11a for Windows for Workgroups

Article ID: Q99891

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SUMMARY

=======

Microsoft TCP/IP-32 version 3.11a is an update to Microsoft's TCP/IP-32, a

32-bit protect mode VxD TCP/IP network protocol stack for Windows for

Workgroups version 3.11. This update is a complete refresh of TCP/IP-32 and

contains all components of the product.

MORE INFORMATION

================

WFWT32.EXE is a self-extracting file containing the TCP/IP-32 version 3.11a

files. You can download it from the Internet (anonymous FTP) from the

following directory:

   ftp://ftp.microsoft.com/peropsys/windows/public/tcpip

You can also find WFWT32.EXE in the Microsoft Software Library (MSL) of the

following services:

 - CompuServe

      GO MSL

      Search for WFWT32.EXE or S14856

      Display results and download

 - Microsoft Download Service (MSDL)

      Dial (206) 936-6735 to connect to MSDL

      Download WFWT32.EXE

 - Internet (anonymous FTP)

      ftp://ftp.microsoft.com/softlib/mslfiles

      Get WFWT32.EXE

Additional reference words: prodtcp32 3.11a S14856 wfw wfwg

KBCategory: kbnetwork kbfile kbfasttip

KBSubCategory: ntprotocol nttcp ntdistrib


Windows NT File System Files

Article ID: Q100012

------------------------------------------------------------------

The information in this article applies to:

 - Windows NT operating system version 3.1

------------------------------------------------------------------

Following is a list of Windows NT files system files organized by

location. Following filenames are short explanations.

WINNT\SYSTEM32

--------------

FATBOOT.BIN    FAT boot sector template

HPFSBOOT.BIN   HPFS boot cluster template

DISKCOMP.COM   Disk comparison utility

DISKCOPY.COM   Disk copy utility

FORMAT.COM     Disk format utility

TREE.COM       Graphical directory display utility

ACLEDIT.DLL    Access control list (ACL) editor

CUFAT.DLL      FAT file system conversion

CUHPFS.DLL     HPFS file system conversion

FMIFS.DLL      Interface between File Manager and installable file

               system

IFSUTIL.DLL    Installable file system utility

IOLOGMSG.DLL   I/O log

UFAT.DLL       Provides FORMAT and CHKDSK support for FAT file system.

UHPFS.DLL      Provides FORMAT and CHKDSK support for HPFS file

               system.

ULIB.DLL       Provides support for commands: DISKCOPY, SUBST, DOSKEY,

               ACLCONV, CHCP, KEYB, CONVERT, MODE, XCOPY, REPLACE,

               MORE, PRINT, RECOVER, COMP, FC, CHKDSK, FIND, TREE,

               SORT, DISKCOMP, ATTRIB, FORMAT, etc.

UNTFS.DLL      Provides FORMAT and CHKDSK support for NTFS file

               system.

ACLCONV.EXE    ACL conversion utility. Converts OS/2 LAN Manager

               server access control lists. Uses BACKACC data file.

APPEND.EXE     Enables programs to open data files in specified

               directories as if they were in the current directory.

ATTRIB.EXE     Attribute utility.

AUTOCHK.EXE    Auto check utility. Run automatically by the system at

               boot to check disks.

AUTOCONV.EXE   Auto file system conversion utility. Run automatically

               by the system when the user has requested a file system

               conversion of a volume that cannot be locked at run

               time or during Windows NT Setup.

BACKUP.EXE     Backup utility

BACKUP.HLP     Backup help

CHKDSK.EXE     Check disk utility

COMP.EXE       File compare utility

CONVERT.EXE    File system conversion utility. Converts FAT or HPFS

               volumes to NTFS.

DISKPERF.EXE   Starts or stops disk performance counters for use by

               Performance Monitor.

FASTOPEN.EXE   Dummy file for backward compatibility

FC.EXE         File compare utility

FIND.EXE       Find string utility

FINDSTR.EXE    Searches for strings in files. Can use regular

               expressions.

LABEL.EXE      Disk label utility

NTBACKUP.EXE   Tape backup utility

NTIO.SYS       Provides IO.SYS support for MS-DOS-based applications.

PERFMON.EXE    Performance Monitor

PERFMON.HLP    Performance monitor help

PORTUAS.EXE    Utility for UAS to SAM database conversion

RECOVER.EXE    File recovery utility

REPLACE.EXE    Replace file utility

RESTORE.EXE    File restore utility

SETACL.EXE     Sets ACLs on directory tree during Windows NT Setup.

SHARE.EXE      Dummy file for backward compatibility

WINDISK.EXE    Disk Administrator

WINDISK.HLP    Disk administrator help

WINFILE.EXE    File Manager

WINFILE.HLP    File Manager help

XCOPY.EXE      Extended Copy Utility

WINNT\SYSTEM32\CONFIG

---------------------

SYSTEM         Master copy of partition information.

SYSTEM.ALT     Alternate copy of SYSTEM.

WINNT\SYSTEM32\DRIVERS

----------------------

ATDISK.SYS     IBM AT (ST506) driver used my most ISA PCs

CDFS.SYS       CD file system driver

CDFS_REC.SYS   Mini-file system recognizer for CDFS

DISKPERF.SYS   Disk performance driver

FASTFAT.SYS    Fast FAT file system driver

FAT_REC.SYS    Mini-file system recognizer for FAT

FLOPPY.SYS     Floppy driver

FTDISK.SYS     Fault tolerance disk driver

HPFS_REC.SYS   Mini-file system recognizer for HPFS

NTFS.SYS       Windows NT file system (NTFS) driver

NTFS_REC.SYS   Mini-file system recognizer for NTFS

PINBALL.SYS    HPFS file system driver

SCSICDRM.SYS   SCSI CD-ROM driver

SCSIDISK.SYS   SCSI disk driver

SCSIFLOP.SYS   SCSI floppy driver

SCSIPORT.SYS   SCSI port driver

Additional reference words: prodnt 3.10

KBCategory: kbother kbfasttip

KBSubcategory: ntfilesys


Overview of FAT, HPFS, and NTFS File Systems

Article ID: Q100108

---------------------------------------------------------------

The following information applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

---------------------------------------------------------------

SUMMARY

=======

This article explains the differences between FAT, HPFS, and NTFS

under Windows NT, and their advantages and disadvantages. It is

divided into the following sections:

 - FAT Overview

 - HPFS Overview

 - NTFS Overview

FAT OVERVIEW

============

FAT is by far the most simplistic of the file systems supported by

Windows NT. The FAT file system is characterized by the file

allocation table (FAT), which is really a table that resides at the

very "top" of the volume. To protect the volume, two copies of the FAT

are kept in case one becomes damaged. In addition, the FAT tables and

the root directory must be stored in a fixed location so that the

system's boot files can be correctly located.

A disk formatted with FAT is allocated in clusters, whose size are

determined by the size of the volume. When a file is created, an entry

is created in the directory and the first cluster number containing

data is established. This entry in the FAT table either indicates that

this is the last cluster of the file, or points to the next cluster.

Updating the FAT table is very important as well as time consuming. If

the FAT table is not regularly updated, it can lead to data loss. It

is time consuming because the disk read heads must be repositioned to

the drive's logical track zero each time the FAT table is updated.

There is no organization to the FAT directory structure, and files are

given the first open location on the drive. In addition, FAT supports

only read-only, hidden, system, and archive file attributes.

FAT Naming Convention

---------------------

FAT uses the traditional 8.3 file naming convention and all filenames

must be created with the ASCII character set. The name of a file or

directory can be up to eight characters long, then a period (.)

separator, and up to a three character extension. The name must start

with either a letter or number and can contain any characters except

for the following:

   . " / \ [ ] : ; | = ,

If any of these characters are used, unexpected results may occur. The

name cannot contain any spaces.

The following names are reserved:

   CON, AUX, COM1, COM2, COM3, COM4, LPT1, LPT2, LPT3, PRN, NUL

All characters will be converted to uppercase.

Advantages of FAT

-----------------

It is not possible to perform an undelete under Windows NT on any of

the supported file systems. Undelete utilities try to directly access

the hardware, which cannot be done under Windows NT. However, if the

file was located on a FAT partition, and the system is restarted under

MS-DOS, the file can be undeleted. The FAT file system is best for

drives and/or partitions under approximately 200 MB, because FAT

starts out with very little overhead. For further discussion of

FAT advantages, see the following:

 - Windows NT "System Guide," Chapter 18, section titled "Selecting a

   File System for the Windows NT Partition"

 - Windows NT Advanced Server "System Guide," Chapter 20, section

   titled "Selecting a File System for the Windows NT Partition"

 - Windows NT Advanced Server "Concepts and Planning Guide," Chapter

   5, section titled "Choosing a File System"

Disadvantages of FAT

--------------------

Preferably, when using drives or partitions of over 200 MB the FAT

file system should not be used. This is because as the size of the

volume increases, performance with FAT will quickly decrease. It is

not possible to set permissions on files that are FAT partitions. For

further discussion of other disadvantages of FAT, see the following:

 - Windows NT "System Guide," Chapter 18, section titled "Selecting a

   File System for the Windows NT Partition"

 - Windows NT Advanced Server "System Guide," Chapter 20, section

   titled "Selecting a File System for the Windows

   NT Partition"

 - Windows NT Advanced Server "Concepts and Planning Guide," Chapter

   5, section titled "Choosing a File System"

HPFS OVERVIEW

=============

The HPFS file system was first introduced with OS/2 1.2 to allow for

greater access to the larger hard drives that were then appearing on

the market. Additionally, it was necessary for a new file system to

extend the naming system, organization, and security for the growing

demands of the network server market. HPFS maintains the directory

organization of FAT, but adds automatic sorting of the directory based

on filenames. Filenames are extended to up to 254 double byte

characters. HPFS also allows a file to be composed of "data" and

special attributes to allow for increased flexibility in terms of

supporting other naming conventions and security. In addition, the

unit of allocation is changed from clusters to physical sectors (512

bytes), which reduces lost disk space.

Under HPFS, directory entries hold more information than under FAT. As

well as the attribute file, this includes information about the

modification, creation, and access date and times. Instead of pointing

to the first cluster of the file, the directory entries under HPFS

point to the FNODE. The FNODE can contain the file's data, or pointers

that may point to the file's data or to other structures that will

eventually point to the file's data.

HPFS attempts to allocate as much of a file in contiguous sectors as

possible. This is done in order to increase speed when doing

sequential processing of a file.

HPFS organizes a drive into a series of 8 MB bands, and whenever

possible a file is contained within one of these bands. Between each

of these bands are 2K allocation bitmaps, which keep track of which

sectors within a band have and have not been allocated. Banding

increases performance because the drive head does not have to return

to the logical top (typically cylinder 0) of the disk, but to the

nearest band allocation bitmap to determine where a file is to be

stored.

Additionally, HPFS includes a couple of unique special data objects:

Super Block

-----------

The Super Block is located in logical sector 16 and contains a pointer

to the FNODE of the root directory. One of the biggest dangers of

using HPFS is that if the Super Block is lost or corrupted due to a

bad sector, so are the contents of the partition, even if the rest of

the drive is fine. It would be possible to recover the data on the

drive by copying everything to another drive with a good sector 16 and

rebuilding the Super Block. However, this is a very complex task.

Spare Block

-----------

The Spare Block is located in logical sector 17 and contains a table

of "hot fixes" and the Spare Directory Block. Under HPFS, when a bad

sector is detected, the "hot fixes" entry is used to logically point

to an existing good sector in place of the bad sector. This technique

for handling write errors is known as hot fixing.

Hot fixing is a technique where if an error occurs because of a bad

sector, the file system moves the information to a different sector

and marks the original sector as bad. This is all done transparent to

any applications that are performing disk I/O (that is, the

application never knows that there were any problems with the hard

drive). Using a file system that supports hot fixing will eliminate

error messages such as the FAT "Abort, Retry, or Fail?" error message

that occurs when a bad sector is encountered.

Note: The version of HPFS that is included with Windows NT does not

support hot fixing.

Advantages of HPFS

------------------

HPFS is best for drives in the 200-400 MB range. For more discussion

of the advantages of HPFS, see the following:

 - Windows NT "System Guide," Chapter 18, section titled "Selecting a

   File System for the Windows NT Partition"

 - Windows NT Advanced Server "System Guide," Chapter 20, section

   titled "Selecting a File System for the Windows NT Partition"

 - Windows NT Advanced Server "Concepts and Planning Guide," Chapter

   5, section titled "Choosing a File System"

Disadvantages of HPFS

---------------------

Because of the overhead involved in HPFS, it is not a very efficient

choice for a volume of under approximately 200 MB. In addition, with

volumes larger than about 400 MB, there will be some performance

degradation. You cannot set security on HPFS under Windows NT. For

additional disadvantages of HPFS, see the following:

 - Windows NT "System Guide," Chapter 18, section titled "Selecting a

   File System for the Windows NT Partition"

 - Windows NT Advanced Server "System Guide," Chapter 20, section

   titled "Selecting a File System for the Windows NT Partition"

 - Windows NT Advanced Server "Concepts and Planning Guide," Chapter

   5, section titled "Choosing a File System"

NTFS OVERVIEW

=============

From a user's point of view, NTFS continues to organize files into

directories, which, like HPFS, are sorted. However, unlike FAT or

HPFS, there are no "special" objects on the disk and there is no

dependence on the underlying hardware, such as 512 byte sectors. In

addition, there are no special locations on the disk, such as FAT

tables or HPFS Super Blocks.

The goals of NTFS are to provide:

 - Reliability, which is especially desirable for high end systems

   and file servers

 - A platform for added functionality

 - Support POSIX requirements

 - Removal of the limitations of the FAT and HPFS file systems

Reliability

-----------

To ensure reliability of NTFS, three major areas were addressed:

recoverability, removal of fatal single sector failures, and hot

fixing.

NTFS is a recoverable file system because it keeps track of

transactions against the file system. When a CHKDSK is performed on

FAT or HPFS, the consistency of pointers within the directory,

allocation, and file tables is being checked. Under NTFS, a log of

transactions against these components is maintained so that CHKDSK

need only roll back transactions to the last commit point in order to

recover consistency within the file system.

Under FAT or HPFS, if a sector that is the location of one of the file

system's special objects fails, then a single sector failure will

occur. NTFS avoids this in two ways: first, by not using special

objects on the disk and tracking and protecting all objects that are

on the disk. Secondly, under NTFS, multiple copies (the number depends

on the volume size) of the Master File Table are kept.

Similar to OS/2 versions of HPFS, NTFS supports hot fixing.

Added Functionality

-------------------

One of the major design goals of Windows NT at every level is to

provide a platform that can be added to and built upon, and NTFS is no

exception. NTFS provides a rich and flexible platform for other file

systems to be able to use. In addition, NTFS fully supports the

Windows NT security model and supports multiple data streams. No

longer is a data file a single stream of data. Finally, under NTFS, a

user can add his or her own user-defined attributes to a file.

POSIX Support

-------------

NTFS is the most POSIX.1 compliant of the supported file systems

because it supports the following POSIX.1 requirements:

Case Sensitive Naming:

Under POSIX, README.TXT, Readme.txt, and readme.txt are all

different files.

Additional Time Stamp:

The additional time stamp supplies the time at which the file was last

accessed.

Hard Links:

A hard link is when two different filenames, which can be located in

different directories, point to the same data.

Removing Limitations

--------------------

First, NTFS has greatly increased the size of files and volumes, so

that they can now be up to 264. NTFS has also returned to the FAT

concept of clusters in order to avoid HPFS problem of a fixed sector

size. This was done because Windows NT is a portable operating system

and different disk technology is likely to be encountered at some

point. Therefore, 512 bytes per sector was viewed as having a large

possibility of not always being a good fit for the allocation. This

was accomplished by allowing the cluster to be defined as multiples of

the hardware's natural allocation size (see Cluster Factor in the NTFS

module for more details). Finally, in NTFS all filenames are Unicode

based, and 8.3 filenames are kept along with long filenames.

Advantages of NTFS

------------------

NTFS is best for use on volumes of about 400 MB or more. This is

because performance does not degrade under NTFS, as it does under FAT,

with larger volume sizes.

The recoverability designed into NTFS is such that a user should

never have to run any sort of disk repair utility on an NTFS

partition. For additional advantages of NTFS, see the following:

 - Windows NT "System Guide," Chapter 18, section titled "Selecting a

   File System for the Windows NT Partition"

 - Windows NT Advanced Server "System Guide," Chapter 20, section

   titled "Selecting a File System for the Windows NT Partition"

 - Windows NT Advanced Server "Concepts and Planning Guide," Chapter

   5, section titled "Choosing a File System"

Disadvantages of NTFS

---------------------

It is not recommended to use NTFS on a volume that is smaller than

approximately 400 MB, because of the amount of space overhead involved

in NTFS. This space overhead is in the form of NTFS system files that

typically use at least 4 MB of drive space on a 100 MB partition.

Currently, there is no file encryption built into NTFS. Therefore,

someone can boot under MS-DOS, or another operating system, and use

a low-level disk editing utility to view data stored on an NTFS

volume.

It is not possible to format a floppy disk with the NTFS file system;

Windows NT formats all floppy disks with the FAT file system because

the overhead involved in NTFS will not fit onto a floppy disk.

For further discussion of NTFS disadvantages, see the following:

 - Windows NT "System Guide," Chapter 19, section titled "Selecting a

   File System for the Windows NT Partition"

 - Windows NT Advanced Server "System Guide," Chapter 21, section

   titled "Selecting a File System for the Windows NT Partition"

 - Windows NT Advanced Server "Concepts and Planning Guide," Chapter

   5, section titled "Choosing a File System"

NTFS Naming Conventions

-----------------------

File and directory names can be up to 255 characters long, including

any extensions. Names preserve case, but are not case sensitive. NTFS

makes no distinction of filenames based on case. Names can contain any

characters except for the following:

   ?  "  /  \  <  >  *  |  :

Note: Currently, from the command line, you can only create filenames

of up to 253 characters.

Additional reference words: prodnt 3.10

KBCategory: kbother kbfasttip

KBSubcategory: ntfilesys


Windows NT Driver Library

Article ID: Q100209

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

NOTE: THESE DRIVERS ARE TESTED AND CERTIFIED WITH WINDOWS NT VERSION 3.5

ONLY.

Microsoft provides the files in the Microsoft Windows NT Driver Library

(WNTDL). Files in the WNTDL support many printers, displays, sound cards,

and network card adapters that the Windows NT version 3.5 release does not

support directly. If you have a modem, the drivers are available at no

charge on CompuServe, GEnie, Microsoft OnLine, and the Microsoft Download

Service (MSDL). However, note that standard connect-time fees and long-

distance telephone charges, if any, apply when you download files. When you

connect to any of these services, please read the WNTDL.TXT file for

downloading instructions and a complete list of the devices that the WNTDL

supports.

The phone number for the MSDL is (206) 936-MSDL (6735). There is no

connect-time charge to use the MSDL.

On CompuServe, the WNTDL is in the Microsoft Software Library, which you

can access by typing "go msl" (without quotation marks) at any CompuServe

system prompt.

On the GEnie and Microsoft OnLine systems, the WNTDL is in the Microsoft

Software Library.

If you do not have access to a modem, you can obtain an individual driver

from the WDL on a disk by calling Microsoft Product Support Services at

(206) 635-7018.

NOTE: If your first 30 days of free phone support have expired, you must

call (206) 635-7022.

The text below presents the complete text of the WNTDL.TXT file distributed

with WNTDL.

MORE INFORMATION

================

The Microsoft Windows NT Driver Library (WNTDL) contains device drivers for

printers, displays, audio devices, storage devices, and network card

adapters. These drivers enable these devices to run with the Microsoft

Windows NT operating system.

As new and updated drivers become available, they will be added to the

WNTDL.

This WNTDL.TXT file includes a list of all the devices supported by the

drivers in the WNTDL and instructions for downloading the drivers. This

file is updated on a regular basis.

NOTE: All the drivers included in this library are intended for use with

Windows NT.

Instructions for Downloading

----------------------------

1. Locate your device in the listing included at the end of this WNTDL.TXT

   file. Note the name of the file listed next to the device. You need to

   download this file from your download service.

2. If you are downloading to a floppy disk, you need to have a formatted,

   blank disk. If you are downloading to your hard disk, create a new

   subdirectory in which you will place the files.

   CAUTION: Do not download files directly into your main Windows NT

   directory. Doing so could overwrite files essential to the proper

   operation of your system.

3. Follow the downloading procedure used by your downloading service. The

   file you download is the executable or program (.EXE) file that you

   identified in step 1. This file contains all the files you need to

   support your device.

   Download the .EXE file to your floppy disk or to the new subdirectory

   you created on your hard disk.

4. Change to the floppy disk drive (or the subdirectory on your hard disk)

   that contains the .EXE file. At the MS-DOS prompt, type the filename,

   and then press ENTER.

   When the .EXE file finishes running, all the files you need to support

   your device, such as a .DRV file and an OEMSETUP.INF file, are set up.

   You are also provided with a .TXT file that contains instructions for

   installing the device drivers (or other software) and a licensing

   agreement.

   If you have problems extracting files, try downloading the files again.

WINDOWS NT 3.5 DRIVER LIBRARY CONTENTS

======================================

Audio                         Filename     Ver      Date      S#

---------------------------------------------------------------------

CD-ROM                        Filename     Ver      Date      S#

---------------------------------------------------------------------

Creative Labs Sound Blaster   MKECR.EXE    3.1      08/20/93  S14233

Panasonic CR52x               MKECR.EXE    3.1      08/20/93  S14233

Panasonic CR56x               MKECR.EXE    3.1      08/20/93  S14233

CPU                           Filename      Ver     Date     S#

---------------------------------------------------------------------

Display                       Filename      Ver     Date     S#

---------------------------------------------------------------------

Artist Graphics               ARTGRP.EXE    3.1     01/31/94  S14523

Compaq AVGA 640x480 16 Color  CPAVGA.EXE    3.1     08/20/93  S14235

Compaq AVGA 640x480 256 Color CPAVGA.EXE    3.1     08/20/93  S14235

Compaq AVGA 800x600 256 Color CPAVGA.EXE    3.1     08/20/93  S14235

Video Artist Graphics ISA 1.5 ART35.EXE     1.5     10/18/94  S14950

Video ATI GraphWonderXL24     ISAATINT.EXE  3.50    09/23/94  S14900

Video Cirrus 5422 Embedded    CIRRUS.EXE    3.50    09/23/94  S14899

Video Compaq AVGA EISA        AVGA.EXE      3.50    09/23/94  S14895

Video Compaq QVision EISA     CPQ-QV.EXE    1.10    09/23/94  S14897

Video Compaq QVision2000 PCI  CPQ200.EXE    2.00    09/23/94  S14896

Video Matrox MGA-PCI PCI      MATROX.EXE    2.00    11/10/94  S14898

Miscellaneous                 Filename      Ver     Date      S#

---------------------------------------------------------------------

Wacom ArtZ/ArtPad Tablets 1.0 ARTZ-PAD.EXE  1.0     11/29/94  S15017

Network Card Adapters         Filename      Ver     Date      S#

---------------------------------------------------------------------

3Com Etherlink/MC 32 Ethernet 3C527.EXE     1.00f   09/04/93  S14299

Cabletron T30XX TokenRing     DNICTT30.EXE  3.1     03/14/94  S14623

Compaq NetFlex                NFLEX.EXE     3.1     03/14/94  S14620

Cisco C320 FDDI/CDDI          C320NT.EXE    1.1     01/10/94  S14354

Intel 16-bit Token Ring       TKXP16.EXE    1.01    09/20/93  S14307

Intel 32-bit Token Ring Svr   TKXP32.EXE    1.01    09/20/93  S14306

Intel PCLA82xx Ethernet       82595.EXE     3.1     10/29/93  S14355

Net Intel EE16 ETH ISA 3.50   EE16NT.EXE    3.50    10/10/94  S14471

NCR WaveLAN AT & MCA          WAVLAN.EXE    1.0a    10/12/93  S14356

Net 3Com 3C77x FDDI EISA      3C770.EXE     1.16    09/23/94  S14300

Net AMD PCnet ETH FAMILY      PCNET.EXE     1.99    09/23/94  S14901

Net Andrew IIA TR ISA         ANDTOK.EXE    1.02    09/23/94  S14902

Net Cabletron CTE21 ETH ISA   CTE21.EXE     1.00.06 09/23/94  S14903

Net Cabletron F30XX FDDI MCA  CTF30.EXE     1.00.06 09/23/94  S14622

Net Cabletron F70XX FDDI EISA CTF70.EXE     1.00.06 09/23/94  S14624

Net Cabletron T20XX TR ISA    CTT20.EXE     1.00.03 09/23/94  S14628

Net DCA IRMAtrac TR ISA/MCA   IRMANT.EXE    4.0c    09/23/94  S14489

Net DE DE435 ETH PCI          DE435.EXE     6.0     09/23/94  S14904

Net DEC DE300 FDDI EISA1.5    DE300A.EXE    1.50    10/18/94  S14952

Net DEC DE300 FDDI EISA1.5    DE300X.EXE    1.50    10/18/94  S14953

Net HP 100VG ETH EISA         HPVGE.EXE     3.10    09/23/94  S14906

Net HP 100VG ETH ISA          HPVGI.EXE     3.10    09/23/94  S14905

Net HP Ethertwist ETH ISA     HPISA.EXE     3.11    09/23/94  S14358

Net HP Ethertwist MCA         HPMCA.EXE     3.10    09/23/94  S14358

Net IBM LANStreamer TR MCA    IBM32.EXE     1.30    09/23/94  S14907

Net Intel EEPRO ETH ISA       EPRONT.EXE    1.13    09/23/94  S14908

Net Intel Flash32 ETH EISA1.5 FL32NT.EXE    1.5     10/18/94  S14621

Net Madge Ringnode TR SMART   MADGNT.EXE    1.02.02 09/23/94  S14297

Net Olicom 16/4 TR FAMILY     OCKT16.EXE    2.00    09/23/94  S14304

Net Olicom Server TR EISA     OCTK32.EXE    2.00    09/23/94  S14305

Net SMC 8432 ETH PCI          SMCPCI.EXE    6.0     09/23/94  S14909

Net SMC EtherCard ETH FAMILY  SMC16.EXE     1.09    09/23/94  S14625

Net SMC Ultra32 ETH EISA      SMC32.EXE     1.03    09/23/94  S14626

Net ThomasConrad TC404x TR    TCTOK.EXE     1.0     09/23/94  S14627

Net Xircom CCard ETH PCMCIA   XCE10.EXE             09/23/94  S14912

Net Xircom PE2 ETH PARPORT    XPE2.EXE      3.10    09/23/94  S14910

Net Xircom PE3 ETH PARPORT    XPE3.EXE      3.10    09/23/94  S14911

Proteon p1390 ISA Token Ring  P139XX.EXE    3.03    09/01/93  S14302

Proteon p1392 ISA Token Ring  P139XX.EXE    3.03    09/01/93  S14302

Proteon p1392+ ISA Token Ring P139XX.EXE    3.03    09/01/93  S14302

Proteon p1892 MCA Token Ring  P189X.EXE     3.03    09/01/93  S14301

Proteon p1990 EISA Token Ring P199X.EXE     3.03    09/01/93  S14303

Proteon p1990+ Eisa TokenRing P199X.EXE     3.03    09/01/93  S14303

Printers A-G                  Filename      Ver     Date      S#

---------------------------------------------------------------------

Printers H-O                  Filename      Ver     Date      S#

---------------------------------------------------------------------

Printer HP 4V/4MV ALPHA 1.0   HP4V_AXP.EXE  1.0     11/29/94  S15014

Printer HP 4V/4MV MIPS 1.0    HP4VMIPS.EXE  1.0     11/29/94  S15015

Printer HP 4V/4MV X86 1.0     HP4VI386.EXE  1.0     11/29/94  S15016

Printer HP Color LJ ALPHA 1.0 HPCLJAXP.EXE  1.0     12/13/94  S15042

Printer HP Color LJ MIPS 1.0  HPCLJMIP.EXE  1.0     12/13/94  S15040

Printer HP Color LJ X86 1.0   HPCLJI38.EXE  1.0     12/13/94  S15041

Printers P-Z                  Filename      Ver     Date      S#

---------------------------------------------------------------------

Storage                       Filename      Ver     Date      S#

---------------------------------------------------------------------

Archive 4326NP Tape Drive     4MMS2.EXE     1.0     06/09/94  S14784

Archive 4326RP Tape Drive     4MMS2.EXE     1.0     06/09/94  S14784

Archive 4356XP Tape Drive     4MMS2.EXE     1.0     06/09/94  S14784

Compaq 4/16 Gigabyte TurboDAT 4MMS2.EXE     1.0     06/09/94  S14784

Conner 4326NP Tape Drive      4MMS2.EXE     1.0     06/09/94  S14784

Conner 4326RP Tape Drive      4MMS2.EXE     1.0     06/09/94  S14784

Conner 4356XP Tape Drive      4MMS2.EXE     1.0     06/09/94  S14784

Exabyte 2501 SCSI Tape Drive  EX2501.EXE    1.0     06/09/94  S14785

Hewlett-Packard C1533a        4MMS2.EXE     1.0     06/09/94  S14784

IBM 2Gb 4mm Tape Drive        IBM4MM.EXE    3.1     03/11/94  S14231

Sankyo SCSI Tape Drive        SANKYO.EXE    3.10    03/11/94  S14639

SCSI AMD PCNET/SCSI Embedded  AMD.EXE       1.95    09/23/94  S14890

SCSI AMI Series48 EISA Cache  AMI48.EXE     1.03    09/23/94  S14522

SCSI AMI Series48 EISA NonCch AMI48.EXE     1.03    09/23/94  S14522

SCSI ASP ABP-842 VLB          ASP.EXE       3.10    09/23/94  S14891

SCSI CMD CSA-6000/F EISA      CMD600.EXE    1.1     09/23/94  S14629

SCSI IBM IBMRAID MCA          IBMRAD.EXE    3.10    09/23/94  S14892

SCSI NCR 8xxxx PCI 1.00.06    NCRX86.EXE    1.00.06 10/18/94  S14951

SCSI Procom Xelerator ISA     PRXEL.EXE     3.10    09/23/94  S14470

SCSI QLogic Fast!SCSI ISA     QLOGIC.EXE    1.31    09/23/94  S14783

SCSI QLogic Fast!SCSI EISA    QLOGIC.EXE    1.31    09/23/94  S14783

SCSI QLogic Fast!SCSI VLB     QLOGIC.EXE    1.31    09/23/94  S14783

SCSI QLogic Fast!SCSI PCI     QLPCI.EXE     3.5     09/23/94  S14893

SCSI Rancho RT1600-5 ISA      RANCHO.EXE    2.10    09/23/94  S14894

Sony 31A MIPS                 S31AM.EXE     3.1     08/20/93  S14234

Sony 31A X86                  S31X86.EXE    3.1     08/20/93  S14236

Sony SCSI Tape Driver         S4MM.EXE      3.1     01/31/94  S14524

Trantor T348 Mini SCSI Plus   T348.EXE      3.1     08/20/93  S14232

WangDAT Model 3400DX          4MMS2.EXE     1.0     06/09/94  S14784

Additional reference words: prodnt 3.50

KBCategory: kbhw kbfasttip

KBSubcategory: nthw ntgeneral


Detecting Windows NT Serial Ports

Article ID: Q100372

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

--------------------------------------------------------------------

Windows NT manages serial (COM) ports somewhat differently from the

way Windows 3.1 does. In Windows 3.1, you can observe and configure

all the COM ports from Ports in Control Panel. In Windows NT, only

unused COM ports are displayed in Control Panel. For example, if a

mouse is connected to COM1, COM1 is not available in Control Panel,

nor is it listed. To check a COM port and perform any trouble-shooting

steps, you need to use Registry Editor.

Finding Serial Ports in Registry Editor

---------------------------------------

To determine what is using a COM port, from Registry Editor go to the

following hive and subkey:

   \HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System

   \MultifunctionAdapter\0\SerialController\...

Note: If you have an EISA type machine, MultifunctionAdapter will be

EisaAdapter.

Each COM port is stored in one of the numbered subkeys. If you have

two COM ports, COM1 and COM2, you would find them stored under 0 and

1, respectively.

If a mouse is using a COM port, you will find a PointerPeripheral

subkey under the serial ports subkey. For example: If you have a mouse

on COM1, you would see the following:

   ...\SerialController\0\PointerPeripheral

If PointerPeripheral is absent, then the serial port is in use by some

other device.

Additional Differences in Windows NT Control Panel

--------------------------------------------------

You might notice an additional difference in Windows NT Control Panel.

If you select a COM port, choose Settings, and then choose Advanced,

the following message may be displayed in a dialog box:

   There are no user configurable Advanced I/O parameters for this

   COM port.

This means that Windows NT has obtained all the information it needs

for the port from NTDETECT.COM (or OSLOADER.EXE on RISC-based

computers). This ensures that redundant or incorrect information is

not entered.

Additional reference words: prodnt 3.10

KBCategory: kbfasttip kbhw

KBSubCategory: nthw


Environment Variables in Windows NT

Article ID: Q100843

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

--------------------------------------------------------------------

There are three levels of environment variables in Windows NT; the

system environment variables, the user environment variables, and the

environment variables that are set in the AUTOEXEC.BAT file. There are

also some predefined environment variables that are set when the user

logs on. This article discusses the following topics:

 - System environment variables

 - User environment variables

 - AUTOEXEC.BAT environment variables

 - How environment variables are set

 - How the path is built

 - Changing user environment variables using control panel

System Environment Variables

----------------------------

System environment variables can be viewed from Control Panel by

choosing the System icon. These variables are always set no matter who

logs on and they cannot be changed by any user.

There are a few additional predefined environment variables that are

set when the user logs on that do not appear in the System dialog box:

   USERNAME

   USERDOMAIN

   NTVERSION

   WINDIR

   OS

   PROCESSOR_ARCHITECTURE

      values: x86, MIPS or ALPHA

   PROCESSOR_LEVEL

      values for x86: 3, 4, 5

      values for MIPS: 3000, 4000

      values for ALPHA: 21064

   HOMEPATH

   HOMEDRIVE

   HOMESHARE

      These three environment variables are set based on the value of

      the home directory. The user's home directory is specified in

      User Manager (Choose Profile and Properties). If the home

      directory uses universal naming conventions (UNC), then they

      will have the following values:

          HOMESHARE=\\<server name>\<share name>

          HOMEPATH=\<path>

          HOMEDRIVE=<drive letter>:

      If the home directory is a local path such as c:\nt then they

      will look like this:

          HOMEDRIVE=c:

          HOMESHARE=

          HOMEPATH=\nt

All above environment variables are always present and therefore may

be used in logon scripts.

User Environment Variables

--------------------------

User environment variables can be viewed from Control Panel as well.

The user may add, delete or modify the environment variables in the

User Environment Variables for User field. These variables take

precedence over system environment variables. The user path is

appended to the system path.

AUTOEXEC.BAT Environment Variables

----------------------------------

All environment variables and the paths set in the AUTOEXEC.BAT file

are used to create the Windows NT environment. Any paths in the

AUTOEXEC.BAT file are append to the system path.

How Environment Variables Are Set

---------------------------------

Environment variables are set in the following order:

 - System variables

 - AUTOEXEC.BAT variables

 - User variables

How the Path Is Built

---------------------

The Path is constructed from the system path, which can be viewed in

the System Environment Variables field in the System dialog box. The

User path is appended to the system path. Then the path from the

AUTOEXEC.BAT file is appended.

Note: The environment variables LibPath and Os2LibPath are built the

same way (system path + user path + AUTOEXEC.BAT path).

Changing User Environment Variables Using Control Panel

-------------------------------------------------------

User environment variables can be added, changed or deleted from

Control Panel. There is no need to reboot after making any of these

changes. Changes take effect immediately after exiting the System

dialog box.

The next application you start will use the new settings. All other

applications running before the changes were made will not recognize

the changes.

Additional reference words: prodnt 3.10 winnt

KBCategory: kbenv kbfasttip

KBSubcategory: ntconfig


Windows NT Removable Media Requirements and Limitations

Article ID: Q101626

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system, version 3.1

 - Microsoft Windows NT Advanced Server, version 3.1

----------------------------------------------------------------------

Windows NT supports most removable hard disks and magnetic-optical

disk drives. These disks are treated as hard disks because they must

be partitioned and they are assigned a drive letter. However, Windows

NT does not support write-once disk drives.

Windows NT supports removable media subject to the following

restrictions:

 - A removable hard disk can have only one primary partition. Extended

   or logical partitions are not supported.

 - Windows NT supports only the Windows NT filesystem (NTFS) and

   MS-DOS-compatible (FAT) file system on removable media.

 - The user cannot assign the drive letter for the device.

 - Removable disks are not supported in a fault tolerant manner.

 - You can install the Windows NT system files (the files contained in the

   WINNT directory) on a removable disk. However, the boot partition and

   associated files must be on a hard disk drive (fixed disk).

 - If the paging file is located on the device or if the device has

   the NTFS installed, the media is locked until the system is

   shutdown.

 - The FAT file system locks the media while it is in use and unlocks

   it after approximately 10 seconds of inactivity.

      NOTE: Windows NT supports a 20.8MB "floptical" disk as a floppy

      disk, not as a hard disk. Each write to a floppy disk is

      performed on a write-through cache basis and you can remove a

      floppy disk as long as the drive light is not on.

Additional reference words: prodnt 3.10 iomega bernoulli WORM

KBCategory: kbfasttip kbhw

KBSubCategory: nthw NTFILESYS


Reconstructing BOOTSECT.DOS

Article ID: Q101789

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system, version 3.1

 - Microsoft Windows NT Advanced Server, version 3.1

----------------------------------------------------------------------

BOOTSECT.DOS is created by Windows NT Setup. The boot sector found in

sector 0 of drive C is copied into BOOTSECT.DOS before Setup writes

the Windows NT boot sector. (Setup will not overwrite an existing

BOOTSECT.DOS.) If you choose a previous operating system, Windows NT

executes BOOTSECT.DOS, simulating the previous operating system's

normal boot procedure.

Because the information in BOOTSECT.DOS is really created by the

previous operating system, it is very difficult to re-create. You must

transfer the BIOS parameter block (BPB) from the boot drive (C) at

sector 0 into the boot code from the previous operating system and

write this into BOOTSECT.DOS. To do this, use the following procedure:

1. Use the proper utility to regenerate a boot sector for the previous

   operating system. For example, if the previous operating system is

   MS-DOS, boot MS-DOS from a floppy disk and run the SYS C: command.

2. Start Windows NT Setup from the boot floppy disk (this may be disk

   1 of the Windows NT floppy disk set, the boot floppy disk for the

   Windows NT CD-ROM, or may have been created during a setup using

   WINNT.EXE), and initiate repairs by pressing R at the first Setup

   screen.

3. Follow the instructions provided by Setup. When Setup presents you

   with the list of optional repair tasks, make sure you have enabled the

   "Verify boot files on your C: drive" item.

4. Follow instructions until you see a message stating "Setup Repair

   is complete."

BOOTSECT.DOS should now be restored to its original state. You should

be able to boot your previous operating system.

Additional reference words: prodnt 3.10

KBCategory: kbfasttip kbsetup kbfasttip

KBSubCategory: ntsetup  ntfilesys


Recreating the Windows NT Mail Postoffice

Article ID: Q101899

----------------------------------------------------------------------

The following information applies to:

 - Microsoft Windows NT operating system, version 3.1

 - Microsoft Windows NT Advanced Server, version 3.1

----------------------------------------------------------------------

When you first run Workgroups Mail in Windows NT or Windows NT

Advanced Server, you have to option to connect to an existing post

office or to create a new post office. After you make your choice, you

cannot make a different choice. To recreate the postoffice or to

change your initial selection, you must perform the following nine

steps to edit the Registry database.

WARNING: Using Registry Editor incorrectly can cause serious,

system-wide problems that may require you to reinstall Windows NT to

correct them. Microsoft cannot guarantee that any problems resulting

from the use of Registry Editor can be solved. Use this tool at your

own risk.

1. Start REGEDT32.

2. In the Local Machine hive, select HKEY_CURRENT_USER and search for

   the following subkey:

      Software\Microsoft\Mail\Microsoft Mail

3. From the right side of the window, choose the Login:REG_SZ: value.

4. From the Edit menu, choose String.

5. Edit the string to remove any references; leave it blank.

6. From the right side of the window, choose the ServerPath:REG_SZ:

   value.

7. From the Edit menu, choose String.

8. Edit the string to remove any references; leave it blank.

9. Exit REGEDT32. When you start Mail it presents you with the

   initialization screens.

MORE INFORMATION

================

The Mail initialization procedure stores information in the Local

Machine hive of the Registry database in the HKEY_CURRENT_USER key.

When you start Mail, it determines if the Login:REG_SZ: and

ServerPath:REG_SZ: keys exist. If values exist for these keys, Mail

attempt to execute the initialization procedure. If initialization

fails because the WGPOMG32 dynamic-link library (DLL) is not found or

is corrupted, Mail gives the following error message and asks if you

would like to work offline:

   Mail could not connect to your Mail server. The configuration

   for the Mail server path is missing or invalid.

A procedure in WGPOMG32 displays the Connect Or Create dialog box to

allow you to either connect to an existing remote post office or to

create a new workgroup post office. If you choose Cancel, WGPOMG32

closes Mail. If you choose OK, WGPOMG32 creates the following subkeys

of HKEY_CURRENT_USER in the Local Machine hive of the Registry

database and returns to Mail which signs you in to the postoffice.

   Software\Microsoft\Mail\Custom Commands

     EXF:REG_SZ:3.0;File;&Export Folder...;11;IMPEXP32.DLL;0;;Exports

     folder to a backup file;MSMAIL32.HLP;2860

     IMEX:REG_SZ:3.0;File;;10

     IMF:REG_SZ:3.0;File;&Import Folder...;12;IMPEXP32.DLL;1;;Imports

     folder from a backup file;MSMAIL32.HLP;2861

     WGPOMgr1:REG_SZ:3.0;Mail;;13

     WGPOMgr2:REG_SZ:3.0;Mail;&Postoffice Manager...;14;WGPOMG32.DLL;

     0;;Manage Workgroup Postoffice;MSMAIL32.HLP;2870

   Software\Microsoft\Mail\Custom Messages

     IPM.Microsoft Schedule.MtgCncl:REG_SZ:3.0;;;;SchMsg32.DLL;;

     1100100000000000;;;;

     IPM.Microsoft Schedule.MtgReq:REG_SZ:3.0;;;;SchMsg32.DLL;;

     1111100000000000;;;;

     IPM.Microsoft Schedule.MtgRespA:REG_SZ:3.0;;;;SchMsg32.DLL;;

     1100100000000000;;;;

     IPM.Microsoft Schedule.MtgRespN:REG_SZ:3.0;;;;SchMsg32.DLL;;

     1100100000000000;;;;

     IPM.Microsoft Schedule.MtgRespP:REG_SZ:3.0;;;;SchMsg32.DLL;;

     1100100000000000;;;;

   Software\Microsoft\Mail\Microsoft Mail

     DemosEnabled:REG_SZ:0

     LocalMMF:REG_SZ:1

a    Login:REG_SZ:username

     MAPIHELP:REG_SZ:MSMAIL32.HLP

     NetBios::REG_SZ:1

     ServerPassword:REG_SZ:

b    ServerPath:REG_SZ:<drive>:\<path>\WGPO  or \\<server>\<share>

     WG:REG_SZ:1

c    Windows:REG_SZ:198 189 796 522 1 1 1 0

NOTES

=====

a   Login:REG_SZ is the Mailbox name for a particular user.

b   ServerPath:REG_SZ can a <logical drive>:\<path> or a UNC

    connection to the workgroup postoffice.

c   In Windows:REG_SZ:, the first and second number give the size of

    the Mail window, the third and fourth numbers give the position of

    the Mail window, the fifth number is the zoom value (minimized,

    maximized, or normal), the sixth number is the toolbar value

    (enabled or disabled), the seventh number is the status bar value

    (enabled or disabled), and the eighth value is the scrollbar value

    (enabled when required or disabled).

Additional reference words: prodnt 3.10 po post postoffice

KBCategory: kbother kbfasttip

KBSubCategory: nt32ap


How to Manually Delete Print Shares or Printers

Article ID: Q102116

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system, version 3.1

 - Microsoft Windows NT Advanced Server, version 3.1

----------------------------------------------------------------------

WARNING: Using Registry Editor incorrectly can cause serious,

system-wide problems that may require you to reinstall Windows NT to

correct them. Microsoft cannot guarantee that any problems resulting

from the use of Registry Editor can be solved. Use this tool at your

own risk.

If you are troubleshooting Windows NT or applications that are running

with Windows NT, you may need to verify that a print share or

installed printer has been completely deleted.

Th following information shows the default locations in the registry

database for references to installed printers or print shares.

To remove references to the printer or print share, use the Registry

Editor. Note that ALL references must be deleted to insure complete

removal of the print share or installed printer.

NOTE: Text enclosed in angle brackets (<>) brackets refers to

machine-specific names. "\\PrintShare\Printer" refers to the UNC path

to the specific printshare.

If the printer was installed from Print Manager using the Connect

To Printer option, the printer information will be located in the

following keys:

HKEY_USERS on Local Machine

   S-<user id number> \ Printers \Connections

      PrintShare\Printer

   Delete the key "\\Printshare\Printer"

HKEY_CURRENT_USER on Local Machine

   Printers \ Connections \\PrintShare\Printer

   Delete the key "\\Printshare\Printer"

HKEY_LOCAL_MACHINE on Local Machine

   Software \ Microsoft \ Windows NT \ Current Version \ Devices

   Delete the value "\\Printshare\Printer" : REG_SZ

HKEY_LOCAL_MACHINE on Local Machine

   Software \ Microsoft \ Windows NT \ Current Version

      PrinterPorts

   Delete the value "\\Printshare\Printer" : REG_SZ

NOTE: You must log off and log back on for the changes to take

effect. You may need to restart your computer as well.

If the printer was installed from Print Manager using the Create

Printer option, the printer information will be located in the

following keys:

HKEY_CURRENT_USER on Local Machine

   SOFTWARE \ Microsoft \ Windows NT

      Current Version \ Print Manager \ Printers

Delete the value < Printer Name > : REG_BINARY

HKEY_USERS on Local Machine

   < SID Number > \ SOFTWARE \ Microsoft \ Windows NT

      Current Version \ Print Manager \ Printers

Delete the value < Printer Name > : REG_BINARY

HKEY_LOCAL_MACHINE on Local Machine

   Software \ Microsoft \ Windows NT \ Current Version \ Devices

Delete the value < Printer Name > : REG_SZ

HKEY_LOCAL_MACHINE on Local Machine

   Software \ Microsoft \ Windows NT \ Current Version

      Printer Ports

Delete the value < Printer Name > : REG_SZ

HKEY_LOCAL_MACHINE on Local Machine

   SYSTEM \ CurrentControlSet \ Control \ Print \ Printers

Delete the key < Printer Name >

There may also be references to printers in other ControlSets, such as

ControlSet001, but since this may be the Control Set for the Last

Known Good Configuration, it should not be modified.

NOTE: You must log off and log back on for the changes to take

effect. You may need to restart your computer as well.

Additional reference words: prodnt 3.10 tshoot

KBCategory: kbfasttip kbprint

KBSubCategory: ntprint


Migrating Windows 3.1 Program Groups to Windows NT

Article ID: Q102424

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

--------------------------------------------------------------------

SUMMARY

=======

It is possible to migrate Windows program groups and .INI file

settings to Windows NT without installing NT in the same subdirectory

as Windows.

MORE INFORMATION

================

If Windows 3.1 and Windows NT are installed on the same machine but

are located in different subdirectories, it is possible to migrate the

.INI settings and Windows Program Manager groups into Windows NT by

following the procedure outlined below.

NOTE: If you have added program icons other than the default icons in

the Main, Startup, Accessories, or Games groups in Windows 3.1, you

will need to start Windows 3.1 and either move these program icons to

another group or create a new program group and move these icons to

the newly created group. If you do not move these icons, you will not

be able use the following procedure to move the Main, Startup,

Accessories, and Games groups.

To migrate your .INI files and Windows Program Groups to NT:

1. Copy the .INI files from your Windows 3.1 directory to your Windows

   NT directory.

2. To copy the program groups and .INI file settings to your current

   user ID, you must delete the user profile and log off and log on

   again.

   NOTE: You do not need to delete the user, just the user profile.

   CAUTION: When you delete your user profile, any personal program

   groups you have created for this user will be lost.

   To delete the user profile:

   a. Log on as Administrator (NT will not let you delete your

      profile if you are logged on as that user).

   b. Run Windows NT Setup from the Main program group.

   c. Press ALT+O (to select the Options menu).

   d. Press D (to choose Delete User Profiles).

   e. Select the profile to which you want to copy the Windows 3.1

      groups and .INI file settings.

   f. Delete the selected user profile.

3. Log off as Administrator and log back on as the user whose profile

   you have just deleted. After your Username and Password have been

   successfully validated, you will see a screen prompting you to

   confirm migration of program groups and .INI file settings. These

   are selected by default. When you choose OK, the migration process

   will begin. When migration is complete, all program groups and .INI

   file settings will be migrated into your Windows NT user profile.

NOTE: Only users that have their user profiles deleted will be

prompted to migrate. If the profile is not deleted, NT will use the

existing profile and migration will not occur.

MORE INFORMATION

================

For more information on Windows NT program groups, query on the

following words in the Microsoft Knowledge Base:

   migrated and icons and items and video

Additional reference words: prodnt 3.10 WIN.INI initialization

KBCategory: kbusage kbfasttip

KBSubcategory: nthowto


README.TXT: Windows NT Version 3.1 U.S. Service Pack

Article ID: Q102544

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

----------------------------------------------------------------------

This article contains the complete text of the README.TXT file included

with U.S. Service Pack 3 for Windows NT and Windows NT Advanced Server

version 3.1. For information on obtaining U.S. Service Pack 3, query on the

following word (without the spaces) in the Microsoft Knowledge Base:

   S E R V P A C K

---------------------------------------------------------------------------

         Microsoft Windows NT and Windows NT Advanced Server 3.1

                        U.S. Service Pack 3

---------------------------------------------------------------------------

Contents

--------

1.0  Introduction

2.0  Installation Instructions for the Windows NT U.S. Service Pack 3

2.1  User Notes

2.2  List of Bugs Fixed in the Windows NT U.S. Service Pack 3

1.0  Introduction

-----------------

This release of Microsoft Windows NT 3.1 U.S. Service Pack 3 contains all

the components that have been fixed since the retail release of Windows NT

3.1 and Windows NT Advanced Server 3.1.  The Service Pack is easy to apply

from within Windows NT and changes only those files that were originally

set up on the Windows NT or Windows NT Advanced Server system.  Service

Pack releases are cumulative:  they contain all previous fixes, as well as

any new fixes made to the system.

2.0  Installation Instructions for the Windows NT U.S. Service Pack

-------------------------------------------------------------------

Installing the Service Pack from a floppy disk:

1. Insert Service Pack Disk 1 into the floppy drive.

2. At the Windows NT Command Prompt, change to that floppy drive (that is,

   A: or B:) and type UPDATE.

3. Follow the instructions given on the screen.

Installing the Service Pack from a CD-ROM:

1. Insert the Service Pack CD-ROM disk into the CD-ROM drive.

2. At the Windows NT Command Prompt, change to that CD-ROM drive, then

   change to the i386, MIPS, or ALPHA directory (depending upon whether

   you have an Intel, MIPS, or ALPHA AXP CPU), and type UPDATE.

3. Follow the instructions given on the screen.

Installing the Service Pack from a network drive:

1. At the Windows NT Command Prompt, type the command to connect to the

   network drive on which the Service Pack files reside.

2. Change to that network drive and type UPDATE.

3. Follow the instructions given on the screen.

2.1  User Notes

---------------

*** Installing Service Pack 3 on a Dual-Boot computer with the Windows NT

    3.5 (Daytona) Beta

If your computer is dual-booting Windows NT 3.1 and the Windows NT 3.5

(Daytona) Beta, you must perform the following steps before you install

Service Pack 3:

1. Copy the files NTLDR and NTDETECT.COM in your root drive to NTLDR.SAV

   and NTDETECT.SAV.

2. Install the Service Pack.

3. Copy NTLDR.SAV to NTLDR, and NTDETECT.SAV to NTDETECT.COM.

This will allow your machine to continue dual-booting both versions of

Windows NT.

*** Running the File System Update from the Windows NT 3.5 (Daytona) Beta

Once you have installed Service Pack 3, you should not install the file

system update for Windows NT 3.1 from the Windows NT 3.5 (Daytona) Beta.

Service Pack 3 contains all the fixes that are in the Windows NT 3.5

(Daytona) Beta file system update, as well as other fixes.

*** Issues with MS-DOS-based Communications Programs

If you experience difficulties with MS-DOS-based communications programs

after installing Service Pack 3, change the configuration of the program to

enable software flow control (XON/XOFF) instead of hardware flow control

(RTS/CTS).  Changing this parameter has been found to correct problems with

these applications in most cases.

*** Installing the Service Pack on a System with an OEM supplied HAL.DLL

If your Windows NT system uses a HAL.DLL supplied by an OEM (one that was

not installed from the Microsoft Windows NT 3.1 disk set) you need to

follow the steps below to reinstall the OEM HAL after the Service Pack

Update program has been run, but before the machine is rebooted.  If you do

not reinstall the OEM HAL properly, your system may not boot after

installing the Service Pack (because the OEM HAL will have been replaced by

a HAL from the Service Pack). If this happens, use your Emergency Repair

Disk to repair your system, then follow the steps below.

1. Before the Update program is run, copy the HAL.DLL file to HAL.OEM to

   save it.  On an x86 machine, HAL.DLL is located in the %windir%\system32

   directory.  On a MIPS or Alpha machine, the following command should

   locate it:

      DIR /S %windir%\..\hal.dll

2. After the Update program has been run, but before you have it reboot

   your system, start a Command Prompt window, and restore the HAL.DLL you

   saved in step (1).  On an x86 machine,

      CD %windir%\system32

      COPY HAL.OEM HAL.DLL

3. Now switch back to the Update program and have it reboot your system.

*** Configuring the NWLink Transport

When configuring the NWLink transport using the Network option in Control

Panel, you must enter the Network Number as a hexadecimal value rather than

as a decimal value as stated in the Help file.

*** Converting Macintosh Filenames to Win32 Filenames

In general, the Windows NT (Win32) interface can view and use filenames

created by a Macintosh client.  There are two exceptions, where the

filename is an illegal Win32 filename:

   The Macintosh client creates a filename that ends with a period.

   The Macintosh client creates a filename that ends with a blank space.

In both of these cases, the Windows NT interface displays the filename

with a thick vertical bar (|) or question mark (?) character replacing

the final period or space.  Only the last character is replaced.

For example:

   Macintosh filename         Windows NT displays the filename as . . .

   ------------------         -----------------------------------------

   An important file.         An important file|

   Very important file ...    Very important file ..|

   One space at the end       One space at the end|

   Two spaces at the end      Two spaces at the end |

You can view and use the converted filenames in the Windows NT interface.

You cannot view and use them from the Command Prompt (CMD.EXE).  A Win16

application that converts long filenames to the 8.3 format can convert

these filenames to the 8.3 format.

For Macintosh filenames that already exist on the Services For Macintosh

server, before this updated functionality, the server will rename such

files the first time they are accessed.

The final character is mapped to an unused UNICODE character (0xF000+xx).

Windows NT does this same mapping for characters that are illegal in the

NTFS file system.

*** Updating Printer Drivers Installed for a Different Platform

The Service Pack only updates printer drivers for the platform you install

it on.  For example: If you update an Intel-based print server that you

have MIPS computers printing to, it needs to have the MIPS version of the

printer driver installed. The Service Pack only copies the Intel-based

printer driver to the print server. In this case, you need to copy over the

appropriate driver by hand.

The following procedure describes how to install the PostScript printer

driver by hand.

1.  Rename PSCRIPT.DLL and PSCRPTUI.DLL in the directory below to

    PSCRIPT.OLD and PSCRPTUI.OLD

       system32\spool\drivers\<platform>

    where <platform> is w32mips, w32alpha, or w32x86.

2.  For MIPS or ALPHA drivers, copy the PSCRIPT.DLL and PSCRPTUI.DLL files

    from the MIPS or ALPHA subdirectories on the CD-ROM to the subdirectory

    in Step 1 above. For Intel-based drivers, type

       expand -r PSCRIPT.DL_ <subdirectory from step 1>

       expand -r PSCRPTUI.DL_ <subdirectory from step 1>

    from the i386 subdirectory on the CD-ROM where <subdirectory> is the

    subdirectory from Step 1.

*** Emergency Repair Disk

If it is necessary to use the Windows NT Emergency Repair Disk to repair

your Windows NT system at some time after you apply the Service Pack, you

will need to re-apply the Service Pack after the repair is completed.  This

is because the Emergency Repair Disk repairs your system by restoring your

original Windows NT setup.  After the repair has completed, simply follow

the above Installation Instructions to re-apply the Service Pack.

*** Adding New Components to the System

If new software or hardware components are changed or added to your system

after you have applied the Service Pack, it will be necessary to re-apply

the Service Pack.  This is because the files taken from the original

Windows NT disk set may not be equivalent to the files on the Service Pack

disk set. It is not possible to install new components directly from the

Service Pack media (such as a new keyboard or printer driver).  New

components must be installed from the original product media.

*** Command Reference Colors

Some commands in the Command Reference (NTCMDS.HLP) list of commands are

not visible if your system colors are set to Window Text = white and Window

Background = black.  Change your Windows Background to a lighter color to

see all the commands in the list.

*** Previous Versions of NTBackup

Backup tapes created with the version of NTBackup shipping with this

Service Pack cannot be restored or read with versions of NTBackup shipped

prior to Service Pack 2.  However, tapes created with previous versions of

NTBackup  can be read and restored by the version of NTBackup in this

Service Pack. NTBackup now uses Unicode whenever it writes to tape, which

was not understood by previous versions of NTBackup.

*** Previous Versions of Services For Macintosh (SFM)

To correct a problem with file names ending in a space or period, a change

was made to the Services For Macintosh software which makes earlier

versions of this software unable to correctly read Macintosh file names on

the Windows NT Advanced Server system.  The new Services For Macintosh

software will alter the NTFS file name to allow Macintosh clients to

properly view them.  This means that once you update your Services For

Macintosh system files with this Service Pack, versions of the SFM software

prior to Service Pack 2 will not function properly if installed on the

system.

*** Installing Symbol Files from the CD-ROM

To install the symbol files corresponding to the new binaries in Service

Pack 3, do the following (assuming your CD-ROM drive is D:, your symbol

files are located in the C:\WINNT\SYMBOLS directory, and you are installing

the files for an x86 machine):

   XCOPY /S /U /D D:\SUPPORT\DEBUG\I386\SYMBOLS C:\WINNT\SYMBOLS

This will copy the Service Pack 3 .DBG files over the existing versions of

these files.  The XCOPY command shown will copy only those .DBG files that

are already installed (/U switch), and only those with a more recent time-

date stamp (/D switch).

2.2  List of Bugs Fixed in Windows NT U.S. Service Pack 3

---------------------------------------------------------

NOTE: Use the Qxxxxxx number that precedes the title of the bug fix to

query the Microsoft Knowledge Base to find an article about that bug.

Q102117: Specified Home Directory May Default to USERS\DEFAULT

Q102819: Error Moving File If File Already Exists on Destination Drive

Q103010: Read-Only Files Don't Copy Correctly to Net One Server

Q103147: Err Msg: An Application Error Has Occurred... in SPOOLSS.EXE

Q103362: Publisher 2.0 May Cause an Exception in the Win16 Subsystem

Q103395: ALT+Double-Click Allows (Restricted) Program Item Creation

Q103445: Advanced Server Hang with Service for Macintosh

Q103473: SFM: MacFile Menu Not Displayed if NTAS Drive Letter Changes

Q103476: Windows NT Terminal May Disable a COM Port for all VDMs

Q103828: RAS Password Authentication Failed

Q103923: Files with Umlauts Cannot be Seen on Shared NTFS Partition

Q103931: Err Msg: An Application Error Has Occurred...(LMSRVCS.EXE)

Q103936: Err Msg: MSPUB Caused an Exception in the Win16 Subsystem

Q104164: File Manager Send Mail May Fail with Check Spelling Enabled

Q104181: Large File Copies May Fail After 4 Gigabytes in Windows NT

Q104184: Windows NT Terminal and Telnet May Cause an Access Violation

Q104198: SFM: Macintosh Locked Folders Are Not Completely Secure

Q104227: XCOPY from CD-ROM on DPT 2012b Controller Can Cause Hang

Q104549: Cannot Restore Backup After Upgrading to U.S. Service Pack 2

Q104665: Err Msg: InitializeMemory failed 00000010

Q104668: Backup Truncates Long Mac Filenames w/ Trailing Dots or Spaces

Q105158: Schedule Service Doesn't Run on Sundays

Q105249: Serial Printers May Print Garbage During Windows NT Startup

Q105266: SFM: Print Spooler Does Not Work in Embedded Print Jobs

Q105268: Pressing CTRL+C in PORTUAS Causes Password Problems

Q105328: Cannot Log On to Domain, Lowercase Extended Characters

Q105330: FORMAT Err Msg: Error Writing Partition Table

Q105332: Print Monitor Cannot Handle More Than 255 Zones

Q105486: Control Panel, Drivers: Cannot Browse Compressed Files

Q105487: WINMSD: Viewing File Details Generates Access Violation

Q105488: Backup Err Msg: Fatal Error on Drive 1

Q105489: Access Violation: Performance Monitor Playing Back Log Data

Q105491: Cannot Connect if Share Name is Longer than 17 Characters

Q105492: System Hot-keys Incorrectly Received by Application

Q105493: Memory Manager Doesn't Reset Event when Paging in Executable

Q105554: Changing NonPagedPool Value Causes Boot Problems

Q105555: TCP/IP Data Corruption Problem

Q105556: RAS: Bad Disconnection from Windows for Workgroups Computer

Q105568: Novell WorkPlace TCP/IP Client Stops Responding

Q105570: GDI.EXE (16-bit) Causes General Protection Fault

Q105577: Odd-byte 16-bit Data Transfers Cause Time-outs and NMIs

Q105578: PROTEON.SYS Causes Fatal System Error

Q105601: Terminal: ALT Key Dysfunctional

Q105602: Paintbrush Starts in Monochrome with Color Display

Q105620: Mail: Cannot Save Attachments with Extended Characters

Q105622: Unplugging DEC EtherWorks Turbo Ethernet Hangs Computer

Q105623: Some CPU Time is Calculated as Idle Time

Q105624: File Times on LAN Manager Server Set Wrong

Q105625: RASPHONE: Login Fails on Callback After Changing Password

Q105626: Can Read Redirected, Locked File

Q105627: Memory in Page Pool Not Deallocated Correctly

Q105629: NCR Video Driver Fails on Fast Computers

Q105630: Browser Monitor Causes Bugcheck

Q105636: Redundant Line of Code Causes Access Violation in LSASS.EXE

Q105637: Problems with NCR Miniport Driver and MS-DOS Applications

Q105720: PORTUAS: Character Mapping Problems

Q105722: GP Faults Running SQL Server 4.2

Q105723: MS-DOS Clients Report Zero Disk Space on Windows NT Server

Q105724: Sharing Violations from Windows for Workgroups Client

Q105725: FTP: Use of Wild Card Port Results in Denial of Service

Q105727: CD-ROM File System Generates Bugcheck Under Stress

Q105729: PortUAS: /log:<filename> Switch Added

Q105730: Err Msg: ...OEMNADNF is Missing the Referenced File

Q105734: Registry String That Ends at Page Boundary Causes Fault

Q105735: NDIS.SYS Causes MIPS Computers to Stop Responding

Q105736: Server Stops Responding while Processing LAN Manager API

Q105737: Classifying Illegal Datagram Causes Browser Access Violation

Q105738: Digiboard DIGIFEP5 Driver Doesn't Load

Q105739: NTFS Does Not Correctly Set Archive Bit

Q105742: Memory Manager Problem Causes System to Stop Responding

Q105786: SFM: Deleted User Accounts Not Aged Out of Cache

Q105787: Calling a Pageable Function While Holding Spinlock

Q105788: Two Network Adapters Do Not Work for TCP/IP

Q105798: Changing Subdirectory on Macintosh Volume Causes Bugcheck

Q105799: NDIS Indications Stop Responding when No Memory is Available

Q105800: Backup Program Loops Indefinitely

Q105801: WOW Sets Sound Pointer Incorrectly

Q105802: Printing from Macintosh to Advanced Server Causes Bugcheck

Q105805: WOW32 Access Violation

Q105832: 1280x1024 Video Mode Doesn't Work with Number 9 Boards

Q105851: Recursive Batch File Causes System to Stop Responding

Q106220: GP Fault After Choosing Copy

Q106434: System Clock Appears to Lose About One Second per Hour

Q106555: SFM: Critical Error After Applying U.S. Service Pack 1

Q106618: After DLC Installed, Exception Error in SPOOLSS.EXE

Q106735: Closing Word for Windows 6.0 Causes General Protection Fault

Q106737: ATI Video Driver Problems

Q106738: NetLogon: Primary Group Not Replicated Properly

Q106739: Visual C++ 1.0: Breakpoints Not Working with DPMI Calls

Q106740: Exception Error Printing from Word 6.0 to Windows NT Server

Q106742: External Monitor on Toshiba 4400sx Monochrome Doesn't Work

Q106743: After Converting FAT to NTFS SYSTENT32AP Directory Corrupted

Q106744: Deleting Connection Closes Files on Open Share

Q107118: Multiple Calls of GetHostByName to DNS Causes Errors

Q107149: Cannot Restart After Converting FAT Partition to NTFS

Q107150: Service Pack Update Fails with Not Enough Free Disk Space

Q107154: Event Viewer Uses Too Much Memory After Some Time

Q107155: DLC: MP Computer STOP Message After SNA Stopped

Q107187: Data Download from CompuServe Stops with OzCIS

Q107234: One Processor Shows 100% Usage Constantly on NCR MP

Q107235: French MIPS: Illegal Instruction in WOWEXEC

Q107236: Unable to Run Word for Windows 6.0 on RISC-based Computers

Q107237: LAN Manager NET USE Generates MS-DOS Error 55

Q107238: Fault Tolerance Errors on Striped Set with Parity

Q107239: Portuguese Language: Accent Circumflex (^) Key Dysfunctional

Q107240: STOP Message After You Detach Token Ring Cable

Q107241: Backup Does Not Back Up Files Ending in Spaces or Periods

Q107242: Local Path Set to UNC Path in User Manager

Q107243: Setup: Some COMPAQ Qvision Video Adapters Are Not Detected

Q107246: Screg Access Violates Intermittently When Stopping Driver

Q107247: Spaces Not Removed From Short Filenames in NTFS Shares

Q107248: File Manager Hangs Opening Many New Network Drive Windows

Q107251: Disk Administrator Only Supports 50 Hard Disk Drives

Q107252: Share Not Recreated if SYSTEM Cannot Access Share

Q107253: ACLCONV Err Msg: ...PAGEFILE.SYS is corrupt. Run CHKDSK

Q107378: STOP Message: Exception Error in NTOSKRNL.EXE

Q107379: Disk Media Format Error During Setup

Q107447: File and Directory Display Problems in Borland Workshop

Q107448: Publisher 2.0a May GP Fault Due to Window Property Problem

Q107449: Cannot Start Application with Long Path (64+ Characters)

Q107452: ALT+F4+F6 in 16-bit MDI Applications Hangs Windows NT

Q107456: Must Restart Computer Running ACLCONV on Large Volume

Q107509: Word for Windows 6.0 Closing Header Toolbar Hangs Windows NT

Q107548: Update Incorrectly States That Setup Failed

Q107552: Problems Trying to Add Digiboard PC/16E Drivers

Q107554: Backup Hangs During Verification

Q107633: Exceed/NT Fonts Don't Load Over Network on SP2a

Q107663: Embedded Document Doesn't Load When Double-clicked

Q107666: SP2b NTDETECT Doesn't Recognize Submodel Bytes of IBM Thinkpad

Q108044: Intel EtherExpress 16 Adapter Fails Occasionally

Q108046: Slow Network Performance in Mail or Access

Q108048: Printing Graphics from DOS Client Prints Incorrectly

Q108056: Macintosh Finder Sometimes Does Not Display File

Q108057: Win32 Applications Don't Support Some Macintosh Filenames

Q108058: Not All Groups Are Listed in File Manager in User Browser

Q108070: Err Msg: Application Log Full When Overwrite As Needed is Set

Q108103: Service Pack 1 Resets Permissions on an NTFS Volume

Q108104: STOP Message: 0x0000001E in STREAMS.SYS

Q108240: Setup Fails with IBM Thinkpad Model 750

Q108255: Windows NT TCP/IP Server Freezes

Q108256: Event ID:2000 Errors in Event Log

Q108263: Err Msg: The Conversion Failed...Was Not Converted to NTFS

Q108264: Word 6.0 Find File Generates Application Error in NTVDM.EXE

Q108266: Event Viewer Won't Run If Application Registry Keys Removed

Q108465: Saving Changes to a File on an SFM Volume Fails

Q108486: Server Manager Reports Incorrect Number of Open Files

Q108646: Mandatory Profiles Cause Access Error Message When Logging On

Q108647: STOP Message: 0x00000051... REGISTRY_ERROR

Q108648: Macintosh Locks Up When Changing Zones with SP2

Q108920: Stopping System Error Messages From Appearing on Desktop

Q109098: STOP Message: 0x0000001E in NTOSKRNL.EXE

Q109586: PARALLEL.SYS Causes STOP Message

Q109850: DIR Command from Windows for Workgroups Returns Incomplete

Q110065: System Stops Responding When Printing from UNIX

Q110066: Print Server Slow Down and GP Fault in LMSVCS.EXE

Q110079: System Stops Responding When Copying Corrupt SFM Files

Q110089: Problems with ATI Adapters and DrvSaveScreenBits Stacks

Q110149: NTBACKUP: Fails to Detect Network Failure

Q110151: Boot Failure on Large Hard Disk Drives

Q110153: General Protection Fault in Lotus 1-2-3 for Windows

Q110154: Access Violation in Backup

Q110155: Photoshop Does Not Print Correctly to PostScript Printer

Q110156: PageMaker 5.0 Does Not Print to PostScript Printer

Q110158: Err Msg: ...Can Only be Updated When You Exit Paintbrush

Q110184: RAS Admin Doesn't See Changes to COM Port

Q110275: File Manager Hangs During Network Stress

Q110326: Long Directory Path, Access Violation in Backup

Q110345: Word 2.0: Blank Items in File List Boxes and Missing Letters

Q110347: Giving Dial-In Permissions to Users of a Trusted Domain

Q110426: SMC 661-666 Floppy Controller, Errors Reading Disks

Q110431: SFM: File Time and Date Stamp Change on Copy

Q110458: Setup Fails with 16 or 32 BIOS Drives

Q110481: Backup Doesn't Back Up Entire Hard Disk or Create Log File

Q110686: Access: Toolbar Disappears Instead of Docking

Q110689: Winlogon Does Not Release Thread Handles

Q110763: Postscript Error Printing to Macintosh from Windows NT

Q110942: Hang on Reboot Autocheck of Stripe Set with Parity

Q110946: SP2 Prohibits Administrator Access to Locked Workstations

Q111471: Access Violation in SPOOLSS.EXE

Q111995: STOP Message: 0xc000000D

Q112016: Print Jobs Incomplete or Corrupt with Serial Printing

Q112022: Mac Client Cannot Print After Service Pack 2 is Installed

Q112145: Err Msg: Performance Monitor: Illegal to Append Data From...

Q112201: Spooling More than 127 Jobs to Print Queue Causes Corruption

Q112455: Err Msg: STOP Message 0xC0000021A Starting Windows Application

Q112760: STOP Message 0xA when Lots of Data is Sent Over SNA Bridge

Q112810: STOP Message: 0x1E Trap Uploading File on Clark PCBoard BBS

Q112826: Server Manager Cannot Find DC with TCP/IP and ELNK3

Q112862: SFMATALK.SYS Could Cause STOP Message 0x0000000A

Q112871: SNMP Always Returns an Error Index of One

Q112872: Access Violation in SNMP When Processing Short OIDs

Q112873: SNMPTRAP Quits When Sending Information

Q113047: Incomplete NTBACKUP Directory Listing

Q113130: MS-DOS-Based Applications Print Jobs Incomplete

Q113192: STOP Message: 0x0000000A with ARROW.SYS Driver

Q113576: WinSocket App's Reject Connection Requests with Reset Frames

Q113709: NTBACKUP Doesn't Create Set Description from Command Line

Q113747: Err Msg: The Browser Has Received an Illegal Datagram...

Q113909: NTBACKUP Creates Additional Backup Set Description File

Q113941: Err Msg: "The Handle is Invalid"  with Console Applications

Q114231: STOP 0x1E in SFMRV.SYS When Running Services for Macintosh

Q114232: User Attempt to Change Password Causes Error 2242

Q114244: Unable to Upgrade Service Pack 2 On Magneto Optical Drives

Q114637: Windows NT Hangs on Start Up When No Keyboard is Connected

Q114638: Only 60 Clients Can Simultaneously Access a TCP/IP Share

Q114684: SFM Err Msg: A Device Attached to the System is Not...

Q114685: STOP - The Parameter is Incorrect

Q114698: STOP Message: 0x0000000A IRQL2 in NBT.SYS

Q114703: DEL *.* Through Gateway Services for NetWare Leaves Files

Q114704: Cannot Print in Landscape Mode with Super Project

Q114705: Pressing ENTER in Pop-Up Menu Causes Erratic Behavior

Q114706: Olivetti LSX 5025/E Won't Boot with ARROW.SYS Driver

Q114707: Windows NT Does Not Allow %servername% in Profile Path

Q114734: NTBACKUP Fails When Backing Up and Restoring Over the Network

Q114735: Service Pack 2: COM2 Port Problem

Q114736: NTBACKUP Cannot Open Log File During Batch Mode

Q114737: SNMP Fails With More Than Four Trap Sources

Q114738: Streams Sometimes Sends Error Messages to Wrong Queue

Q114739: AppleTalk Print Jobs Stay in Queue and Don't Print

Q114740: Virtual Memory Runs Out When Running Event Log Batch File

Q114759: Dot Matrix Printer Controls Don't Function

Q114765: EVENTLOG.EXE Causes Memory Access Violation

Q114766: Profiles with %profileserver% in Path Do Not Load

Q114767: Reconnecting Through the Serial Port Hangs Pentium Computers

Q114768: Exception Violation in LMSVCS.EXE with TCP/IP

Q114769: DigiBoard Installation Fails to Write Registry Information

Q114770: Program Manager Disappears When Browsing a Corrupt Icon File

Q114784: IBM Exabyte 8200 Tape Drive Not Fully Supported

Q114805: Exabyte 4200 Tape Unit with Future Domain 1650: STOP Message

Q115281: Renaming Files Over Network Causes Out of Memory Error

Q115875: Problem with Scope ID on Alpha and MIPS Systems

Q117360: Browser Service Has Hung and Other TCP/IP Errors

Q117414: Communication Through FDDI to MAC Address Fails

Q117425: Err Msg: SCREG.EXE Application Error

Q117860: STOP Message May Appear When You Administer 3.5 Server

Q118476: Err Msg on File Server: XXXXXX Target Directory is Corrupt...

Q119644: Copying Files from Windows NT Using NBF Can Be Very Slow

Q120492: Periodic Polling Causes Problems with Removable Media

Q120520: Server Manager Disconnects Multiple Users

Q120770: STOP: 0x0000000A When CadexNet on LM Clients Stress NTAS SRV.SYS

Q120941: STOP 0x0000007B Inaccessible_Boot_Device IBM PS/2 Model 53

Additional reference words: prodnt 3.10 qfe servpack sp3

KBCategory: kbreadme kbfasttip

KBSubCategory: ntdistrib


User Authentification with Windows NT

Article ID: Q102716

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

----------------------------------------------------------------------

SUMMARY

=======

This article discusses the following aspects of user authentication:

 - Storage of the Passwords in the SAM Database

 - User Authentication by the MSV1_0 Authentication Package

 - Pass-Through Authentication

MORE INFORMATION

================

Storage of the Passwords in the SAM Database

--------------------------------------------

User records are stored in the security accounts manager (SAM)

database. Each user has two passwords with which it is associated: the

LAN Manager compatible password and the Windows NT password. Each

password is stored doubly encrypted in the SAM database. The first

encryption is a one-way function (OWF) version of the clear text

generally considered to be non-decryptable. The second encryption is

an encryption of the user's relative ID (RID). The second encryption

is decryptable by anyone who has access to the double-encrypted

password, the user's RID, and the algorithm. The second encryption is

used for obfuscation purposes.

The LAN Manager compatible password is 100 percent compatible with the

password used by LAN Manager. It is based on the original equipment

manufacturer (OEM) character set, not case sensitive (enforced by

upper casing before encryption), and up to 14 characters long. The OWF

version (called the LAN Manager OWF or ESTD version) of the password

is computed by encrypting a constant with the clear text password

using DES encryption. The LAN Manager OWF password is 16 bytes long.

The first 7 bytes of the clear text password are used to compute the

first 8 bytes of the LAN Manager OWF password. The second 7 bytes of

the clear text password are used to computer the second 8 bytes of the

LAN Manager OWF password.

The Windows NT password is based on the Unicode character set, is case

sensitive, and can be up to 128 characters long. The OWF version

(called the Windows NT OWF password) is computed using the RSA MD-4

encryption algorithm, which computes a 16-byte "digest" of a variable

length string of clear text password bytes.

Any particular user account might be missing either the LAN Manager or

Windows NT password, however, every attempt is made to maintain both

versions of the password. For instance, only the LAN Manager version

of the password exists if the user account was ported from a LAN

Manager UAS database using PortUas or if the password was changed from

a LAN Manager or Windows for Workgroups client. Only the Windows NT

version of the password exists if the password is set or changed from

a Windows NT client and the password has no LAN Manager representation

(that is, it is longer than 14 characters or the characters cannot be

represented in the OEM character set). All the existing user interface

limits do not allow Windows NT passwords to exceed 14 characters. The

implications of this are discussed below.

User Authentication by the MSV1_0 Authentication Package

--------------------------------------------------------

All user authentication in Windows NT occurs using the LsaLogonUser

API. LsaLogonUser actually authenticates users by calling an

authentication package. The default authentication package that comes

with Windows NT is the MSV1_0 Authentication Package. The MSV

Authentication Package uses the SAM database as its database of users,

and it supports pass-through authentication of users in other domains

by using the Netlogon service.

Internally, the MSV authentication package is split into two halves: a

top half and a bottom half. The top half executes on the machine being

logged onto (or connected to). The bottom half executes on the machine

that contains the user account. When both machines are the same

machine, the MSV Authentication Package top half simply calls the

bottom half without involving the Netlogon service. When the MSV

authentication package top half recognizes that pass-through

authentication is needed (based on the fact that the domain name

passed to it is not its own domain name), MSV passes the request to

the Netlogon service, which routes the request to the Netlogon service

on the appropriate machine, which in turn passes the request to the

bottom half of the MSV Authentication Package on that machine.

LsaLogonUser supports interactive logons, service logons, and network

logons. All forms of logon through the MSV Authentication Package pass

the name of the domain containing the user account, the name of the

user account, and some function of the user's password. These

different types of logon differ in the way the password is represented

as it is passed to LsaLogonUser.

For interactive logons and service logons, the client logging on is

physically on the machine running the top half of the MSV

Authentication Package. In this case, the clear text password is

passed into LsaLogonUser and the top half of the MSV Authentication

Package. The top half of the MSV Authentication Package converts the

clear text password to both a LAN Manager OWF password and a Windows

NT OWF password before passing it on to either the Netlogon service or

the lower half. The lower half queries the OWF passwords from SAM and

compares the OWF passwords to ensure they are identical.

For network logons, the client connecting to the machine was

previously given a 16-byte challenge (or "nonce"). If the client is a

LAN Manager client, the client computed a 24-byte challenge response

by encrypting the 16-byte challenge with the 16-byte LAN Manager OWF

password. This is the algorithm used by LAN Manager. The LAN Manager

client passes this "LAN Manager Challenge Response" to the Windows NT

server. If the client is an Windows NT client, the client computed a

LAN Manager Challenge Response, just as above. In addition, the

Windows NT client computes an "Windows NT Challenge Response" by using

the identical algorithm but using the 16-byte Windows NT OWF password

instead of the LAN Manager OWF password. The Windows NT client then

passes both the LAN Manager Challenge Response and the Windows NT

Challenge Response to the Windows NT server. In either case, the

Windows NT server authenticates the user by passing all of the

following to LsaLogonUser: the domain name, the user name, the

original challenge, the LAN Manager Challenge Response, and the

optional Windows NT Challenge Response. The top half of the MSV

Authentication Pack passes this unchanged to the bottom half. The

bottom half queries the OWF passwords from SAM, computes the

appropriate Challenge Response using the OWF password from SAM and the

passed in Challenge, then compares the computed challenge response to

the one passed in.

As mentioned above, either the Windows NT password or LAN Manager

password might be missing from the SAM database. Also, either the

Windows NT password (or a function thereof) or the LAN Manager

password might be missing from the call to LsaLogonUser. This

paragraph describes which passwords are compared in which cases. If

both the Windows NT version of password from SAM and the Windows NT

version of the password from LsaLogonUser are available, they are both

used. Otherwise, the LAN Manager version of the password is used to

compare against. This rule allows case sensitivity to be enforced when

going Windows NT to Windows NT, but it also allows backward

compatibility.

Pass-Through Authentication

---------------------------

The NetLogon service implements pass-through authentication. Its role

is three fold: it selects the domain to pass the authentication

request to, it selects the server within the domain, and it actually

passes the authentication request through to the selected server.

Selecting the domain is straightforward. The domain name is passed to

LsaLogonUser. The domain name is processed as follows:

 - If the domain name matches the name of the SAM database, the

   authentication is processed on that machine. The name of the SAM

   database on a Windows NT workstation that is a member of a domain is

   considered to the name of the Windows NT machine. The name of the SAM

   database on a Windows NT Advanced Server is the name of the domain.

   All logons to Windows NT machines that are not members of a domain

   process requests locally.

 - If the domain name specified is trusted by this domain, the

   authentication request is passed through to the trusted domain. On

   Windows NT Advanced Server, the list of trusted domains is readily

   available so this comparison is trivial. On a Windows NT workstation,

   the request is always passed through to the primary domain of the

   workstation, allowing the primary domain to determine if the specified

   domain is trusted.

 - If the domain name specified is not trusted by this domain, the

   authentication request is processed on the machine being connected to

   as if the domain name specified were that domain name. NetLogon does

   not differentiate between a nonexistent domain, an untrusted domain,

   and an incorrectly typed domain name.

Some network clients don't specify the domain name. These clients

include Windows for Workgroups 3.1 and LAN Manager OS/2 version 2.2. A

patch is available to LAN Manager OS/2 2.2 that causes it to pass a

domain name. A Windows NT workstation handles this NULL domain name by

checking to see if the account exists locally. If so, the request is

processed locally; otherwise, the request is passed to the primary

domain. The Windows NT Advanced Server also checks if the account

exists locally. If so, the request is processed locally; otherwise,

the Advanced Server tries to determine if a trusted domain has the

account. If does this by sending a second-class mailslot message to

each trusted domain. Each trusted domain responds indicating whether

it defines the account specified. The request is passed through to the

first domain that responds affirmatively. If no domain responds

affirmatively, this NULL domain is treated as an untrusted domain (as

described above). If more than one domain responds affirmatively, only

the first response is used. (This is a strong argument for upgrading

clients that pass NULL domain names and having only a single account

for any particular user in the enterprise.)

NetLogon picks a server in the domain by a process called "discovery."

A Windows NT workstation "discovers" the name of one of the Windows NT

Advanced Servers in its primary domain. A Windows NT Advanced Server

"discovers" the name of an Windows NT Advanced Server in each trusted

domain.

Pass-through authentication is merely an I_NetLogonSamLogon API call

over the secure channel. If the logon call is an interactive logon,

Netlogon encrypts the OWF passwords with the secure channel session

key before passing them to the NetLogon service. The session key

encrypted OWF passwords are decrypted before they are passed to the

bottom half of the MSV authentication package.

Additional reference words: prodnt 3.10

KBCategory: kbother kbfasttip

KBSubCategory: ntsecurity


LMHOSTS File Information and Predefined Keywords

Article ID: Q102725

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

--------------------------------------------------------------------

The LMHOSTS file is a local text file that maps IP addresses to NetBIOS

names of remote servers with which you want to communicate over the TCP/IP

protocol. Windows NT recognizes names instead of IP addresses for network

requests and a name discovery process is used to correctly route network

requests with TCP/IP. Because the name discovery process is generally not

routed by an IP router, the LMHOSTS file allows Windows NT machines to

communicate using TCP/IP across a subnet.

This article is divided into the following sections:

 - Comprehensive Information

 - LMHOSTS Entry Cache

 - Predefined Keywords

 - More Information on Block Inclusion

Comprehensive Information

-------------------------

 - LMHOSTS contains IP address to "NetBIOS over TCP/IP" name translations.

 - LMHOSTS is only used by the NBT (NetBIOS over TCP/IP) interface.

 - LMHOSTS file contains some valuable additions to the LAN Manager and

   Windows for Workgroups LMHOSTS file, such as the ability to support

   routed domain logon validation.

 - LMHOSTS contains static information about TCP/IP addresses, but using

   logon scripts and/or the replicator service, the "master" file can be

   distributed transparently across all stations.

 - By default, the LMHOSTS file should be located in the directory

   %SYSTEMROOT%\SYSTEM32\DRIVERS\ETC (usually

   C:\WINNT\SYSTEM32\DRIVERS\ETC).

LMHOSTS Entry Cache

-------------------

By default, entries specified with the #PRE keyword are cached at

initialization up to a maximum of 100 entries. More initially cached

entries can be obtained modifying the following Registry value:

   \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

   \NBT\Parameters\MaxPreload

The sequence used to determine NetBIOS to IP address resolution is the

following: the cache is verified, a broadcast to the subnet is performed,

and then additional entries from LMHOSTS are checked. If a connection is

not established within 15 seconds, the TDI times-out and an error message

is displayed.

Predefined Keywords

-------------------

All predefined keywords that are valid for Windows NT and Windows NT

Advanced Server computers are not valid for LMHOSTS files on Microsoft LAN

Manager or Microsoft Windows for Workgroups computers. These computers

can't be validated by routed domain controllers the same way Windows NT

computers can. To be able to validate them, use the LAN Manager TCP/IP

Extensions Service available on all OS/2 LAN Manager (version 2.1a or

later) servers.

   # <"remark line">

      Used to remark IP address to NetBIOS names.

   #PRE

      Defines which entries should be initially preloaded into the

      name cache.

   #DOM:<"domain_name">

      Distinguishes Windows NT Advanced Server servers from Windows NT

      workstations, a LAN Manager server, or a Windows for Workgroups

      computer. This keyword is needed for all servers that validate logon

      requests.

   #NOFNR

      Avoid Directed Name Queries (DNS). Some earlier versions of LAN

      Manager cannot handle NetBIOS DNS requests and return error 53.

      Specifying this flag on the same line will avoid using NetBIOS

      directed name queries.

   #BEGIN_ALTERNATE

      #INCLUDE <\\"server_name01"\"sharename"\LMHOSTS>

      #INCLUDE <\\"server_name02"\"sharename"\LMHOSTS>

      ...

   #END_ALTERNATE

      Defines a redundant list of alternate locations for LMHOSTS files.

      The recommended way to #INCLUDE remote files is using a UNC path,

      to ensure access to the file. Of course, the UNC names must exist

      in the LMHOSTS file with a proper IP address to NetBIOS name

      translation.

The first 3 keywords can be used together to specify 1 NetBIOS over TCP/IP

name to IP address translation. For example:

102.54.94.97   rhinodc   #DOM:rhino   #The rhino domain PDC   #PRE

102.54.94.99   zoobdc    #DOM:rhino   #BDC for rhino domain   #PRE

To start with the IP Address followed by the NetBIOS name, the predefined

entries can be defined in diverse order. It is recommended to insert

important entries first, because the the file is accessed in sequential

order.

More Information on Block Inclusion Keywords

--------------------------------------------

Windows NT provides new block commands that permit centralized location and

management of the LMHOSTS file. In addition, provisions are included to

permit redundant backup copies on multiple servers. The following Windows

NT LMHOSTS file block commands are discussed in detail below:

 - #INCLUDE

 - #BEGIN_INCLUDE

 - #END_INCLUDE

 - #BEGIN_ALTERNATE

 - #END_ALTERNATE

Block Inclusion Keywords (#BEGIN_INCLUDE, #END_INCLUDE):

   130.20.26.169  Trustedserver  #PRE   #DOM:Testing  # Test group domain

   #BEGIN_INCLUDE

   #INCLUDE \\localsrv\public\lmhosts       # Local domain

   #INCLUDE \\Trustedserver\public\lmhosts  # Server in Testing domain

   #END_INCLUDE

In the above block inclusion, the specified LMHOSTS file is scanned under

the following conditions:

 - During TCP/IP initialization, the local LMHOSTS file is scanned for

   #PRE commands. It places all these entries in its name cache. In

   addition, all LMHOSTS files specified by the #INCLUDE command are

   scanned.

 - When resolving a computer name (NetBIOS name) to an IP address, the

   #INCLUDE file is also searched if the name cannot be found in the

   preloaded entries of the cache.

 - The LMHOSTS files are scanned to resolve the address of a domain

   controller of a domain that is not found in the preloaded cache name

   list.

The benefit of this command is that it allows system administrators to

easily maintain a centrally-located master LMHOSTS file that can be

accessed over the network by each node. This method also works across

subnets because of the use of UNC (universal naming convention) names and

LMHOSTS mappings for these entries.

If the domain spans multiple subnets or if the domain controller for a

domain is across a router, it is necessary to have an entry in the LMHOSTS

file for locating the domain controller for that server, with a #DOM prefix

added (for our example, trustedserver is the domain controller for domain

TESTING). See the IP line above the block inclusion. This line must appear

before the #INCLUDE.

In the above case, the TESTING domain has a trust relationship with the

local domain. This is important for servers included in the block that are

not in the local domain.

NOTE: The LMHOSTS files located on servers that are in a trusted domain

should have read privileges for the Everyone group, which includes all of

the local users and the trusted domain users.

Alternate Block Inclusion (#BEGIN_ALTERNATE, #END_ALTERNATE):

   #BEGIN_ALTERNATE

   #INCLUDE \\localsrv\public\lmhosts      # Local domain

   #INCLUDE \\Trustedserver\public\lmhosts # Server in Testing Domain

   #END_ALTERNATE

In this case, the "Alternate Include" condition is satisfied if one of the

#INCLUDE's is successful. This means that only one LMHOSTS file will be

scanned. The first successful #INCLUDE is the only LMHOSTS file that will

be read.

This is helpful in keeping multiple copies of the same file on different

servers. If one of the servers is down, it will attempt to read the LMHOSTS

file from the alternate server identified in the block inclusion.

Additional information, including a full description of all these

features, is available in the "Windows NT Resource Kit."

Additional reference words: prodnt 3.10

KBCategory: kbnetwork kbfasttip

KBSubCatergory: nttcp


Problems with WFW to Windows NT Connectivity

Article ID: Q102775

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

----------------------------------------------------------------------

SUMMARY

=======

In some cases, you may have problems accessing Windows NT servers from

Windows for Workgroups (WFW) computers. This article covers some of

the better known connectivity issues.

When you are using Workgroup Connections or Windows for Workgroups

network functions from MS-DOS, connecting to a computer with a space

in the computer name will result in a syntax error.

WORKAROUND

==========

Use quotation marks around the computer name and share name. This will

allow the connections. For example:

  NET USE F: "\\Computer Name\share"

MORE INFORMATION

================

Using Lowercase Extended Characters for Passwords

-------------------------------------------------

Lower level machines such as WFW should not use lowercase extended

characters for passwords on Windows NT servers. By convention, the

down level client converts the password to uppercase before it is sent

to Windows NT. Some of the international characters do not have an

uppercase equivalent, which causes Windows NT to fail to validate the

password.

Using a Windows for Workgroups Machine as a Backup Browser

----------------------------------------------------------

If Windows NT is the master browser and Windows for Workgroups is the

backup browser, you may get an empty browser list under the following

conditions:

 - A user logs on to the Windows for Workgroups machine and does not

   have a valid username/password for the domain.

 - The Windows NT master browser goes down and promotes the Windows

   for Workgroups browser.

The Windows for Workgroups machine may have a empty browser list

caused by a failure to authenticate with the master before Windows for

Workgroups was promoted.

Using International Characters in the Windows NT Share Name

-----------------------------------------------------------

If you try to connect to a Windows NT share that contains one or more

international characters in the share name, you will receive an error

message.

Access Denied Errors

--------------------

Windows for Workgroups does not send out domain information when:

 - It attempts to log on to the Windows for Workgroups system

 - You issue a "NET USE" command for a Windows NT server causing a

   logon to an Windows NT system

This may cause access denied errors in the case where you have primary

accounts with different passwords in more than one trusted domain.

Your access to the server will depend on which trusted domain can

authenticate the users credential first.

Error 2242

----------

A Windows for Workgroups computer may be unable to connect to a

Windows NT or Windows NT Advanced server computer, for the purposes of

sharing resources. When you try to connect, the Windows for Workgroups

computer generates the following error message: Error 2242.

Windows for Workgroups computers need accounts on Windows NT computers

to use shared resources on the Windows NT computers. Error 2242 is

generated if the given password on that account has expired. This

error can also be generated if the "User must change password on next

logon" box was checked when the account was created.

To correct this error use the following procedure:

1. Make sure the "User must change password on next logon" box is

   unchecked.

2. Type the user password for the Windows for Workgroups computer

   account.

Additional reference words: prodnt WC 3.10 browse

KBCategory: kbinterop kbfasttip

KBSubcategory: ntINTEROP


Information on Browser Operation

Article ID: Q102878

-----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

-----------------------------------------------------------------------

SUMMARY

=======

The Computer Browser service lets you track servers that are active on

the network with a minimum of network overhead. It consists of two

components on a Windows NT or Windows NT Advanced Server computer.

The User Mode component is the Browser, which is part of the LAN

Manager Server service. This portion is responsible for maintaining

the browse list, remoting the NetServerEnum API, and managing the

computer's role as a Browser (or non-Browser).

The Kernel Mode component is the Datagram Receiver and is in charge of

receiving and managing datagrams.

Browser Roles

-------------

A network can contain the following types of servers related to

browsing:

Non-Browser Servers - Do not maintain browse lists, but announce

themselves periodically to the Master Browser.

Potential Browser - Can become a Browser server if needed.

Backup Browser - Maintains a browse list of servers and domains that

it retrieves from the Master Browser.

Master Browser - Receives server and Domain announcements, sends

browse lists to Backup Browsers, responds to clients requesting browse

server lists, promotes Potential Browsers to Backup when needed, and

announces the domain to inform the Master Browsers of other domains of

the domain name and Master Browser for that domain.

Preferred Master Browser - Same as Backup Browser except that it is

biased in elections through setting the IsDomainMasterBrowser to TRUE

is the registry's browser parameters.

Domain Master Browser - The primary domain controller of a domain is

given a special bias in browser elections so that it will become the

Domain Master Browser. This allows browsing to be effective when a

domain spans multiple subnets. A directed datagram is used by Master

Browsers on each subnet to announce itself to the Domain Master

Browser. This is made possible through an entry in the LMHOSTS file on

the Master Browsers for the Domain Controller. This makes it necessary

to have a Windows NT Advanced Server computer to browse across wide

area network (WAN) connections.

There will be at least one Master Browser on a workgroup/domain and

one Backup Browser for every 32 systems in that workgroup/domain. This

means that in a domain/workgroup with fewer than 32 systems, there

will be one Master and one Backup Browser. One more Backup Browser

will be added for every 32 systems. This is accomplished by the Master

Browser telling a Potential Browser to become a Backup Browser.

Browser NetBIOS Names

---------------------

Several special NetBIOS names and Mailslots are used to maintain and

retrieve browse lists. Names listed here as "DOMAIN(xx)" indicate the

domain name followed by the hex value (xx) and padded with spaces to

the 16th byte.

<01><02>__MSBROWSE__<02><01>

This name is registered by the Master Browser and is used to broadcast

and receive domain announcements on the local subnet. It is through

this name that Master Browsers for different domains learn the names

of different domains and the names of the Master Browsers on those

domains.

DOMAIN(00)

This is the name to which server announcements are broadcast in

Microsoft LAN Manager so that other Microsoft LAN Manager computers

can track the servers on the network. Windows NT computers do not make

these broadcasts unless the LMAnnounce option has been enabled by

configuring the Server service with the Control Panel/Networks

application. This means that LAN Manager systems will not see these

computers unless this option is enabled.

A LAN Manager server within the Windows NT domain will be seen by the

Browser and therefore other systems on the network. A LAN Manager

domain that doesn't contain any Windows NT computers will not appear

on the browse lists unless it is specified as an Other Domain through

the Control Panel/Networks application in the Computer Browser

configuration.

DOMAIN(1D)

This name is registered by Master Browsers. It is used by clients to

find a Master Browser server. A client will broadcast to this name to

get a list of browser servers from the Master Browser. The Master

Browser will send a list of browser servers to the client from which

the client will cache three of these server names. The client will

then randomly pick one of these servers to request a list of servers

and domains from.

DOMAIN(1B)

This name is registered by the primary domain controller in a domain

only and allows unique identification of that computer.

DOMAIN(1E)

This name is registered by all Browser servers and Potential Browser

servers in a domain or workgroup. It is used for announcement requests

which are sent by Master Browsers to fill up its browse lists, and for

election request packets to force an election. Elections are performed

by sending a packet out to this name that contains your election

criteria.

The election criteria for a Browser is based on the Browser's current

role in the domain and its current state, using the following

hierarchy:

   Operating System Type:        0xFF000000

   Windows for Workgroups:       0x00000000

   Windows NT:                   0x01000000

   Windows NT Advanced Server:   0x02000000

   Election Version:             0x00FFFF00

   Per version criteria:         0x000000FF

   PDC:                          0x00000080

   Preferred Master:             0x00000008

   Running Master:               0x00000004

   MaintainServerList = Yes:     0x00000002

   Running Backup Browser:       0x00000001

The Browser will OR all of the appropriate election criteria and use

this to determine the system's election criteria.

The criteria for determining if a Browser has won an election is the

following:

 - If your election version is greater than the sender's election

   version, you win.

 - Else if your election criteria is greater than the sender's

   criteria, you win.

 - Else if you have been up longer than the sender, you win.

 - If the above comparisons fail to determine a Master Browser, the

   computer with the lexically lowest name will win the election.

If a Browser receives an election request, it compares the criteria to

its own and if it wins it will send out up to four election packets.

If after this time it does not receive an election packet with a

better criteria, it will become the Master Browser. Elections can be

caused by any computer that cannot locate a Master Browser, or by a

Potential Browser during initialization. An election is also

instigated by a Master Browser when it shuts down gracefully.

Mail Slots

----------

Server and Domain Names in the browse list are aged and are removed

from the browse list if they have not been heard from in three

Announce periods.

The Browser uses Mailslot Transactions to pass these messages between

systems. Two Mailslots are used.

For messages intended for all systems including LAN Manager and

Windows for Workgroups, MAILSLOT\LANMAN is used.

MAILSLOT\BROWSE is used for messages intended for Windows NT and

Windows NT Advanced Server systems.

Additional reference words: prodnt 3.10 WFW browsemaster

KBCategory: kbnetwork kbfasttip

KBSubCategory: ntnetserv


Migrating Windows 3.1 Groups After Installation

Article ID: Q102884

------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Operating System Version 3.1

 - Microsoft Windows NT Advanced Server Version 3.1

------------------------------------------------------------------

When a user is logging on to Windows NT for the first time after

setting up Windows NT over an existing version of Windows 3.1 or

Windows for Workgroups, and if the user has not chosen to migrate

their WIN.INI, CONTROL.INI, and program groups, you can still perform

this migration by using REGEDT32.EXE. You can do this by doing the

following:

WARNING: Using Registry Editor incorrectly can cause serious, system-

wide problems that may require you to reinstall Windows NT to correct

them. Microsoft cannot guarantee that any problems resulting from the

use of Registry Editor can be solved. Use this tool at your own risk.

1. If Windows NT is installed in a directory other than the directory

   containing the Windows or Windows for Workgroups files, copy all of

   the initialization files (*.INI) from the Windows directory to the

   Windows NT directory (\WINNT).

2. Log on as the user you want to modify.

3. Run REGEDT32.EXE (located in the systent32ap subdirectory).

4. Choose the window titled "HKEY_CURRENT_USER on local machine."

5. Choose and highlight the subkey called WINDOWS 3.1 MIGRATION STATUS.

6. Press the DELETE key to remove that subkey and those below it,

   answering Yes when prompted.

7. Quit REGEDT32 by clicking Registry and then Exit from the menu.

8. Quit Windows NT by pressing CTRL+ALT+DELETE and choosing Logoff.

9. Logon again as the user and choose OK to migrate.

Additional reference words: prodnt 3.10 setup groups

KBCategory: kbfasttip kbsetup  kbfasttip

KBSubCategory: ntsetup  ntgeneral


How To Install the Sony CDU-31A CD-ROM with Windows NT

Article ID: Q102906

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

----------------------------------------------------------------------

The Sony CDU-31A CD-ROM is not by default available for setup or for

use with Windows NT. However, there is a driver and setup information

for this CD-ROM on the Windows NT CD-ROM.

NOTE: Most Gateway 2000 computers that ship with the Sony CDU-31A

CD-ROM drive come with the Sony COR-334 host adapter. This host

adapter is an OEM version of the Sony CDB-334 and is identical to this

card in all respects. There is more information in the Microsoft

Knowledge Base on Sony CD-ROM drives and Gateway 2000 computers

available in article Q104764.

The factory defaults for the Sony COR-334 and CDB-334 are: I/O base

port address set to 340 hex, DMA channel set to none, and IRQ set to

none. No IRQ setting is neccessary for the card to operate correctly

under MS-DOS, and therefore most COR-334 and CDB-334 adapters are not

configured for an IRQ. However, Windows NT requires the use of an IRQ.

Use the instructions in the README.TXT file to configure the adapter

for use with Windows NT. Installation instructions are in the

following directory:

   \drvlib\storage\sony_31a\x86 (or MIPS)

It is necessary to view the README.TXT from MS-DOS. The directory

includes the following files:

   OEMSETUP.INF

   README.TXT

   SLCD32.SYS

   TXTSETUP.OEM

Jumper settings for the Sony COR-334 and CDB-332 host adapter are

as follows:

   Jumper Row   Function

   -------------------------

   JP1           Base Address

   JP2          DMA Channel

   JP3          DMA Channel

   JP4          IRQ Channel

Base Address Jumper Pin Settings

--------------------------------

On indicates the presence of a jumper switch on the pin. Jumper pins

are read from left to right. JP1.1 refers to jumper row 1 pin 1.

   Base Address   JP1.1   JP1.2   JP1.3   JP1.4

   --------------------------------------------

   320            on      on      off     off

   330            on      off     off     off

   340*           off     on      off     off

   360            off     off     off     off

   (*default setting)

Interrupt Jumper Settings

-------------------------

IRQ    JP4.1   JP4.2   JP4.3   JP4.4

------------------------------------

3      off     off     on      off

4      off     on      off     on

5      on      off     off     off

6      off     on      off     off

MORE INFORMATION

================

For reference, the contents of the README.TXT file with installation

instructions follow:

README.TXT

----------

   Sony CDU-31A device driver for the Windows NT(tm) operating system

The device drivers and this file are owned by Sony and protected by

United States copyright laws, international treaty provisions, and all

other applicable national laws. You may not reverse engineer,

decompile, or disassemble the device drivers.

Copy all files from this directory to the root directory of a floppy

disk and mark it 'Sony - CDU-31A setup disk'.

Installing from a CDU-31A - x86 processor

-----------------------------------------

To install Windows NT from a CDU-31A drive with no other supported

SCSI host adapter installed, boot the computer from the Boot floppy

provided with the operating system. After you hit ENTER to indicate

'install now' and then choose either Express or Custom install, the

installation software searches for a supported host adapter and CD-ROM

drive. It displays 'Scanning for SCSI adapters' in the bottom of the

screen. The device drivers used during this phase of installation are

expected to be on the Windows NT CD-ROM disc, which these currently

are not. When the scan is complete, the install program asks if you

want to 'Configure Additional SCSI adapters', hit 'S' to select this.

It then displays a list of adapters with the last line highlighted

reading: 'Other (Requires disk provided by a hardware manufacturer)'.

This is the setup floppy created above. Hit Enter to select other, the

program prompts to insert the floppy, do so and hit Enter again. The

install program then reads the slcd32.sys device driver from the

floppy, installs it, finds the CDU-31A drive and uses it to install

the operating system.

The install program also makes all of the necessary registry entries

automatically.

For this to work the CDU-31A host adapter MUST be set for IRQ 5. NOTE,

THIS IS A CHANGE FROM THE PREVIOUS BETA. PREVIOUSLY THE DRIVER USED

IRQ 3. If the host adapter jumpers are later changed the registry must

be manually edited using REGEDT32.

Adding support for CDU-31A to a pre-existing NT system

------------------------------------------------------

Within Windows NT under the window 'main', 'Windows NT Setup' select

'Options', then 'Add/Remove SCSI Adapters'. Then click on the 'Add'

button. In the window 'Select SCSI Adapter Option', scroll the

'Adapter' selection down to 'Other (Requires a disk from a hardware

manufacturer)'. Click on this option and when prompted insert the

floppy with the Sony files. The system copies the device driver from

the floppy and makes all the necessary registry entries automatically.

These entries assume an IRQ of 5. If the host adapter jumpers are

later changed or if you are using an IRQ other than 5, the registry

must be manually edited using REGEDT32.

31A Unique registry entry data

------------------------------

In addition to the normal mini-port stuff, the registry entry allows

specifying a base port address for the host adapter and which IRQ it's

set for. If the base port address is specified, then the driver does

not do its search for a host adapter and drives.

Specifically, under the entry for Slcd32 add a key for 'Parameters',

and under this add the key 'Device0'. This is for the first host

adapter. Under this add a value named 'DriverParameter' of type

REG_SZ. This is a string where you can specify the parameters. Entries

are of the form: 'name = value' where allowable names are: 'base' and

'irq'. Upper or lowercase is not important and all values are hex.

Entries are separated by spaces. For example to specify the defaults

of the adapter jumpers and driver use the value:

   base = 340 irq = 5

The driver defaults to irq 5 and will search for a host adapter and

drives if no entry is made. The hex port addresses searched are:

   340, 230, 330, 350, 360, 250, and 348

The base address and irq must match the host adapter jumper settings.

Note that the Sony host adapter model CDB-334 currently does NOT come

shipped with an irq selected since interrupts are not used with the

MS-DOS device driver.

For installation, my registry entry is:

HKEY_LOCAL_MACHINE

   SYSTEM

      CurrentControlSet

         Services

            Slcd32   -> Type: REG_DWORD: 0x1

                        Start: REG_DWORD: 0x1

                        Group: REG_SZ: SCSI miniport

                        ErrorControl: REG_DWORD: 0x1

               Parameters

                  Device0 -> DriverParameter: REG_SZ: base = 340 irq = 5

Jumper settings for the Sony CDB-334 host adapter.

Base Address jumpers

--------------------

   Address   Jp1.1   Jp1.2

     360      off     off

     340      off     on

     350      on      off

     320      on      on

IRQ jumper settings

-------------------

  Interrupt  JP4.3   JP4.4   JP4.1   JP4.2

      3       on      off     off     off

      4       off     on      off     off

      5       off     off     on      off

      6       off     off     off     on

SONY DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING

WITHOUT LIMITATION, WARRANTIES OF FITNESS AND MERCHANTABILITY WITH

RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS

DOCUMENT, SONY GRANTS NO LICENSES TO ANY RELATED PATENTS OR

COPYRIGHTS.

   Copyright Sony Corporation, 1993, all rights reserved

---------------------------------------------------------------------

   Sony CDU-31A device driver for the Windows NT(tm) operating system

The CDU-31A CD-ROM is manufactured by Sony, a vendor independent of

Microsoft; we make no warranty, implied or otherwise, regarding this

products' performance or reliability.

Additional reference words: prodnt 3.10 cdu 33A

KBCategory: kbhw kbfasttip

KBSubCategory: nthw


How to Troubleshoot TCP/IP Connectivity with Windows NT

Article ID: Q102908

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

----------------------------------------------------------------------

SUMMARY

=======

The ARP, PING, FTP, NETSTAT, and NBTSTAT utilities can provide useful

information when you are trying to determine the cause of TCP/IP

networking problems with Windows NT. Below is a list of possible

TCP/IP symptoms with recommendations for using these utilities to

diagnose the problems. Although this is not a complete list, these are

examples of how you might use these utilities to track down problems

on the network.

MORE INFORMATION

================

Q: How can I determine whether TCP/IP is installed correctly on a

   Windows NT system?

A: Trying using PING on the local system by typing the IP loopback

   address of 127.0.0.1 at the command line:

      ping 127.0.0.1

   The system should respond immediately. If PING is not found, or the

   command fails, check the event log with Event Viewer and look for

   problems reported by Setup or the TCP/IP service. You should also

   attempt to use PING with the IP addresses of your local

   interface(s) to determine whether you configured IP properly.

   Successful use of PING indicates that the IP layer on the target

   system is probably functional.

Q: How can I determine if the FTP Server service is installed

   correctly on a Windows NT system?

A: Try using FTP on the local system by typing the IP loopback

   address at the command line:

      ftp 127.0.0.1

   The interaction with the server locally is identical to the

   interaction expected for other Windows NT (and most UNIX) clients.

   This command can also be used to determine whether the directories,

   permissions, and so on of the FTP Server service are configured

   properly.

Q: What causes Error 53 when I'm connecting to a Windows NT, Windows

   for Workgroups, or Microsoft LAN Manager server?

A: Error 53 is returned when the specified computername cannot be

   resolved. If the computer is on the local subnet, confirm that the

   name is spelled correctly and that the target system is running

   TCP/IP as well. If the computer is not on the local subnet, make

   sure that its name and IP address mapping are available in the

   LMHOSTS file. If everything appears to be installed properly, try

   using PING with the remote system to make sure that its TCP/IP

   software is functional.

Q: After I've added a new mapping to the LMHOSTS file, what can I do

   if it takes an unusually long time to connect to the server?

A: A large LMHOSTS file with an entry at the end of the file, possibly

   following some #INCLUDEs, could cause this behavior. You can do two

   things to speed up the connect time: either mark the entry as a

   preloaded entry by following the mapping with the #PRE tag and use

   the NBTSTAT -R command to update the local name cache immediately,

   or place the mapping higher in the LMHOSTS file.

   The LMHOSTS file is parsed sequentially to locate non #PREloaded

   entries. Therefore, you should place frequently used entries near

   the top of the file and the #PRE entries near the bottom.

Q: What should I do if users are having difficulty connecting to a

   particular server, even when specifying the same name?

A: Use the NBTSTAT -N command to determine (authoritatively) what name

   the server registered on the network. The output of this command

   lists several names that the system has registered using NetBIOS

   over TCP/IP. One resembling the system's computername should be

   present. If not, try one of the other unique names displayed. The

   NBTSTAT command can also display the cached entries for remote

   systems either #PREloaded from LMHOSTS or recently resolved names

   due to current network activity. If the name the remote users are

   using is the same, and the other systems are on a remote subnet,

   make sure that they have the system's mapping in their LMHOSTS

   file.

Q: What should I do when I cannot connect to foreign systems with

   hostnames using TELNET, FTP, and so on, but can only connect using

   IP addresses?

A: Using the Network icon in Control Panel, check the hostname

   resolution configuration (found under the TCP/IP Connectivity

   option) to be sure that the appropriate HOSTS and DNS setup has

   been configured for the system. If you are using the HOSTS file,

   make sure the remote system is spelled the same way in the file as

   it is being used by the application. If you are using DNS, make

   sure the IP addresses of the DNS servers are correct and in the

   proper order. To determine whether the hostname is being resolved

   properly, try using PING with the remote system by typing both the

   hostname and IP address.

Q: The banner displayed when I'm using TELNET with a particular

   computer identifies a computer other than the one that I intended

   to connect to, even when I'm specifying the correct IP address.

   How can this be?

A: Situations like this usually arise when two systems on the same

   network are configured (mistakenly) with the same IP address. The

   Ethernet and IP address mapping is done by the address resolution

   protocol (ARP) module, which believes the first response it

   receives. So the impostor computer's reply sometimes comes back

   before the intended computer's reply. These problems are difficult

   to isolate and track down. The command ARP -g displays the mappings

   in the ARP cache. If you know the Ethernet address for the intended

   remote system, you can easily determine if the two match. If not,

   try using ARP D to delete the entry, then PING the same address

   (forcing a new ARP mapping) and check the Ethernet address in the

   cache again using ARP -g. Chances are that if both systems are on

   the same network, you will eventually get a different response. If

   not, you may need to filter the traffic from the impostor host to

   determine the owner or location of the system.

Q: What should I do when a TCP/IP connection to a remote system

   appears to be hung?

A: The NETSTAT -a command shows the status of all activity on TCP and

   UDP ports on the local system. The state of a good TCP connection

   is usually established with 0 bytes in the send and receive queues.

   If data is blocked in either queue or if the state is irregular,

   there is probably a problem with the connection. If not, you are

   probably experiencing network or application delay.

Q: What should I do when the TCP/IP configuration dialog box reports:

   "Your default gateway does not belong to one of the configured

   interfaces. Do you want to change it?"

A: This error indicates that the default gateway is not located on the

   same logical network as any of the installed interface(s) on the

   system. This is determined by comparing the net ID portion of the

   default gateway (by computing a bitwise AND operation between the

   subnet mask and the default gateway) and the net ID(s) of any of

   the installed interfaces. For example, a system with a single

   interface configured with an IP address of 102.54.0.1 and a subnet

   mask of 255.255.0.0 would require that the default gateway be of

   the form 102.54.a.b because the net ID portion of the IP interface

   is 102.54.

Additional reference words: prodnt 3.10 tshoot

KBCategory: kbfasttip kbnetwork

KBSubCategory: nttcp


Network Access Validation with Windows for Workgroups

Article ID: Q103028

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Advanced Server version 3.1

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows for Workgroups version 3.1

--------------------------------------------------------------------

SUMMARY

=======

Windows for Workgroups 3.1 does not provide domain information when it

issues network commands. The following is an example of how Windows NT

Advanced Server treats Windows for Workgroups 3.1 clients in this

situation.

Example

-------

I am logged on to my Windows NT workstation and a Windows for

Workgroups 3.1 system with the same account and password. The account

and password match the one in SCRATCH-DOMAIN (the Advanced Server

domain). I can successfully NET USE a share on \\NET (Advanced Server

that is a trusted domain of SCRATCH-DOMAIN) from my Windows for

Workgroups 3.1 system but the same command fails under Windows NT. The

Windows NT client receives the error message "System error 1326 has

occurred. Logon failure: unknown user name or bad password."

Configurations

--------------

Windows for Workgroups 3.1 workstation:

 - Login account: USER1

 - Password:      PSW1

 - Login Domain:  N/A

Windows NT workstation:

 - Login account: USER1

 - Password:      PSW1

 - Login Domain:  LOCAL1. Not logged on to Advanced Server domain.

Advanced Server for Windows NT:

 - Server Name: NET

 - Advanced Server Domain: NET-DOMAIN

 - Trust:  NET-DOMAIN Trust SCRATCH-DOMAIN (Therefore, accounts on

   SCRATCH-DOMAIN can be granted permissions in the NET-DOMAIN.)

 - Domain Account Database for NET-DOMAIN does NOT contain an

   account for USER1.

 - Guest Account is DISABLED.

Advanced Server for Windows NT:

 - Server Name:                       SCRATCH

 - Advanced Server Domain:            SCRATCH-DOMAIN

 - Domain Database contains account:  USER1

 - Domain Database contains password: PSW1

In this example, the Windows NT workstation is logged on to its local

workstation domain--not the domain of the Advanced Server. The Windows

for Workgroups 3.1 system is not logged on to any domain.

We should first cover some important technical background information.

When two Microsoft network systems communicate over a network, they

use a high-level protocol called server message block (SMB). These

commands are embedded in the transport protocols like NetBEUI or

TCP/IP. When a client executes a NET USE command, it sends out an SMB

Session Setup frame.

In Windows NT, the Session Setup SMB (0x73) includes the user account,

encrypted password, and login domain. An Advanced Server will look at

all of this information to determine if the client has permissions to

complete the NET USE command. Windows for Workgroups 3.1 includes only

account and password information--no domain name.

The Windows for Workgroups 3.1 client does the following:

 - Windows for Workgroups 3.1 client carries out the

   NET USE X: \\NET\share command.

 - A Windows for Workgroups 3.1 client includes only the user account

   "USER1" and encrypted password "PSW1." It does not include any domain

   information.

 - \\NET looks at the domain name in the SMB and realizes that it is

   NULL or does not exist.

 - The Advanced Server then attempts to validate the account information

   on its own SAM (Security Account Manager) domain database, NET-DOMAIN.

   This is done just like the client had specified the domain name of the

   Advanced Server.

 - \\NET fails to find a matching account "USER1" in its domain account

   database because it does not exist.

 - It then systematically and simultaneously checks all domains that it

   trusts until one responds.

 - SCRATCH-DOMAIN is selected because NET-DOMAIN trusts it.

 - \\SCRATCH is a Domain Controller and looks in the Domain database and

   finds an account "USER1" that matches the SMB account "USER1."

 - \\NET asks \\SCRATCH to perform pass-through authentication of the user

   account.

 - The SMB account "USER1" and password "PSW1" are now compared to the

   SAM Domain on the trusted server \\SCRATCH.

 - The passwords match so the "Command Completes Successfully" message

   is generated.

The Windows NT client does the following:

 - Windows NT client carries out the NET USE X: \\NET\share command.

 - The Windows NT client is logged on to the local workstation domain.

 - It did not log on to the Advanced Server's domain.

 - Therefore, when the NET USE command was carried out, the Session Setup

   SMB information that was sent out was account = "USER1", password =

   "PSW1" and domain = "LOCAL1."

 - \\NET receives the request and looks at the Domain name.

 - It does not recognize the domain name as its own or one that it

   trusts.

 - It does NOT check any of the domains that it trusts.

 - The Advanced Server \\NET then looks at the SMB Account name

   "USER1".

 - \\NET looks in the SAM Domain Database for "USER1" and it does not

   find a match.

 - \\NET now checks the Guest account because the user is unknown.

 - The Guest account is DISABLED in this case on \\NET.

 - Windows NT client receives the error message "System error 1326 has

   occurred. Logon failure: unknown user name or bad password."

The real answer here is to have all workstations, both Windows NT and

Windows for Workgroups 3.1, log on to an Advanced Server domain. In

order to login, the user must specify their correct domain, account

and password. After this is done, all NET USE type commands will pass

the correct domain password. To do this in Windows for Workgroups 3.1,

you must specify a MS LAN Manager login in the Network Control Panel

application.

MORE INFORMATION

================

Both Windows NT and MS LAN Manager clients do provide domain

information. This problem only exist on Windows for Workgroups 3.1

clients.

Windows NT Workaround

---------------------

There is one workaround that can be used in these cases. From the

Windows NT workstation, carry out the following command

   NET USE X: \\NET\SHARE /USER:SCRATCH-DOMAIN\USER1 PSW1

where:

    - \\NET = The computer name of the Advanced Server being accessed.

    - \SHARE = The share name.

    - /USER: command line parameter that lets you specify the domain,

      account and password that should be specified in the Session Setup

      SMB.

    - SCRATCH-DOMAIN = Domain name of the Advanced Server where the user

      account resides.

    - \USER1 = Account to be validated against.

    - PSW1 = Password that matches account on the domain.

At a Windows NT command prompt, type the following for more

information:

   NET USE /?

For information on trust relationships, user permissions, and domain

logins, please see your Windows NT Advanced Server "Concepts and

Planning" guide. For additional information, query on the following

words in the Microsoft Knowledge Base:

   algorithm and access and validation

   -or-

   authentication and pass-through

Additional reference words: prodnt 3.10

KBCategory: kbnetwork kbfasttip

KBSubCategory: ntnetserv


How to Remove Windows NT Boot Sector

Article ID: Q103049

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system, version 3.1

 - Microsoft Windows NT Advanced Server, version 3.1

----------------------------------------------------------------------

This article details procedures that enable you to remove Windows NT

boot sector from your system. Before you begin, make sure you know

where Windows NT is installed, how much of it you want to remove, and

how your hard disk drive is partitioned and formatted. Then, go to one

of the following sections:

 - Removing Windows NT from the Boot Sequence

 - Removing a Primary NTFS Partition

Removing Windows NT from the Boot Sequence

------------------------------------------

There are two ways to remove the Windows NT boot sector from your

machine:

 - If you want to return to your original MS-DOS configuration, boot

   MS-DOS and type "sys c:" (without the quotation marks). This

   command replaces the Windows NT boot sector with the MS-DOS boot

   sector, and allows your machine to boot straight into MS-DOS. The

   following files are left in the root directory and can be deleted

   after you perform the SYS operation:

      PAGEFILE.SYS

      BOOT.INI

      NTLDR

      NTDETECT.COM

      NTBOOTDD.SYS

   NOTE: NTBOOTDD.SYS is installed only if you have a SCSI Host

   Adapter installed in Windows NT.

 - If you want to leave NTLDR on the disk, you can boot MS-DOS without

   prompting by changing the startup operating system and time-out

   value. To do so, choose the System icon in the Control Panel,

   select MS-DOS in the Startup box, and type "0" (without the

   quotation marks) in the Show List For box.

   NOTE: If the primary partition was converted to NTFS, the only way

   to return to starting MS-DOS only is to reformat the drive and

   reinstall MS-DOS. See the next section if this is the case.

Removing a Primary NTFS Partition

---------------------------------

In general, attempts to modify the primary, bootable, NTFS partition

fail for the following reasons:

 - MS-DOS versions 5.0 and 6.0 do not recognize an NTFS partition. The

   MS-DOS Fdisk program reports an NTFS partition as an OS/2

   high-performance file system (HPFS) partition.

 - You cannot modify or delete an NTFS primary partition within

   itself.

To delete or modify a primary NTFS partition, perform any one of the

following four procedures:

 - Boot MS-DOS version 6.0 from a floppy disk and press RETURN to

   continue installing MS-DOS 6. When prompted to do so, choose

   "Remove files".

 - Initiate Windows NT installation from floppy disks or CD-ROM.

   When prompted to do so, choose "P" to remove the partition.

 - Use the DELPART utility to delete the NTFS partition. DELPART is

   provided in the Microsoft Windows NT Resource Kit. Note that

   DELPART cannot delete a logical drive in the extended partition.

 - Boot OS/2 version 1.x from a floppy disk and run its Fdisk program.

   To remove the partition, specify the /D option.

Additional reference words: prodnt 3.10 uninstall

KBCategory: kbsetup kbfasttip

KBSubCategory: ntsetup  ntgeneral


Descriptions of Bug Codes for Windows NT

Article ID: Q103059

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system, version 3.1

 - Microsoft Windows NT Advanced Server, version 3.1

----------------------------------------------------------------------

Below is a list of bug codes, listed in order of bug code number. Some

codes include parameter definitions and explanations.

Bug codes with no descriptions are usually from checked builds of

Windows NT. If you get one of these, run the kernel debugger and enter

the following commands:

   kb

   !process 0 7

   !vm

   !errlog

NOTE: BUGCODES.H and EXLEVELS.H are both in the Windows NT DDK.

BUG CODES

=========

APC_INDEX_MISMATCH               (0x1)

This is a kernel internal error. This error could be caused by a

mismatch between KeEnterCricticalRegion and KeLeaveCriticalRegion in a

file system.

DEVICE_QUEUE_NOT_BUSY            (0x2)

INVALID_AFFINITY_SET             (0x3)

INVALID_DATA_ACCESS_TRAP         (0x4)

INVALID_PROCESS_ATTACH_ATTEMPT   (0x5)

INVALID_PROCESS_DETACH_ATTEMPT   (0x6)

INVALID_SOFTWARE_INTERRUPT       (0x7)

IRQL_NOT_DISPATCH_LEVEL          (0x8)

IRQL_NOT_GREATER_OR_EQUAL        (0x9)

IRQL_NOT_LESS_OR_EQUAL           (0xA)

An attempt was made to touch pageable memory at a process internal

request level (IRQL) that is too high. This error is usually caused by

drivers using improper addresses. If the kernel debugger is available,

get a stack back trace.

Parameters

----------

   1 - Memory referenced

   2 - IRQL

   3 - Value: 0 = read operation, 1 = write operation

   4 - Address that referenced memory

NO_EXCEPTION_HANDLING_SUPPORT    (0xB)

MAXIMUM_WAIT_OBJECTS_EXCEEDED    (0xC)

MUTEX_LEVEL_NUMBER_VIOLATION     (0xD)

Try to identify the mutexes using the NTOS\EX\EXLEVELS.H header file.

You should be able to pinpoint the mutexes that are getting acquired

in an incorrect sequence.

Parameters

----------

   1 - Current thread's mutex level

   2 - Mutex level attempting to acquire

NO_USER_MODE_CONTEXT             (0xE)

SPIN_LOCK_ALREADY_OWNED          (0xF)

SPIN_LOCK_NOT_OWNED              (0x10)

THREAD_NOT_MUTEX_OWNER           (0x11)

TRAP_CAUSE_UNKNOWN               (0x12)

EMPTY_THREAD_REAPER_LIST         (0x13)

CREATE_DELETE_LOCK_NOT_LOCKED    (0x14)

LAST_CHANCE_CALLED_FROM_KMODE    (0x15)

CID_HANDLE_CREATION              (0x16)

CID_HANDLE_DELETION              (0x17)

REFERENCE_BY_POINTER             (0x18)

BAD_POOL_HEADER                  (0x19)

MEMORY_MANAGEMENT                (0x1A)

PFN_SHARE_COUNT                  (0x1B)

PFN_REFERENCE_COUNT              (0x1C)

NO_SPIN_LOCK_AVAILABLE           (0x1D)

KMODE_EXCEPTION_NOT_HANDLED      (0x1E)

This is a very common bug code. Usually the exception address

pinpoints the driver or function that caused the problem. Always note

this address as well as the link date of the driver or image that

contains this address. A common error is exception code 0x80000003.

This error means a hard-coded breakpoint or assertion was hit, but the

system was booted with the /NODEBUG switch. This problem should not

occur very often. If it occurs repeatedly, make sure a debugger is

connected and the system is booted with the /DEBUG switch.

On non-Intel systems, if the address of the exception is 0XBFC0304,

the bug code is the result of a cache-parity error on the CPU. If the

problem reoccurs frequently, contact the hardware manufacturer.

Parameters

----------

   1 - The exception code that was not handled

   2 - The address that the exception occurred at

   3 - Parameter 0 of the exception

   4 - Parameter 1 of the exception

SHARED_RESOURCE_CONV_ERROR       (0x1F)

KERNEL_APC_PENDING_DURING_EXIT   (0x20)

The key data item is the thread's APC disable count. If the count is

nonzero, it is the source of the problem. A negative value indicates

that a file system has called FsRtlEnterFileSystem more times than

FsRtlExitFileSystem. A positive value indicates that the reverse is

true. If you see this situation, check all file systems installed on

the machine. Third-party redirectors are especially suspect since they

do not receive the heavy-duty testing that NTFS, FAT, HPFS, and RDR

receive.

The current IRQL should also be 0. If it is not, then a driver's

cancellation routine can cause this bug code by returning at an

elevated IRQL. Always attempt to note what you were doing or closing

and note all the installed drivers at the time of the bug code. This

symptom is usually caused by a severe bug in a third-party driver.

Parameters

----------

   1 - The address of the APC found pending during exit

   2 - The thread's APC disable count

   3 - The current IRQL

QUOTA_UNDERFLOW                  (0x21)

FILE_SYSTEM                      (0x22)

FAT_FILE_SYSTEM                  (0x23)

NTFS_FILE_SYSTEM                 (0x24)

NPFS_FILE_SYSTEM                 (0x25)

CDFS_FILE_SYSTEM                 (0x26)

RDR_FILE_SYSTEM                  (0x27)

CORRUPT_ACCESS_TOKEN             (0x28)

SECURITY_SYSTEM                  (0x29)

INCONSISTENT_IRP                 (0x2A)

An IRP was encountered that was in an inconsistent state; that is,

some field or fields of the IRP were inconsistent with the remaining

state of the IRP--for example, an IRP that was being completed, but

was still marked as being queued for a driver's device queue. This bug

code is not currently being used in the system, but exists for

debugging purposes.

Parameter

---------

   1 - Address of the IRP that was found to be inconsistent

PANIC_STACK_SWITCH               (0x2B)

This error indicates that the kernel mode stack was overrun. This

error normally occurs when a kernel mode driver uses too much stack

space. It can also occur when serious data corruption occurs in the

kernel.

PORT_DRIVER_INTERNAL             (0x2C)

SCSI_DISK_DRIVER_INTERNAL        (0x2D)

DATA_BUS_ERROR                   (0x2E)

This bug code is normally caused by a parity error in the system

memory. This error can also be caused by a driver accessing a

0x8XXXXXXX address that does not exist.

Parameters

----------

   1 - Virtual address that caused the fault

   2 - Physical address that caused the fault

   3 - Processor status register (PSR)

   4 - Faulting instruction register (FIR)

INSTRUCTION_BUS_ERROR            (0x2F)

SET_OF_INVALID_CONTEXT           (0x30)

PHASE0_INITIALIZATION_FAILED     (0x31)

System initialization failed early on. The kernel debugger is required

to make sense of this error, since this code tells you almost nothing.

PHASE1_INITIALIZATION_FAILED     (0x32)

Parameters

----------

   1 - Windows NT status code that describes why the system thinks

       initialization failed

   2 - Indicates location within INIT.C where phase 1 initialization

       failure occurred

UNEXPECTED_INITIALIZATION_CALL   (0x33)

CACHE_MANAGER                    (0x34)

NO_MORE_IRP_STACK_LOCATIONS      (0x35)

A higher level driver has attempted to call a lower level driver

through the IoCallDriver() interface, but there are no more stack

locations in the packet, so the lower level driver would not be able

to access its parameters, as there are no parameters for it. This is a

disastrous situation, since the higher level driver thinks it has

filled in the parameters for the lower level driver (something it MUST

do before it calls it); but, since there is no stack location for the

latter driver, the former has written off of the end of the packet.

This means that some other memory has probably been corrupted.

Parameter

---------

   1 - Address of the IRP

DEVICE_REFERENCE_COUNT_NOT_ZERO  (0x36)

A device driver has attempted to delete one of its device objects from

the system but the reference count for that object was nonzero,

meaning there were still outstanding references to the device. (The

reference count indicates the number of reasons why this device object

cannot be deleted.) This is a bug in the calling device driver.

Parameter

---------

   1 - Address of the device object

FLOPPY_INTERNAL_ERROR            (0x37)

SERIAL_DRIVER_INTERNAL           (0x38)

SYSTEM_EXIT_OWNED_MUTEX          (0x39)

SYSTEM_UNWIND_PREVIOUS_USER      (0x3A)

SYSTEM_SERVICE_EXCEPTION         (0x3B)

INTERRUPT_UNWIND_ATTEMPTED       (0x3C)

INTERRUPT_EXCEPTION_NOT_HANDLED  (0x3D)

MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED (0x3E)

The system has multiple processors, but they are asymmetric in

relation to one another. In order to be symmetric, all processors must

be of the same type and level. For example, trying to mix a

Pentium-level processor with an 80486 would cause this error.

Additionally, on x86 systems, floating-point capabilities must be

present on all or no processors.

NO_MORE_SYSTEM_PTES              (0x3F)

No System PTEs left. Usually caused by a driver not cleaning up

properly. If kernel debugger is available, get a stack trace and enter

the following command:

   !sysptes 3

TARGET_MDL_TOO_SMALL             (0x40)

A driver has called the IoBuildPartialMdl() function and passed it an

MDL to map part of a source MDL, but the target MDL is not large

enough to map the entire range of addresses requested. This is a

driver bug. The source and target MDLs, as well as the address range

length to be mapped, are the arguments to the IoBuildPartialMdl()

function:

   IoBuildPartialMdl( IN PMDL SourceMdl,

                      IN OUT PMDL TargetMdl,

                      IN PVOID VirtualAddress,

                      IN ULONG Length )

MUST_SUCCEED_POOL_EMPTY          (0x41)

If kernel debugger is available, the VM command lists various sizes.

Parameters

----------

   1 - Size of the request that could not be satisfied

   2 - Number of pages used of nonpaged pool

   3 - Number of too large PAGE_SIZE requests from nonpaged pool

   4 - Number of pages available

ATDISK_DRIVER_INTERNAL           (0x42)

NO_SUCH_PARTITION                (0x43)

MULTIPLE_IRP_COMPLETE_REQUESTS   (0x44)

A driver has requested that an IRP be completed [IoCompleteRequest()],

but the packet has already been completed. This is a tough bug to find

because the easiest case, a driver actually attempted to complete its

own packet twice, is generally not what happened. Rather, two separate

drivers each believe that they own the packet, and each attempts to

complete it. The first actually works, and the second fails. Tracking

down which drivers in the system actually did this is difficult,

because the tracks of the first driver have been covered by the

second. However, the driver stack for the current request can be found

by examining the DeviceObject fields in each of the stack locations.

Parameter

---------

   1 - Address of the IRP

INSUFFICIENT_SYSTEM_MAP_REGS     (0x45)

DEREF_UNKNOWN_LOGON_SESSION      (0x46)

REF_UNKNOWN_LOGON_SESSION        (0x47)

CANCEL_STATE_IN_COMPLETED_IRP    (0x48)

This error indicates that an I/O Request Packet (IRP) that is to be

canceled has a cancel routine specified in it, meaning the packet is

in a state in which the packet can be canceled. However, the packet no

longer belongs to a driver, as it has entered I/O completion. This is

either a driver bug, or more than one driver is accessing the same

packet, which is not likely and much more difficult to debug.

Parameter

---------

   1 - Pointer to the IRP

PAGE_FAULT_WITH_INTERRUPTS_OFF   (0x49)

This means exactly what it says. Treat it as a case of 0x0A above.

IRQL_GT_ZERO_AT_SYSTEM_SERVICE   (0x4A)

STREAMS_INTERNAL_ERROR           (0x4B)

FATAL_UNHANDLED_HARD_ERROR       (0x4C)

If a hard error occurs during system boot before Windows NT is up, and

it is a real error, the system will halt with a blue screen.

Some common cases are:

x218 - A necessary Registry hive file could not be loaded. The hive

       file may be corrupt or missing. The Emergency Repair disk may

       be required to recover from this.

       The driver may have corrupted the Registry data while loading

       into memory, or the memory where the Registry file was loaded

       is not actually memory. In particular, AST EISA machines with

       16 MB or more of memory must have access to the memory above 16

       MB that is ENABLED in the EISA configuration utility, or the

       Registry file is liable to get loaded in this spot, but will

       return just 0xffffffff when the memory is read.

x21A - Either Winlogon, or CSRSS (Windows) died unexpectedly. The exit

       code tells more information. Usually it is c0000005, meaning

       that an unhandled exception crashed either of these processes.

       There is not much you can do unless this becomes a persistent

       problem.

x221 - This means that a driver is corrupt, or a system DLL was

       detected to be corrupt. Windows NT does its best to check the

       integrity of drivers and important system DLLs. A blue screen

       is displayed with the name of the corrupt file. If this occurs,

       boot an alternate operating system, or reinstall if no

       alternate exists. Make sure the on-disk file that is listed as

       bad matches the version on CD and replace it if necessary. In

       some cases, random corruption can mean that there is a hardware

       problem in the I/O path to the file.

NO_PAGES_AVAILABLE               (0x4D)

No free pages available to continue operations. If the kernel debugger

is available, enter the following:

   !process 0 7

   !vm

   dd mmpagingfiles

   dd @$p

Parameters

----------

   1 - Number of dirty pages

   2 - Number of physical pages in machine

   3 - Extended commit value in pages

   4 - Total commit value in pages

PFN_LIST_CORRUPT                 (0x4E)

Caused by corrupting I/O driver structures. If the kernel debugger is

available, get a stack trace.

Parameters

----------

   1 - Value 1

   2 - ListHead value that was corrupt

   3 - Number of pages available

   4 - 0

   1 - Value 2

   2 - Entry in list being removed

   3 - Highest physical page number

   4 - Reference count of entry being removed

NDIS_INTERNAL_ERROR              (0x4F)

PAGE_FAULT_IN_NONPAGED_AREA      (0x50)

REGISTRY_ERROR                   (0x51)

Something has gone wrong with the Registry. If a kernel debugger is

available, get a stack trace. If the stack trace indicates you are in

a system worker thread (CmpWorker will be on the call list), enter the

following kernel debugger commands:

    dd CmpRegistryMutex+18 L1

    !thread <whatever value the above command printed out>

This will give you the thread and stack trace that made the Registry

call.

This error can also indicate that the Registry received an I/O error

while trying to read one of its files, so the error can be caused by

hardware problems or file system corruption. It can also occur because

of a failure in a refresh operation that is used only by the security

system, and then only when resource limits are encountered. When you

see this bug code, note if the machine is a PDC or BDC, and how many

accounts are in its security accounts manager (SAM) database, whether

it might be a replication target, and whether the volume where the

hive files reside is nearly full.

Parameters

----------

   1 - Value 1 (indicates where bug code occurred)

   2 - Value 2 (indicates where bug code occurred)

   3 - May be pointer to hive

   4 - May be return code of HvCheckHive if the hive is corrupt

MAILSLOT_FILE_SYSTEM             (0x52)

NO_BOOT_DEVICE                   (0x53)

LM_SERVER_INTERNAL_ERROR         (0x54)

DATA_COHERENCY_EXCEPTION         (0x55)

INSTRUCTION_COHERENCY_EXCEPTION  (0x56)

XNS_INTERNAL_ERROR               (0x57)

FTDISK_INTERNAL_ERROR            (0x58)

The system was booted from a revived primary partition, so the hives

say the mirror is alright, when in fact it is not. The real images of

the hives are on the shadow. You must boot from the shadow.

PINBALL_FILE_SYSTEM              (0x59)

CRITICAL_SERVICE_FAILED          (0x5A)

SET_ENV_VAR_FAILED               (0x5B)

HAL_INITIALIZATION_FAILED        (0x5C)

HEAP_INITIALIZATION_FAILED       (0x5D)

OBJECT_INITIALIZATION_FAILED     (0x5E)

SECURITY_INITIALIZATION_FAILED   (0x5F)

PROCESS_INITIALIZATION_FAILED    (0x60)

HAL1_INITIALIZATION_FAILED       (0x61)

OBJECT1_INITIALIZATION_FAILED    (0x62)

SECURITY1_INITIALIZATION_FAILED  (0x63)

SYMBOLIC_INITIALIZATION_FAILED   (0x64)

MEMORY1_INITIALIZATION_FAILED    (0x65)

CACHE_INITIALIZATION_FAILED      (0x66)

CONFIG_INITIALIZATION_FAILED     (0x67)

This means the Registry could not allocate the pool needed to contain

the Registry files. This error should never occur, since it is early

enough in system initialization that there is always plenty of the

paged pool available.

Parameters

----------

   1 - 5

   2 - Indicates location in NTOS\CONFIG\CMSYSINI that failed

FILE_INITIALIZATION_FAILED       (0x68)

IO1_INITIALIZATION_FAILED        (0x69)

Initialization of the I/O system failed for some reason. There is

practically no other information available. In general, this error

occurs because Setup made some incorrect decisions about the

installation of the system, or the user has reconfigured the system.

LPC_INITIALIZATION_FAILED        (0x6A)

PROCESS1_INITIALIZATION_FAILED   (0x6B)

Parameters

----------

   1 - Indicates the status code that made Windows NT think

       initialization failed

   2 - Indicates the location in NTOS\PS\PSINIT.C where the failure

       was detected

REFMON_INITIALIZATION_FAILED     (0x6C)

SESSION1_INITIALIZATION_FAILED   (0x6D)

SESSION2_INITIALIZATION_FAILED   (0x6E)

SESSION3_INITIALIZATION_FAILED   (0x6F)

SESSION4_INITIALIZATION_FAILED   (0x70)

SESSION5_INITIALIZATION_FAILED   (0x71)

These bug code codes (SESSION1 - SESSION5) indicate the location in

NTOS\INIT\INIT.C where the failure was detected.

Parameter

---------

   1 - Indicates the status code that made Windows NT think

       initialization failed

ASSIGN_DRIVE_LETTERS_FAILED      (0x72)

CONFIG_LIST_FAILED               (0x73)

Indicates that one of the core system hives is corrupt or unreadable.

This hive can be either SOFTWARE, SECURITY, or SAM.

Parameters

----------

   1 - 5

   2 - 2

   3 - Index of hive in list

   4 - Pointer to UNICODE_STRING containing filename of hive

BAD_SYSTEM_CONFIG_INFO           (0x74)

This error may indicate that the SYSTEM hive loaded by the

OSLOADER/NTLDR was corrupt. However, this is unlikely, since OSLOADER

checks a hive to make sure it is not corrupt after loading it.

This error may also indicate that some critical Registry keys and

values are not present. Booting from LastKnownGood may correct the

problem, but you may need to reinstall or use the Emergency Repair

Disk.

CANNOT_WRITE_CONFIGURATION       (0x75)

This error will occur if the SYSTEM hive files (SYSTEM and SYSTEM.ALT)

cannot be grown to accommodate additional data written into the hive

between Registry initialization and phase one initialization (when the

file systems are available). This error usually means there are 0

bytes of free space available on the drive, though it could be caused

by trying to store the Registry on a read-only device.

PROCESS_HAS_LOCKED_PAGES         (0x76)

This error is caused by a driver not cleaning up completely after an

I/O operation.

Parameters

----------

   1 - Process address

   2 - Number of locked pages

   3 - Number of private pages

   4 - 0

KERNEL_STACK_INPAGE_ERROR        (0x77)

The requested page of kernel data could not be read in. This error is

caused by a bad block in a paging file or a disk controller error (in

extremely rare cases, it is caused by running out of resources,

specifically, the nonpaged pool with a status of c0000009a

[STATUS_INSUFFICIENT_RESOURCES]).

If the first and second arguments are 0, the stack signature in the

kernel stack was not found. This error is caused by bad hardware.

An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or C000016AL

(STATUS_DISK_OPERATION_FAILED) normally indicates the data could not

be read from the disk due to a bad block. Upon reboot, Autocheck will

run and attempt to map out the bad sector. If the status is C0000185

(STATUS_IO_DEVICE_ERROR) and the paging file is on a SCSI disk device,

the cabling and termination should be checked.

Parameters

----------

   1 - 0

   2 - 0

   3 - PTE value at time of error

   4 - Address of signature on kernel stack

   1 - Status code

   2 - I/O status code

   3 - Page file number

   4 - Offset into page file

PHASE0_EXCEPTION                 (0x78)

MISMATCHED_HAL                   (0x79)

The HAL revision level and HAL configuration type do not match that of

the kernel or the machine type. This error is probably occurring

because the user has manually updated either NTOSKRNL.EXE or HAL.DLL.

Or, the machine has a multiprocessor (MP) HAL and a uniprocessor (UP)

kernel, or the reverse.

Parameters

----------

   1 - Type of mismatch (1, 2, or 3):

       1 - The PRCB release levels mismatch (something is out of

           date). If this is the case, parameters 2 and 3 are:

           2 - Major PRCB level of NTOSKRNL.EXE

           3 - Major PRCB level of HAL.DLL

   2 - The build types mismatch. If this is the case, parameters

       2 and 3 are:

           2 - Build type of NTOSKRNL.EXE

           3 - Build type of HAL.DLL

           Build Types

           -----------

              0 - Free multiprocessor-enabled build

              1 - Checked multiprocessor-enabled build

              2 - Free uniprocessor build

    3 - Micro Channel Architecture (MCA) computers require a

        MCA-specific HAL. If this is the case, parameters 2 and 3

        are:

           2 - Machine type as detected by NTDETECT.COM

               A value of a 2 would mean the computer is MCA.

           3 - Machine type that HAL supports

               A value of a 2 would mean the HAL is built for MCA.

KERNEL_DATA_INPAGE_ERROR         (0x7A)

The requested page of kernel data could not be read in. This error is

caused by a bad block in the paging file or a disk controller error.

See also KERNEL_STACK_INPAGE_ERROR.

Parameters

----------

   1 - Lock type that was held (value 1, 2, 3, or PTE address)

   2 - Error status (normally I/O status code)

   3 - Current process (virtual address for lock type 3, or PTE)

   4 - Virtual address that could not be in-paged

INACCESSIBLE_BOOT_DEVICE         (0x7B)

During the initialization of the I/O system, the driver for the boot

device may have failed to initialize the device that the system is

attempting to boot from, or the file system that is supposed to read

that device may have either failed its initialization or simply not

recognized the data on the boot device as a file system structure. In

the former case, the first argument is the address of a Unicode string

data structure that is the ARC name of the device from which the boot

was being attempted. In the latter case, the first argument is the

address of the device object that could not be mounted.

If this is the initial setup of the system, this error may have

occurred because the system was installed on an unsupported disk or

SCSI controller. Note that some controllers are supported only by

drivers that are in the Windows Driver Library (WDL), which requires

the user to do a custom installation.

This error can also be caused by the installation of a new SCSI

adapter or disk controller or by repartitioning the disk with the

system partition. If this is the case, on x86 systems, the BOOT.INI

file must be edited; on ARC systems, Setup must be run. For

information on changing BOOT.INI, see the Windows NT Advanced Server

"Administrator's Guide."

If the argument is a pointer to an ARC name string, the format of the

first two (and in this case only) long words will be:

   USHORT Length;

   USHORT MaximumLength;

   PVOID Buffer;

That is, the first long word will contain something like 00800020,

where 20 is the actual length of the Unicode string, and the next long

word will contain the address of buffer. This address will be in

system space, so the high-order bit will be set.

If the argument is a pointer to a device object, the format of the

first word will be:

   USHORT Type;

That is, the first word will contain a 0003, where the Type code will

always be 0003.

Note that this makes it immediately obvious whether the argument is a

pointer to an ARC name string or a device object, since a Unicode

string can never have an odd number of bytes, and a device object will

always have a Type code of 3.

Parameter

---------

   1 - Pointer to the device object or Unicode string of ARC name

BUGCODE_PSS_MESSAGE              (0x7C)

INSTALL_MORE_MEMORY              (0x7D)

Not enough memory to boot Windows NT (needs 5 MB).

Parameters

----------

   1 - Number of physical pages found

   2 - Lowest physical page

   3 - Highest physical page

   4 - 0

WINDOWS_NT_BANNER                (0x4000007E)

UNEXPECTED_KERNEL_MODE_TRAP      (0x7F)

This error means a trap occurred in kernel mode, either a kind of trap

that the kernel is not allowed to have or catch (a bound trap), or a

kind of trap that is always instant death (double fault). The first

number in the bug code parentheses is the number of the trap (8 =

double fault). To learn more about what these traps are, consult an

Intel x86 family manual.

From kernel debugger, a KB and !TRAP on the appropriate frame (which

will be the EBP that goes with a procedure named KiTrap--at least on

x86 machines) will show where the trap was taken.

NMI_HARDWARE_FAILURE             (0x80)

The HAL is supposed to report whatever specific data it has and to

tell the user to call his or her hardware vendor for support.

SPIN_LOCK_INIT_FAILURE           (0x81)

Additional reference words: prodnt 3.10 bugcode bugcheck

KBCategory: kbother kberrmsg kbfasttip

KBSubcategory: ntstop


Installing the Sound Blaster CD-ROM Driver for Windows NT

Article ID: Q103105

------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

------------------------------------------------------------------

SUMMARY

=======

The Windows NT CD includes a driver for the CD-ROM interface on the

Creative Labs Sound Blaster card. This driver is included only on the

CD (not on the floppy disks) and is located in the

DRVLIB\STORAGE\MKECR5XX\X86 directory. This driver also supports the

Panasonic CR-52x family of CD-ROM drives and the Panasonic CR-56x

family of CD-ROM drives.

MORE INFORMATION

================

The following information is contained in the README0.TXT file

included with the driver.

To install Windows NT on one of the aforementioned drives:

1. Copy all files from this directory to a blank formatted floppy disk

   in drive A.

2. Label this disk "PANASONIC SETUP."

3. Boot the computer with the bootable floppy disk included with

   Windows NT.

4. Press ENTER to install Windows NT.

5. Select Custom Setup. (Be sure to read your "Windows NT System

   Guide" for information on Custom Setup.)

6. After Windows NT scans for SCSI adapters, press "S" to add an

   adapter.

7. Select "Other (Requires Disk Provided by Hardware Manufacturer)."

8. Insert the disk labeled "PANASONIC SETUP" in drive A and press

   ENTER.

9. Follow the normal Custom Setup installation procedure.

NOTE: When installing the driver for this device, it is listed as

"Matsushita-Kotobuki Cr-52x/56x." Nowhere in the installation process

is the Sound Blaster card actually mentioned.

To add support for these drives to an existing Windows NT

installation:

 1. Copy all files from this directory to a blank formatted floppy disk

    in drive A.

 2. Label this disk "PANASONIC SETUP."

 3. Run the Windows NT SETUP application.

 4. Select Add/Remove SCSI Adapters from the Options menu.

 5. Choose the ADD button.

 6. Select the option "Other (Requires a Disk from a Hardware

    Manufacturer)."

 7. Insert the "PANASONIC SETUP" disk in drive A and press ENTER.

 8. Select the driver option provided (Matsushita-Kotobuki Cr-52x/56x)

    and press ENTER.

 9. Choose Install and then Continue.

10. Choose Close and exit Setup.

You need to restart Windows NT to activate the driver.

Additional reference words: prodnt 3.10 pro asp 16 proprietary Boot Floppy

KBCategory: kbhw kbfasttip

KBSubCategory: nthw


Network Access Validation Algorithm and Example

Article ID: Q103390

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Advanced Server version 3.1

--------------------------------------------------------------------

The following is a simplified algorithm that explains how Windows NT

Advanced Server account validation is observed to function during

network access. This discussion does not cover the internal workings

of this process. With this information, you can predict Windows NT

network logon behavior under deterministic conditions.

Background Information

----------------------

When two Microsoft network systems communicate over a network, they

use a high-level protocol called server message block (SMB). These

commands are embedded within the transport protocols like NetBEUI or

TCP/IP. When a client carries out a NET USE command, it sends out a

"SMB Session Setup and X" frame.

In Windows NT, the Session Setup SMB includes the user account, a

function of the encrypted password and login domain. An Advanced

Server will look at all of this information to determine if the client

has permissions to complete the NET USE command.

Algorithm

---------

Windows NT workstation sends the following command to an Advanced

Server:

   NET USE x: \\server\share

The Windows NT client sends a Session Setup SMB that contains its

    Login Domain, User Account and Password.

The Advanced Server checks the SMB specified Domain name

If  the domain is the Advanced Server's own Domain then

    It checks its own Domain SAM[Security Account Manager]database for

        a matching account.

    If  it finds a matching account then

        The SMB password is compared to the Domain Database password.

        If  the password matches then

            The Command Completed Successfully.

        If  the password does NOT match then

            User is prompted for a password.

                It is retested as above.

            System error 1326 has occurred.  Logon failure: unknown

            user name or bad password.

        End

    If  it does NOT find the account in the domain SAM database then

        Guest permissions are tested.

        If  the Guest account is Enabled

            The Command Completed Successfully.

        If  the Guest account is Disabled

            * See Note A.

            User is prompted for a password.

            System error 1326 has occurred.  Logon failure:

                unknown user name or bad password.

        End

If  the Domain specified in the SMB is one that the Advanced

        Server TRUSTS then

    The Advanced Server will do pass through authentication.  The

        network logon request will be sent to an Advanced Server in the

        specified Trusted Domain.

    The Trusted Domain Advanced Server checks its own Domain database

        for a matching account.

    If  it finds a matching account then

        It looks to see if the Account is a Local or Global Account.

        If  the Account is Local then

            Guest permissions on the Original Server are tested.

            If  the Guest account is Enabled

                The Command Completed Successfully.

            If  the Guest account is Disabled

                * See Note A.

                User is prompted for a password.

                System error 1326 has occurred.  Logon failure:

                unknown user name or bad password.

        End

        If  the Account is Global

            The SMB password is compared to the Domain Database

                password.

            If  the password matches then

                The Command Completed Successfully.

                * See Note B.

            If  the password does NOT match then

                User is prompted for a password.

                    It is retested as above.

                System error 1326 has occurred.  Logon failure:

                unknown user name or bad password.

        End

    If  it does NOT find the account in the Trusted domain

            database then

        Guest permissions are tested on the ORIGINAL Advanced

            Server -NOT the Trusted Advanced Server.  * See Note C.

        If  the Guest account is Enabled

            User will have original server guest access.

            The Command Completed Successfully.

        If  the Guest account is Disabled

            * See Note A.

            User is prompted for a password.

            System error 1326 has occurred.  Logon failure:

                unknown user name or bad password.

    End

If  the Domain specified in the SMB is UNKNOWN by the Advanced

        Server. [A Domain was specified but it was not

        recognized by the Server as a Trusted Domain or

        its own.]

    It  will check its own Domain Account Database for

        a matching account.  This is done just as if the user had

        specified the Advanced Servers domain instead of an unknown

        domain.

    If  the Advanced Server finds a matching account then

        The SMB password is compared to the Domain Database password.

        If  the password matches then

            The Command Completed Successfully.

        If  the password does NOT match then

            The User is prompted for a password.

                It is retested as above.

            System error 1326 has occurred.  Logon failure: unknown

            user name or bad password.

    End

    If  it does NOT find the account in the domain database then

        Guest permissions are tested.

        If  the Guest account is Enabled

            The Command Completed Successfully.

        If  the Guest account is Disabled

            System error 1326 has occurred.  Logon failure:

            unknown user name or bad password.

    End

If  the Domain specified in the SMB is NULL [None specified] then

    The Advanced Server will treat this a local network logon.  It

        will check for a matching account in its own SAM Database.

    If  it finds a matching account then

        The SMB password is compared to the SAM Database password.

        If  the password matches then

            The Command Completed Successfully.

        If  the password does NOT match then

            The User is prompted for a password.

                It is retested as above.

            System error 1326 has occurred.  Logon failure: unknown

            user name or bad password.

    End

    If  it does NOT find the account in the local SAM Database then

        The Advanced Server will Simultaneously ask another Advanced

            Server in each Domain that it Trusts if it has account that

            matches the SMB account.

        The first Trusted Advanced Server to reply is sent a request to

            perform pass through authentication of the client

            information.

        The Trusted Advanced Server will look in its own SAM Database.

        If  an account that matches the SMB account is found then

            It looks to see if the Account is a Local or Global

                Account.

            If  the Account is Local then

                Guest permissions on the original Server are tested.

                If  the Guest account is Enabled

                    The Command Completed Successfully.

                If  the Guest account is Disabled

                The user will be prompted for a password.

                No matter what password is entered, user will receive

                    "Error 5: Access has been denied."

            End

            If  the Account is Global

                The password specified in the SMB is compared

                    to the SAM Database password.

                If  the password matches then

                    The Command Completed Successfully.

                If  the password does NOT match then

                    The User is prompted for a password.

                        It is retested as above.

                    System error 1326 has occurred.  Logon failure:

                    unknown user name or bad password.

            End

    If  no Trusted Domains respond to request to identify the

        account then

        Guest permissions are tested on the Original Advanced Server -

            not the Trusted server.

        If  the Guest account is Enabled

            The Command Completed Successfully.

        If  the Guest account is Disabled

            System error 1326 has occurred.  Logon failure:

            unknown user name or bad password.

    End

Notes

-----

1. At the point that the GUEST account is disabled and the user does

   not have an account, the Windows NT Server will still request a

   password. Although no password will meet its requirements, it will

   still request it. This is a security measure. It insures that an

   unauthorized user cannot tell the difference between a case where

   an account exists and when the account does not exist. Password

   prompting always occurs regardless if the account exists.

2. At this point, the following information is returned from the

   Trusted Domain in the Response:  Domain SID, User ID, Global Groups

   Memberships, Logon Time, Logoff Time, KickOffTime, Full Name, Password

   LastSet, Password Can Change Flag, Password Must Change Flag, User

   Script, Profile Path, Home Directory and Bad Password Count.

 - Guest account only matters in the domain of the Server you are

   attempting to access. Guest accounts on trusted domains never come

   into play.

 - All steps above assume Global Account unless specified as Local

   Account. See the "Concepts and Planning Guide" for more information

   on account types.

 - The actual internal process is more complicated than the steps

   described above.

 - This does not cover the actual pass-through authentication

   mechanics. For more information, query on the following words in

   the Microsoft Knowledge Base:

      authentication and msv

 - This does not cover the password encryption process used in Windows NT.

   For more information, query on the following words in the Microsoft

   Knowledge Base:

      authentication and msv

   A function of the One Way Encrypted password is sent.

 - This article does not detail the internal workings of the MS

   Authentication Module.

 - The above model assumes that the Guest Account, when enabled, has no

   password. This is the default in Windows NT. If a guest account

   password is specified, it must match the users password that sends in

   the SMB.

Example

-------

The following are examples of this algorithm in action:

I am logged on to my Windows NT workstation local computer. I am using

the same account name and password that is in SCRATCH-DOMAIN Advanced

Server Domain account database. When I carry out the NET USE \\SCRATCH

(Domain Controller for SCRATCH-DOMAIN) command, the command completes

successfully. When I carry out the NET USE \\NET (Controller that

Trust SCRATCH-DOMAIN) command. I receive the error message "System

error 1326 has occurred. Logon failure: unknown user name or bad

password." My account \SCRATCH-DOMAIN\USER1 has permissions on \\NET?

What is the problem?

Configurations

--------------

Windows NT workstation:

 - Login account: USER1

 - Password:      PSW1

 - Login Domain:  LOCAL1

Windows NT Advanced Server:

 - Server Name:            NET

 - Advanced Server Domain: NET-DOMAIN

 - Trust:                  NET-DOMAIN Trust SCRATCH-DOMAIN (Therefore,

   accounts on SCRATCH-DOMAIN can be granted permissions in the NET-DOMAIN.

 - Domain Account Database for NET-DOMAIN does NOT contain an

   account for USER1.

 - Guest Account is DISABLED.

Windows NT Advanced Server:

 - Server Name:                       SCRATCH

 - Advanced Server Domain:            SCRATCH-DOMAIN

 - Domain Database contains account:  USER1

 - Domain Database contains password: PSW1

Answer

------

In this example, the Windows NT workstation is logged on to its local

workstation domain--not the Advanced Server SCRATCH-DOMAIN where its

domain account resides.

NET USE x: \\NET\share

 - When the Windows NT workstation carried out the NET USE x:

   \\NET\share command, it sent out account = "USER1", password = "PSW1"

   and domain = "LOCAL1" in the Session Setup SMB.

 - The Advanced Server \\NET received the SMB and looked at the account

   name.

 - It looks in its local domain account database and does not find a

   match.

 - \\NET then looks at the SMB Domain name.

 - It does not trust "LOCAL1" so it does not check any of its trusted

   domains.

 - \\NET then checks its Guest account.

 - The guest account is disabled so the "System error 1326 has

   occurred. Logon failure: unknown user name or bad password." message

   is generated.

NET USE x: \\SCRATCH\share

 - When the Windows NT workstation carried out the NET USE x:

   \\SCRATCH\share command, it sent out account = "USER1",

   password = "PSW1" and domain = "LOCAL1" in the Session Setup SMB.

 - The Advanced Server \\SCRATCH receives the SMB and looks at the account

   name.

 - It looks in its local domain account database and finds a match.

 - \\SCRATCH then compares the SMB password to the Domain account password.

 - The passwords match so the "Command Completes Successfully" message

   is generated.

In these cases, the trust relationship does not come into play. If the

Workstation had been logged on to the SCRATCH-DOMAIN, the

NET USE x: \\NET\share command would have been successful.

The real answer here is to have all workstations log on to an Advanced

Server domain. In order to login, the user must specify their correct

domain, account, and password. After this is done, all NET USE type

commands will pass the correct domain, account, and password.

Administrators should try and avoid duplicate accounts on both Windows

NT workstations and multiple Advanced Server domains.

USER: Workaround

----------------

There is one workaround that can be used in these cases. From the

Windows NT workstation, you could carry out the following command

   NET USE X: \\NET\SHARE /USER:SCRATCH-DOMAIN\USER1 PSW1

where

  - \\NET = The computer name of the Advanced Server being accessed.

  - \SHARE = The share name.

  - /USER: command line parameter that lets you specify the domain,

    account and password that should be specified in the Session Setup

    SMB.

  - SCRATCH-DOMAIN = Domain name of the Advanced Server where the user

    account resides.

  - \USER1 = account to be validated against.

  - PSW1 = password that matches account on the domain.

For more information, type the following at a Windows NT command

prompt:

   NET USE /?

NULL Domain Names

-----------------

In addition to Windows for Workgroups 3.1, other Microsoft network

clients also send NULL Domain Names in the Session Setup SMB [x73].

They will also exhibit the behavior described above in the example

problem. The following is a table of how each client handles the

Domain Name.

MS Network                        Domain Name

  Client                           Specified

---------------------------------------------

Windows for Workgroups 3.1         NULL

MS OS/2 LAN Manager 2.0, 2.1,

and 2.2                            NULL

MS-DOS LAN Manager 2.0             NULL

MS-DOS LAN Manager 2.1 & 2.2       Logon domain name. * See Note below.

(Including Windows on MS-DOS)

Windows NT 3.1                     Logon domain name.

Notes

-----

The default domain name is specified in the LANMAN.INI file on the

"DOMAIN =" line. This can be overridden by the /DOMAIN: switch with

the NET LOGON command.

There are typically two representations for "NULL" in the SMB: A

zero-length domain name and a one-byte domain name consisting of the

character '?'. The Windows NT SMB server catches the '?' and

translates it to NULL before passing it to the local security

authority (LSA).

Troubleshooting

---------------

A good tip for troubleshooting network access problems is to enable

auditing by doing the following:

1. In the User Manager for Domains window, choose Audit from the Policies

   menu.

2. Select the Audit These Events button.

3. Select the Logon and Logoff Success and Failure options.

Now, anytime a network user access this server remotely, an audit

trail will be logged in the Event Viewer. In the Event Viewer, choose

Security from the Log menu to see the events.

For information on trust relationships, pass-through authentication,

user permissions, and domain logins, please see your Windows NT

Advanced Server "Concepts and Planning" guide or query on the

following words in the Microsoft Knowledge Base:

   authentication and pass-through

Additional reference words: prodnt 3.10

KBCategory: kbnetwork kbfasttip

KBSubCategory: ntnetserv


Windows NT Parallel Ports Do Not Use Interrupts

Article ID: Q103411

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system, version 3.1

 - Microsoft Windows NT Advanced Server, version 3.1

----------------------------------------------------------------------

In Windows NT, parallel ports do not use any hardware interrupt

request lines (IRQs).

The Windows NT parallel port driver is thread-based, and the port is

polled at background priority. This eliminates a number of potential

hardware conflicts with other devices that might want to use IRQ 7 or

5, which used to be the parallel port interrupts.

NOTE: If you boot OS/2 or MS-DOS, you still need to check for IRQ

conflicts; the Windows NT port driver will not be used.

Additional reference words: prodnt 3.10

KBCategory: kbfasttip kbprint

KBSubCategory: ntprint


Setup Hangs During SCSI Detection; Disabling SCSI Detection

Article ID: Q103471

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

----------------------------------------------------------------------

Windows NT Setup may fail during SCSI detection for a variety of

reasons. In some cases, the SCSI-detection routine may conflict with

the SCSI adapter, hindering further detection and sometimes even

halting the installation. You may be able to avoid these problems by

disabling some or all of the SCSI-detection phase of Windows NT Setup.

HOW TO DISABLE THE SCSI-DETECTION ROUTINES

==========================================

If you have a SCSI adapter, you can disable all the SCSI-detection

routines except the one for your particular adapter by modifying the

TXTSETUP.INF file on Disk 1 of your Setup disks. If you have no SCSI

adapters, you can disable all the SCSI-detection routines.

NOTE: Before you can modify TXTSETUP.INF, you need to make a backup

copy of the first Setup disk since it is write-protected. To do so,

choose Copy Disk from the Disk menu in File Manager (or use the MS-DOS

DISKCOPY command). Make sure you use the same media type and density,

and that you modify the copy of TXTSETUP.INF, not the original.

Before you can disable any SCSI-detection routines, you need to know

what type of computer you have: ISA, EISA, or MCA. There are three

corresponding sections in the TXTSETUP.INF file:

   [SCSI.ISA.LOAD]

   [SCSI.EISA.LOAD]

   [SCSI.MCA.LOAD]

Go to the appropriate section for your computer and disable all the

SCSI routines you do not need by inserting the pound sign (#) in front

of each line. For example, if you had an MCA computer and wanted to

disable all the SCSI-detection routines, your [SCSI.MCA.LOAD] section

would look like this:

   [SCSI.MCA.Load]

   #d0,ncr53c9x

   #d0,spock

   #d0,ncrc700

   #d0,ncrc710

   #d0,aha154x

   #d0,buslogic

   #d0,fd16_700

After you make your changes, save the file and start Windows NT Setup

again.

SCSI LOAD SECTIONS OF TXTSETUP.INF

==================================

The following text was taken directly from the TXTSETUP.INF file:

   [SCSI.ISA.Load]

   d0,ncr53c9x

   d0,aha154x

   d0,sparrow

   d0,dptscsi

   d0,ultra14F

   d0,buslogic

   d0,fd8xx

   d0,fd16_700

   d0,t128

   d0,t13b

   d0,always

   d0,dtc329x

   d0,tmv1

   [SCSI.EISA.Load]

   d0,ncr53c9x

   d0,oliscsi

   d0,ncrc700

   d0,ncrc710

   d0,aha154x

   d0,sparrow

   d0,aha174x

   d0,dptscsi

   d0,ultra14F

   d0,ultra124

   d0,ultra24F

   d0,buslogic

   d0,fd7000ex

   d0,fd8xx

   d0,fd16_700

   d0,t128

   d0,t13b

   d0,always

   d0,arrow

   #d0,dce376nt

   d0,dtc329x

   d0,tmv1

   [SCSI.MCA.Load]

   d0,ncr53c9x

   d0,spock

   d0,ncrc700

   d0,ncrc710

   d0,aha154x

   d0,buslogic

   d0,fd16_700

Additional reference words: prodnt 3.10 compaq prosignia ncr ncrc710

KBCategory: kbsetup kbhw kbfasttip

KBSubCategory: ntsetup nthw nthowto


Implementing Scheduled Backups with Windows NT Backup

Article ID: Q103474

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

----------------------------------------------------------------------

The Backup utility included with Windows NT and Windows NT Advanced

Server does not include functionality for scheduling unattended

backups. However, using the Schedule service in conjunction with the

command line capabilities of the Backup utility, you can set up

unattended backups.

The following procedure shows how to use the Schedule service and the

Backup utility to schedule an unattended backup of the entire C: drive

of a computer with an installed tape device. With minor modifications,

these steps could also allow for scheduling unattended backups from a

computer on a network to a computer with a tape device installed or

other configurations.

1. Start the Schedule service on the machine with the tape device

   installed. This can be done by using the Services portion of

   Control Panel, selecting Schedule, and choosing Start. In addition,

   you may wish to configure the Schedule service to start every time

   Windows NT starts by choosing Startup and setting the Schedule

   Service Startup Type to Automatic. Please refer to pages 471-472 of

   the Windows Advanced Server System Guide to verify the correct "log

   on" account needed for local and/or remote backup priviliges. For

   Windows NT, please refer to the System Guide pages 177-178.

2. Using any text editor, such as Notepad, create a command file

   (MYBACKUP.CMD) to perform the commands to backup the requested

   files.

   The following example would back up all files on the C: drive,

   replacing any files currently on the tape, label the backup set

   "My Backup Files," backup the local registry, and log all backup

   information to C:\BACKUP.LOG:

      ntbackup backup c: /D "My Backup Files" /B /L "c:\backup.log"

   NOTE: For additional information on available NTBACKUP options,

   search Windows NT Help for NTBACKUP.

3. Using the AT command, schedule the command file (MYBACKUP.CMD)

   to run when desired. The following AT command will schedule

   MYBACKUP.CMD to execute at 11:00 P.M. every Monday, Wednesday,

   and Friday:

   AT 23:00 /every:M,W,F MYBACKUP.CMD

   NOTE: For additional information on available AT options, type "AT /?"

   at a command prompt or search the online Command Reference for AT.

Additional reference words: prodnt 3.10 W_NTAS scheduler

KBCategory: kbtool kbfasttip

KBSubCategory: ntutil


Troubleshooting 16-Bit Windows Applications Under Windows NT

Article ID: Q103656

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

--------------------------------------------------------------------

Many different 16-bit applications designed to run under Windows 3.1

have been tested with Windows NT. When you are troubleshooting a

16-bit Windows-based application that is not working properly under

Windows NT, the following items should be taken into consideration:

 - If possible, verify that the application works correctly under

   Windows 3.0 and 3.1.

 - If the application requires a VxD (virtual device driver), it will

   not work properly under Windows NT.

 - If the application requires Windows 3.0 or 3.1 to be running in 386

   enhanced mode, the application will not function properly on either

   the DEC Alpha or MIPS versions of Windows NT at this time because

   these platforms currently emulate only the Intel 80286

   architecture.

 - Check Print Manager to see that a default printer has been

   selected. Some applications (such as Microsoft Word version 2.0 for

   Windows) will not function properly under Windows NT unless a

   default printer has been selected.

 - Make sure that any dynamic link libraries (DLLs) used by the

   application are both current and locatable by the application

   (either on the system path or explicitly defined within the

   application or working directory.)

 - Make sure that the default items in the CONFIG.NT and AUTOEXEC.NT

   files are present and in the proper order.

   CONFIG.NT contains the following commands by default:

      files=50

      lastdrive=k

      fcbs=4,0

      dos=high, umb

      device=%SystemRoot%\system32\himem.sys

   AUTOEXEC.NT contains the following commands by default:

      @echo off

      lh %SystemRoot%\system32\mscdexnt.exe

      lh %SystemRoot%\system32\redir

      lh %SystemRoot%\system32\dosx

 - Any environment variables required by the Windows-based application

   should be in the AUTOEXEC.BAT file; if they are, Windows NT will

   use them appropriately.

   Note that if any changes are made to variables related to the

   Windows 3.0 or 3.1 subsystem (WOWEXEC.EXE), the user may have to

   restart the computer in order for these changes to be implemented.

 - Determine whether Windows NT has been installed as a stand-alone

   operating system or as an upgrade of a previous Windows 3.0 or 3.1

   installation. If it is an upgrade, information from the WIN.INI

   and/or SYSTEM.INI files may have not been correctly copied into the

   Windows NT Registry database.

   To correct this problem, you may have to either migrate these

   settings again, or reinstall the application that is not working.

   For help with migrating application information into the Windows NT

   Registry, query on the following reference words in the Microsoft

   Knowledge Base:

      migrate and WIN.INI

Additional reference words: prodnt 3.10 WOW apps tshoot

KBCategory: kb3rdparty kbinterop kbfasttip

KBSubCategory: nt16ap


Adding More Than Two IDE or ESDI Drives in Windows NT

Article ID: Q103934

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

----------------------------------------------------------------------

WARNING: Using Registry Editor incorrectly can cause

    serious, system-wide problems that may require you to

    reinstall Windows NT to correct them. Microsoft cannot

    guarantee that any problems resulting from the use of

    Registry Editor can be solved. Use this tool at your own

    risk.

If a computer has more than two IDE or ESDI hard disk drives and needs

an MS-DOS-based device driver to use the extra drives, Windows NT may

not be able to use the extra drives by default.

To configure more than two IDE or ESDI hard disk drives with Windows

NT, the Registry (REGEDT32.EXE) must be modified to add the

information on the extra drives. You will also need technical

information about your drives, which should be the documentation that

came with them.

NOTE: To make the changes in the Registry, you must be logged on as an

Administrator.

MORE INFORMATION

================

This procedure should only be necessary if you are adding a third or

higher IDE or ESDI hard disk drive or your secondary IDE or ESDI drive

is at a nonstandard address. If the drive is at a nonstandard address,

then use the following procedure to add the correct address in the

Registry. The Key name in this case would be either 1 or 2.

NOTE: The information in this article applies only to Intel x86

architecture computers.

To add support for three or more IDE or ESDI hard disk drives in

Windows NT, do the following:

1. Open the Registry Editor (REGEDT32.EXE).

2. Use the following path:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Atdisk

3. From the Edit menu, choose Add Key to create the following entry:

      Key Name: PARAMETERS

      Class: <blank>

4. Open the PARAMETERS key that you created in Step 3.

5. From the Edit menu, choose Add Key to create the following entries

      Key Name: X

      Class: <blank>

   where X = number of the additional drive, such as 2 for the third

   drive. For each additional drive, increment the Key Name by 1. You

   generally MUST specify the starting parameter as 2 or higher. This is

   so that you don't interfere with the primary or secondary controller

   that most BIOS's support.

6. Select the key that you created in step 5.

7. From the Edit menu, choose Add value and add the following values.

   Set the Data Type of all three entries to REG_DWORD.

      BaseAddress

      -----------

      This is the physical address of the Data register for the controller.

      DriveControl

      ------------

      This is the physical address of the drive control register of

      the controller. Often this is 0x206 off of the BaseAddress

      register.

      Interrupt

      ---------

      This is the interrupt that the controller will use.

Here what a sample registry entry looks like for adding a Quantum EZ

hard disk onto a COMPAQ 486/33L. This computer has a simple ESDI drive

as its primary controller.

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Atdisk

      \Parameters\2

         BaseAddress = REG_DWORD 0x320

         DriveControl = REG_DWORD 0x32e

         Interrupt = REG_DWORD 0xa

NOTE: On an R4000 ARC computer, you should not have to add anything if

you use the IDE "adapter" card at the usual 0x1f0 or 0x170 address.

Additional reference words: prodnt 3.10 W_NTAS gateway compaq

KBCategory: kbhw kbfasttip

KBSubCategory: nthw


Changing Setup Media, Description of Setup Information Files

Article ID: Q103972

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

----------------------------------------------------------------------

Windows NT Setup copies setup information files designed for the media

Setup is running from. If you install Windows NT from floppy disks,

setup information files containing directions and disk numbers for

floppy disks are copied to your hard disk drive. If you later need to

use files from a CD-ROM disc, Windows NT Setup prompts you for floppy

disks.

You can change the source media for a given device driver or Windows

NT component by copying the appropriate setup information file to your

Windows NT \SYSTENT32AP subdirectory. In this manner, you can install new

device drivers and components from any media you choose.

The names and locations of the setup information files you need are

listed later in this article in the section titled "Setup Information

Filenames, Descriptions, and Locations." The following example

describes how to install a new pointing device or mouse driver.

INSTALLING A NEW MOUSE DRIVER FROM FLOPPY DISKS

===============================================

To install a new pointing device or mouse driver from floppy disks

after installing Windows NT Advanced Server from a compact disc, use

the following procedure:

NOTE: To install a different type of device or component, see the

following section, "Setup Information Filenames, Descriptions, and

Locations." Substitute the appropriate filename and disk for

POINTER.IN_ and "Disk 2" respectively.

1. Insert the disk labeled "Disk 2" from the Microsoft Windows NT

   Advanced Server 3.1 disk set.

2. Start Command Prompt from the Main group in Program Manager.

3. Go to the \SYSTENT32AP subdirectory.

4. Substitute the appropriate floppy disk drive letter for <floppy

   disk drive> in the following command line:

      expand <floppy disk drive>:\pointer.in_ pointer.inf

   NOTE: Some information files are not compressed and do not need to be

   expanded. For example, the PRINTER.INF file is not compressed. If this

   is the case, substitute the COPY command for EXPAND.

5. Start Setup to install the new device driver as you would usually

   do.

You are now prompted for the appropriate floppy disk instead of a CD-

ROM disc.

SETUP INFORMATION FILENAMES, DESCRIPTIONS, AND LOCATIONS

=========================================================

Setup information files are listed by file name and include short

descriptions and disk locations. The disk locations are listed for

both Windows NT and Windows NT Advanced Server, in that order.

NOTE: If you want to install a device driver from a CD-ROM disc after

having installed Windows NT from floppy disks, copy the appropriate

setup information file from the CD-ROM disc.

File Name

Disk, Disk     Description

------------------------------------------------------------------------

APP.INF        Used when searching the hard disk drive for existing

7, 7           applications and for automatically configuring MS-DOS

               application Program Information Files (PIFs).

DOSNET.INF     Used by text-mode Windows NT Setup.

22, 23

FILELIST.INF   Setup information file containing the master file list.

4, 4

HARDWARE.INF   Hardware configuration file used by Windows NT Setup.

8, 8

INITIAL.INF    Windows NT Setup script file.

7, 7

IPINFO.INF     TCP/IP default IP address.

10, 10

KEYBOARD.INF   Setup information for keyboards.

8, 4

LANGUAGE.INF   Setup information for installing language-specific

3, 3           support files.

LAYOUT.INF     Setup information to install specific keyboard layout

9, 9           support.

MMDRIVER.INF   Setup information for multimedia drivers.

15, 15

MODEM.INF      Remote Access Server modem setup script file.

7, 7

NBINFO.INF     Setup information for NetBIOS.

5, 8

NCPARAM.INF    Network card parameters setup information file.

9, 9

NCPASHEL.INF   Network Control Panel tool shell setup information.

file.

8, 8

NETDTECT.INF   Network card auto-detection setup information file.

9, 9

NTLANMAN.INF   Windows NT LAN Manager setup information file.

7, 7

NTLMINST.INF   Network installation setup information file.

20, 21

OEMNADAM.INF   Network adapter setup information for AMD AM2100,

8, 8           AM1500T, and PCnet adapters, also Novell/Anthem

               NE1500T, and NE2100 adapters.

OEMNADD1.INF   Network driver setup script for DEC EtherWORKS LC

8, 8           adapter and Turbo/LC adapter cards.

OEMNADD2.INF   Network driver setup script for DEC EtherWORKS Turbo

8, 8           adapter.

OEMNADD4.INF   Network driver setup script for DEC EtherWORKS Turbo

8, 8           EISA adapter.

OEMNADDE.INF   Network driver setup script for DEC Turbo Channel

8, 8           Ethernet adapter.

OEMNADDI.INF   Network driver setup script for DigiBoard PCIMAC (ISA,

8, 8           PCIMAC) MC, and PCIMAC/4 adapters (DigiBoard ISDN

               adapters).

OEMNADDP.INF   Network driver setup script for DEC EtherWORKS DEPCA

8, 8           adapter.

OEMNADDS.INF   Digiboard C/X, PC/Xem, PC/8i, PC/2e, PC/4e, PC/8e

7, 7           adapter setup script.

OEMNADE1.INF   Network driver setup script for 3Com EtherLink 16 TP

8, 8           adapter.

OEMNADE2.INF   Network driver setup script for 3Com EtherLink II

8, 8           adapter.

OEMNADE3.INF   Network driver setup script for 3Com EtherLink III

8, 8           adapter.

OEMNADEE.INF   Network driver setup script for 3Com EtherLink III EISA

8, 8           adapter.

OEMNADEM.INF   Network driver setup script for 3Com 3C523 EtherLink/MC

8, 8           adapter.

OEMNADEN.INF   Network driver setup script for 3Com EtherLink III MCA

8, 8           adapter.

OEMNADFD.INF   Network Peripherals FDDI, MCA network adapter setup

8, 8           script.

OEMNADIN.INF   Network driver setup script for Intel Ether Express 16

8, 8           LAN adapter.

OEMNADLB.INF   Network driver setup script for MS Loop Back adapter.

8, 8

OEMNADLM.INF   Network driver setup script for DayStar Digital

8, 8           LocalTalk adapter (MCA).

OEMNADLT.INF   Network driver setup script for DayStar Digital

8, 8           LocalTalk adapter.

OEMNADN1.INF   Network driver setup script for Novell NE1000 adapter.

8, 8

OEMNADN2.INF   Network driver setup script for Novell NE2000 adapter.

8, 8

OEMNADNE.INF   Network driver setup script for Novell NE3200 EISA

8, 8           adapter.

OEMNADNF.INF   Network driver setup script for COMPAQ

8, 8           NetFlex/DualSpeed Token Ring adapter.

OEMNADNP.INF   Network driver setup script for Network Peripherals

8, 8           FDDI EISA adapter.

OEMNADP3.INF   Network driver setup script for Proteon P1390 adapter.

8, 8

OEMNADP9.INF   Network driver setup script for Proteon P1990 adapter.

8, 8

OEMNADTK.INF   Network driver setup script for IBM Token Ring adapter.

8, 8

OEMNADTM.INF   Network driver setup script for IBM Token Ring

8, 8           adapter/A.

OEMNADUB.INF   Network driver setup script for Ungermann-Bass EtherNet

8, 8           NIUpc, NIUpc/EOTP, NIUps adapters.

OEMNADUM.INF   Network driver setup script for Ungermann-Bass EtherNet

8, 8           NIUps adapter.

OEMNADWD.INF   Network driver setup script for SMC (Western Digital)

8, 8           ISA adapter.

OEMNADWM.INF   Network driver setup script for SMC (Western Digital)

8, 8           adapters: 8003E /A, 8003W /A, 8013WP /A, 8013EP /A.

OEMNSVFT.INF   Network service setup script for FTP Server.

8, 8

OEMNSVNB.INF   Network service setup script for NetBIOS Transport

8, 8           Interface.

OEMNSVRA.INF   Network service setup script for Remote Access Server,

4, 4           NetBIOS Gateway, API Layer, RAS Hub, and AsyMAC driver.

OEMNSVRP.INF   Network service setup script for Remote Procedure Call

8, 8           Locator service.

OEMNSVSV.INF   Network service setup script for Windows NT LAN Manager

8, 8           Server.

OEMNSVWK.INF   Network service setup script for Windows NT LAN Manager

8, 8           Workstation.

OEMNXPDL.INF   Network transport setup script for DLC protocol.

8, 8

OEMNXPIP.INF   Network transport setup script for NWLink Transport

8, 8           driver and NWLink NetBIOS driver.

OEMNXPNB.INF   Network transport setup script for NetBEUI 3.0

8, 8           Transport.

OEMNXPSN.INF   Network transport setup script for SNMP Network

8, 8           Management Service.

OEMNXPSM.INF   Network transport setup script for Services for

0, 7           Macintosh, including the AppleTalk protocol, File

               Server for Macintosh, Kernel driver, and Print Server

               for Macintosh.

OEMNXPST.INF   Network transport setup script for Streams environment.

8, 8

OEMNXPTC.INF   Network transport setup script for TCP/IP protocol,

7, 7           including TCP/IP NetBIOS, Telnet, Loop Support

               Environment, and TCP/IP NetBIOS helper.

OTHER.INF      Setup script for "Other Driver" selections.

8, 8

PAD.INF        PAD script information for Remote Access Server

9, 9           configuration (X.25).

PARTIAL.INF    Windows NT Setup script to configure Windows NT partial

8, 8           installation.

POINTER.INF    Pointing devices setup script (including mouse).

2, 2

PRINTER.INF    Printer setup script file; specific printer driver

6, 6           information.

PRNSETUP.INF   Printer setup script file.

9, 9

REGISTRY.INF   Registry setup script file.

7, 8

REPAIR.INF     Repair disk setup script file.

9, 8

SCSI.INF       SCSI installation setup script.

4, 5

SETUP.INF      Windows NT Setup script file.

8, 8

SETUP16.INF    Win16 SETUP.INF.

19, 21

SFMICONS.INF   Services for Macintosh icon information.

0, 11

SFMMAP.INF     Services for Macintosh Type Creator mappings

0, 11          information.

SUBROUTN.INF   Windows NT Setup common subroutines script file.

9, 9

SWITCH.INF     Remote Access Server switch configuration information.

6, 5

TAPE.INF       Setup script for tape devices.

8, 8

TXTSETUP.INF   Text mode setup script.

(See Note)     NOTE: The "Setup Disk for CD-ROM Installation" and

               "Setup Disk for Floppy Disk Installation" disks both

               contain the TXTSETUP.INF file in the Windows NT and

               Windows NT Advanced Server disk sets.

UTILITY.INF    Utility script used for network setup.

7, 7

VIDEO.INF      Video driver setup script.

8, 7

VIRTUAL.INF    Setup information for configuring the Windows NT paging

9, 9           file.

Additional reference words: prodnt 3.10

KBCategory: kbfasttip kbsetup

KBSubCategory: ntsetup


Troubleshooting Directory Replicator Problems

Article ID: Q104204

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

----------------------------------------------------------------------

If you experience problems during directory replication, the following

list of troubleshooting steps may be helpful.

NOTE: Some steps only require that you note information for use in

subsequent steps.

 1. What operating system is running on the import computer? (Windows

    NT, Windows NT Advanced Server, OS/2, UNIX)

 2. Is there anything interesting in the error log in the import

    computer? The applications log has entries for the replicator

    service and often contains useful information. Look at the logs on

    both the import and export computers.

 3. What file systems are installed in the partitions pointed to by

    the import and export paths?

 4. How many import computers exhibit this behavior?

 5. What time zones are the import and export computers running in?

 6. Make sure the import computer has Backup Operator permissions. If

    these permissions are not set up, errors 5, 1300, and 1307 will

    show up in the event log.

 7. Are the import and export computers in the same domain? If so, are

    the password and user name the same in both domains? Do the

    domains trust each other?

 8. Are alerts being received by administrative accounts? (Has the

    alerter service been started?)

 9. Are there any extended attributes in the files or directories

    being replicated?

10. If the source directory is on an NTFS partition, are there any

    alternate data streams in the files or directories being

    replicated?

11. If the source or destination directories are on an NTFS partition,

    look at the access control lists (ACLs) on the import and export

    trees with File Manager. Does the Replicator local group have at

    least CHANGE privileges to these directories?

12. Is it possible that an account has a file open (on import or

    export) all the time? This would show up as a sharing violation in

    the event log (error 32).

13. Is there an REPL$ share on the export computer? (The share is

    created as a side effect of the Directory Replicating dialog box

    on the export computer. This dialog box also sets an ACL for the

    REPL$ share. Using the NET command or any other means to create

    the REPL$ share is likely to cause problems.)

14. If you run the NET START command on the export and import

    computers, do both computers show "Directory Replicator" (or

    equivalent) in the list?

15. If you are exporting or importing from an NTFS directory, does

    either tree have filenames that differ only in case? Which file

    gets replicated is not predictable. It is possible that the export

    computer will choose one file and the import computer will choose

    another. This results in the replication being out of sync.

16. If the export computer is running OS/2 or UNIX and the import

    computer is running Windows NT, is the export computer's local

    time within half of an hour of the import computer's time? If not,

    the Windows NT network redirector will "bias" the times. This can

    cause everything to be copied again and again. Replication may

    never occur.

17. Some versions of the OS/2 importer leave the archive bit set on

    all files imported, whether or not it was set on the export side.

    This too could result in continuous copying. One workaround is to

    set the archive bit on all files on the export computer. (Windows

    NT to Windows NT replication correctly clones the archive bit.)

18. Some LAN Manager 2.1a import computers do not set their status

    file to OK.RP$. The cause is currently unknown, but there are

    few side effects. Files will not be recopied each pass but a file

    comparison will occur. Except for the status file state, the files

    are correctly replicated. This behavior does not occur on LAN

    Manager 2.2 importers.

19. Some versions of LAN Manager for OS/2 and UNIX allow hard disk

    files with reserved names, such as LPT1 or COM1. This can cause

    problems and should be avoided. The Windows NT replicator

    currently lets these filenames exist.

20. There is a design limitation of OS/2 LAN Manager that you should

    be aware of if you are using it to replicate files. OS/2 LAN

    Manager only allows one set of credentials to be in use at a

    time. (The credentials consist of the user name and password.) If

    someone is interactively logged on to one user identification (ID)

    and the replicator is trying to use a different user ID, then the

    replicator runs into that limitation. Replication will be delayed

    until the interactive user logs off. On the other hand, if the

    interactive user and the replicator user have the same user ID,

    then replication is possible, depending on the value of the

    TryUser value in the LANMAN.INI file.

21. The OS/2 and UNIX LAN Manager importers are generally designed

    with a limit of 1000 files per directory. You should be aware that

    the "." and ".." directory entries use two of those 1000 entries.

    Also, some versions may have an off-by-one error that causes

    repeated file copies with exactly 1000 entries. This gives a

    practical limit of 997 files for those importers. The Windows NT

    importer does not have these limitations.

22. Are there some files being replicated from an HPFS partition

    (written by OS/2) to a Windows NT server? Do these files have

    extended attributes (EAs)? There may be problems with the EAs.

    OS/2 might have written the EAs in discontiguous parts of the

    disk; Windows NT does not support this. The directory replicator

    includes the EA sizes in its checksums, and they may be wrong in

    this case. The replication may stay out of sync permanently. You

    can use Windows NT to rewrite the same EA values to a single

    contiguous area, if you know the original EA values. Note that

    accessing an HPFS volume over the network while OS/2 is directly

    reading or writing the volume will work correctly.

Additional reference words: prodnt 3.10

KBCategory: kbnetwork kbfasttip

KBSubCategory: NTDOMAIN


Operating the HP ScanJet IIC/P with Windows NT

Article ID: Q104235

------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

------------------------------------------------------------------

WARNING: Using Registry Editor incorrectly can cause serious,

system-wide problems that may require you to reinstall Windows NT to

correct them. Microsoft cannot guarantee that any problems resulting

from the use of Registry Editor can be solved. Use this tool at your

own risk.

SUMMARY

=======

Windows NT version 3.1 supports the use of the Hewlett-Packard (HP) ScanJet

IIc color scanner if you use it with the DeskScan II software supplied by

Hewlett-Packard. In order to ensure that the scanner runs correctly under

Windows NT, you must carefully observe the following:

NOTE: Much of the information in this article also applies to the HP

ScanJet IIp scanner.

 - The scanner must be connected and turned on before you start the

   computer.

 - The scanner must be unlocked.

 - The Microsoft-provided driver, HPSCAN16.SYS, must be loaded through a

   device= line in the CONFIG.NT file.

 - The HP-provided 25-pin terminator must be connected to the 25-pin

   Macintosh SCSI-out connection.

 - A supported SCSI Host Adapter must be used.

 - The cables must be SCSI I or SCSI II specification.

 - Install the most current version of DeskScan II software. (The latest

   version is 2.0, which works only with the ScanJet +, ScanJet IIP, and

   the ScanJet IIC series, and is available on the CompuServe HP

   Peripherals Forum or by calling HP at (800) 227-8164.)

 - The proprietary HP scanner interface card which ships with the scanner

   is not supported under Windows NT.

MORE INFORMATION

================

The following operational notes discuss each of the essential elements

for correct operation of the HP ScanJet IIc. Troubleshooting tips and

hints for more effective operation of the HP ScanJet IIc with Windows

NT version 3.1 follow the operational notes.

Operational Notes:

1. The scanner needs to be connected to the SCSI Host Adapter in the

   computer, turned on, and unlocked before you start the computer.

   Otherwise, the computer will not recognize the scanner. Unlike

   some versions of the Windows NT Beta, the scanner does not have to

   be installed, unlocked, and turned on when installing the released

   version of Windows NT.

2. Edit the CONFIG.NT file so that it contains a line which loads the

   HPSCAN16.SYS driver. Use a text editor, such as Notepad, to add

   the following line to the CONFIG.NT file:

            DEVICE=%SYSTEMROOT%\SYSTEM32\DRIVERS\HPSCAN16.SYS

   The CONFIG.NT file can be found in the SYSTEM32 subdirectory.

   Setup copies the files HPSCAN16.SYS, HPSCAN32.DLL, and SCSISCAN.SYS

   to the hard disk when you install Windows NT.

3. The Hewlett-Packard provided in-line terminator must be connected

   to the 25-pin Macintosh SCSI-out port. The scanner may not be

   recognized by the system or the DeskScan II software may fail to

   work if the SCSI bus is incorrectly terminated. Usually, a SCSI

   bus is terminated at both ends, but not in the middle. Therefore,

   if the scanner is the last device on the bus, the end of the bus

   will be at the 25-pin Macintosh SCSI-out port. Do not place an

   in-line terminator at the 50-pin SCSI-in connection. The scanner may

   not work properly if the HP provided terminator is replaced with a

   terminated cable or other SCSI device connected to the 25-pin SCSI-

   out port.

4. Microsoft has tested all of the SCSI Host Adapters listed in the

   Windows NT version 3.1 Hardware Compatibility List (HCL) with the

   HP ScanJet IIc. However, as stated in the HCL, not all of the SCSI

   Host Adapters listed will work correctly with the HP ScanJet IIc.

   The following SCSI Host Adapters on the HCL will not work correctly

   with the HP ScanJet IIc:

      Maynard 16-bit SCSI Adapter  (ISA)

      Data Technology Corp. 3292   (EISA Adapter)

      Olivetti ESC-1               (EISA Adapter)

   The Maynard 16-bit and DTC 3292 SCSI Adapters are appropriately

   footnoted in the HCL as not working with scanners, but the HCL

   documentation does not mention that the Olivetti ESC-1 adapter will

   not work with the HP ScanJet IIc.

5. The HP ScanJet IIc is very sensitive to incorrect cabling. In

   order for the scanner to work, the cables must be of high quality

   and meet the SCSI I or SCSI II specification where appropriate

   (SCSI II Host Adapters require SCSI II cabling). You must ensure

   that all connections are firm, with all connector pins in solid

   contact. Shorter cables have a greater chance of success than

   longer cables. Be certain that the cables are in very good

   condition.

6. Use the most current version of the HP DeskScan II software.

   Presently, the most current version is 1.62. Versions earlier than

   1.61 may not function properly under Windows NT.

7. Do not attempt to use the proprietary HP-provided scanner interface

   card with Windows NT. The supported SCSI Host Adapter takes the place

   of this card. However, HP has developed a driver that allows you to

   use the scanner with a SCSI adapter in the MS-DOS and Windows 3.0 or

   3.1 environments. The name of this driver is SJIIIx.SYS and it is

   available by calling HP or from the HP forum on CompuServe.

Troubleshooting Hints and Tips:

If the scanner does not function or you get error messages from the

DeskScan II software advising you that the scanner cannot be found,

then try the following steps:

WARNING: Using Registry Editor incorrectly can cause serious, system-

wide problems that may require you to reinstall Windows NT to correct

them. Microsoft cannot guarantee that any problems resulting from the

use of Registry Editor can be solved. Use this tool at your own risk.

1. To check if Windows NT has recognized the scanner hardware, start

   the Registry Editor (REGEDT32.EXE) and choose the HKEY_LOCAL_MACHINE

   key. Select the following subkey

      \HARDWARE\DEVICEMAP\Ssci\Scsi Port 0\Scsi Bus 0\Target Idx

      \logical Unit Id 0

   where x represents the SCSI ID number for the scanning device.

   Examine the entry at the SCSI ID number of the scanner. This

   entry should have a value of HP C1750 A.

2. In the Control Panel window, choose Devices to see if the 32-bit

   driver SCSISCAN.SYS was started. If it has not started, attempt to

   start it by choosing the Start button. Do not attempt to change the

   method by which it starts by using the Startup button. The default

   setting in the Startup dialog box is System. If you try to change this

   setting to Boot or some other setting, you may lock your Windows NT

   installation. If this happens, you will have to disconnect the

   scanner, start MS-DOS, and disable HPSCAN16.SYS in the CONFIG.NT

   before returning to Windows NT.

3. If HPSCAN16.SYS is loaded as a device driver in the CONFIG.NT file,

   but you do not have the HP ScanJet IIc connected to the SCSI Host

   Adapter, then your Windows NT will hang when started. The computer

   will need to be restarted. To recover, either turn the machine off

   and reconnect the scanner, or use the "dual boot" functionality of

   Windows NT by starting the MS-DOS environment and editing the

   CONFIG.NT to disable the HPSCAN16.SYS device line.

4. The DeskScan II software installation program will create a group

   called Scanner in the Program Manager. In this group, you will see an

   icon of a scanner with the icon title of DeskScan II. You may also see

   icons titled Scanner Test and SCSI Addresses, however, these two

   applications are not compatible with Windows NT. No resolution or

   workaround to this problem exists at this time.

5. Be sure that the SCSI ID number set for the scanner does not

   conflict with the SCSI ID number for any other device on the SCSI bus.

   SCSI addresses 0 through 7 are displayed on a small, circular SCSI

   address indicator located between the 50-pin SCSI-in and the 25-pin

   Macintosh SCSI-out ports at the back of the scanner. In the middle of

   the indicator dial is a small, narrow slot which can be turned with a

   tiny flat-bladed screwdriver. Once you change the SCSI ID to a

   non-conflicting SCSI address, the new SCSI ID will be recognized at

   system startup and will be written into the Windows NT Registry.

6. To determine whether the HP ScanJet is locked or unlocked, look for

   a rectangular opening at the back of the scanner just above the 50-pin

   SCSI port. If there is a half-height black plastic block in the

   opening, then the scanner is unlocked. To lock the scanner, you must

   press down firmly on the plastic block. When the block is in the

   depressed position, a black bar will appear in the rectangular

   opening. To unlock the scanner, push the horizontal black bar back up

   to the top of the rectangular opening.

The central technical support number for Hewlett-Packard (HP) is (208)

323-2551.

The Hewlett-Packard products included here are manufactured by a

vendor independent of Microsoft; we make no warranty, implied or

otherwise, regarding these products' performance or reliability.

Additional reference words: prodnt hewlett packard scan jet iicx

KBCategory: kbhw kbfasttip

KBSubCategory: nthw ntdocerr


STOP Message: Trap 7F Exception Errors in Windows NT

Article ID: Q104292

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

--------------------------------------------------------------------------

SYMPTOMS

========

You may encounter a Trap 0x0000007F Exception Error and a STOP message when

you are installing or using Windows NT or Windows NT Advanced Server. This

exception error may have several possible causes, including corrupt system

files or hardware problems.

CAUSE

=====

The following is a list of known causes of this error:

 - Corrupt files. File system drivers (FASTFAT.SYS, HPFS.SYS or

   NTFS.SYS) or other critical system files.

 - Low-level hardware problems, such as mismatched RAM memory modules

   or a defective motherboard. In this case the error may occur when

   switching from character mode to graphical mode during Setup.

RESOLUTION

==========

To troubleshoot this problem, do the following:

1. Start the computer from the Windows NT Setup Disk 1 and select

   Repair mode and then select "Verify Windows NT System Files" from the

   repair menu. Any corrupt files should be replaced. If the error still

   occurs, go to step 2.

2. Run diagnostic software and test the RAM in the machine. Replace

   any RAM reported to be bad. Also, make sure that all the RAM in the

   computer is the same speed. If the error still occurs, go to step 3.

3. At this point, try a different motherboard on the computer because

   it may be the faulty component.

Additional reference words: prodnt 3.10 blue trap

KBCategory: kbhw kbfasttip

KBSubCategory: nthw ntstop


How To Obtain Windows NT Version 3.1 U.S. Service Pack

Article ID: Q104597

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft U.S. Service Pack 3 for Windows NT and Windows NT

   Advanced Server version 3.1

----------------------------------------------------------------------

 ** U.S. SERVICE PACK 3 TO BE APPLIED TO WINDOWS NT VERSION 3.1 ONLY!! **

The U.S. Service Pack 3 for Windows NT and Windows NT Advanced Server

version 3.1 (SP3) is a cumulative build of all fixes to Windows NT and

Windows NT Advanced Server version 3.1.

To find out which bugs are fixed by the update, see the README.TXT file or

the SP3_FIX.HLP help file that accompanies the Service Pack or query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

AVAILABLE FORMATS

-----------------

Service Pack 3 is available as single self-extracting archive files for

Intel (x86), MIPS, and ALPHA based computers. For x86 based computers, 10

self-extracting files are available to create a 3.5-inch floppy disk

upgrade set and 12 self-extracting files are available to create a 5.25-

inch set.

New symbol files for debugging Windows NT and Windows NT Advanced Server

version 3.1 with SP3 on x86, MIPS, and ALPHA based computers are also

available on the Internet and CompuServe.

ELECTRONIC SERVICES

-------------------

Not all formats are available on all electronic forums. Because of their

size, the single large archive files for the x86, MIPS, and ALPHA versions

of SP3 are only available on the Internet and CompuServe.

SP3 is available on the following electronic services:

   Internet: ftp.microsoft.com (198.105.232.1)

     \bussys\winnt\winnt-public\fixes\ussp3       (all formats)

   CompuServe: WINNTDL download area              (all formats)

   GEnie: Software Library                        (x86 3.5 and 5.25 only)

   - search on file names or KBFile numbers

   Microsoft OnLine: Software Library             (x86 3.5 and 5.25 only)

   - search on file names or KBFile numbers

   Microsoft Download Service (206)936-6735       (x86 3.5 and 5.25 only)

   - search on file names or KBFile numbers

SP3 DOWNLOAD FILE LISTING

-------------------------

CPU     File           Size         Format    KBFile#

-----------------------------------------------------

ALPHA   SP3ALPHA.EXE   12,340,815   Network   N/A

ALPHA   ASYMBOLS.EXE    1,836,625   Network   N/A   (Debug Symbol Files)

MIPS    SP3MIPS.EXE    12,293,110   Network   N/A

MIPS    MSYMBOLS.EXE    2,353,291   Network   N/A   (Debug Symbol Files)

x86     SP3I86.EXE     11,483,919   Network   N/A

x86     ISYMBOLS.EXE    2,267,080   Network   N/A   (Debug Symbol Files)

x86     RUNME3.EXE        350,904   3.5"      S14556

x86     SP3_31.EXE      1,239,807   3.5"      S14958

x86     SP3_32.EXE      1,394,037   3.5"      S14959

x86     SP3_33.EXE      1,389,410   3.5"      S14960

x86     SP3_34.EXE      1,395,152   3.5"      S14961

x86     SP3_35.EXE      1,384,727   3.5"      S14962

x86     SP3_36.EXE      1,392,813   3.5"      S14963

x86     SP3_37.EXE      1,397,556   3.5"      S14964

x86     SP3_38.EXE      1,380,684   3.5"      S14965

x86     SP3_39.EXE        645,159   3.5"      S14966

x86     RUNME5.EXE        351,035   5.25"     S14566

x86     SP3_51.EXE      1,015,181   5.25"     S14967

x86     SP3_52.EXE      1,157,420   5.25"     S14968

x86     SP3_53.EXE      1,158,876   5.25"     S14969

x86     SP3_54.EXE      1,163,121   5.25"     S14970

x86     SP3_55.EXE      1,164,047   5.25"     S14971

x86     SP3_56.EXE      1,156,296   5.25"     S14972

x86     SP3_57.EXE      1,160,909   5.25"     S14973

x86     SP3_58.EXE      1,164,630   5.25"     S14974

x86     SP3_59.EXE      1,145,420   5.25"     S14975

x86     SP3_5A.EXE      1,145,930   5.25"     S14976

x86     SP3_5B.EXE        223,677   5.25"     S14977

If you are unable to access these files, contact Microsoft Product Support

Services.

INSTALLING SERVICE PACK 3

-------------------------

ALPHA, MIPS, or x86 Network Upgrade

-----------------------------------

Copy the archive file to a directory on your hard drive and type the name

of the archive file with a "-d" switch after it. For example, to decompress

the file, SP3I86.EXE, enter the following command:

   SP3I86.EXE -d

After the service pack has been decompressed, run the UPDATE.EXE program to

install the updated files.

x86 3.5-inch Disk Set Upgrade

-----------------------------

1. Copy the following files to a directory on your hard disk:

      SP3_31.EXE

      SP3_32.EXE

      SP3_33.EXE

      SP3_34.EXE

      SP3_35.EXE

      SP3_36.EXE

      SP3_37.EXE

      SP3_38.EXE

      SP3_39.EXE

      RUNME3.EXE

2. Run the RUNME3.EXE program.

3. Run the MAKE35.BAT batch file to create the update disks.

   NOTE: You need nine formatted 1.44 MB 3.5-inch disks for this procedure.

4. Read the README.TXT file and proceed as directed.

x86 5.25-inch Disk Set Upgrade

------------------------------

1. Copy the following files to a directory on your hard disk:

      SP3_51.EXE

      SP3_52.EXE

      SP3_53.EXE

      SP3_54.EXE

      SP3_55.EXE

      SP3_56.EXE

      SP3_57.EXE

      SP3_58.EXE

      SP3_59.EXE

      SP3_5A.EXE

      SP3_5B.EXE

      RUNME5.EXE

2. Run the RUNME5.EXE program.

3. Run the MAKE525.BAT batch file to create the update disks.

   NOTE: You need eleven formatted 1.2 MB 5.25-inch disks for this

   procedure.

4. Read the README.TXT file and proceed as directed.

Additional reference words: prodnt 3.10 servpack fix bug sp3

KBCategory: kbfasttip kbfile

KBSubcategory: ntdistrib


Microsoft Networking Client Pack Availability

Article ID: Q108242

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

--------------------------------------------------------------------------

SUMMARY

=======

The following is an excerpt from the README.TXT file that is included with

the Microsoft Network Client Software.

MORE INFORMATION

================

--------------------------------------------------------------------------

While we have endeavored to supply as complete and accurate information as

possible, MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE

COMPLETENESS AND ACCURACY OF THIS INFORMATION. This document nor the lists

contained herein do not constitute an endorsement of any particular

manufacturer.

Microsoft and MS-DOS are registered trademarks and Windows and Windows NT

are trademarks of Microsoft Corporation. Other product names and trademarks

are property of their respective owners.

--------------------------------------------------------------------------

The Microsoft Network Client Software is available for download free of

charge on CompuServe(R), MSDL, Microsoft's Internet server,

ftp.microsoft.com, or at a charge of $49.95 from Microsoft Inside Sales.

The terms and conditions of the software is an unlimited user license

described in the README.TXT file, available for download as README.EXE in

the same locations as the software.

To download the software from Compuserve type GO MNC from any ! prompt. To

download the software from the MSDL, dial (206) 936-6735. To download the

software from the Internet, use FTP to connect to Microsoft's Internet

server, ftp.microsoft.com (ip address 198.105.232.1), use Anonymous as your

login name and your complete e-mail name as your password. To obtain the

software from Microsoft Inside sales call (800) 426-9400 and request SKU

#2723850V100.

The Microsoft Network Client software contains the following network

clients and software:

   LAN Manager Basic Client Software for MS-DOS(R) Clients

   LAN Manager Enhanced Software for MS-DOS Clients

   LAN Manager Client Software for OS/2 Clients

   TCP/IP Protocol Stack

   Microsoft Data Link Control (DLC) Protocol

   Microsoft Remote Access Service (RAS) Client

   NetWare(R) Client Software for MS-DOS Clients

Before you can run the Setup program to install the Microsoft Network

Client, you must download the appropriate disk image files, and create

floppy disk installation sets of the Network Client files. For MS-DOS based

clients, there are five files that you must download. For OS/2 based

clients, there are four files that you must download. Each file is a self-

extracting zip file that expands into a disk image of one of the

installation disks.

Within the respective MS-DOS and OS/2 client download areas, the file

naming convention is

   DSKx-n.EXE (for MS-DOS based clients)

   OS23-n.EXE (for OS/2 based clients)

where x specifies the size of the floppy disk (3 for 3.5-inch 1.44 MB

floppies, or 5 for 5.25-inch 1.2 MB floppies), and n specifies the disk

number (1 to 5 for MS-DOS based client, 1 to 4 for OS/2 based client).

To create a floppy disk installation set, use the following syntax to copy

each of the disk images to an external drive

   <filename> -d <destination drive>

at the command prompt. The -d indicates that the directories on DSK3-1.EXE

are to be copied onto a disk located in the B drive. For example, to create

a 3.5-inch (1.44 MB) floppy disk of DSK3-1.EXE, type the following:

   DSK3-1.EXE -d b:

For the Microsoft Network Client for MS-DOS, label each of the five disks

as follows:

   ZIP FILE        DISK LABEL

   =====================================

   DSKx-1.EXE      Setup

   DSKx-2.EXE      Drivers1

   DSKx-3.EXE      Drivers2

   DSKx-4.EXE      Remote Access Service

   DSKx-5.EXE      NetWare(R) Client

For the Microsoft Network Client for OS/2, label each of the four disks as

follows:

   ZIP FILE        DISK LABEL

   ==================================

   OS23-1.EXE      OS/2 Setup

   OS23-2.EXE      OS/2 Workstation 1

   OS23-3.EXE      OS/2 Workstation 2

   OS23-4.EXE      OS/2 Driver 1

Microsoft Network Client Documentation Offer

============================================

Microsoft offers full printed documentation for the Microsoft Network

Clients (either with or without disks), including the following titles:

   Installation Guide for Clients

   User's Guide for Microsoft Windows(TM) Clients

   User's Guide for MS-DOS(R) Clients

   NetWare Connectivity Guide

To order or obtain further information about these products call Microsoft

Inside Sales at (800) 426-9400 and ask about either of the following

products:

   Part #272-055-040

   Microsoft Network Client 2.2 MLP Documentation Kit

   (contains printed documentation only)

   Part #2723850V100

   Microsoft Network Client Pack

   (same as above, but includes disks)

When you order the Documentation Kit, please indicate that you would like

to order the documentation (part #272-055-040) for the Network Client

software that is posted on the Internet or CompuServe. (Ordering

documentation usually requires proof of purchase.)

**************************************************************************

Your Guide to Service and Support for the Microsoft Network Client Pack

MICROSOFT SUPPORT NETWORK

ADVANCED SYSTEMS PRODUCTS SUPPORT OPTIONS

=========================================

The following support services are available from Microsoft for Microsoft

Advanced Systems products, including Microsoft Mail Server and its

gateways, SQL Server, LAN Manager, Windows NT, Windows NT Advanced Server,

and SNA Server.

Electronic Services

-------------------

Microsoft Forums:

These forums are provided through the CompuServe Information Service, (800)

848-8199, representative 230 (sales information only). Access is available

24 hours a day, seven days a week, including holidays.

These forums enable an interactive technical dialogue between users as well

as remote access to the Microsoft Knowledge Base of product information,

which is updated daily. These forums are monitored by Microsoft support

engineers for technical accuracy. If you are already a subscriber, type "GO

<forum name>" at any ! prompt.

   MSCLIENT    Microsoft Network Client

   WINNT       Microsoft Windows NT support

   MSSQL       Support for Microsoft SQL Server

   MSWRKGRP    Microsoft Mail

   MSNETWORKS  Microsoft LAN Manager support

   MSWIN32     Information on Win32

   MSDR        Development-related discussion forum

   WINEXT      Support for extensions and drivers for Windows

   WINSDK      Support for Microsoft Windows Software Development Kit

Microsoft Download Service:

Use the Microsoft Download Service (MSDL) to access the latest technical

notes on common advanced system products support issues by modem. MSDL is

at (206) 936-6735, available 24 hours a day, seven days a week, including

holidays (1200, 2400, or 9600 baud; no parity, 8 data bits, 1 stop bit).

Internet:

Use the Internet to access the Microsoft Driver Library and Microsoft

Knowledge Base  The Microsoft Internet FTP archive host ftp.microsoft.com

(ip address 198.105.232.1) supports anonymous login. When logging in as

anonymous, please offer your complete e-mail name as your password.

Telephone Support

-----------------

Microsoft FastTips:

An interactive, automated system providing support at no charge through

toll lines and accessed by touch-tone phone. FastTips provides fast access

to answers to common questions and a library of technical notes delivered

by phone recording or fax. FastTips is available 24 hours a day, seven days

a week, including holidays. For FastTips on Microsoft Advanced Systems

products, call (800) 936-4400.

Priority Telephone Support:

Get technical support from a Microsoft engineer. Microsoft offers pay-as-

you-go telephone support from a Microsoft engineer, available 24 hours a

day, seven days a week, except holidays. Choose from these options:

   Per Incident: Dial (900) 555-2100. $150.00 per incident.

   (Charges appear on your telephone bill.)

   Per Incident: Dial (800) 936-5900. $150.00 per incident.

   (Charges billed to your Visa, MasterCard, or American Express.)

   10-pack: Ten incidents for $995 prepaid.

Additional Information

----------------------

For additional information about Microsoft support options or for a list of

Microsoft Solution Providers, call Microsoft Support Network Sales and

Information Group at (800) 936-3500, Monday through Friday, 6:00 A.M. to

6:00 P.M., Pacific time, excluding holidays.

This list includes only domestic support programs.

Microsoft's customer support services are subject to Microsoft's then-

current price, terms, and conditions.

**************************************************************************

Additional reference words: prodnt 3.10

KBCategory: kbother kbfasttip

KBSubcategory: ntdistrib


WFW RAS to Windows NT: "Access Denied" After Password Change

Article ID: Q110927

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Remote Access Services for Windows for Workgroups 3.11

----------------------------------------------------------------------

SYMPTOMS

========

When you dial in from your Windows for Workgroups client using Remote

Access Service (RAS) to connect to a Windows NT or Windows NT Advanced

Server version 3.1 RAS server and your password is expired, the server will

prompt you for a new password during the authentication process. After you

give a new password you will be authenticated, but when your RAS client

tries to automatically reconnect to a shared directory or when you use File

Manager to browse the available shares on a server the following error

message appears:

   Access denied

If you specify the full share point name:

   \\<servername>\<sharename>

you are prompted for the new password, and then successfully connected to

the share.

CAUSE

=====

This problem occurs because when you change your password over the RAS

connection, the RAS client's local password file is not updated.

Conversely, when you change your password over a direct network connection,

your local password file is updated, so you are logged on with the new

password and you are not denied access to new or persistent connections.

WORKAROUND

==========

After giving a new password during authentication, choose Control Panel. In

the Control Panel window choose the Network icon. Choose the Password

button to change your password (again). Then log off and log on again from

within the Network dialog box. These steps can be done during the same RAS

connection.

STATUS

======

Microsoft has confirmed this to be a problem in Microsoft Remote Access

client for Windows for Workgroups 3.11. We are researching this problem and

will post new information here in the Microsoft Knowledge Base as it

becomes available.

Additional reference words: 3.10 logon logoff

KBCategory: kbnetwork kbfasttip

KBSubCategory: ntprotocol ntras


Mitsumi CD-ROM Support Information

Article ID: Q112216

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

--------------------------------------------------------------------------

SUMMARY

=======

Mitsumi Electronics manufactures low-cost CD-ROM drives that operate on non-

SCSI host adapters. These drives are not currently on the Windows NT

Hardware Compatibility List.

MORE INFORMATION

================

There are three sources for Mitsumi CD-ROM drivers for Windows NT:

 - Mitsumi Electronics has released a driver which supports the LU005S,

   FX001, and FX001D CD-ROM drives. This driver can be obtained from

   Library 4 of the CDROM forum on CompuServe. This driver is supported by

   Mitsumi Technical Support at (408) 970-9699.

 - A shareware driver written for the Mitsumi LU002 and LU005 CD-ROM drives

   is available on CompuServe. This driver works only for 30 days after

   installation unless you send the author a registration fee of $20. This

   unsupported driver can be obtained from the Third Party section of

   Microsoft's MSWIN32 forum on CompuServe. Please note that this driver is

   not supported by Microsoft or Mitsumi.

 - Media Synergy has written a driver that supports the Mitsumi LU005S,

   LU002, and FX001D CD-ROM drives. This driver is included in a package

   titled CD-ROM NOW! Call Media Synergy at (416) 593-0647 for information

   and support

The products included here are manufactured by vendors independent of

Microsoft; we make no warranty, implied or otherwise, regarding these

products' performance or reliability.

Additional reference words: prodnt 3.10

KBCategory: kbfasttip kbhw

KBSubCategory: nthw ntdriver


Creating a Setup Disk for the Updated WFW 3.11 TCP/IP Drivers

Article ID: Q112578

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SUMMARY

=======

The updated TCP/IP for WFW 3.11 files does not contain a SETUP.EXE program

that can be executed for a first time installation.  If you have the old

TCP/IP Windows for Workgroups 3.11 disk, it can be modified to install the

updated  files.

MORE INFORMATION

================

Using the self-extracting file WFWTCP.EXE and your old TCP/IP Windows for

Workgroups 3.11 disk, follow these steps to install the new Windows for

Workgroups TCP/IP network protocol drivers:

1. Download the self-extracting 408k file, WFWTCP.EXE, dated 01/27/94, from

   one of the following electronic services:

      Internet: ftp.microsoft.com (198.105.232.1) \bussys\msclient\wfw

      CompuServe: MSCLIENT forum

      Microsoft Download Service (MSDL): (206) 936-6735 MSCLIENT\WFW

2. Copy WFWTCP.EXE to your hard disk.

3. Insert the old TCP/IP for WFW 3.11 disk in a floppy drive.

4. From the command prompt, change directory to the directory where the

   file WFWTCP.EXE is located.

5. Type "WFWTCP <floppy drive>" without the quotes and press ENTER. This

   extracts the new TCP/IP files archived in the WFWTCP.EXE file and

   overwrites the old files on the floppy disk. Two extra files containing

   windows help for TCP/IP will also be added to the disk.

6. Start Windows for Workgroups and choose the Network icon.

7. In the Network window choose the Network Setup icon.

8. In the Network Setup window choose the Drivers button.

9. In the Network Drivers window choose the Add Protocol button.

10.Select Unlisted or Update Protocol from the edit list and choose the OK

   button.

11.Indicate which floppy drive you have inserted the Windows for Workgroups

   TCP/IP installation disk in and choose the OK button.

12.Microsoft TCP/IP should be selected in the edit list.  Choose the OK

   button.

13.The Microsoft TCP/IP Configuration appears.  Enter your IP address other

   network information. Choose the OK button.

14.Continue to choose the OK button until you are prompted to reboot your

   computer.  Select the restart option.

Following is a list of the 30 files archived in the WFWTCP.EXE file:

ADDNAME  EXE              14887 12/20/93  12:00a

DNR      EXE              31152 12/20/93  12:00a

EMSBFR   EXE               4294 12/20/93  12:00a

HOSTS                       749 05/08/93  08:47p

LMHOSTS                     846 05/08/93  08:47p

MSTCPIP  HLP             132028 12/30/93  12:26p

NEMM     DOS               2619 12/20/93  12:00a

NETWORKS                    395 05/08/93  08:47p

NMTSR    EXE              22874 12/20/93  12:00a

OEMSETUP INF               1267 01/04/94  11:21a

PING     EXE              66460 12/20/93  12:00a

PROTOCOL                    795 05/08/93  08:47p

READTCP! TXT               9317 01/27/94  02:49p

RPC16C3  DLL               5632 06/14/93  05:15p

SERVICES                   5962 05/08/93  08:47p

SOCKETS  EXE              50144 12/20/93  12:00a

TCPDRV   DOS               4180 12/20/93  12:00a

TCPOVER  HLP              82990 02/26/93  11:23a

TCPSETUP DLL              38192 06/09/93  04:09p

TCPSETUP HLP              13487 05/08/93  08:51p

TCPTSR   EXE              66752 12/20/93  12:00a

TCPUTILS INI                233 06/03/93  01:49p

TINYRFC  EXE              33376 12/20/93  12:00a

UMB      COM               3325 12/20/93  12:00a

VBAPI    386               9524 12/20/93  12:00a

VSOCKETS 386               9535 12/20/93  12:00a

WIN_SOCK DLL              30912 12/20/93  12:00a

WINSOCK  DLL              47968 12/20/93  12:00a

WSAHDAPP EXE               5152 12/20/93  12:00a

WSOCKETS DLL              32768 12/20/93  12:00a

Additional reference words: 3.11 tcp WFW setup

KBCategory: kbnetwork kbfasttip

KBSubCategory: ntprotocol nttcp


Error Messages Caused by Incorrect Serial Port Configuration

Article ID: Q112584

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

--------------------------------------------------------------------------

SYMPTOMS

========

If you configure a serial port incorrectly in the Ports option of Control

Panel, there are several error messages that may appear in Event Viewer

after you restart the computer. The specific error message that appears

depends on which configuration parameter is incorrect. The three main

sources of serial errors are Input Output (I/O) address conflicts, hardware

interrupt (IRQ) conflicts, and configuring serial ports that do not exist.

CAUSE

=====

Incorrect I/O Address

---------------------

Suppose you have added a serial port or serial device to your computer

since you first installed Windows NT. You can use the Advanced Settings

dialog to configure the port. In the Advanced Settings dialog, you can

configure a COM port number, a Base I/O Port Address, and an Interrupt

Request Line (IRQ). If you assign an I/O address to the new COM port, and

that I/O address is already assigned to another COM port, the following

error message appears in Event Viewer after you restart the computer

   The Control registers for COMx overlaps with the COMy control registers.

where x and y represent the number of the COM port. This error message

appears even if you create a duplicate entry for the same COM port, thus

making x and y the same number.

Incorrect IRQ Setting

---------------------

On ISA and EISA computers, COM1 and COM3 both use IRQ 4, and COM2 and COM4

both use IRQ 3. Thus you can configure COM1 - COM4 to their respective

interrupts, but if you configure one of these COM ports to an IRQ being

used by any other device, an error message appears. Suppose, for example,

you configured COM4 to IRQ 5, and you have a bus mouse on the system also

configured to IRQ 5; the following error message appears in Event Viewer

after you restart the computer:

   A conflict has been detected between two drivers which claimed

   equivalent IRQs. Driver <driver name>, with device <\Device\device name.

   Translated> claimed an interrupt with level in data address <hex

   address>, vector in data address <hex address> and Affinity in data

   address <hex address>.

There will be an entry with this format in Event Viewer for each of the

conflicting devices.

After identifying the IRQ conflict, Event Viewer then displays another

warning about using the COM port in question:

   The hardware resources for COM<X> are already in use by another device.

COM Port Doesn't Exist

----------------------

An error message appears in Event Viewer if you attempt to configure a COM

port that physically does not exist on the system. Suppose you went to the

Ports option in Control Panel and added a COM3 port, when in fact you

physically only have COM1 and COM2 on the system. The following error

message appears in Event Viewer the next time you restart the computer:

   While validating that COM3 was really a serial port, the contents of the

   divisor latch register was identical to the interrupt enable and receive

   registers. The device is assumed not to be a serial port and will be

   deleted.

This error message means that the system will delete the I/O address entry

for the non-existent port in the Windows NT internal I/O port address

table. The entry for this non-existent port will still exist in the Ports

option of Control Panel and in the appropriate key of the Registry.

RESOLUTION

==========

To clear these messages from Event Viewer, do one of the following:

 - Use the Advanced Settings dialog box to change the I/O, IRQ, or the COM

   Port Number setting

   -or-

 - Delete the appropriate entry from the Windows NT Registry using Registry

   Editor.

Using the Advanced Settings dialog box clears the error messages in many

cases, but in two cases you need to delete certain entries in the Registry:

 - If you want to change the settings for a COM port already detected at

   Setup by NTDETECT.

   -or-

 - If the COM port in question doesn't physically exist on the system.

In the first case, the Advanced Settings option will not be available. In

the second case, no facility exists in the Ports dialog box to delete the

entry for the non-existent COM port.

WARNING: Using Registry Editor incorrectly can cause serious, system-wide

   problems that may require you to reinstall Windows NT to correct them.

   Microsoft cannot guarantee that any problems resulting from the use of

   Registry Editor can be solved. Use this tool at you own risk.

To delete the false entry from the Registry, use the Registry Editor

(REGEDT32.EXE) to find the following key:

   \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet

       \Services\Serial\Parameters

The Parameters key lists one or more subkeys listed as Serial10000,

Serial10001, and so on. Check the DosDevice value to find which subkey

represents the non-existent COM port. Then, highlight the subkey for the

erroneous serial port and choose Delete from the Edit menu.

Additional reference words: prodnt 3.10

KBCategory: kbhw kbfastip

KBSubCategory: nthw ntregistry


Using the Windows NT NetDDE Share Manager

Article ID: Q114089

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

----------------------------------------------------------------------

SUMMARY

=======

Before applications can share data, they must establish a communication

channel called a trusted share. APIs exist for creating Network DDE shares

under Windows for Workgroups 3.1x, but applications you write using these

APIs cannot communicate when run on Windows NT systems because they can't

create trusted shares.

The Windows NT DDE Share Manager allows you to create and manage Network

DDE shares. This article discusses how to use Share Manager to create a

DDE share for an application that runs on Windows NT, rather than rewriting

the application.

MORE INFORMATION

================

There are two types of DDE applications: source and destination. The DDE

source application defines the DDE Share on the system on which it runs and

provides data to the DDE destination application.

To run the DDE Share Manager, execute DDESHARE.EXE, located in the

WINNT\System32 sub-directory. Two shared-folder icons are shown. The first

lists all shares on the system and the second (checked) lists the shares

trusted by the currently logged on user.

To view a share's properties:

1. Select the Shares menu.

2. Select DDE Shares or double-click on the unchecked shared-folder icon.

3. Select the share name then select Properties.

A default installation of Windows NT will have three existing shares:

Chat$, CLPBK$, and Hearts$.

Step One: Creating a Share

--------------------------

When adding a new share, you are required to provide three properties:

 - Share Name: This is used by the destination program when it requests

   data. By convention, system DDE share names end with a dollar sign ($).

 - Application Name: This is for the Service name used by the DDE source

   application. Generally, each application provides only one DDE service,

   the name of which usually matches the application name. Do not include

   extension or path information.

 - Topic Name: This is a general name for a set of data. One service can

   have multiple topics. The source application defines the topic name,

   and the destination application uses it to request specific data.

Since there are now two types of Network DDE, Share Manager offers three

text-boxes for application and topic name, allowing you the option of

including application and topic names in "old style," "new style," or in

the "static" field. If you are creating a share used to communicate with

an existing Windows for Workgroups application, enter the application name

and topic name in the "static" field. Old style DDE is message-based; new

style DDE uses a DDE Management Library--a layer that sits on top of the

DDE protocol. An application written specifically for Windows NT can take

advantage of the new style DDE. Having these entries allows for different

naming conventions while still providing old and new style DDE programs

access to the shared data through the same share name.

The option "Start Application on Connect" lets the destination application

initiate a conversation with a source application that isn't running at the

moment, although it must be in the system path. If you select the "In

Service" option the program must be registered to the Windows NT system

as a service, for example Chat. The "Item Security" options control access

to the data items within a topic. For some applications, you may need to

restrict access to specific items. Under "Item Security" select "Grant

access only to these items" and enter the item names. If no restrictions

are required, select "Grant access to all items."

You can specify permissions for any user known to the NT security system,

set up specific permissions for each user who will be accessing the share,

and limit a user to specific DDE actions. The default allows everyone read

and link permissions.

When you select OK, the share is created and the share information is

written to the registry in the following location:

   \HKEY_LOCAL_MACHINE\Software\Microsoft\NetDDE\DDE Shares\sharename\...

Step Two: Trusting the Share

----------------------------

On the Windows NT system, the Network DDE DSDM service maintains a database

of shared conversations. When a Network DDE share is accessed, the shared

conversation is referenced and security checks determine if the requester

can be granted access. Applications on a computer run in the "security

context" of the user who is interactively logged on to the computer, so

when a remote request is serviced by a running application on a computer

sharing a Network DDE conversation, the application handling the request

runs in the security context of the user logged onto the sharing computer,

not in the security context of the remote user.

This design complicates security issues. If, for instance, a remote user

who establishes a Network DDE share and remotely connects to it while

someone else is logged on, has the same access privileges to the sharing

computer as the logged on user. To avoid this violation, users logged onto

the source machine cannot access its applications unless they have this

share in their trusted shares list.

To add the share to the list of trusted shares, highlight the share name

and select "trust share." Select the options that apply in the context of

the currently logged on user. The trusted share information is written to

the registry in the path:

   \HKEY_CURRENT_USER\Software\Microsoft\NetDDE\DDE Trusted Shares

Additional reference words: prodnt 3.10 NDdeShareAdd NDdeShare

KBCategory: kbtool kbfasttip

KBSubCategory: ntutil  nt16ap


Windows NT Boot Process and Hard Disk Constraints

Article ID: Q114841

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

----------------------------------------------------------------------

SUMMARY

=======

This article describes hard disk size constraints under Windows NT and

Windows NT Advanced Server. To understand these constraints, it is

necessary to understand both the data structures that define the disk

partitions and the interactions between Windows NT and the system BIOS

interface used during the hardware and operating system's boot process.

MORE INFORMATION

================

-------------------

The Partition Table

-------------------

The data structure that describes the hard disk's partitions is known

as the partition table. It consists of a maximum of four 16-byte entries.

Each entry has 10 fields that describe the following attributes of a

partition:

   FIELD                SIZE

   -----------------   --------

   Boot Flag           1  byte

   Starting Side       1  byte

   Starting Cylinder   10 bits

   Starting Sector     6  bits

   System Indicator    1  byte

   Ending Side         1  byte

   Ending Cylinder     10 bits

   Ending Sector       6  bits

   Relative Sectors    4  bytes

   Number of sectors   4  bytes

System Indicator

----------------

The System Indicator is used to specify the type of file system that is

contained in the partition.  Some common values include:

   VALUE   FILE SYSTEM

   -----   -----------

   0x05    Extended partition

   0x06    BIGDOS File Allocation Table (FAT) format.

   0x07    Installable File System (IFS), eg: HPFS and NTFS

When a partition is a part of a Fault Tolerant (FT) set, Windows NT sets

the high bit of the System Indicator to distinguish it from non-FT

partition of the same type. For example, an FT FAT partition has a System

Indicator value of 0x86 and an FT NTFS partition has a System Indicator

value of 0x87.

When a member of an FT set is disabled, Windows NT sets the two highest

bits.  For example, a disabled FAT partition has a System Indicator value

of 0xC6 and a disabled FT NTFS partition has a System Indicator value of

0xC7.

Boot Flag

---------

The Boot Flag indicates which partition is active or bootable. Only one

partition on a disk can be active.  The Boot Flag value for the active

partition is set to 0x80. Other partitions on the disk are set to 0x00. The

Master Boot Record (described later in more detail) searches for this flag

to locate the active boot sector.

Starting and Ending Side, Cylinder, and Sector

----------------------------------------------

The Starting and Ending Side, Cylinder and Sector fields are very important

with respect to how Windows NT interacts with the disk.

The maximum number of Sides (read/write heads) that can be represented with

1 byte is 256. The maximum number of Cylinders that can be represented with

10 bits is 1024. The maximum number of Sectors that can be represented with

6 bits is 63 because Sectors start counting with 1 (versus Cylinders and

Sides which start counting with 0).

The Cylinder value, represented by 10 bits, is too large to fit into a

single byte.  To store 10 bits, two bits are taken from the byte which

stores the 6 bit Sector value.

With a standard sector size of 512 bytes, the 24 bits used to record the

starting and ending sector addresses translates into a maximum possible

partition size of 7.8GB (8,455,716,864 bytes) which can be described with

these fields.  This is particularly important because the same field sizes

are employed by the INT 13 BIOS interface which defines how the system BIOS

interacts with the hard disk.

Relative Sectors

----------------

The Relative Sectors represents the offset from the beginning of the

partition table to the beginning of the partition, counting by sectors.

Number of Sectors

-----------------

The Number of Sectors represents the total number of sectors in the

partition.

NOTE: The Relative Sectors and Number of Sectors fields are each 32 bits in

size. Under most conditions, together they contain the same information as

Starting and End Side, Cylinder, and Sector values that are represented

with a total of 24 bits for Starting and 24 bits for Ending.

-----------------------

Windows NT Boot Process

-----------------------

On Intel-based computers, the system BIOS controls the initial operating

system boot process. After the initial Power On Self Test (POST) when

hardware components are initialized, the system BIOS identifies the boot

device. Typically, this is a floppy disk or a hard disk. In the case of the

hard disk, the BIOS reads the first physical sector on the disk, called the

Master Boot Sector, and loads an image of it into memory. The BIOS then

transfers execution to that image of the Master Boot Sector.

The Master Boot Record contains the partition table and a small amount of

executable code. The executable code examines the partition table and

identifies the active (or bootable) partition. The Master Boot Record then

finds the active partition's starting location on the disk and loads an

image of its first sector, called the Boot Sector, into memory. The Master

Boot Record then transfers execution to that Boot Sector image.

Whereas the Master Boot Record is generally operating system independent,

the Boot Sector of the active partition is dependent on both the operating

system and the file system. In the case of Windows NT and Windows NT

Advanced Server, the Boot Sector is responsible for locating the executable

file, NTLDR, which continues the boot process. The only disk services

available to the Boot Sector code at this stage of system boot up are

provided by the BIOS INT 13 interface. The Boot Sector code must be able to

find NTLDR and file system data structures such as the root directory, the

File Allocation Table (FAT) in the case of an MS-DOS FAT volume or the

Master File Table in the case of an NTFS volume. These must be present

within the area of the disk addressable by the 24-bit side, cylinder,

sector structure used by the BIOS INT 13 interface and the partition table.

This limits the size of the boot partition to 7.8 gigabytes regardless of

which file system is used.

NOTE: Other constraints may apply depending on the computer hardware and

file system. Some of these constraints are discussed below.

In order to accommodate partitions larger than 7.8 gigabytes, Windows NT

ignores the values in the Starting and Ending sector address fields of the

partition table in favor of the Relative Offset and Number Of Sectors

fields. This provides eight additional bits to represent sectors. These

additional bits allow partitions to be described with up to 2^32 sectors.

With a standard sector size of 512 bytes, the 32 bits used to represent the

Relative Offset and Number of Sectors translates into a maximum possible

partition size of 2 terabytes or (2,199,023,255,552 bytes).

When partitioning a disk, Windows NT will write the correct values to the

partition table fields whenever possible. When the total number of sectors

in a partition exceeds the number which can be described in Side, Cylinder,

Sector notation, Windows NT writes the maximum permitted values to these

fields in the partition table. This prevents the system BIOS from

attempting to calculate the Starting and Ending addresses based on

erroneous data.

For example, assume you have a 3.5GB SCSI drive attached to an Adaptec 154x

series SCSI controller. If the extended sector translation feature is

disabled on the adapter, it might report the following disk characteristics

to the system BIOS:

   Cylinders: 1023, Sides: 64, Sectors: 32

which translates to about 1 gigabyte. With the extended translation

enabled, the device might be reported as having these characteristics:

   Cylinders: 435, Sides: 255, Sectors: 63

which translates to about 3.5GB.

Once Windows NT is up and running, it uses its SCSI drivers to directly

interact with the disk without using the BIOS INT 13 interface. So, during

normal operation the BIOS parameters are largely unimportant.  However, the

differences are critical if the disk is to be formatted with a single

partition and used as the boot drive.

Without extended translation, Windows NT notices that the disk is larger

than the BIOS parameters indicate.  When Windows NT partitions the drive

during initial installation, the starting and ending sector addresses will

be filled in with their maximum possible values. This makes it impossible

for the Master Boot Record code to function correctly despite the fact that

the drive is less than 7.8 gigabytes.

With extended translation, Windows NT will be able to write valid values

for the starting and ending addresses into the partition table, and thus,

the partition remains bootable.

These error messages may appear when extended translation is not enabled

and the Master Boot Record is unable to locate the Boot Sector of the

active partition:

   Error loading operating system.

   - or -

   Missing operating system.

File Systems

------------

FAT and HPFS both have internal limits of 4 GB due to the fact that they

use 32-bit fields to store file sizes.  NTFS uses 64-bit fields for all

sizes, permitting its data structures to handle volumes up to 2^64 bytes

(16 exabytes or 18,446,744,073,709,551,616 bytes).

This value is the theoretical limit for the NTFS file system. Practical

limits having to do with the maximum allowable partition size described

above limit the size of an NTFS partition to approximately 2 terabytes.

Because the 32-bit fields of the partition table refer to the number of

sectors in the partition, disks with larger sector sizes translate into

larger permissible partition sizes. Currently Windows NT supports sector

sizes up to 4 Kilobytes. With 4KB sectors, Windows NT can support a 16

terabyte partition. As new hardware or software schemes become available,

NTFS will be able to handle substantially lager volume sizes.

Drive and Controller Types

--------------------------

IDE drives use a different data structure for representing the number of

cylinders, heads, and sectors per track than the partition table and BIOS

INT 13 interface. According to the IDE specifications, the maximum number

of cylinders is 65536, the maximum number of heads is 16, and the maximum

number of sectors per track is 255. This yields a maximum of 136.9

gigabytes, but because the BIOS/IDE interface has been constrained to use

the lowest common denominator, the result is a limit of about 528MB for an

IDE drive on an Intel-based ISA bus computer. There are new drives and

drivers which use an "Enhanced Drive Parameter Table" to translate between

the logical sector layout internal to the IDE drive and the logical sector

layout addressable by the BIOS INT 13 interface. These drivers and devices

can support larger disks.

The SCSI II command set uses its own form of sector addressing which

currently supports disks as large as approximately 7 gigabytes.

Windows NT Fault Tolerant Volumes

---------------------------------

Through the use of volume sets and stripe sets, Windows NT and Windows NT

Advanced Server permit the construction of logical volumes from multiple

physical disk partitions. This technique permits Windows NT to overcome the

physical hardware limitations imposed by various disk controllers and

construct a logical volume larger than a single disk can support by itself.

NOTE: A logical volume is constructed to look just like a physical disk

partition and it still must conform to the partition table layout described

above.  This means that a fault tolerant construct, such as a volume set,

must have no more than a total of 2^32 sectors (or 2 terabytes at 512 bytes

per sector).

Additional reference words: prodnt 3.10

KBCategory: kbother kbfasttip

KBSubCategory: ntfilesys ntboot  ntfault


RAS Event ID (Error Code) Information

Article ID: Q117304

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SUMMARY

=======

This article explains Remote Access Service (RAS) Event IDs as they appear

in the Event Viewer System Log of Windows versions 3.1 and 3.5. The

following list contains the error code (RAS EVENT ID), the symbol name, the

message text, a brief explanation of the code, and a suggested course of

action to correct the problem causing the error code.

NOTE: RAS Event ID's begin with RAS_LOG_BASE = 20000. However, RAS Event ID

codes specific to Windows NT version 3.5 begin with RAS_LOG_BASE = 20064.

MORE INFORMATION

================

RAS EVENT ID: 20001

SYMBOL NAME : RASLOG_CANT_LOAD_NBGATEWAY

MESSAGE TEXT: Cannot load the NetBIOS gateway DLL components.

EXPLANATION : The RAS NetBIOS gateway could not load.

USER ACTION : Reconfigure RAS by removing and then re-installing it.

RAS EVENT ID: 20002

SYMBOL NAME : RASLOG_CANT_OPEN_REGKEY

MESSAGE TEXT: Cannot open the RAS Server parameters Registry key

EXPLANATION : Registry problem

USER ACTION : Reconfigure RAS by removing and then re-installing it.

RAS EVENT ID: 20003

SYMBOL NAME : RASLOG_CANT_GET_REGKEYVALUES

MESSAGE TEXT: Can't access Registry key values

EXPLANATION : Registry problem

USER ACTION : Reconfigure RAS by removing and then re-installing it.

RAS EVENT ID: 20004

SYMBOL NAME : RASLOG_NOT_ENOUGH_MEMORY

MESSAGE TEXT: Memory allocation failure

EXPLANATION : Not enough free memory for the RAS service to function

              properly.

USER ACTION : Free up some memory on the server by optimizing memory

              allocations to other resources, or by stopping some non-

              essential services, or by installing additional memory on the

              server.

RAS EVENT ID: 20005

SYMBOL NAME : RASLOG_CANT_ENUM_REGKEY_VALUES

MESSAGE TEXT: Cannot enumerate Registry key values

EXPLANATION : Possible Registry problem

USER ACTION : Reconfigure RAS by removing and then re-installing it.

RAS EVENT ID: 20006

SYMBOL NAME : RASLOG_INVALID_PARAMETER_TYPE

MESSAGE TEXT: Parameter %1 has an invalid type.

EXPLANATION :

USER ACTION : Reconfigure RAS by removing and then re-installing it.

RAS EVENT ID: 20007

SYMBOL NAME : RASLOG_CANT_ENUM_PORTS

MESSAGE TEXT: Cannot enumerate the RAS Connection Manager ports

EXPLANATION : Multiport adapter may not have been installed properly

              (Hardware and/or Software)

USER ACTION : Use Network Control to reconfigure the multiple port adapter

RAS EVENT ID: 20008

SYMBOL NAME : RASLOG_NO_DIALIN_PORTS

MESSAGE TEXT: The Remote Access Server is not configured to receive calls.

EXPLANATION : The RAS server is configured for dialing out only or some

              other program is using the port.

USER ACTION : Use Network Control to reconfigure RAS for Dial out and

              Receive calls.

RAS EVENT ID: 20009

SYMBOL NAME : RASLOG_CANT_RECEIVE_FRAME

MESSAGE TEXT: Cannot receive initial frame on port %1. The user has been

              disconnected

EXPLANATION : RAS may not be installed on client.

USER ACTION : Re-install RAS on the client.

RAS EVENT ID: 20010

SYMBOL NAME : RASLOG_AUTODISCONNECT

MESSAGE TEXT: The user connected to port %1 has been disconnected due to

              inactivity.

EXPLANATION :

USER ACTION : Re-dial and then reconnect to the port.

RAS EVENT ID: 20011

SYMBOL NAME : RASLOG_EXCEPT_MEMORY

MESSAGE TEXT: The user connected to port %1 has been disconnected because

              there is not enough memory available in the system.

EXPLANATION :

USER ACTION : Install more memory in the RAS server.

RAS EVENT ID: 20012

SYMBOL NAME : RASLOG_EXCEPT_SYSTEM

MESSAGE TEXT: The user connected to port %1 has been disconnected due to a

              system error.

EXPLANATION : A system error caused the RAS user to be disconnected.

USER ACTION : Look in the Event Viewer for other system error messages,

              correct the failure and re-dial.

RAS EVENT ID: 20013

SYMBOL NAME : RASLOG_EXCEPT_LAN_FAILURE

MESSAGE TEXT: The user connected to port %1 has been disconnected due to a

              fatal network error on the local network.

EXPLANATION : Possible physical network error

USER ACTION : Verify that the network adapter is connected and working

              properly.

RAS EVENT ID: 20014

SYMBOL NAME : RASLOG_EXCEPT_ASYNC_FAILURE

MESSAGE TEXT: The user connected to port %1 has been disconnected due to a

              fatal network error on the async network.

EXPLANATION : Possible serial port problems.

USER ACTION : Verify that the serial ports are working properly.

RAS EVENT ID: 20015

SYMBOL NAME : RASLOG_DEV_HW_ERROR

MESSAGE TEXT: The communications device attached to port %1 is not

              functioning

EXPLANATION : Hardware failure

USER ACTION : Verify that the modem is working properly. Check the cabling.

RAS EVENT ID: 20016

SYMBOL NAME : RASLOG_AUTH_FAILURE

MESSAGE TEXT: The user %1 has connected and failed to authenticate on port

              %2. The line has been disconnected.

EXPLANATION :

USER ACTION : Check the permissions on the user in the RAS admin utility.

              Check user name and password.

RAS EVENT ID: 20017

SYMBOL NAME : RASLOG_AUTH_SUCCESS

MESSAGE TEXT: The user %1 has connected and has been successfully

              authenticated on port %2.

EXPLANATION :

USER ACTION : None

RAS EVENT ID: 20018

SYMBOL NAME : RASLOG_AUTH_CONVERSTION_FAILURE

MESSAGE TEXT: The user connected to port %1 has been disconnected because

              there was a transports-level error during the authentication

              conversation.

EXPLANATION :

USER ACTION : Re-dial and try again

RAS EVENT ID: 20019

SYMBOL NAME : RASLOG_USER_DISCONNECTED

MESSAGE TEXT: The user has disconnected from port %2

EXPLANATION : the remote user has hung up.

USER ACTION : NONE

RAS EVENT ID: 20020

SYMBOL NAME : RASLOG_CANT_RESET_LAN

MESSAGE TEXT: Cannot reset the network adapter for LANA %1. The error code

              is the data.

EXPLANATION :

USER ACTION : Reconfigure RAS.

RAS EVENT ID: 20021

SYMBOL NAME : RASLOG_CANT_GET_COMPUTERNAME

MESSAGE TEXT: Remote Access Server Security Failure. Cannot locate the

              computer name.

EXPLANATION : The message appears when the remote computer name cannot be

              found, so the computer cannot be validated.

USER ACTION : Reconfigure RAS on the client.

RAS EVENT ID: 20022

SYMBOL NAME : RASLOG_CANT_ADD_RASSECURITYNAME

MESSAGE TEXT: Remote Access Server Security Failure. Cannot add the name

              for communication with the security agent on LANA %1.

EXPLANATION : Possible duplicate name on LANA %1

USER ACTION : Verify that another server on LANA %1 does not have the same

              name.

RAS EVENT ID: 20023

SYMBOL NAME : RASLOG_CANT_GET_ADAPTERADDRESS

MESSAGE TEXT: Remote Access Server Security Failure. Cannot access the

              network adapter address on LANA %1.

EXPLANATION :

USER ACTION : Reconfigure RAS

RAS EVENT ID: 20024

SYMBOL NAME : RASLOG_SESSOPEN_REJECTED

MESSAGE TEXT: Remote Access Server Security Failure. The security agent has

              rejected the Remote Access server's call to establish a

              session on LANA %1.

EXPLANATION : A remote access security agent is running on your local

              network.

USER ACTION : Contact your system administrator.

RAS EVENT ID: 20025

SYMBOL NAME : RASLOG_START_SERVICE_REJECTED

MESSAGE TEXT: Remote Access Server Security Failure. The security agent has

              rejected the Remote Access server's request to start the

              service on this computer on LANA %1.

EXPLANATION : A remote access security agent is running on your local

              network.

USER ACTION : Contact your system administrator.

RAS EVENT ID: 20026

SYMBOL NAME : RASLOG_SECURITY_NET_ERROR

MESSAGE TEXT: Remote Access Server Security Failure. A network error has

              occurred when trying to establish a session with the security

              agent on LANA %1. The error code is the data.

EXPLANATION :

USER ACTION : Reconfigure RAS

RAS EVENT ID: 20027

SYMBOL NAME : RASLOG_EXCEPT_OSRESNOTAV

MESSAGE TEXT: The user connected to port %1 has been disconnected because

              there are no operating system resources available.

EXPLANATION :

USER ACTION : Free up some memory on the server by optimizing memory

              allocations to other resources, or by stopping some non-

              essential services, or by installing additional memory on the

              server.

RAS EVENT ID: 20028

SYMBOL NAME : RASLOG_EXCEPT_LOCKFAIL

MESSAGE TEXT: The user connected to port %1 has been disconnected because

              of a failure to lock user memory.

EXPLANATION :

USER ACTION :

RAS EVENT ID: 20029

SYMBOL NAME : RASLOG_CANNOT_OPEN_RASHUB

MESSAGE TEXT: Remote Access Connection Manager failed to start because

              RASHUB could not be opened.

EXPLANATION :

USER ACTION : Reinstall RAS

RAS EVENT ID: 20030

SYMBOL NAME : RASLOG_CANNOT_INIT_SEC_ATTRIBUTE

MESSAGE TEXT: Remote Access Connection Manager failed to start because it

              could not initialize the security attributes.

EXPLANATION :

USER ACTION : Re-boot computer, or re-install RAS if problem persists.

RAS EVENT ID: 20031

SYMBOL NAME : RASLOG_CANNOT_GET_ENDPOINTS

MESSAGE TEXT: Remote Access Connection Manager failed to start because no

              endpoints were available.

EXPLANATION :

USER ACTION : Re-boot computer, or re-install RAS if problem persists.

RAS EVENT ID: 20032

SYMBOL NAME : RASLOG_CANNOT_GET_MEDIA_INFO

MESSAGE TEXT: Remote Access Connection Manager failed to start because it

              could not load one or more communication DLL's.

EXPLANATION : Possible hardware problem

USER ACTION : Ensure that your communications H/W is installed properly and

              re-boot. If problem persists, re-install RAS.

RAS EVENT ID: 20033

SYMBOL NAME : RASLOG_CANNOT_GET_PORT_INFO

MESSAGE TEXT: Remote Access Connection Manager failed to start because it

              could not locate port information from Media DLL's.

EXPLANATION : Possible hardware problem

USER ACTION : Ensure that your communications H/W is installed properly and

              re-boot. If problem persists, re-install RAS.

RAS EVENT ID: 20034

SYMBOL NAME : RASLOG_CANNOT_GET_PROTOCOL_INFO

MESSAGE TEXT: Remote Access Connection Manager failed to start because it

              could not access protocol information from the Registry.

EXPLANATION : Possible Registry problem

USER ACTION : Re-boot computer. If problem persists, re-install RAS.

RAS EVENT ID: 20035

SYMBOL NAME : RASLOG_CANNOT_REGISTER_LSA

MESSAGE TEXT: Remote Access Connection Manager failed to start because it

              could not register with the Local Security Authority.

EXPLANATION : Possible Registry problem

USER ACTION : Re-boot computer. If problem persists, re-install RAS.

RAS EVENT ID: 20036

SYMBOL NAME : RASLOG_CANNOT_CREATE_FILEMAPPING

MESSAGE TEXT: Remote Access Connection Manager failed to start because it

              could not create shared file mapping.

EXPLANATION :

USER ACTION : Re-boot computer. If problem persists, re-install RAS.

RAS EVENT ID: 20037

SYMBOL NAME : RASLOG_CANNOT_INIT_BUFFERS

MESSAGE TEXT: Remote Access Connection Manager failed to start because it

              could not create buffers

EXPLANATION :

USER ACTION : Re-boot computer. If problem persists, re-install RAS.

RAS EVENT ID: 20038

SYMBOL NAME : RASLOG_CANNOT_INIT_REQTHREAD

MESSAGE TEXT: Remote Access Connection Manager failed to start because it

              could not access resources

EXPLANATION :

USER ACTION : Re-boot computer. If problem persists, re-install RAS.

RAS EVENT ID: 20039

SYMBOL NAME : RASLOG_CANNOT_START_WORKERS

MESSAGE TEXT: Remote Access Connection Manager failed to start because it

              could not start worker threads.

EXPLANATION :

USER ACTION : Re-boot computer. If problem persists, re-install RAS.

RAS EVENT ID: 20040

SYMBOL NAME : RASLOG_CANT_GET_LANNETS

MESSAGE TEXT: Remote Access Server failure. Cannot find the LANA numbers

              for the network adapters.

EXPLANATION : RAS was not installed properly.

USER ACTION : Remove and re-install RAS

RAS EVENT ID: 20041

SYMBOL NAME : RASLOG_CANNOT_OPEN_SERIAL_INI

MESSAGE TEXT: RASSER.DLL cannot open the SERIAL.INI file.

EXPLANATION :

USER ACTION : Check configuration of RAS with Network option in Control

              Panel.

RAS EVENT ID: 20042

SYMBOL NAME : RASLOG_CANNOT_GET_ASYNCMAC_HANDLE

MESSAGE TEXT: An attempt by RASSER.DLL to get a async media access control

              handle failed.

EXPLANATION :

USER ACTION : Check configuration of RAS with Network option in Control

              Panel. Reinstall RAS if needed.

RAS EVENT ID: 20043

SYMBOL NAME : RASLOG_CANNOT_LOAD_SERIAL_DLL

MESSAGE TEXT: RASMXS.DLL cannot load RASSER.DLL.

EXPLANATION :

USER ACTION : Remove and re-install RAS

RAS EVENT ID: 20044

SYMBOL NAME : RASLOG_CANNOT_ALLOCATE_ROUTE

MESSAGE TEXT: The Remote Access Server cannot allocate a route for the user

              connected on port %1. The user has been disconnected.

              Check the configuration of your Remote Access Service.

EXPLANATION :

USER ACTION : Check configuration of RAS with Network option in Control

              Panel. Reinstall RAS if needed.

RAS EVENT ID: 20045

SYMBOL NAME : RASLOG_ADMIN_MEMORY_FAILURE

MESSAGE TEXT: Cannot allocate memory in the admin support thread for the

              Remote Access Service.

EXPLANATION : Since the memory can't be allocate, RAS cannot be used.

USER ACTION : Check configuration of RAS with Network option in Control

              Panel. Reinstall RAS if needed.

RAS EVENT ID: 20046

SYMBOL NAME : RASLOG_ADMIN_THREAD_CREATION_FAILURE

MESSAGE TEXT: Cannot create an instance thread in the admin support thread

              for Remote Access Service

EXPLANATION :

USER ACTION : Re-boot computer. If problem persists, re-install RAS.

RAS EVENT ID: 20047

SYMBOL NAME : RASLOG_ADMIN_PIPE_CREATION_FAILURE

MESSAGE TEXT: Cannot create a named pipe instance in the admin support

              thread for Remote Access Service.

EXPLANATION :

USER ACTION : Re-boot computer. If problem persists, re-install RAS.

RAS EVENT ID: 20048

SYMBOL NAME : RASLOG_ADMIN_PIPE_FAILURE

MESSAGE TEXT: General named pipe failure occurred in the admin support

              thread for Remote Access Service.

EXPLANATION :

USER ACTION : Re-boot computer. If problem persists, re-install RAS.

RAS EVENT ID: 20049

SYMBOL NAME : RASLOG_ADMIN_INVALID_REQUEST

MESSAGE TEXT: An invalid request was sent to the admin support thread for

              Remote Access Service, possibly from a down level admin tool.

              The request was not processed.

EXPLANATION :

USER ACTION : Re-boot computer. If problem persists, re-install RAS.

RAS EVENT ID: 20050

SYMBOL NAME : RASLOG_USER_ACTIVE_TIME

MESSAGE TEXT: The user %1 was active on port %2 for %3 minutes %4 minutes.

EXPLANATION :

USER ACTION : none

RAS EVENT ID: 20051

SYMBOL NAME : RASLOG_REGVALUE_OVERIDDEN

MESSAGE TEXT: Using the default value for Registry parameter %1 because the

              value given is not in the legal range for the parameter.

EXPLANATION : Illegal entry in the registry for the parameter given.

USER ACTION : Check the Registry entries.

RAS EVENT ID: 20052

SYMBOL NAME : RASLOG_AUTH_TIMEOUT

MESSAGE TEXT: The user connected to port %1 has been disconnected due an

              authentication time-out.

EXPLANATION : The caller has taken to long to authenticate

USER ACTION : Try to connect to port again. If problem persisted, increase

              the authentication time.

RAS EVENT ID: 20053

SYMBOL NAME : RASLOG_AUTH_NO_PROJECTIONS

MESSAGE TEXT: The user %1 connected to port %2 has been disconnected

              because the computer could not be projected onto the network.

EXPLANATION :

USER ACTION : Disconnect and the re-connect to the network. Make sure that

              the remote computer has a UNIQUE computer name.

RAS EVENT ID: 20054

SYMBOL NAME : RASLOG_AUTH_INTERNAL_ERROR

MESSAGE TEXT: The user %1 connected to port %2 has been disconnected

              because and internal authentication error occurred.

EXPLANATION :

USER ACTION : Try to connect to port again. Re-boot and re-install RAS.

RAS EVENT ID: 20055

SYMBOL NAME : RASLOG_NO_LANNETS_AVAILABLE

MESSAGE TEXT: The Remote Access server could not be started because it has

              been configured to access the network and there are no

              network adapters available.

EXPLANATION : The configuration of RAS does not match the configuration of

the computer.

USER ACTION : Reconfigure RAS to access the local computer only, or put a

              network adapter on the computer.

RAS EVENT ID: 20056

SYMBOL NAME : RASLOG_NETBIOS_SESSION_ESTABLISHED

MESSAGE TEXT: The user %1 established a NetBIOS session between the remote

              workstation and the network server.

EXPLANATION :

USER ACTION : None

RAS EVENT ID: 20057

SYMBOL NAME : RASLOG_RASMAN_NOT_AVAILABLE

MESSAGE TEXT: Remote Access Service failed to start because the Remote

              Access Connection Manager failed to initialize.

EXPLANATION : RAS Connection Manager is configured incorrectly.

USER ACTION : Check the Event viewer for related errors to determine the

              configuration problem.

RAS EVENT ID: 20058

SYMBOL NAME : RASLOG_CANT_ADD_NAME

MESSAGE TEXT: Cannot add the remote computer name %1 on LANA %2. the

              error code is the data.

EXPLANATION : Another computer on the network has the same name as the

              remote computer.

USER ACTION : Remove the other computer from the network, or rename the

              remote computer.

RAS EVENT ID: 20059

SYMBOL NAME : RASLOG_CANT_DELETE_NAME

MESSAGE TEXT: Cannot delete the remote computer name %1 from LANA %2. The

              error code is the data.

EXPLANATION : An internal error has occurred.

USER ACTION : Get the data from the Event Viewer and contact technical

              support.

RAS EVENT ID: 20060

SYMBOL NAME : RASLOG_CANT_ADD_GROUPNAME

MESSAGE TEXT: Cannot add remote computer group name %1 on LANA %2. The

              error code is the data.

EXPLANATION :  A computer has the same name as the remote computer group

              name.

USER ACTION :  Remove the computer with the duplicate name from the

              network.

RAS EVENT ID: 20061

SYMBOL NAME : RASLOG_CANT_DELETE_GROUPNAME

MESSAGE TEXT: Cannot delete the remote computer group name %1 from LANA %2.

              the error code is the data.

EXPLANATION : An internal error has occurred.

USER ACTION : Get the data from the Event Viewer and contact technical

              support.

RAS EVENT ID: 20062

SYMBOL NAME : RASLOG_UNSUPPORTED_BPS

MESSAGE TEXT: The modem on %1 moved to an unsupported BPS rate.

EXPLANATION : The COM port does not support the speed that the modem tried

              to use.

USER ACTION : Try a different COM port, or change the BPS rate to a

              supported value.

RAS EVENT ID: 20063

SYMBOL NAME : RASLOG_SERIAL_QUEUE_SIZE_SMALL

MESSAGE TEXT: The serial driver could not allocate adequate I/O queues. the

              may result in a unreliable connection.

EXPLANATION : If you are using a muli-port adapter card, it may be

              configured to use too many ports. Or you are out of memory.

USER ACTION : Reduce the number of ports being used on the multiport

              adapter. Add more memory.

RAS EVENT ID: 20064

SYMBOL NAME : RASLOG_CANNOT_REOPEN_BIPLEX_PORT

MESSAGE TEXT: Remote Access connection Manager could not re-open bi-plex

              port %1. The port will not be available to calling in or

              calling out. Restart all Remote Access Service components.

EXPLANATION : Possible hardware of configuration problem.

USER ACTION : Stop and re-start all RAS services and components. If

              problems still persists, reinstall RAS

RAS EVENT ID: 20065

SYMBOL NAME : RASLOG_DISCONNECT_ERROR

MESSAGE TEXT: Internal Error: Disconnect operation on %1 completed with an

              error.

EXPLANATION : Disconnected from remote user with an error.

USER ACTION : Have the remote user call in again and retry operation.

              Re-boot computer if needed.

RAS EVENT ID: 20066

SYMBOL NAME : RASLOG_PPP_PIPE_FAILURE

MESSAGE TEXT: General named pipe failure occurred in the Point to Point

              Protocol engine.

EXPLANATION :

USER ACTION : Re-boot computer. Re-install RAS with PPP if needed

RAS EVENT ID: 20067

SYMBOL NAME : RASLOG_CANNOT_INIT_PPP

MESSAGE TEXT: Remote Access Connection Manager failed to start because the

              Point to Point Protocol failed to initialize.

EXPLANATION :

USER ACTION : Re-boot computer. Re-install RAS with PPP if needed

RAS EVENT ID: 20068

SYMBOL NAME : RASLOG_CLIENT_CALLED_BACK

MESSAGE TEXT: The user %1 on port %2 was called back at the number %3.

EXPLANATION :

USER ACTION : None

RAS EVENT ID: 20069

SYMBOL NAME : RASLOG_PROXY_CANT_CREATE_PROCESS

MESSAGE TEXT: The Remote Access Gateway Proxy could not create a process.

EXPLANATION :

USER ACTION : Check RAS Gateway installation.

RAS EVENT ID: 20070

SYMBOL NAME : RASLOG_PROXY_CANT_CREATE_PIPE

MESSAGE TEXT: The Remote Access Gateway Proxy could not create a process.

EXPLANATION :

USER ACTION : Check RAS Gateway installation.

RAS EVENT ID: 20071

SYMBOL NAME : RASLOG_PROXY_CANT_CONNECT_PIPE

MESSAGE TEXT: The Remote Access Gateway Proxy could not establish a named

              pipe connection with the Remote Access Supervisor Proxy.

EXPLANATION :

USER ACTION :

RAS EVENT ID: 20072

SYMBOL NAME : RASLOG_PROXY_PIPE_FAILURE

MESSAGE TEXT: A general error occurred on the named pipe in the remote

              Access %1 Proxy.

EXPLANATION :

USER ACTION :

RAS EVENT ID: 20073

SYMBOL NAME : RASLOG_CANT_OPEN_PPP_REGKEY

MESSAGE TEXT: cannot open obtain information about the PPP key or one its

              subkeys.

EXPLANATION : Possible Registry problem.

USER ACTION : Check the Registry for PPP entries

RAS EVENT ID: 20074

SYMBOL NAME : RASLOG_PPP_CANT_LOAD_DLL

MESSAGE TEXT: Point to Point Protocol engine was unable to load the %1

              module.

EXPLANATION :

USER ACTION :

RAS EVENT ID: 20075

SYMBOL NAME : RASLOG_PPPCP_DLL_ERROR

MESSAGE TEXT: The Point to Point Protocol module %1 return an error while

              initializing.

EXPLANATION :

USER ACTION :

RAS EVENT ID: 20076

SYMBOL NAME : RASLOG_NO_AUTHENTICATION_CPS

MESSAGE TEXT: The point to Point protocol failed to load the required PAP

              and/or CHAP authentication modules.

EXPLANATION :

USER ACTION :

RAS EVENT ID: 20077

SYMBOL NAME : RASLOG_PPP_FAILURE

MESSAGE TEXT: An error occurred in the Point to Point Protocol module. The

              error code is the data.

EXPLANATION :

USER ACTION : Save the data from the event log and call Tech Support.

RAS EVENT ID: 20078

SYMBOL NAME : RASLOG_IPXCP_NETWORK_NUMBER_CONFLICT

MESSAGE TEXT: The IPX network number %1 configured for the WAN interface is

              already in use on the LAN.

EXPLANATION :

USER ACTION : Re-configure the IPX network number in question.

RAS EVENT ID: 20079

SYMBOL NAME : RASLOG_IPXCP_CANNOT_CHANGE_WAN_NETWORK_NUMBER

MESSAGE TEXT: The IPX network number %1 requested by the remote client for

              the WAN interface cannot be used on the local IPX router

              because the router is not configured to change its local WAN

              network numbers. You should configure the IPX Remote Access

              Service to allocate addresses automatically and use different

              address for remote IPX clients.

EXPLANATION :

USER ACTION : You should configure the IPX Remote Access Service to

              allocate addresses automatically and use different address

              for remote IPX clients.

Additional reference words: prodnt 3.10 3.50

KBCategory: kbnetwork kbfasttip

KBSubCategory: ntras


How Browsing a Wide Area Network Works

Article ID: Q117633

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

----------------------------------------------------------------------

SUMMARY

=======

This article explains how browsing over a wide area network (WAN) works

in a domain and a workgroup.

MORE INFORMATION

================

The PDC of a WAN domain that spans subnets acts as a domain master browser

server. Each subnet in that domain has its own master browser server, which

sends master browser announcement requests to the domain master browser. On

receipt of a request from a server, the domain master browser replies with

a remote NetServerEnum API, collects the servers from that master, then

merges that list with its current list. This guarantees that the domain

master browser server maintains a complete list of domain servers. When a

client remotely sends a NetServerEnum API to the domain master browser

server, the domain master returns to all servers in its browse list.

WAN browsing support is available only in a domain environment among

Windows NT and Windows NT Advanced Server machines. If a domain contains

at least one Windows NT Advanced Server machine, you can browse that

domain. A subnet that has only Windows NT workstations running Browser

services can browse the entire contents of that domain.

To guarantee that the master browser for each subnet can access the PDC,

a domain's PDC must be listed in each client's LMHOSTS file. To guarantee

that the PDC can request the local subnet's list from the subnet master

browser, the TCP/IP transport must cache client addresses for some amount

of time. In addition, lists of domains retrieved by the master browser

have only the domains that are occupied by other master browser servers

in that domain.

Windows NT or WFW workgroups cannot span multiple subnets. Workgroups

can view only other workgroups on the local subnet.

Here are some conditions under which browsing does not work:

1. Computers in a remote subnet cannot be seen by clients in a Windows NT

   or WFW workgroup. However, if there is a Windows NT on the workgroup,

   the workgroup administrator can configure one or more of the Windows

   NT workstations as "Configured Master Browsers," then add those

   computers in the remote subnet to the LMHOSTS file.

2. You cannot browse remote subnets with only WFW clients, because

   the WFW browser is not WAN-aware.

3. When browsing, you cannot see an isolated workgroup or a domain that

   is on a subnet with no machines in the current domain.

   For example: Suppose domain A spans 3 subnets(S1,S2 and S3). PDC for

   domain A is on S1. S2 has a BDC for domain A. S3 has an NT machine that

   is a part of domain A. S3 also has a few machines that belong to domain

   B, the PDC for which is elsewhere.

   Now, when the browse master of S3 (NT wksta) sends the list of servers

   in its local subnet to the PDC of domain A, it also sends a list of

   domains in its subnet that includes domain B. So PDC of domain A has a

   list of domains that has domain B listed in it. When browse master of

   S2 gets the browse list from PDC, it gets the list of domains as well,

   and that includes domain B. So it knows the existence of domain B. But

   for a client (on S2) to get the list of servers in domain B, it sends

   a request to its browse master on S2 and S2 in turn contacts the browse

   master of domain B on S3. For the browse master of S2 to contact the

   browse master of S3, its IP address has to be listed in its LMHOSTS

   file.

   Now, if S3 does not have any machines in its subnet that belong to

   domain A, then S1 and S2 cannot browse domain B.

4. You cannot browse domains on other subnets where the browse masters

   are not listed in the LMHOSTS file.

Additional reference words: prodnt 3.10

KBCategory: kbnetwork kbfasttip

KBSubCategory: ntdomain


How to Install ISDN on WFWG 3.11 RAS

Article ID: Q118665

------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

------------------------------------------------------------------------

This article provides instructions to install ISDN on your Windows for

Workgroups version 3.11 computer. These instructions are divided into the

following sections and should be performed in the order given:

 - Before You Install ISDN

 - To Install ISDN

 - To Add an Entry in Remote Access Service (RAS) to Call an ISDN Server

 - To Receive Incoming Calls on the ISDN Line

Before You Install ISDN

-----------------------

1. Because ISDN service is not available in all areas, check with your

   local telephone company to see if ISDN service is available in your

   area before you order an ISDN board.

2. If ISDN service is available in your area, you can order an ISDN card

   from Digi International at (612) 943-9020.

3. When you order ISDN lines from your local ISDN service provider, make

   note of the following information they give you because you will need to

   enter it in Windows for Workgroups when you set up ISDN:

    - Service Profile ID (SPID)

    - Switch type

    - Line type

4. Obtain the ISDN Windows for Workgroups version 3.11 software from

   Microsoft.

To Install ISDN

---------------

1. In the Program Manager window, double-click the Network Setup icon, or

   use the arrow keys to select the Network Setup icon, and then press

   ENTER.

2. Choose the Drivers button.

3. Choose the Add Adapter button.

4. In the Network Adapters box, select DigiBoard PCIMAC - ISA ISDN Adapter,

   and then choose the OK button.

5. Follow the on-screen instructions, and then when you are prompted with

   the DigiBoard PCIMAC - ISA ISDN Adapter Card Setup dialog box:

   a. For IRQ Level, choose Disabled.

   b. For I/O Base Address, choose an address that is not used by any

      other device yet; if in doubt, leave at the default of 0x320.

   c. For Memory Base Address, choose an address that is not used by any

      other device yet; if in doubt, leave at the default of 0xD0000.

   d. For Switch Type, select the switch type you got from your ISDN

      service provider.

6. Choose the LineOptions button. The Line Configuration Options dialog box

   appears.

7. In the Line Configuration Options dialog box:

   a. For Line Number, leave at the default of Line 1.

   b. Do not select the Enable Terminal Management check box. (This

      option applies only to the AT&T switch type. For more information,

      see the RAS Help file.)

   c. For Number Of Logical Terminals, leave at the default of 1. (This

      information is provided by the ISDN service provider. For more

      information, see the RAS Help file.)

   d. Enter your Service Profile ID (SPID) number in the format provided

      by your ISDN service provider.

   e. Enter your ISDN phone number, which is probably identical to your

      seven-digit SPID.

8. Choose the OK buttons and Close buttons as prompted until you are

   prompted to choose Restart Computer or Continue; at this point, choose

   the Restart Computer button if you don't have any unsaved open files in

   other applications. If you need to save files in other applications,

   switch to those applications to save the files and close the

   applications, and then choose the Restart Computer button.

To Add an Entry in Remote Access Service (RAS) to Call an ISDN Server

---------------------------------------------------------------------

1. Start RAS and choose the Add button.

2. Enter an appropriate Entry Name, and then the server's ISDN Phone Number

   and Description.

3. In the Port box, select ISDN1.

4. At the bottom of the Add Phone Book Entry dialog box, choose the ISDN

   button.

5. In the ISDN Settings dialog box, select the appropriate line type that

   was provided by your ISDN service provider (leave at 64K Digital if you

   are unsure of the line type).

6. Leave the Negotiate Line Type and Enable Hardware Compression check

   boxes selected.

7. In the Channels To Use box, leave the "1" if you want to use only one

   64k line during your communication with the ISDN server; enter "2" if

   you want to use both ISDN B channels for a total of 128K Digital line

   speed.

8. Choose the OK buttons in this and the previous dialog box.

You are now ready to dial the ISDN RAS server.

To Receive Incoming Calls on the ISDN Line

------------------------------------------

1. Make sure the RAS Point-to-Point (PTP) server is installed.

2. Select the Allow Incoming Calls To This Computer check box.

3. In the Server Port box, select ISDN1.

4. Enter the password if you want a password that callers must know before

   they can access your RAS PTP server.

5. Choose the OK button.

6. When you are prompted to quit RAS right now or to continue, choose the

   Yes button.

7. Restart RAS.

When you choose the Answer button, your server will be ready to receive

incoming ISDN calls.

The third-party products discussed here are manufactured by vendors

independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

Additional reference words: 3.11 wfw w_wfw wfwg

KBCategory: kbnetwork kbfasttip

KBSubCategory: ntprotocol


File Copy to Netware Server Fails in File Manager

Article ID: Q118826

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Advanced Server version 3.1

----------------------------------------------------------------------

SYMPTOMS

========

When you try to copy files from File Manager to a Novell Netware server

over a 56KB link using Client or Gateway Service for Netware, the following

error message appears:

   Cannot complete the file copy operation.

   No connection to remote computer.

If you run the NET USE command, the connecting and disconnecting network

drives seems to work successfully. However, after disconnecting from a

network drive, the connection list displays the drive as still being

connected.

CAUSE

=====

This problem occurs due to NWRDR not negotiating the right packet size.

WORKAROUND

==========

To workaround to this problem, disable the Netware PBurst option on the

Windows NT Advanced Server 3.1 computer. To disable PBurst, use the

following procedure:

WARNING: Using Registry Editor incorrectly can cause serious, system-wide

problems that may require you to reinstall Windows NT to correct them.

Microsoft cannot guarantee that any problems resulting from the use of

Registry Editor can be solved. Use this tool at your own risk.

1. Start Registry Editor and go to the following subkey:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

      \NwcWorkstation\Parameters

2. From the Edit menu, choose Add Value.

3. Enter the following value:

      Value Name: MaxBurstSize

      Data Type: REG_DWORD

      Value: 0

4. Exit Registry Editor and restart Windows NT.

NOTE: This procedure disables PBurst for all servers. There is no way to

change this on individually on each server from the client computer. The

default value of MaxBurstSize is 1 (enable).

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT and Windows NT

Advanced Server version 3.1. We are researching this problem and will post

new information here in the Microsoft Knowledge Base as it becomes

available.

Additional reference words: prodnt 3.10 csnw gsnw

KBCategory: kbnetwork kbfasttip

KBSubCategory: ntnetserv


Supported NetWare Utilities and Applications Under Windows NT

Article ID: Q118829

------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

------------------------------------------------------------------------

The following lists NetWare utilities and NetWare-aware applications that

are supported under Windows NT version 3.1 using the Microsoft Client and

Gateway Services for NetWare.

Supported NetWare Utilities

---------------------------

The following table lists NetWare utilities and any known issues

corresponding to each of them.

Utility         Issues

----------------------

chkvol          None

colorpal        None

dspace          None

flag            None

flagdir         None

fconsole        None

filer           None

grant           None

help            None

listdir         None

ncopy           None

ndir            None

pconsole        None

psc             None

pstat           None

rconsole        None

remove          None

revoke          None

rights          None

security        None

send            None

session         Search mapping option not supported because it always

                maps as root.

setpass         None

settts          None

slist           None

syscon          None

tlist           None

userlist        None

volinfo         If update interval = 5, command executes very slowly.

whoami          None

Supported NetWare-Aware Applications

------------------------------------

Lotus Notes, SPX connectivity option

NetWare 3270 LAN Workstation for MS-DOS

NetWare 3270 LAN Workstation for Windows

Attachmate Extra! for MS-DOS to the NetWare SAA Gateway

Attachmate Extra! for MS-DOS to the Attachmate 3270 Gateway

Attachmate Extra! for Windows to the NetWare SAA Gateway

Attachmate Extra! for Windows to the Attachmate 3270 Gateway

DCA IRMA LAN for MS-DOS to Novell's SAA

Btrieve requester (BREQUEST.EXE)

Gupta SQLBase for NetWare systems

The third-party products discussed here are manufactured by vendors

independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

Additional reference words: prodnt 3.10 CSNW GSNW

KBCategory: kbnetwork kbfasttip

KBSubCategory: ntnetserv nt16ap


Using WIN32S Windows Sockets Applications with TCP/IP-32

Article ID: Q119369

---------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft TCP/IP-32

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------------

SUMMARY

=======

Windows Sockets applications that use the WIN32S API do not function

properly under Windows for Workgroups version 3.11 with the Microsoft

TCP/IP-32 VxD. In order for these applications (for example, NCSA's Mosaic

Alpha 3) to operate properly with TCP/IP-32, an updated version of WIN32S

is required.

MORE INFORMATION

================

Windows Sockets applications that use WIN32S have memory locking issues

with Win32S and the TCP/IP-32 VxD that are corrected in version 115a or

later of the WIN32S distribution. The updated distribution of WIN32S can be

found in the following locations:

 - On CompuServe, the file is located in the MSWIN32 forum with a filename

   of 115A.ZIP.

 - On the Internet, the file is located in the following path:

      ftp://FTP.MICROSOFT.COM/DEVELOPER/DEVTOOLS/WIN32SDK/WIN32S115A.ZIP

Mosaic Alpha 3 is manufactured by NCSA, a vendor independent of Microsoft;

we make no warranty, implied or otherwise, regarding this product's

performance or reliability.

Additional reference words: prodtcp32 1.0 WFWG

KBCategory: kbnetwork kbfasttip

KBSubCategory: ntprotocol nttcp


Creating Customized Configuration Defaults for TCP/IP-32

Article ID: Q119370

---------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft TCP/IP-32

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------------

SUMMARY

=======

Microsoft TCP/IP-32 includes a MSTCP32.DEF file, which allows you to

specify customized configuration defaults during installation of TCP/IP-32.

You can use this file to have user installations default to specific values

for the given settings.

MORE INFORMATION

================

If the MSTCP32.DEF file is modified, performing any installations from the

location of the modified MSTCP32.DEF file causes the installations to have

the specified settings. When the user installs the file, they will not be

prompted with the Microsoft TCP/IP Configuration dialog box. Setup copies

the necessary files and makes the necessary changes to the .INI files; the

user then needs to restart their computer.

The default contents of the file are:

   ; MSTCP32.DEF for Microsoft TCP/IP-32 for Windows For Workgroups 3.11

   ; Copyright (C) 1994 Microsoft Corporation

   ;

   ; This file allows administrators to specify customized

   ; configuration defaults for Microsoft TCP/IP-32. By

   ; altering the values in this file, you can alter the

   ; defaults that the user experiences during installation.

   ; The valid parameter files are described in your User's

   ; Guide or in online help.

   [MSTCP]

   deadgwdetect=1

   pmtudiscovery=1

   [NBT]

   NameServer1=

   NameServer2=

   ScopeID=

   [DNS]

   DomainName=

   DNSServers=

   DNSDomains=

   [MISC]

   DHCPEnabled=0

   RouterEnabled=1

   IPMask=

   DefaultGateway=

NOTE: The settings in the [MISC] section of the MSTCP32.DEF file are not

documented in the online Help.

These settings are defined as:

   DHCPEnabled= 0 or 1

      Specifies whether Microsoft TCP/IP-32 will use dynamic host

      configuration.

      Default=0 (false)

   RouterEnabled= 0 or 1

      Specifies whether the "Enable IP Routing" check box will be available

      or unavailable (grayed out) in the Advanced Microsoft TCP/IP

      Configuration dialog box.

      Default=1 (true)

   IPMask= #.#.#.#

      Specifies the subnet mask.

      Default= (blank)

   DefaultGateway= #.#.#.#

      Specifies the IP Address for the default gateway.

      Default= (blank)

Additional reference words: prodtcp32 1.0 WFWG

KBCategory: kbnetwork kbfasttip

KBSubCategory: ntprotocol nttcp


DEC 205 EtherNet Card and TCP/IP-32

Article ID: Q119371

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft TCP/IP-32

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SUMMARY

=======

Microsoft TCP/IP-32 does not function properly with a DEC 205 (DE205)

EtherNet network adapter unless the EtherWorks III driver is version 2.77

or later.

MORE INFORMATION

================

Using a driver earlier than version 2.77 functions properly with NetBEUI,

but no connectivity will be possible with TCP/IP-32 except that the system

will be able to PING other workstations. An updated driver is available on

CompuServe in the DECPCI forum (GO DECPCI).

For additional information on Digital products, please call Digital at

(800) 344-4825.

The Digital products discussed here are manufactured by Digital Equipment

Corporation (DEC), a vendor independent of Microsoft; we make no warranty,

implied or otherwise, regarding these products' performance or reliability.

Additional reference words: prodtcp32 1.00 WFWG

KBCategory: kbnetwork kbfasttip

KBSubCategory: ntprotocol NTTCP


Setting the Name Resolution Search Order for TCP/IP-32

Article ID: Q119372

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft TCP/IP-32

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SUMMARY

=======

The Microsoft TCP/IP-32 stack uses various means to resolve a host name to

an IP address of a given host. Four mechanisms are used; Local Cached

Information, Hosts File, DNS Servers, and NetBIOS name resolution

mechanisms. The default resolution order for resolving a host name is Local

Cached Information -> Hosts File -> DNS Servers -> NetBt (NetBIOS over

TCP/IP). NetBIOS over TCP/IP name resolution can consist of local subnet

broadcasts.

MORE INFORMATION

================

Under most circumstances, the default resolution order does not need to be

changed. However, if a change is necessary there are SYSTEM.INI parameters

that you can use to alter this default behavior. This is done by using the

four parameters: LocalPriority, HostsPriority, DnsPriority, and

NetbtPriority. These parameters are Specified in the [DNS] section of the

SYSTEM.INI file. Valid values can be between -32768 and 32767. The lower

the value, the higher the priority in the search order. If you specify any

of these parameters in the SYSTEM.INI, only those parameters specified will

take effect, and none of the other resolution methods will be used.

Example

-------

   [DNS]

   DnsPriority=1

   HostsPriority=2

Will search the configured DNS server first, followed by the local HOSTS

file. Local Cached Information and NetBIOS name resolution mechanisms would

not be used.

Additional reference words: prodtcp32 1.00 WFWG

KBCategory: kbnetwork kbfasttip

KBSubCategory: NTTCP


Using a Numeric Hostname with TCP/IP-32

Article ID: Q119373

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft TCP/IP-32

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SUMMARY

=======

In order to use a Hostname that is numerical (for example, 1 ) you must use

single quotation marks (for example, '1') on the command line and in the

HOSTS file where the name is defined.

MORE INFORMATION

================

Example

-------

If you want to assign the IP Address 44.44.45.1 to the Hostname 3 you would

use the following command when you try to PING the Host:

   PING '3'

You also need to make sure the following entry is in the HOSTS file:

   44.44.45.1    '3'

If you do not use single quotation marks, TCP/IP-32 interprets the Hostname

as an IP Address and the request will time-out.

Additional reference words: prodtcp32 1.00 WFWG

KBCategory: kbnetwork kbfasttip

KBSubCategory: ntprotocol NTTCP


Err Msg: Setup Error 108 or 110 During TCP/IP-32 Installation

Article ID: Q119374

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft TCP/IP-32

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SYMPTOMS

========

If you had a beta version of Microsoft TCP/IP-32 installed on Windows for

Workgroups version 3.11, one of the following error messages may appear

when you attempt to install the released version of Microsoft TCP/IP-32:

   Setup Error 108: Could not create or open the PROTOCOL.INI file.

   -or-

   Setup Error 110: Could not find or open WIN.INI.

CAUSE

=====

When you install TCP/IP-32, the OEMSETUP.INF file is copied to the SYSTEM

directory and renamed OEMx.INF (where x is a number). The OEMx.INF file is

then used by Setup to perform the necessary transactions for installation.

The above error messages may appear due to earlier (beta) versions of the

OEMx.INF file being in the SYSTEM directory.

RESOLUTION

==========

To resolve this problem:

1. Remove any previous versions of Microsoft TCP/IP-32.

2. Quit Network Setup and restart your system.

3. Rename any OEMx.INF (where x is a number) files that are in your

   WINDOWS\SYSTEM directory.

4. Start Network Setup again and install Microsoft TCP/IP-32, following

   the installation instructions in the manual.

Additional reference words: prodtcp32 1.00 err msg

KBCategory: kbnetwork kbfasttip

KBSubCategory: ntprotocol NTTCP


Shiva Remote 3.1.0 and TCP/IP-32

Article ID: Q119375

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft TCP/IP-32

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SUMMARY

=======

The ODI drivers (DIALODI) that are provided with Shiva Remote version 3.1.0

do not work with Microsoft TCP/IP-32. The Shiva Remote NDIS driver

(SDIALIN) does function properly with TCP/IP-32.

MORE INFORMATION

================

When a system is configured using Microsoft TCP/IP-32 and Shiva's DIALODI

driver, you will only be able to PING the loopback address (127.0.0.1) and

the workstation's own IP Address. PING will fail with all other addresses.

In order for Shiva Remote to function properly with TCP/IP-32, the Shiva

NDIS driver must be used.

For additional information on Shiva Remote, call Shiva Technical Support at

(617) 270-8400.

Shiva Remote is manufactured by Shiva, a vendor independent of Microsoft;

we make no warranty, implied or otherwise, regarding this product's

performance or reliability.

Additional reference words: prodtcp32 1.00

KBCategory: kbnetwork kbfasttip

KBSubCategory: ntprotocol NTTCP


Microsoft TCP/IP-32 and Sockets Support

Article ID: Q119466

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft TCP/IP-32

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SUMMARY

=======

The only supported interface for Microsoft TCP/IP-32 for Windows for

Workgroups version 3.11 is Windows Sockets version 1.1. Support for

previous versions of the Sockets specification is not provided. In

addition, there is no support provided for Raw Sockets (SOCK_RAW), DOS

Sockets, or vendor-specific socket implementations.

MORE INFORMATION

================

The Windows Sockets application programming interface (API) was developed

to provide a standard application interface to different vendors protocol

implementations. The official name for the dynamic-link library (DLL) used

for Windows Sockets 1.1 support is WINSOCK.DLL. Previous DLL versions that

were distributed with Microsoft LAN Manager (for example, WIN_SOCK.DLL and

WSOCKETS.DLL) are not supported by Microsoft TCP/IP-32. In order for a

Windows Sockets application to function with Microsoft TCP/IP-32, the

application must support Windows Sockets version 1.1 (WINSOCK.DLL).

Additional reference words: prodtcp32 1.00

KBCategory: kbnetwork kbfasttip

KBSubCategory: ntprotocol nttcp


Creating a Boot Disk for an NTFS Partition

Article ID: Q119467

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

----------------------------------------------------------------------

SUMMARY

=======

This article describes how to create a boot disk to access a drive with a

faulty boot sequence and an NTFS file system. This can be useful when an

incorrect hardware driver replaced a working one and there is no Emergency

Repair Disk to repair the boot files.

MORE INFORMATION

================

To create a boot disk for an NTFS partition:

1. Use the diskcopy utility to copy the Setup Installation disk.

2. Copy NTLDR from the Windows NT CD-ROM disc or floppy disks, and name it

   SETUPLDR on the disk. (You may need to expand this file from NTLDR._ to

   NTLDR by using the EXPAND NTLDR._ NTLDR command line)

3. Copy NTDETECT.COM to the disk.

4. Copy the correct device driver for the required SCSI device to the disk

   if it is not already on the disk or if is the incorrect version. (This

   may be something such as ARROW.SYS). Copy this file to NTBOOTDD.SYS.

5. Create a BOOT.INI file with the following lines: (This example is for a

   single partition SCSI drive with Windows NT installed under \WINNT.)

      [boot loader]

      timeout=30

      Default=SCSI(0)disk(0)rdisk(0)partition(1)\winnt

      [operating systems]

      SCSI(0)disk(0)rdisk(0)partition(1)\winnt="Windows NT"

The following files are usually set with their attributes as System,

Hidden, Read Only.

   Boot.ini

   NTLDR

   NTDETECT.COM

You do not need to reset these attributes for this disk to work properly.

If you run out of space on the disk, remove driver files that you will not

be needing.

Boot from the floppy disk and logon to Windows NT.

Troubleshooting

---------------

 - The following message appears when the path to the system files is

   incorrect or includes the drive letter:

      Windows NT could not start because of the following ARC firmware boot

      configuration problem: Did not properly generate ARC name for HAL and

      system paths. Please check the Windows NT (TM) documentation about

      ARC configuration options and your hardware reference manuals for

      additional information. Boot Failed.

 - The following message appears when the incorrect SCSI driver has been

   selected for the system or the NTBOOTDD.SYS does not exist:

      Windows NT could not start because of a computer disk hardware

      configuration problem. Could not read from selected boot disk. Check

      boot path and disk hardware. Please check the Windows NT (TM)

      documentation about hardware disk configuration and your hardware

      disk configuration and your hardware reference manuals for additional

      information. Boot Failed.

Additional reference words: prodnt 3.10

KBCategory: kbother kbfasttip

KBSubCategory: ntfilesys


TCP/IP-32: ARP -S Switch Fails on First Entry Added to ARP Cache

Article ID: Q120016

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft TCP/IP-32

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SYMPTOMS

========

With Microsoft TCP/IP-32, when you attempt to add the first Address

Resolution Protocol (arp) entry into an empty arp cache using the arp -s

switch, it will appear to function correctly, but the entry will fail to

load if you provide only the first two parameters. For example, when you

execute the command:

   arp -s 22.101.33.237 08-00-2b-2e-98-b3

it will appear to have been added, but when you interogate the protocol

data by executing the command:

   ARP -a

you will receive no results, indicating the arp cache is still empty.

WORK AROUND

===========

You can work around this problem by providing all three of the arp -s

parameters when adding an initial entry into an empty arp cache.

After the following complete arp -s initial arp cache entry:

   arp -s 22.101.33.236 08-00-2b-30-d1-e0 22.101.33.237

the following results would be reported from the arp cache using arp -a:

Interface: 22.101.33.237

  Internet Address       Physical Address          Type

  22.101.33.236          08-00-2b-30-d1-e0         Static

NOTE: To get a complete description of arp switches and parameters, at the

command prompt type "arp" (without the quotation marks) and press ENTER.

STATUS

======

Microsoft has confirmed this to be a problem in MS TCP/IP-32. We are

researching this problem and will post new information in the Microsoft

Knowledge Base as it becomes available.

Additional reference words: prodtcp32 1.0 wfwg wfw

KBCategory: kbnetwork kbbug1.00 kbfasttip

KBSubCategory: ntprotocol NTTCP


Network DDE Applications Fail with TCP/IP-32

Article ID: Q120122

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft TCP/IP-32

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SYMPTOMS

========

Network DDE Windows-based applications (like File Manager) fail to operate

successfully between Windows for Workgroups workstations configured with

TCP/IP-32 when they are in different sub-nets connected by routers. The

following error message appears:

   The computer name specified in the network path cannot be located

You can observe workstations with a protocol analyzer. Unsuccessful

Name Query requests broadcasted to the local sub-net are transmitted by

workstations to resolve the name of the workstation in question:

"computername   <1F>".

The NET USE command functions correctly.

CAUSE

=====

The NetBIOS naming table on the workstation does not include the name

required by Network DDE for computer names specified in the LMHOSTS file.

This problem only occurs under TCP/IP-32 if you do not use the #PRE

keyword.

When a name entry is parsed from the LMHOSTS file, three entries are added

to the workstation's NetBIOS naming table. These are added to provide the

computer name, messenger, and server functionality:

   computername   00h

   computername   01h

   computername   20h

   computername   03h

RESOLUTION

==========

TCP/IP-16 Real Mode

-------------------

Use the ADDNAME2 keyword available from the LAN Manager resource kit. The

following syntax adds an additional entry which can then be saved to the

LMHOSTS file:

   addname2 "computername   " /p0x1f

The entire length of the name must be 16 characters including the hidden

character (1f) in the 16th place. You must pad the computer name with

spaces so that it equals 15 characters in length.

TCP/IP-32 for Windows for Workgroups 3.11

-----------------------------------------

TCP/IP-32 can add the required NetBIOS name to a workstation's LMHOSTS file

if you use the #PRE keyword:

   ipaddr computername #pre

   ipaddr "computername   \0x1F" #pre

NOTE: As in ADDNAME2 above, the computer name must equal 16 characters in

length. The #PRE keyword is optional for the second entry above. #PRE

speeds up resolution of the Network DDE name which helps to provide

a successful connection accross routers providing a dialup or delayed

remote link.

Additional reference words: prodtcp32 1.0 W_WFW WFWG  NetDDE Chat LMhosts

KBCategory: kbnetwork kbbug1.00 kbfasttip

KBSubCategory: ntprotocol nttcp


IBM Token Ring Adapter Problems with Base I/O Address

Article ID: Q120575

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

----------------------------------------------------------------------

SYMPTOMS

========

When installing two IBM Token Ring network cards, the following event

message appears in Event Viewer:

   Event ID: 5012, Source: IbmTok01, Type: Error

   Description: The I/O base address supplied does not match jumpers

   on adapter.

CAUSE

=====

The IBM Token Ring network adapter driver, IBMTOK.SYS, is looking for

specific Primary and Secondary Base I/O addresses which must match the

switches set on the adapter (Switch 9).

RESOLUTION

==========

Configure the Base I/O ROM addresses and corresponding switches listed

below on the adapter for the following switch 9 positions:

   Switch 9           Base I/O Address   Base I/O Switches

   (Position)         (Size = 8K)

   -------------------------------------------------------

   Primary            CC00               1, 4, 5 - up

   (Switch 9 = up)                       2, 3, 6 - down

   Secondary          DC00               1, 3, 4, 5 - up

   (Switch 9 = down)                     2, 6 - down

NOTE: Although the adapter supports other base I/O addresses, the IBM Token

Ring driver supplied with Windows NT only supports the addresses of CC00

and DC00. If either of these addresses conflict with other installed base

I/O addresses, reconfigure other adapters in order to accommodate the

required I/O base addresses of the IBM Token Ring driver. This adapter

reserves two separate address ranges - One for base I/O and one for Shared

RAM. Make sure that these two address ranges do not overlap by using the

WinMSD utility.

MORE INFORMATION

================

Dip-switch settings for the IBM Token Ring adapter are:

   Switches 1-6     Base I/O ROM Address

   Switches 7,8     Interrupt Level (valid interrupts are 2, 3, 6, 7)

   Switches 9       Primary / Secondary adapter

   Switches 10,11   Shared RAM Size 8K , 16K, 32K, 64K

                    Shared RAM size addresses are reserved as follows:

                    - Primary adapter (Switch 9 = up) starts at D0000.

                    - Secondary adapter (Switch 9 = down) starts at E0000.

                    Listed below is a Length and Size equivalency chart:

                    Length        Size

                    ------------------

                    0x2000         8K

                    0x4000        16K

                    0x8000        32K

                    0x10000       64K

   Switches 12      4Mbs / 16Mbs network

The IBM products included here are manufactured by a vendor independent of

Microsoft; we make no warranty, implied or otherwise, regarding these

products' performance or reliability.

Additional reference words: 3.10

KBCategory: kbhw kb3rdparty kbfasttip

KBSubCategory: nthw ntdriver


Detection of Duplicate IP Addresses by Microsoft TCP/IP

Article ID: Q120599

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

 - Microsoft Lan Manager 2.2 and later

 - Microsoft Windows for Workgroups version 3.11

 - Microsoft TCP/IP-32

NOTE: This article applies to all Microsoft TCP/IP network protocols.

----------------------------------------------------------------------

SUMMARY

=======

The TCP/IP protocol may fail to start if another system using the same IP

address is detected on the network. All the TCP/IP protocols currently

shipping (as of 9/20/94) can detect duplicate IP addresses in most cases.

The following information details how this happens and how to recognize

duplicate addresses in a network trace.

MORE INFORMATION

================

Each computer running TCP/IP uses a cache that contains mappings between IP

addresses and media access control (MAC) or network adapter addresses on

the network. The cache is maintained by the address resolution protocol

(ARP) and is dynamic. When a connection attempt is made from one computer

to another, the calling computer looks in its ARP cache for the target

computer's IP/MAC address entry, and then builds an outgoing frame directed

to the MAC address of the target computer.

If the target computer's IP address is not in the cache, the calling system

broadcasts an ARP frame onto the network. The ARP frame contains the IP

address of the target computer, and requests its MAC address. If the target

computer exists on the local sub-net then an ARP reply will be returned to

the calling computer, which updates its cache accordingly. The cache must

contain correct mappings for communications to function.

At system startup, when the IP protocol initializes, it sends an ARP

request containing its own MAC and IP address so that other computers can

update their ARP caches. If there is already a computer using the IP

address, the "older" computer will respond with an ARP reply containing its

MAC and IP address, indicating a conflict. Unfortunately, many other

computers may have already updated their ARP caches with the new mapping.

At that point, the "younger" computer that is initializing needs to do two

things:

   1. Repair the ARP cache on all affected computers.

   2. Cease using the duplicate address.

Computers running Microsoft TCP/IP will send out a new ARP broadcast to re-

map the ARP cache on all affected computers. This new ARP will contain the

MAC address and IP address of the older owner of the IP address. After

sending this ARP, the IP protocol on the younger machine will report the

problem to the user and the stack will shut down. The stack should not be

re-started until a unique address is obtained. Note that the computer may

still function at this point if another protocol such as NetBEUI is loaded.

Below is a network trace illustrating this behavior. It was captured on a

Token Ring network.

Network Trace Illustrating Handling of Duplicate IP Addresses

-------------------------------------------------------------

1. At IP protocol startup, an ARP package is sent by the younger computer:

Frame  Time    Src MAC Addr  Dst MAC Addr   Protocol  Description

1      1.166   4000DDDD1111  BROADCAST      ARP_RARP  ARP: Request,

                                                      Target IP: 11.1.9.221

+ FRAME: Base frame properties

  TOKENRING: Length =  50, Priority Normal (No token) LLC Frame

    + TOKENRING: Access control = 24 (0x18) Repeated, Frame, Priority:

      Normal (No token)

    + TOKENRING: Frame control = 64 (0x40), LLC Frame

    + TOKENRING: Destination address : FFFFFFFFFFFF

    + TOKENRING: Source address      : 4000DDDD1111

      TOKENRING: Frame length : 50 (0x0032)

      TOKENRING: Tokenring data: Number of data bytes remaining = 36

                 (0x0024)

+ LLC: UI DSAP=0xAA SSAP=0xAA C

+ SNAP: ETYPE = 0x0806

  ARP_RARP: ARP: Request, Target IP: 11.1.9.221

      ARP_RARP: Hardware Address Space = 6 (0x6)

      ARP_RARP: Protocol Address Space = 2048 (0x800)

      ARP_RARP: Hardware Address Length = 6 (0x6)

      ARP_RARP: Protocol Address Length = 4 (0x4)

      ARP_RARP: Opcode = 1 (0x1)

      ARP_RARP: Sender's Hardware Address = 4000DDDD1111

      ARP_RARP: Sender's Protocol Address = 11.1.9.221

      ARP_RARP: Target's Hardware Address = FFFFFFFFFFFF

      ARP_RARP: Target's Protocol Address = 11.1.9.221

2. The older computer already using that address responds directly to the

   younger computer with an ARP reply:

Frame  Time    Src MAC Addr  Dst MAC Addr   Protocol  Description

2      1.166   APRICT093738  4000DDDD1111   ARP_RARP  ARP: Reply, Target

                                                      IP: 11.1.9.221 Target

                                                      Hdwr Addr:

                                                      4000DDDD000

+ FRAME: Base frame properties

  TOKENRING: Length =  50, Priority Normal (No token) LLC Frame

    + TOKENRING: Access control = 16 (0x10) Original, Frame, Priority:

      Normal (No token)

    + TOKENRING: Frame control = 64 (0x40), LLC Frame

    + TOKENRING: Destination address : 4000DDDD1111

    + TOKENRING: Source address      : 0000C9093951

      TOKENRING: Frame length : 50 (0x0032)

      TOKENRING: Tokenring data: Number of data bytes remaining = 36

                 (0x0024)

+ LLC: UI DSAP=0xAA SSAP=0xAA C

+ SNAP: ETYPE = 0x0806

  ARP_RARP: ARP: Reply, Target IP: 11.1.9.221 Target Hdwr Addr:

                 4000DDDD1111

      ARP_RARP: Hardware Address Space = 6 (0x6)

      ARP_RARP: Protocol Address Space = 2048 (0x800)

      ARP_RARP: Hardware Address Length = 6 (0x6)

      ARP_RARP: Protocol Address Length = 4 (0x4)

      ARP_RARP: Opcode = 2 (0x2)

      ARP_RARP: Sender's Hardware Address = 0000C9093951

      ARP_RARP: Sender's Protocol Address = 11.1.9.221

      ARP_RARP: Target's Hardware Address = 4000DDDD1111

      ARP_RARP: Target's Protocol Address = 11.1.9.221

3. The younger computer realizes its mistake, and broadcasts a corrective

   ARP to map all ARP caches back to the MAC address of the older computer:

Frame  Time    Src MAC Addr   Dst MAC Addr  Protocol  Description

3      1.168   4000DDDD1111   BROADCAST     ARP_RARP  ARP: Request,

                                                      Target IP: 11.1.9.221

+ FRAME: Base frame properties

  TOKENRING: Length =  50, Priority Normal (No token) LLC Frame

    + TOKENRING: Access control = 24 (0x18) Repeated, Frame, Priority:

                 Normal (No token)

    + TOKENRING: Frame control = 64 (0x40), LLC Frame

    + TOKENRING: Destination address : FFFFFFFFFFFF

    + TOKENRING: Source address      : 4000DDDD1111

      TOKENRING: Frame length : 50 (0x0032)

      TOKENRING: Tokenring data: Number of data bytes remaining = 36

                 (0x0024)

+ LLC: UI DSAP=0xAA SSAP=0xAA C

+ SNAP: ETYPE = 0x0806

  ARP_RARP: ARP: Request, Target IP: 11.1.9.221

      ARP_RARP: Hardware Address Space = 6 (0x6)

      ARP_RARP: Protocol Address Space = 2048 (0x800)

      ARP_RARP: Hardware Address Length = 6 (0x6)

      ARP_RARP: Protocol Address Length = 4 (0x4)

      ARP_RARP: Opcode = 1 (0x1)

      ARP_RARP: Sender's Hardware Address = 0000C9093951    <----|

      ARP_RARP: Sender's Protocol Address = 11.1.9.221      <----|

      ARP_RARP: Target's Hardware Address = FFFFFFFFFFFF         |

      ARP_RARP: Target's Protocol Address = 11.1.9.221           |

                                                                 |

                                                                 |

                   Here the IP address gets mapped back to the older

                   computer's MAC address.

Additional reference words: 3.10

KBCategory: kbnetwork kbfasttip

KBSubCategory: nttcp


TCP/IP & NBT Configuration Parameters for Windows NT 3.5

Article ID: Q120642

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SUMMARY

=======

The TCP/IP protocol suite implementation for Windows NT version 3.5 reads

all of its configuration data from the registry. This information is

written to the registry by the Network Control Panel Applet (NCPA) as part

of the setup process. Some of this information is also supplied by the

Dynamic Host Configuration Protocol (DHCP) client service if it is enabled.

This document defines all of the registry parameters used to configure the

two protocol suite drivers:

 - TCPIP.SYS, which implements the standard TCP/IP network protocols

 - NETBT.SYS, which implements NetBIOS-over-TCP/IP (NBT) as defined by

   RFCs 1001 and 1002

The implementation of the protocol suite should perform properly and

efficiently in most environments using only the configuration information

gathered by the NCPA and DHCP. Optimal default values for all other

configurable aspects of the protocols have been encoded into the drivers.

There may be some unusual circumstances in certain installations in which

changes to certain default values are appropriate. To handle these cases,

you can create optional registry parameters to modify the default behavior

of some parts of the protocol drivers.

MORE INFORMATION

================

WARNING: Using Registry Editor incorrectly can cause serious, system-wide

problems that may require you to reinstall Windows NT to correct them.

Microsoft cannot guarantee that any problems resulting from the use of

Registry Editor can be solved. Use this tool at your own risk.

To change these parameters, use the following procedure:

1. Open the Registry Editor (REGEDT32.EXE).

2. Traverse the registry to

        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.

3. Add a value to the key described in the appropriate entry below, by

   selecting "Edit -> Add Value", typing in the value, and using the

   "Data Type" checkbox to set the value type.

4. Select "OK."

5. Exit the Registry Editor.

6. Reboot the system to make the change take effect.

--------------------------------------------------------------

            TCP/IP Configuration Parameters

--------------------------------------------------------------

All of the TCP/IP parameters are registry values located under one of

two different subkeys of

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services:

   Tcpip\Parameters

   <Adapter Name>\Parameters\Tcpip

where <Adapter Name> refers the subkey for a network adapter to which

TCP/IP is bound, such as Lance01. Values under the latter key(s) are

specific to each adapter. There may (or may not be) parameters which

can have both a DHCP and a statically configured value; it depends on

whether the system/adapter is DHCP configured and/or static override

values have been specified. You must reboot the system for changes in any

of these parameters to take effect.

*** Standard Parameters Configurable in the Registry Editor ***

These parameters are installed with default values by the NCPA during the

installation of the TCP/IP components. You can modify them using the

Registry Editor (REGEDT32.EXE).

DatabasePath

Key: Tcpip\Parameters

Value Type: REG_EXPAND_SZ - Character string

Valid Range: A valid NT file path

Default: %SystemRoot%\system32\drivers\etc

Description:

      This parameter specifies the path to the standard internet

      database files (hosts, lmhosts, networks, protocols). It is used

      by the Windows Sockets interface.

ForwardBroadcasts

Key: Tcpip\Parameters

Value Type: REG_DWORD - Boolean

Valid Range: 0 or 1 (False or True)

Default: 0 (False)

Description:

      Forwarding of broadcasts is not supported. This parameter is

      ignored.

UseZeroBroadcast

Key: <Adapter Name>\Parameters\Tcpip

Value Type: REG_DWORD - Boolean

Valid Range: 0 or 1 (False or True)

Default: 0 (False)

Description:

      If this parameter is set to 1 (True), then IP uses zeros-flavored

      broadcasts instead of ones-flavored. The ones-flavored local

      broadcast address is 255.255.255.255 while the zeros-flavored is

      0.0.0.0. Most systems use ones-flavored broadcasts, but some

      systems derived from BSD implementations use zeros-flavored. Systems

      which use different flavors do not interoperate well on the same

      network.

*** Optional Parameters Configurable in the Registry Editor ***

These parameters normally do not exist in the registry. You can create

them to modify the default behavior of the TCP/IP protocol driver.

ArpUseEtherSNAP

Key: Tcpip\Parameters

Value Type: REG_DWORD - Boolean

Valid Range: 0,1 (False or True)

Default: 0 (False)

Description:

      Setting this parameter to 1 forces TCP/IP to transmit Ethernet

      packets using 802.3 SNAP encoding. By default, the stack transmits

      packets in DIX Ethernet format. It always receives both formats.

DefaultTOS

Key: Tcpip\Parameters

Value Type: REG_DWORD - Number

Valid Range: 0 - 255

Default: 0

Description:

      Specifies the default Type Of Service (TOS) value set in the

      header of outgoing IP packets. See RFC 791 for a definition of the

      values.

DefaultTTL

Key: Tcpip\Parameters

Value Type: REG_DWORD - Number of seconds/hops

Valid Range: 1-255

Default: 32

Description:

      Specifies the default Time To Live (TTL) value set in the header

      of outgoing IP packets. The TTL determines the maximum amount of

      time an IP packet may live in the network without reaching its

      destination. It is effectively a bound on the number of routers an

      IP packet may pass through before being discarded.

EnableDeadGWDetect

Key: Tcpip\Parameters

Value Type: REG_DWORD - Boolean

Valid Range: 0,1 (False, True)

Default: 1 (True)

Description:

      Setting this parameter to 1 causes TCP to perform dead gateway

      detection: TCP asks IP to change to a backup gateway if it

      retransmits a segment several times without receiving a response.

      You can define backup gateways in the Advanced section of the TCP/IP

      configuration dialog in the Network Control Panel Applet.

EnablePMTUBHDetect

Key: Tcpip\Parameters

Value Type: REG_DWORD - Boolean

Valid Range: 0,1 (False, True)

Default: 0 (False)

Description:

      Setting this parameter to 1 (True) causes TCP to try to detect

      "black hole" routers while doing path MTU Discovery. A black hole

      router does not return "ICMP destination unreachable" messages when

      it needs to fragment a TCP packet with the Don't Fragment bit

      set. TCP depends on receiving these messages to perform path MTU

      discovery. With this feature enabled, TCP tries to send segments

      without the Don't Fragment bit set if several retransmissions of a

      segment go unacknowledged. If the segment is acknowledged as a

      result, the MSS is decreased and the Don't Fragment bit is set in

      future packets on the connection. Enabling black hole detection

      increases the maximum number of retransmissions performed for a

      given segment.

EnablePMTUDiscovery

Key: Tcpip\Parameters

Value Type: REG_DWORD - Boolean

Valid Range: 0,1 (False, True)

Default:  1 (True)

Description:

      Setting this parameter to 1 (True) causes TCP to attempt to

      discover the maximum transmission unit (MTU or largest packet

      size) over the path to a remote machine. By discovering the path

      MTU and limiting TCP segments to this size, TCP can eliminate

      fragmentation at routers along the path which connect networks

      with different MTUs. Fragmentation adversely affects TCP throughput

      and causes network congestion.

ForwardBufferMemory

Key: Tcpip\Parameters

Value Type: REG_DWORD - Number of bytes

Valid Range: <network MTU>  - <some reasonable value smaller than

0xFFFFFFFF >

Default: 74240 (enough for fifty 1480-byte packets, rounded to a multiple

         of 256)

Description:

      This parameter determines how much memory IP allocates to store

      packet data in the router packet queue. When this buffer space is

      filled, the router begins discarding packets at random from its

      queue. Packet queue data buffers are 256 bytes, so the value of this

      parameter should be a multiple of 256. Multiple buffers are chained

      together for larger packets. The IP header for a packet is stored

      separately. This parameter is ignored and no buffers are allocated if

      the IP router is not enabled.

IGMPLevel   REG_DWORD

Key: Tcpip\Parameters

Value Type: REG_DWORD - Number

Valid Range: 0,1,2

Default: 2

Description:

      This parameter determines to what extent the system supports IP

      multicasting and participates in the Internet Group Management

      Protocol. At level 0, the system provides no multicast support. At

      level 1, the system can only send IP multicast packets. At level

      2, the system can send IP multicast packets and fully participate

      in IGMP to receive multicast packets.

KeepAliveInterval

Key: Tcpip\Parameters

Value Type: REG_DWORD - Time in milliseconds

Valid Range: 1 - 0xFFFFFFFF

Default: 1000 (one second)

Description:

      This parameter determines the interval separating keep alive

      retransmissions until a response is received. Once a response is

      received, the delay until the next keep-alive transmission is again

      controlled by the value of KeepAliveTime. The connection is aborted

      after the retransmissions specified by TcpMaxDataRetransmissions

      have gone unanswered.

KeepAliveTime

Key: Tcpip\Parameters

Value Type: REG_DWORD - Time in milliseconds

Valid Range: 1 - 0xFFFFFFFF

Default: 7,200,000 (two hours)

Description:

      The parameter controls how often TCP attempts to verify that an

      idle connection is still intact by sending a keep-alive packet. If

      the remote system is still reachable and functioning, it acknowledges

      the keep-alive transmission. Keep-alive packets are not sent by

      default. An application may enable this feature on a connection.

NumForwardPackets

Key: Tcpip\Parameters

Value Type: REG_DWORD Number

Valid Range: 1 - <some reasonable value smaller than 0xFFFFFFFF>

Default: 50

Description:

      This parameter determines the number of IP packet headers which

      are allocated for the router packet queue. When all headers are in

      use, the router will begin to discard packets at random from the

      queue. This value should be at least as large as the

      ForwardBufferMemory value divided by the maximum IP data size of

      the networks connected to the router. It should be no larger than

      the ForwardBufferMemory value divided by 256, since at least 256

      bytes of forward buffer memory are used for each packet. The

      optimal number of forward packets for a given ForwardBufferMemory

      size depends on the type of traffic carried on the network and

      is somewhere in between these two values. This parameter is

      ignored and no headers are allocated if the router is not enabled.

TcpMaxConnectRetransmissions

Key: Tcpip\Parameters

Value Type: REG_DWORD - Number

Valid Range: 0 - 0xFFFFFFFF

Default: 3

Description:

      This parameter determines the number of times TCP retransmits

      a connect request (SYN) before aborting the attempt. The

      retransmission time-out is doubled with each successive

      retransmission in a given connect attempt. The initial time-out

      value is three seconds.

TcpMaxDataRetransmissions

Key: Tcpip\Parameters

Value Type: REG_DWORD - Number

Valid Range: 0 - 0xFFFFFFFF

Default: 5

Description:

      This parameter controls the number of times TCP retransmits an

      individual data segment (non-connect segment) before aborting the

      connection. The retransmission time-out is doubled with each

      successive retransmission on a connection, and is reset when

      responses resume. The base time-out value is dynamically determined

      by the measured round-trip time on the connection.

TcpNumConnections

Key: Tcpip\Parameters

Value Type: REG_DWORD - Number

Valid Range: 0 - 0xfffffe

Default: 0xfffffe

Description:

      This parameter limits the maximum number of connections that TCP

      may have open simultaneously.

TcpUseRFC1122UrgentPointer

Key: Tcpip\Parameters

Value Type: REG_DWORD  - Boolean

Valid Range: 0,1 (False, True)

Default: 0 (False)

Description:

      This parameter determines whether TCP uses the RFC 1122 specification

      for urgent data or the mode used by BSD-derived systems. The two

      mechanisms interpret the urgent pointer in the TCP header and the

      length of the urgent data differently. They are not interoperable.

      Windows NT 3.5 defaults to BSD mode--a change from Windows NT 3.1.

TcpWindowSize

Key: Tcpip\Parameters

Value Type: REG_DWORD - Number of bytes

Valid Range: 0 - 0xFFFF

Default:

The smaller of:

      0xFFFF OR

The larger of:

      four times the maximum TCP data size on the network OR 8192 rounded

      up to an even multiple of the network TCP data size. The default is

      8760 for Ethernet.

Description:

      This parameter determines the maximum TCP receive window size

      offered by the system, which specifies the number of bytes a sender

      can transmit without receiving an acknowledgment. In general, larger

      receive windows improve performance over high (delay * bandwidth )

      networks. For maximum efficiency, the receive window should be an

      even multiple of this quantity:

         (underlying network MTU) - (40 bytes)

      NOTE: 40 bytes is standard TCP and IP header size.

*** Parameters Configurable through the NCPA ***

These parameters are created and modified automatically by the NCPA as a

result of user-supplied information. There should be no need to configure

them directly.

DefaultGateway

Key: <AdapterName>\\Parameters\Tcpip

Value Type: REG_MULTI_SZ - List of dotted decimal IP addresses

Valid Range: Any set of valid IP addresses

Default: None

Description:

      This parameter specifies the list of gateways to be used to route

      packets not destined for a subnet to which the machine is directly

      connected and for which a more specific route does not exist. This

      parameter, if it has a valid value, overrides the

      DhcpDefaultGateway parameter.

Domain

Key: Tcpip\Parameters

Value Type: REG_SZ - Character string

Valid Range: Any valid DNS domain name

Default: None

Description:

      This parameter specifies the DNS domain name of the system. It is

      used by the Windows Sockets interface.

EnableDhcp

Key: <Adapter Name>\Parameters\Tcpip

Value Type: REG_DWORD - Boolean

Valid Range:  0 or 1 (False or True)

Default: 0 (False)

Description:

      If this parameter is set to 1 (True), then the DHCP client

      service attempts to configure the first IP interface on the

      adapter using DHCP.

Hostname

Key: Tcpip\Parameters

Value Type: REG_SZ - Character string

Valid Range: Any valid DNS hostname

Default: The computername of the system

Description:

      This parameter specifies which DNS hostname of the system is

      returned by the "hostname" command.

IPAddress

Key: <Adapter Name>\Parameters\Tcpip

Value Type: REG_MULTI_SZ - List of dotted-decimal IP addresses

Valid Range: Any set of valid IP addresses

Default: None

Description:

      This parameter specifies the IP addresses of the IP interfaces to

      be bound to the adapter. If the first address in the list is

      0.0.0.0, then the primary interface on the adapter is configured

      through DHCP. A system with more than one IP interface for

      an adapter is called "logically multihomed." There must be a

      valid subnet mask value in the SubnetMask parameter for each IP

      address specified in this parameter.

IPEnableRouter

Key: Tcpip\Parameters

Value Type: REG_DWORD - Boolean

Valid Range: 0 or 1 (False or True)

Default: 0 (False)

Description:

      Setting this parameter to 1 (True) causes the system to route IP

      packets between the networks to which it is connected.

NameServer

Key: Tcpip\Parameters

Value Type: REG_SZ - A space delimited list of dotted decimal IP addresses

Valid Range: Any set of valid IP address

Default: None (Blank)

Description:

      This parameter specifies the DNS name servers to be queried by

      Windows Sockets to resolve names.

SearchList

Key: Tcpip\Parameters

Value Type: REG_SZ - Space delimited list of DNS domain name suffixes

Valid Range: Any set of valid DNS domain name suffixes

Default: None

Description:

      This parameter specifies a list of domain name suffixes to append

      to a name to be resolved through the DNS if resolution of the

      unadorned name fails. By default, the value of the Domain parameter

      is appended only. This parameter is used by the Windows Sockets

      interface.

SubnetMask

Key: <Adapter Name>\Parameters\Tcpip

Value Type: REG_MULTI_SZ - List of dotted decimal IP addresses

Valid Range: Any set of valid IP addresses.

Default: None

Description:

      This parameter specifies the subnet masks to be used with the IP

      interfaces bound to the adapter. If the first mask in the list is

      0.0.0.0, then the primary interface on the adapter is configured

      through DHCP. There must be a valid subnet mask value in this

      parameter for each IP address specified in the IPAddress parameter.

*** Non-Configurable Parameters ***

These parameters are created and used internally by TCP/IP components.

NEVER MODIFY THEM USING THE REGISTRY EDITOR. They are listed here for

reference only.

DhcpDefaultGateway

Key: <Adapter Name>\Parameters\ Tcpip

Value Type: REG_MULTI_SZ - List of dotted decimal IP addresses

Valid Range: Any set of valid IP addresses

Default: None

Description:

      This parameter specifies the list of default gateways to be used

      to route packets not destined for a subnet to which the machine is

      directly connected and for which a more specific route does not

      exist.  This parameter is written by the DHCP client service, if

      enabled. This parameter is overridden by a valid DefaultGateway

      parameter value.

DhcpIPAddress

Key: <Adapter Name>\Parameters\Tcpip

Value Type: REG_SZ - Dotted decimal IP address

Valid Range: Any valid IP address

Default: None

Description:

      This parameter specifies the DHCP-configured IP address for the

      interface. If the IPAddress parameter contains a first value other

      than 0.0.0.0, that value overrides this parameter.

DhcpNameServer

Key: Tcpip\Parameters

Value Type: REG_SZ - A space delimited list of dotted decimal IP addresses

Valid Range: Any set of valid IP address

Default: None

Description:

      This parameter specifies the DNS name servers to be queried by

      Windows Sockets to resolve names. It is written by the DHCP client

      service, if enabled. If the NameServer parameter has a valid value,

      it overrides this parameter.

DhcpServer

Key: <Adapter Name>\Parameters\Tcpip

Value Type: REG_SZ - Dotted decimal IP address

Valid Range: Any valid IP address

Default: None

Description:

      This parameter specifies the IP address of the DHCP server that

      granted the lease on the IP address in the DhcpIPAddress parameter.

DhcpSubnetMask

Key: <Adapter Name>\Parameters\Tcpip

Value Type: REG_SZ - Dotted decimal IP subnet mask

Valid Range: Any subnet mask which is valid for the configured IP address

Default: None

Description:

      This parameter specifies the DHCP-configured subnet mask for the

      address specified in the DhcpIPAddress parameter.

IPInterfaceContext

Key: <Adapter Name>\Parameters\Tcpip

Value Type: REG_DWORD

Valid Range: 0 - 0xFFFFFFFF

Default: None

Description:

      This parameter is written by the TCP/IP driver for use by the DHCP

      client service.

Lease

Key: <Adapter Name>\Parameters\Tcpip

Value Type: REG_DWORD - Time in seconds

Valid Range: 1 - 0xFFFFFFFF

Default: None

Description:

      This parameter is used by the DHCP client service to store the

      time in seconds for which the lease on the IP address for this

      adapter is valid.

LeaseObtainedTime

Key: <Adapter Name>\Parameters\Tcpip

Value Type: REG_DWORD - Absolute time in seconds since midnight of 1/1/70

Valid Range: 1 - 0xFFFFFFFF

Default: None

Description:

      This parameter is used by the DHCP client service to store the

      time at which the lease on the IP address for this adapter was

      obtained.

LeaseTerminatesTime

Key: <Adapter Name>\Parameters\Tcpip

Value Type: REG_DWORD - Absolute time in seconds since midnight of 1/1/70

Valid Range: 1 - 0xFFFFFFFF

Default: None

Description:

      This parameter is used by the DHCP client service to store the

      time at which the lease on the IP address for this adapter will

      expire.

LLInterface

Key: <Adapter Name>\Parameters\Tcpip

Value Type: REG_SZ - NT device name

Valid Range: A legal NT device name

Default: Empty string  (Blank)

Description:

      This parameter is used to direct IP to bind to a different link-

      layer protocol than the built-in ARP module. The value of the

      parameter is the name of the NT device to which IP should bind.

      This parameter is in conjunction with the RAS component, for

      example.

T1

Key: <Adapter Name>\Parameters\Tcpip

Value Type: REG_DWORD - Absolute time in seconds since midnight of

1/1/70

Valid Range: 1 - 0xFFFFFFFF

Default: None

Description:

      This parameter is used by the DHCP client service to store the

      time at which the service will first try to renew the lease on the

      IP address for the adapter by contacting the server that granted

      the lease.

T2

Key: <AdapterName>\Parameters\Tcpip

Value Type: REG_DWORD - Absolute time in seconds since midnight of 1/1/70

Valid Range: 1 - 0xFFFFFFFF

Default: None

Description:

      This parameter is used by the DHCP client service to store the

      time at which the service will try to renew the lease on the IP

      address for the adapter by broadcasting a renewal request. Time T2

      should be reached only if the service has been unable to renew the

      lease with the original server for some reason.

--------------------------------------------------------------

            NBT Configuration Parameters

--------------------------------------------------------------

All of the NBT parameters are registry values located under one of two

different subkeys of

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services:

*     Netbt\Parameters

*     Netbt\Adapters\<Adapter Name>

where <Adapter Name> refers the subkey for a network adapter to which

NBT is bound, such as Lance01. Values under the latter key(s) are

specific to each adapter. If the system is configured through DHCP, then

a change in parameters takes effect if the command "ipconfig /renew"

is issued in a command shell. Otherwise, the system has to be rebooted

for a change in any of these parameters to take effect.

*** Standard Parameters Configurable through the Registry Editor ***

These parameters are installed with default values by the NCPA during the

installation of the TCP/IP components. You can modify them using the

Registry Editor (REGEDT32.EXE).

BcastNameQueryCount

Key: Netbt\Parameters

Value Type: REG_DWORD - Count

Valid Range: 1 to 0xFFFF

Default: 3

Description:

      This value determines the number of times NBT broadcasts a query

      for a given name without receiving a response.

BcastQueryTimeout

Key: Netbt\Parameters

Value Type: REG_DWORD - Time in milliseconds

Valid Range: 100 to 0xFFFFFFFF

Default: 0x2ee (750 decimal)

Description:

      This value determines the time interval between successive

      broadcast name queries for the same name.

CacheTimeout

Key: Netbt\Parameters

Value Type: REG_DWORD - Time in milliseconds

Valid Range: 60000 to 0xFFFFFFFF

Default: 0x927c0 (600000 milliseconds = 10 minutes)

Description:

      This value determines how long the remote name table caches names.

NameServerPort

Key: Netbt\Parameters

Value Type: REG_DWORD - UDP port number

Valid Range: 0 - 0xFFFF

Default: 0x89

Description:

      This parameter determines the destination port number to which NBT

      sends name service related packets such as name queries and name

      registrations to WINS. The Microsoft WINS listens on port 0x89.

      NetBIOS Name Servers from other vendors may listen on different

      ports.

NameSrvQueryCount

Key: Netbt\Parameters

Value Type: REG_DWORD - Count

Valid Range: 0 - 0xFFFF

Default: 3

Description:

      This value determines the number of times NBT sends a query to a

      WINS server for a given name without receiving a response.

NameSrvQueryTimeout

Key: Netbt\Parameters

Value Type: REG_DWORD - Time in milliseconds

Valid Range: 100 - 0xFFFFFFFF

Default: 0x5DC (750 milliseconds)

Description:

      This value determines the interval between successive name queries

      to WINS for a given name.

SessionKeepAlive

Key: Netbt\Parameters

Value Type: REG_DWORD - Time in milliseconds

Valid Range: 60,000  - 0xFFFFFFFF

Default: 60,000 (1 hour)

Description:

      This value determines the interval between keep-alive transmissions

      on a session. Setting the value to 0xFFFFFFF disables keep-alives.

Size/Small/Medium/Large

Key: Netbt\Parameters

Value Type: REG_DWORD

Valid Range: 1, 2, 3 (Small, Medium, Large)

Default: 1 (Small)

Description:

      This value determines the size of the name tables used to store

      local and remote names. In general Small is adequate. If the

      system is acting as a proxy nameserver, the value is automatically

      set to Large to increase the size of the name cache hash table.

      Large sets the number of hash buckets to 256, Medium to 128, Small

      to 16.

*** Optional Parameters Configurable through the Registry Editor ***

These parameters normally do not exist in the registry. You can create

them to modify the default behavior of the NBT protocol driver.

BroadcastAddress

Key: Netbt\Parameters

Value Type: REG_DWORD - Four byte, little-endian encoded IP address

Valid Range: 0 - 0xFFFFFFFF

Default:  The ones-flavor subnet broadcast address for each network.

Description:

      This parameter can be used to force NBT to use a specific address

      for all broadcast name related packets. By default, NBT uses the

      ones-flavor subnet broadcast address appropriate for each net

      (that is, for a net of 11.101.0.0 with a mask of 255.255.0.0, the

      subnet broadcast address is 11.101.255.255). This parameter would be

      set, for example, if the network uses the zeros-flavor broadcast

      address (set using the UseZeroBroadcast TCP/IP parameter). The

      appropriate subnet broadcast address would then be 11.101.0.0 in the

      example above. This parameter would then be set to 0x0b650000. Note

      that this parameter is global and is used on all subnets to which

      NBT is bound.

EnableProxyRegCheck

Key: Netbt\Parameters

Value Type: REG_DWORD - Boolean

Valid Range: 0 or 1 (False or True)

Default: 0 (False)

Description:

      If this parameter is set to 1 (True), then the proxy name server

      sends a negative response to a broadcast name registration if

      the name is already registered with WINS or is in the proxy's

      local name cache with a different IP address. The hazard of

      enabling this feature is that it prevents a system from changing

      its IP address as long as WINS has a mapping for the name. For

      this reason it is disabled by default.

InitialRefreshTimeout

Key: Netbt\Parameters

Value Type: REG_DWORD - Time in milliseconds

Valid Range: 960000 - 0xFFFFFFF

Default: 960000 (16 minutes)

Description:

      This parameter specifies the initial refresh time-out used by NBT

      during name registration. NBT tries to contact the WINS servers at

      1/8th of this time interval when it is first registering names.

      A successful registration response contains the new refresh

      interval to use.

LmhostsTimeout

Key: Netbt\Parameters

Value Type: REG_DWORD - Time in milliseconds

Valid Range: 1000 - 0xFFFFFFFF

Default: 6000 (6 seconds)

Description:

      This parameter specifies the time-out value for Lmhosts and DNS

      name queries. The timer has a granularity of the time-out value, so

      the actual time-out could be as much as twice the value.

MaxDgramBuffering

Key: Netbt\Parameters

Value Type: REG_DWORD - Count of bytes

Valid Range: 0 - 0xFFFFFFFF

Default: 0x20000 (128 Kb)

Description:

      This parameter specifies the maximum amount of memory that NBT

      dynamically allocates for all outstanding datagram sends. Once

      this limit is reached, further sends fail due to insufficient

      resources.

NodeType

Key: Netbt\Parameters

Value Type: REG_DWORD - Number

Valid Range: 1,2,4,8 (Bnode, Pnode, Mnode, Hnode)

Default: 1 or 8 based on the WINS server configuration

Description:

      This parameter determines what methods NBT will use to register

      and resolve names.

      A Bnode system uses broadcasts. A Pnode system uses only point-to-

      point name queries to a name server (WINS). An Mnode system

      broadcasts first, then queries the name server. An Hnode system

      queries the name server first, then broadcasts. Resolution through

      Lmhosts and/or DNS, if enabled, follow s these methods. If this key

      is present it overrides the DhcpNodeType key. If neither key is

      present, the system defaults to Bnode if there are no WINS servers

      configured for the network. The system defaults to Hnode if there is

      at least one WINS server configured.

RandomAdapter

Key: Netbt\Parameters

Value Type: REG_DWORD - Boolean

Valid Range: 0 or 1 (False or True)

Default: 0 (False)

Description:

      This parameter applies to a multihomed machine only. If it is set

      to 1 (True), NBT randomly chooses the IP address to put in a name

      query response from all of its bound interfaces. Normally, the

      response contains the address of the interface on which the query

      arrived. This feature is used for load balancing by servers with two

      interfaces on the same network. The SingleResponse parameter must be

      set to a value of 1 (True) for this parameter to take effect.

RefreshOpCode

Key: Netbt\Parameters

Value Type: REG_DWORD - Number

Valid Range: 8, 9

Default: 8

Description:

      This parameter forces NBT to use a specific opcode in name refresh

      packets. The specification for the NBT protocol is somewhat ambiguous

      in this area. Although 8--the Microsoft implementation default--

      appears to be the intended value, other implementations, such as

      those by Ungermann-Bass, use 9. Two implementations must use the

      same opcode to interoperate.

SingleResponse

Key: Netbt\Parameters

Value Type: REG_DWORD - Boolean

Valid Range: 0 or 1 (False or True)

Default: 0 (False)

Description:

      This parameter applies to a multihomed machine only. If this

      parameter is set to 1 (True) NBT supplies only an IP address from

      one of its bound interfaces in name query responses. By default, the

      addresses of all bound interfaces are included. This parameter must

      be set to 1 (True) to enable the RandomAdapter feature.

WinsDownTimeout

Key: Netbt\Parameters

Value Type: REG_DWORD - Time in milliseconds

Valid Range: 1000 - 0xFFFFFFFF

Default: 15,000 (15 seconds)

Description:

      This parameter determines how long NBT waits before again trying to

      use WINS after failing to contact a WINS server. Primarily, this

      allows machines that are temporarily disconnected from the network,

      such as laptops, to proceed through boot processing without waiting

      to time-out out each WINS name registration or query individually.

*** Parameters Configurable through the NCPA ***

These parameters can be set through the NCPA. There should be no need to

configure them directly.

EnableDns

Key: Netbt\Parameters

Value Type: REG_DWORD - Boolean

Valid Range: 0 or 1 (False or True)

Default: 0 (False)

Description:

      If this value is set to 1 (True) NBT queries the DNS for names that

      cannot be resolved by WINS, broadcast, or the Lmhosts file.

EnableLmhosts

Key: Netbt\Parameters

Value Type: REG_DWORD - Boolean

Valid Range: 0 or 1 (False or True)

Default: 1 (True)

Description:

      If this value is set to 1 (True) NBT searches the Lmhosts file

      if it exists, for names that cannot be resolved by WINS or broadcast.

      By default there is no Lmhosts file database directory (specified by

      Tcpip\Parameters\DatabasePath), so no action is taken. This value is

      written by the Advanced TCP/IP configuration dialog of the NCPA.

EnableProxy

Key: Netbt\Parameters

Value Type: REG_DWORD - Boolean

Valid Range: 0 or 1 (False or True)

Default: 0 (False)

Description:

      If this value is set to 1 (True) the system acts as a proxy name

      server for the networks to which NBT is bound. A proxy name server

      answers broadcast queries for names that it has resolved through

      WINS. A proxy nameserver allows a network of Bnode implementations

      to connect to servers on other subnets registered with WINS.

NameServer

Key: Netbt\Adapters\<Adapter Name>

Value Type: REG_SZ - Dotted decimal IP address (such as: 11.101.1.200)

Valid Range: Any valid IP address

Default: blank (no address)

Description:

      This parameter specifies the IP address of the primary WINS

      server. If this parameter contains a valid value, it overrides the

      DHCP parameter of the same name.

NameServerBackup

Key: Netbt\Adapters\<Adapter Name>

Value Type: REG_SZ - Dotted decimal IP address (i.e. 11.101.1.200)

Valid Range: Any valid IP address.

Default: blank ( no address )

Description:

      This parameter specifies the IP address of the backup WINS server.

      If this parameter contains a valid value, it overrides the DHCP

      parameter of the same name.

ScopeId

Key: Netbt\Parameters

Value Type: REG_SZ - Character string

Valid Range: Any valid DNS domain name consisting of two dot-separated

parts, or a "*".

Default: None

Description:

      This parameter specifies the NetBIOS name scope for the node. This

      value must not begin with a period. If this parameter contains a

      valid value, it overrides the DHCP parameter of the same name. Blank

      values (empty strings) are ignored. Setting this parameter to the

      value "*" indicates a null scope and overrides the DHCP parameter.

*** Non-Configurable Parameters ***

These parameters are created and used internally by the NBT components.

NEVER MODIFY THEM WITH THE REGISTRY EDITOR. They are listed here for

reference only.

DhcpNameServer

Key: Netbt\Adapters\<Adapter Name>

Value Type: REG_SZ - Dotted decimal IP address (i.e. 11.101.1.200)

Valid Range: Any valid IP address

Default: None

Description:

      This parameter specifies the IP address of the primary WINS

      server. It is written by the DHCP client service, if enabled. A

      valid NameServer value overrides this parameter.

DhcpNameServerBackup

Key: Netbt\Adapters\<Adapter Name>

Value Type: REG_SZ - Dotted decimal IP address (i.e. 11.101.1.200)

Valid Range: Any valid IP address

Default: None

Description:

      This parameter specifies the IP address of the backup WINS server.

      It is written by the DHCP client service, if enabled. A valid

      BackupNameServer value overrides this parameter.

DhcpNodeType

Key: Netbt\Parameters

Value Type: REG_DWORD - Number

Valid Range: 1 - 8

Default: 1

Description:

      This parameter specifies the NBT node type. It is written by the

      DHCP client service, if enabled. A valid NodeType value overrides

      this parameter. See NodeType for a complete description.

DhcpScopeId

Key: Netbt\Parameters

Value Type: REG_SZ - Character string

Valid Range: a dot separated name string such as "microsoft.com"

Default: None

Description:

      This parameter specifies the NetBIOS name scope for the node. It

      is written by the DHCP client service, if enabled. This value must

      not begin with a period. See ScopeId for more information.

NbProvider = _tcp

Key: Netbt\Parameters

Value Type: REG_SZ - Character string

Valid Range: _tcp

Default: _tcp

Description:

      This parameter is used internally by the RPC component. Do not change

      the default value.

TransportBindName

Key: Netbt\Parameters

Value Type: REG_SZ - Character string

Valid Range: N/A

Default: \Device\

Description:

      This parameter is used internally during product development. Do not

      change the default value.

Additional reference words: prodnt 3.50 tcp ip

KBCategory: kbnetwork kbenv kbfasttip

KBSubCategory: ntregistry nttcp ntprotocol


DHCP (Dynamic Host Configuration Protocol) Basics

Article ID: Q120829

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

 - Microsoft LAN Manager version 2.2C

 - Microsoft TCP/IP-32

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SUMMARY

=======

Dynamic Host Configuration Protocol (DHCP) is a standard for the automatic

configuration of IP hosts, defined in RFC1541. DHCP was designed to reduce

the complexity of IP network administration.

At a minimum, a DHCP server is expected to provide its clients with:

 - Valid IP addresses to "lease"

 - Subnet masks

 - Default gateways

However, much more information may be provided, depending upon the

implementation and the DHCP service administrator.

MORE INFORMATION

================

Windows NT 3.5 supports DHCP as a client or server. Microsoft TCP/IP-32,

Microsoft LAN Manager 2.2C, and Microsoft Client 3.0 all provide DHCP

client support.

Client Details:

During installation of TCP/IP and related services, a TCP/IP configuration

screen appears including an Enable automatic DHCP configuration check box.

If this box is selected, no further TCP/IP configuration is necessary on

the client. However, if any options are specified, they will override DHCP

server default parameters.

Server Details:

The DHCP service is set up using the DHCPADMN program. The administrator

specifies the scope of the server, what subnets it should administer

addresses for and many other configuration parameters. A typical group of

parameters for a network of Windows NT 3.5 computers might be:

 - Ranges of IP addresses to assign for each subnet

 - Subnet masks for each subnet

 - Default gateways for each subnet

 - Default Windows Internet Name Service (WINS) servers

 - Domain Name Servers

 - Default lease times for addresses

The DHCP Process:

The following events take place the first time the network is started:

   Source     Dest        Source     Dest              Packet

   MAC addr   MAC addr    IP addr    IP addr           Description

   -----------------------------------------------------------------

   Client     Broadcast   0.0.0.0    255.255.255.255   DHCP Discover

   DHCPsrvr   Broadcast   DHCPsrvr   255.255.255.255   DHCP Offer

   Client     Broadcast   0.0.0.0    255.255.255.255   DHCP Request

   DHCPsrvr   Broadcast   DHCPsrvr   255.255.255.255   DHCP ACK

First, the client broadcasts a DHCPDISCOVER packet. (Note that the source

IP address for this is 0.0.0.0, as the client has no address at this

point.) In response, the DHCP server sends a DHCPOFFER packet, offering to

configure the client. This must be sent as a broadcast, as the client still

has no IP address of its own. The client chooses which offer to accept, and

broadcasts DHCPREQUEST for that offer. A transaction ID distinguishes

various offers that might have been received.

Finally, the DHCP server broadcasts a DHCPACK packet containing the final

parameters for the client to use. At this point the server marks the

address internally as "in use" and does not offer it to any other clients.

Upon receiving DHCPACK, the client TCP stack finishes configuring itself.

The client stores the configuration as follows:

Windows NT 3.5 (Registry):

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services:

      Network Interface Specific: <adapter>\parameters\Tcpip

      General: DHCP\parameters\Options\*

LAN Manager 2.2c (Hidden Binary File):

   <lanroot>\dhcp.prm

TCP/IP-32 (Hidden Binary File):

   windows\dhcp.bin

When the client reboots, it will attempt to use the previously stored

configuration by sending a DHCPREQUEST broadcast when the network is

starting. The request will include the IP address that was previously

assigned. The DHCP server will attempt to allow the client to retain the

same configuration and respond with DHCPACK if the address is still

available. If the IP address is invalid for the subnet, or already in use

by another client, the server will instead respond with DHCPNAK,

invalidating the client configuration. Upon receipt of DHCPNAK, the client

must restart the configuration process by sending DHCPDISCOVER.

Configurations obtained from a DHCP server are valid for a "lease

time" that is configurable by the administrator. When a lease is about to

expire, a client must approach the DHCP server again with a request for an

extension. The timers for this are discussed in more detail in the RFC.

Note that in order for a DHCP server to have a scope of more than one

subnet, the IP broadcasts shown above must be forwarded by the routers

between those subnets. The routers must provide RFC1542 (BOOTP Relay Agent)

support.

To observe the configuration that has been provided to a client, use the

"IPCONFIG /ALL" command.

Example Configuration:

   c:\tmp>ipconfig /all

   Windows NT IP Configuration Version 1.0

      Host Name . . . . . . . : myhost

      DNS Servers . . . . . . :

      DNS Lookup Order. . . . :

      Node Type . . . . . . . : Hybrid

      NetBIOS Scope ID. . . . :

      IP Routing Enabled. . . : No

      WINS Proxy Enabled. . . : No

      DNS Resolution For Windows Networking Applications : No Ethernet

      adapter Elnk31:

      Physical Address. . . . : 00-20-AF-1D-2B-91

      DHCP Enabled. . . . . . : Yes

      IP Address. . . . . . . : 22.101.101.15

      Subnet Mask . . . . . . : 255.255.0.0

      Default Gateway . . . . : 22.101.0.1

      DHCP Server . . . . . . : 11.1.200.1

      Primary WINS Server . . : 11.1.200.1

      Secondary WINS Server . : 11.1.200.3

      Lease Obtained. . . . . : Fri 16th. Sep 1994  7:54:51 am

      Lease Expires . . . . . : Wed  5th. Oct 1994  7:54:51 am

Reference(s):

For more information on DHCP, see RFC1541. RFCs may be obtained via the

Internet as follows:

Paper copies of all RFCs are available from the NIC, either individually or

on a subscription basis (for more information contact NIC@NIC.DDN.MIL).

Online copies are available via FTP or Kermit from NIC.DDN.MIL as

rfc/rfc####.txt or rfc/rfc####.PS (#### is the RFC number without leading

zeroes).

Additionally, RFCs may be requested through electronic mail from the

automated NIC mail server by sending a message to SERVICE@NIC.DDN.MIL with

a subject line of "rfc ####" for text versions or a subject line of "rfc

####.PS" for PostScript versions. To obtain the RFC index, the subject line

of your message should read "rfc index".

Additional reference words: prodtcp32 RFC1541

KBCategory: kbnetwork kbfasttip

KBSubCategory: nttcp


DHCP: Spanning Multiple Subnets

Article ID: Q120932

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

 - Microsoft TCP/IP-32

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SUMMARY

=======

A DHCP (Dynamic Host Configuration Protocol) server can provide IP

addresses to clients spanning multiple subnets if the router that

separates them can act as an RFC 1542(BOOTP) relay agent. If the router

cannot function as relay agent, each subnet that has DHCP clients requires

a DHCP server.

MORE INFORMATION

================

A relay agent that conforms to RFC 1542 relays DHCP packets to the remote

side even though they are broadcast packets. Before relaying a DHCP message

from a DHCP client, the agent examines the GIADDR (gateway IP address)

field. If the field has an IP address of 0.0.0.0, the agent fills it with

the router's IP address. When the DHCP server receives the message, it

examines the Relay IP Address field to see if it has a DHCP scope (a pool

of IP addresses) that can be used to supply an IP address lease. If the

DHCP server has multiple DHCP scopes, the address in the Relay IP Address

field identifies the DHCP scope from which to offer an IP address lease.

This process allows one DHCP server to manage different scopes for subnets.

You can use a multihomed Windows NT Server 3.5 system configured as a DHCP

server, with multiple network cards and IP routing enabled, instead of a

relay agent for subnetting purposes.

When it receives the DHCPDISCOVER message, the DHCP server sends a

DHCPOFFER directly to the relay agent identified in the GIADDR field, and

the agent relays the message to the DHCP client. The client's IP address is

still unknown, thus it has to be a broadcast on the local subnet.

Similarly, a DHCPREQUEST message is relayed from client to server and a

DHCPACK message is relayed from server to client, according to RFC 1542.

When there are multiple DHCP servers, each subnet should have one server

and servers should not have common IP addresses in their scopes (each

server should have a unique pool of addresses).

If the DHCP server in the local subnet goes down, requests are relayed to

a remote subnet, and the DHCP server there can respond to DHCP requests

if it maintains a scope of IP addresses for the requesting subnet. If the

remote server has no scope defined for the requesting subnet, it cannot

provide IP addresses, even if it has available addresses for other scopes.

If each DHCP server has a pool of addresses for each subnet, then it can

provide IP addresses for remote clients whose DHCP server is down.

Additional reference words: 3.50 prodnt

KBCategory: kbnetwork kbfasttip

KBSubCategory: nttcp


Troubleshooting NET USE Across a Router Using TCP/IP-32

Article ID: Q121382

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft TCP/IP-32

 - Microsoft Windows for Workgroups 3.11

----------------------------------------------------------------------

When you use the NET USE command across a router using TCP/IP-32 and

encounter problems, the following troubleshooting techniques are

recommended:

1. Make sure you ping across both sides of the router. This tests to

   make sure the router is configured and working properly.

2. Check to make sure you have an entry in the LMHOSTS file that lists the

   NetBIOS name and IP address of the machine across the router. See the

   LMHOSTS.SAM file for a description and example LMHOST file entries.

3. Make sure the Enable LMHOSTS Lookup check box is selected in the

   Advanced Microsoft TCP/IP configuration dialog box. This is located in

   the Network group; choose the Network Setup icon, and then double-click

   Microsoft TCP/IP-32 3.11, Advanced.

4. If you are having trouble connecting from File Manager, but can connect

   fine from the MS-DOS command prompt, add the #PRE keyword to the LMHOSTS

   file entry. This is noted in the release notes. See the LMHOSTS.SAM file

   for an example of using the #PRE keyword.

Additional reference words: prodtcp32 3.11

KBCategory: kbnetwork kbfasttip

KBSubCategory: nttcp


Obtaining Latest Novell Client Windows Drivers and DLLs

Article ID: Q121462

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

 - Microsoft Windows operating system versions 3.0, 3.0a, 3.1, 3.11

----------------------------------------------------------------------

SUMMARY

=======

Novell has new Windows and DOS client drivers and dynamic-link library

(DLL) files with new naming schemes available. They are WINDRx.EXE and

NWDLLx.EXE (where x stands for the latest revision) for Windows files and

VLMUPx.EXE and NET33x.EXE for DOS. To obtain these files, contact your

local Novell authorized reseller or call Novell Technical Support at (800)

638-9273.

MORE INFORMATION

================

These files are updates to the DOS/Windows kit that is provided with the

NetWare products versions 4.x and 3.12. If you are using NetWare version

3.11 or NetWare version 2.x and have not already purchased the client kit,

you can purchase a site license through the CompuServe NOVFILES forum

Client Kits\Order DOS/Windows client (version 1.1), or call (800) UPDATE1

to order the NetWare Client for DOS/MS Windows version 1.1.

DOSUP9.EXE has been divided into two files (VLMUP1.EXE and NET33X.EXE), and

the Windows NETWARE.DRV version 2.02 is version-specific to NETX.EXE and

has been moved into NET33X.EXE and is not found in WINDR1.EXE.

NET33X.EXE contains the latest NETX.EXE. Novell is recommending that users

upgrade to the ODI/VLMs because NETX.EXE is no longer under development.

Novell's continued 16-bit solution will be focused on ODI/VLMs rather than

NETX.

VLMUP1.EXE contains all the updated VLMs (pre-release version 1.20), the

updated ODI drivers (LSL.COM and IPXODI.COM), the updated MLIDs, and other

associated files. Although the version 1.20 VLMs released in VLMUP1.EXE

return "Pre-release" with their version number, they are fully tested and

have completed BETA test. The file VLMUP2.EXE from NOVLIB\05 was removed

because the VLMs contained in VLMUP1.EXE are newer. The new naming scheme

required the three files be in synchronization on their revision number

upon initial release.

The Novell products included here are manufactured by Novell, Inc., a

vendor independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

Additional reference words: 3.10 3.11 wfwg wfw win3x

KBCategory: kb3rdparty kbfasttip

KBSubCategory: ntinterop nthowto


Using ACM/1600, ACM/400, ACM/100 with Remote Access Service

Article ID: Q121539

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.5

 - Microsoft Windows NT Workstation version 3.1

 - Microsoft Windows NT Server version 3.5

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SUMMARY

=======

This article was created in close collaboration between Microsoft and

Security Dynamics, Inc. It explains how to install the various ACM models

made by Security Dynamics with Microsoft Windows NT versions 3.1 and 3.5

and how to configure the Remote Access Service (RAS) clients that are going

to call the RAS server with the ACM device. This article does not explain

how to program the ACM devices themselves; please refer to the ACM

documentation for that information.

The primary purpose of the ACM products is to give additional security to

the already very secure Windows NT operating system. Windows NT provides

two levels of security for RAS users. First, users need to be in the

domain's user accounts database as valid users. Secondly, users need to be

granted Remote Access permissions by their administrator in order to be

successfully authenticated by a RAS server.

For Microsoft Windows NT customers with higher security needs, Security

Dynamics adds a third level of security by requiring users to identify

themselves to the server's ACM device with a password that dynamically

changes every 30 seconds in a credit card-sized device that the users carry

with them. The ACM device on the Windows NT RAS server is plugged in-line

between the modems and the server's serial ports. If the user's password

doesn't match, the user will be disconnected from the modem without ever

interacting with Windows NT RAS.

The ACM devices work with both Windows NT workstations and Windows NT

servers, but because Windows NT workstations allow only one incoming call

at a time, the ACM devices are used more frequently with Windows NT

Advanced Server version 3.1, which allows up to 64 simultaneous

connections, and Windows NT Server version 3.5, which allows up to 256

simultaneous connections.

MORE INFORMATION

================

Hardware Requirements

---------------------

 - ACM/1600 hardware running software version 4.08-5 or later

   -or-

   ACM/400 hardware running software version 1.08-5 or later

   -or-

   ACM/100 hardware running software version 1.12A or later

 - Microsoft Windows NT Advanced Server software version 3.1 or later

   -or-

   Microsoft Windows NT (to host single session)

 - Microsoft Windows NT Advanced Server Remote Access Service

   software (RAS) for Windows NT version 3.1 or Windows for Workgroups

   version 3.11.

ACM Host and Modem adapters may be needed, depending on the model and

hardware version of your ACM. Refer to Table 1 later in this document to

determine your requirements.

Microsoft Windows NT Server Configuration

-----------------------------------------

The MODEM.INF file supplied with the NT server software contains an entry

for SDI's ACM/400 hardware product. The section is labeled [SD ACM400 w/

AT&T 3820]. This entry is designed for use with an AT&T Comsphere 3820

modem.

If you want to use a different modem with your ACM device, the macro

definitions, such as <speaker_on>=M1, and the COMMAND_INIT= lines must be

changed to comply with the modems to be used with the ACM hardware.

(Although the section heading refers to the ACM/400 product, it can be used

for ACM/100 and ACM/1600 devices as well.)

The easiest way to customize the ACM entry for your particular modem is to

locate, within the MODEM.INF file, the section that refers to your modem

type, and copy and paste that section to the end of the MODEM.INF file.

Rename the section heading to reflect the ACM and modem type you're using.

The length of the section heading must be limited to 31 or fewer

characters, excluding the brackets.

If there is no entry for your specific modem, try to select from the list

of supported modems a model that matches yours as closely as possible. Make

your choice by comparing entries in the MODEM.INF file with commands for

your modem. Refer to your modem's documentation for a description of your

modem's commands. The documentation may also list compatible modems or

models that it can emulate. After you have selected the appropriate modem

and copied its settings to the end of the MODEM.INF file, rename the

section heading to reflect the ACM and modem type you're using. Again, do

not exceed 31 characters, excluding the brackets. (For more information on

making an unsupported modem work with RAS, refer to the RAS client software

Help file section titled "Modifying MODEM.INF.") Once that has been done,

adjust the following settings :

1. Set the MAXCONNECTBPS parameter in the new [SD ACM] section of the

   MODEM.INF file to equal the highest speed that is compatible with the

   ACM hardware and modem being used. This will usually be 38400 or 19200

   baud. For higher baud rates, consult Security Dynamics product support

   first.

2. Set Hardware Flow Control to ON (this is the default value). For

   assistance, refer to "Setting Modem Features" in the RAS Help file.

For more information regarding the MODEM.INF file, refer to your Microsoft

Windows NT Advanced Server Remote Access Service manual.

Microsoft RAS Terminal Configuration

------------------------------------

To prepare the client for Terminal mode:

1. Access the Remote Access Phone Book, and select the entry you want to

   connect to.

2. Choose Edit.

3. If the word "Advanced" appears in the button below the Cancel button,

   choose the Advanced button; otherwise, proceed with step 4.

4. If you are using a Windows for Workgroups version 3.11 or Windows NT

   version 3.1 client, choose the Switch button. If you are using a Windows

   NT version 3.5 client, choose the Security button.

5. If you are using a Windows for Workgroups version 3.11 or Windows NT

   version 3.1 client, select Terminal in the Post-connect Script field. If

   you are using a Windows NT version 3.5 client, select Terminal in the

   After Dialing field.

6. Choose OK.

Connecting to the Remote Access server:

1. In the Remote Access Phone Book, select the entry you want to connect

   to.

2. Choose Dial. When prompted, type your user name, password, and domain

   name, and then choose OK.

3. Type your PIN and CARDCODE in the Enter PASSCODE field of the Terminal

   screen, and then press ENTER.

   The ACM will indicate that your PASSCODE has been accepted when the

   cursor drops down to the next line on the Terminal screen. If a

   connection message has been defined within the ACM, then it will be

   displayed.

4. Choose Done.

Authentication on the Remote Access server will begin.

ACM Hardware Configuration

--------------------------

Channel Settings:

   Baud Rate:     38.4k, 19.2k, 9600, 4800, 2400, 1200, or 300.

      Configure the ACM channel baud rate to match the MAXCONNECTBPS

      parameter in the Windows NT server MODEM.INF file's [SD ACM400]

      section. This would normally be 19200 or 38400 baud.

   Data Bits:     7 or 8 to match NT Server   (default=8)

   Stop Bits:     No setting required

   Parity:        None, Even, Odd, Mark, or Space to match Windows NT

                  Server. (default=none)

   Protocol:     DCD at modem and DCD at Host. (d-d)  (default)

   Host Command Mode:  N  (default)

   Dialout:     Y (enabled)

      NOTE: For the dialout option to function properly, your ACM hardware

      may require Host and Modem adapters to be attached to each port of

      your ACM. Various revisions of the ACM hardware exist, requiring

      different models of these adapters. Refer to table 1 to determine

      your needs.

Cabling Issues

--------------

In order for the ACM to function properly, it is very important that the

cables used to connect devices to the ACM hardware are properly configured.

The cables should include at least the following pins: 1, 2, 3, 4, 5, 6, 7,

8, 20, and 22. The Dialout option, in particular, is reliant on pin 22

(Ring Indicator) to function properly. The cable connecting the modem to

the ACM's DTE port MUST support pin 22 or the Dialout function will not

operate properly. When the Ring Indicator connection protocol is selected,

the cable connecting the ACM on either the modem or host side of the ACM

will require pin 22, depending on the particular setting selected.

If you have any questions regarding the contents or use of this document,

please call Security Dynamics Customer Support Department at (617) 876-

9640.

Table 1  -  Dialout Adapter Requirements by Hardware Type / Serial Number

-------------------------------------------------------------------------

ACM          Rev.     Serial No. Range       Adapter(s)

-------------------------------------------------------------------------

100                   ALL                    No adapters required

400           A       4000 - 4499            AG15 (DCE) / Host Adapter 1

                                             JB15 (DTE) / Modem Adapter

400           B       4500 - 4629            AG11 / Host Adapter -3

                                             Modem adapter not required

400           C       4630 +                 No adapters required

1600        0 - 6     1000 - 1799            AG15 / Host Adapter -1

                      +2000-2003             JB15 / Modem Adapter

1600          7       1800 - 1899            AG24 / Host Adapter -2

1600          8       1900 - 1949            AG11 / Host Adapter -3

1600          9       2050 +                 No adapters required

These adapters are available free of charge on request from Security

Dynamics. Determine the adapter(s) you require according to the model and

serial number of your ACM. Call Security Dynamics Customer Support

Department at (617) 876-9640.

The third-party products discussed here are manufactured by vendors

independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

All product and brand names herein are trademarks and service marks of

their companies.

For additional information please contact Security Dynamics at:

   Security Dynamics

   One Alewife Center

   Cambridge, MA  02140-2312

   USA

   (617) 547-7820

   Fax: (617) 354-8836

   Customer Support: (617) 876-9640

Additional reference words: 3.10 3.50

KBCategory: kbnetwork kbfasttip

KBSubCategory: ntprotocol


Setup and Boot Hangs on HP NetServer Computer

Article ID: Q121703

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Hewlett-Packard (HP) NetServer series computers with onboard Adaptec

AIC7770 SCSI controllers stop responding (hang) during SCSI detection in

Windows NT Setup. Even if Setup completes successfully, Windows NT may hang

during the boot process.

CAUSE

=====

This problem is caused by several factors, such as outdated drivers,

outdated firmware and computer configuration. Another contributor to the

problem is a conflict with the data transfer rate of the onboard AIC7770

SCSI controller.

RESOLUTION

==========

In order to correct this problem, the following procedures for Windows NT

version 3.1 and Windows NT version 3.5 are recommended. If you experience

additional problems, refer to your hardware documentation or contact HP

Technical Support at (303) 635-1000.

Windows NT 3.1

--------------

A fix is available on HP's BBS at (408) 553-3500. The file to download is

LMLFB01D.EXE. This driver replaces ARROW.SYS (which becomes NTBOOTDD.SYS

after installation.) After following the instructions of the README file,

you may do the following to implement the fix:

1. Make a copy of your master Windows NT Setup Disk for CD-ROM Installation

   disk using the MS-DOS DISKCOPY command. Label the copy as the work

   disk.

2. Delete the SCSI driver from the work disk. For example, if the work

   disk is in the A drive, type the following command:

      del a:\arrow.sys

3. Start the installation of Windows NT as normal using the work disk in

   place of the Windows NT Setup Disk for CD-ROM Installation disk.

4. When prompted for the type of setup, choose custom setup.

5. Press S to configure additional SCSI adapters after Setup scans your

   system for SCSI host adapters and displays the list of recognized

   adapters.

6. Select the Other (requires disk provided by a hardware manufacturer)

   option. Setup will prompt you for the location of the disk. Specify the

   following location:

      a:\winnt

7. Insert the HP NetServer LM/LF NetWare, OS/2, MS-DOS and Windows NT SCSI

   Driver disk into drive A and press ENTER. A dialog box will appear that

   displays:

      Adaptec 2740/AIC 777x

8. Press ENTER to select this driver and continue with the Windows NT

   installation.

Windows NT 3.5

--------------

1. Verify that the ARROW.SYS file in the %systemroot%\SYSTEM32\DRIVERS

   subdirectory is the one shipped with Windows NT version 3.5. The file

   size of ARROW.SYS is 38,224 bytes dated 9/4/94.

2. Verify the version number of the Flash BIOS on each Netserver computer,

   which are listed below:

   Models      486-processor          Pentium-procoessor

   -------------------------------------------------------

   LM          1.00.19.AMO or later   1.00.19.AMO or later

   LF and LC   4.02.23.PA or later    4.02.18.PB or later

   LE          Z.04.01 or later       Z.04.01 or later

3. If PCI slots on the Netserver machines are not used, disable them.

4. Verify that the Secondary Cache Mode on the computer is set to

   Write-through. The default is Write-back.

NOTE: For steps 3 and 4 above, run the EISA Configuration utility shipped

with the Hewlett-Packard Netserver series computers.

The products included here are manufactured by Hewlett-Packard, a vendor

independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

Additional reference words: prodnt 3.50 3.10

KBCategory: kbsetup kbfasttip

KBSubCategory: ntsetup ntboot


Settings for 3C509 Not Detected Correctly

Article ID: Q121791

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you upgrade or perform a new installation of Windows NT Workstation

and Windows NT Server version 3.5 with a 3Com EtherLink III (3C509)

adapter, Setup may not correctly detect the settings for the network card.

If you continue with the installation and do not verify the settings, the

following error message may appear when you start your computer:

   At least one service or driver failed during system startup.

WORKAROUND

==========

To work around this problem, the following is recommended:

1. In Windows NT version 3.5, remove all installed network software and the

   network adapter card driver.

2. Boot to MS-DOS and use the 3Com EtherDisk utility to verify the

   settings of the 3Com EtherLink III network adapter.

3. In Windows NT version 3.5, manually select the network adapter driver.

   Do not select the "autodetect" function.

4. Manually reconfigure the network card with the correct settings.

5. Restart your computer.

The EtherLink III is manufactured by 3Com Corporation, a vendor independent

of Microsoft; we make no warranty, implied or otherwise, regarding this

product's performance or reliability.

Additional reference words: prodnt 3.50

KBCategory: kbnetwork kbsetup kbfasttip

KBSubCategory: ntsetup


Windows NT 3.5 Drivers for Compaq Devices

Article ID: Q121851

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SUMMARY

=======

In order to install Windows NT 3.5 on a Compaq Deskpro XL566 computer with

a built-in PCI SCSI-II controller, a built-in Netflex network adapter, and

a QVision 2000 video adapter, drivers for these devices are required. These

drivers are available on the Windows NT 3.5 Installation compact disc at

the following locations:

   DRVLIB\STORAGE\AMD\X86   (for PCI SCSI-II controller)

   DRVLIB\NETCARD\X86\PCNET (for the Netflex network adapter)

   DRVLIB\VIDEO\CPQ2000\X86 (for the QVision 2000 video adapter)

They must be copied from these libraries onto separate floppies, and then

used during Windows NT Setup.

MORE INFORMATION

================

If you do not have a CD-ROM drive or the Windows NT 3.5 Installation

compact disc, you can obtain the drivers from Compaq. Compaq has just

released the official support disk for Windows NT 3.5 for Compaq products

called the Compaq Support Software Diskette (SSD) for Windows NT 3.5

version 1.12a. This will also be available on the Compaq forum on

CompuServe as Softpaq #925. Refer to the README file for a list of drivers.

The Compaq products discussed here are manufactured by Compaq Computer

Corp., a vendor independent of Microsoft; we make no warranty, implied or

otherwise, regarding the products' performance or reliability.

Additional reference words: prodnt 3.50 v112 ssd 3rdparty

KBCategory: kb3rdparty kbfasttip

KBSubCategory: nthw ntdriver


Enabling Routing of IP Packets on RAS Clients

Article ID: Q121877

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

Windows NT 3.5 Remote Access Services (RAS) has a new feature that allows

it to function as a router between two different networks if TCP/IP is the

protocol on both sites and PPP with TCP/IP is the selected protocol for

communication with the RAS server on the RAS client. In order to allow the

RAS client to function as a router a Registry value must be modified. By

default this parameter is set to disable this functionality.

You must set the DisableOtherSrcPackets value on RAS clients if you want to

route IP packets through a RAS client. This value only affects forwarding

of packets on the RAS client side and does not affect the RAS server.

The DisableOtherSrcPackets value is located in the HKEY_LOCAL_MACHINE hive

under the following sub-key:

   \System\CurrentControlSet\Services\RasArp\Parameters

It has a data type of REG_DWORD and can be set to 0 or 1.

It controls the routing of IP packets with an IP source address other than

the IP address of the RAS network adapter card. Set to 0, packets with

source address other than the IP address of the RAS adapter will be sent.

Set to 1, packets with source address other than the IP address of the RAS

adapter will not be sent. The default is 1.

Additional reference words: prodnt 3.50

KBCategory: kbnetwork kbfasttip

KBSubCategory: ntras ntregistry


Disabling Printing Notification Dialog Boxes in Windows NT 3.5

Article ID: Q122160

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

Under Windows NT 3.5, it is possible to disable the Printing Notification

network dialog boxes sent by the Spooler on a Print Server when either a

print job has been completed, there is an error, or if a job has been

deleted.

NOTE: This option is not available in Windows NT or Windows NT Advanced

Server version 3.1. It applies globally to all the printers on a particular

print server. It is not possible to set this option on a per-printer basis.

To disable Printing Notification network dialog boxes, use Registry Editor

as follows:

WARNING: Using Registry Editor incorrectly can cause serious, system-wide

problems that may require you to reinstall Windows NT to correct them.

Microsoft cannot guarantee that any problems resulting from the use of

Registry Editor can be solved. Use this tool at your own risk.

 1. Start Registry Editor.

 2. From the HKEY_LOCAL_MACHINE hive, go to the following subkey:

       \SYSTEM\CurrentControlSet\Control\Print\Providers

 3. From the Edit menu, choose Add Value.

 4. In the Value Name field of the Add Value dialog box, type the

    following:

       NetPopup

 5. Select REG_DWORD for the Data Type.

 6. Choose OK.

 7. In the Dword Editor dialog box, type 0 (zero) in the Data field.

 8. Choose OK.

 9. Exit Registry Editor.

10. Stop and restart the Spooler service from the Services portion of

    Control Panel so the new setting will take effect.

Additional reference words: 3.50 prodnt

KBCategory: kbprint kbnetwork kbfasttip

KBSubCategory: ntprint


Using Rumba with TCP/IP-32

Article ID: Q122311

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft TCP/IP-32

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SUMMARY

=======

Only one version of Rumba, Rumba Mainframe 4.0 update 01, works with

Microsoft TCP/IP-32. You can obtain a patch from Wall Data to use the other

versions of Rumba with TCP/IP-32.

MORE INFORMATION

================

The following are the current versions of Rumba:

   Rumba Office 1.0

   Rumba Mainframe 4.0 update 01

   Rumba AS/400 2.0

   Rumba VAX 1.0 update 02

Only Rumba Mainframe 4.0 update 01 works with TCP/IP-32. All of the other

versions of Rumba require a patch from Wall Data to allow you to configure

Rumba for Windows Sockets version 1.1, which is required to run Rumba with

TCP/IP-32.

If you are using another version of Rumba without the patch, there is no

option to configure Rumba for Windows Sockets within the Rumba interface.

Once you apply the patch, there is an option to configure Rumba for Windows

Sockets on the Options menu, by choosing Interface and then Configure.

To obtain the patch, call Wall Data at (206) 814-9255.

The Rumba products discussed here are manufactured by Wall Data, a vendor

independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

Additional reference words: prodtcp32 3.11

KBCategory: kbnetwork kbfasttip

KBSubcategory: nttcp


Err Msg: Error 7361: IPX or NetBIOS Must Be Running...

Article ID: Q122313

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Workgroup Add-On for MS-DOS, version 3.11

----------------------------------------------------------------------

SYMPTOMS

========

After you install Microsoft Workgroup Add-On for MS-DOS with TCP/IP, the

following message appears on startup:

   Error 7361:

   IPX or NetBIOS must be running in order to load the network

   services.

CAUSE

=====

This message appears when the protocols and network adapter drivers have

not been bound because there is a configuration error in PROTOCOL.INI and

AUTOEXEC.BAT.

RESOLUTION

==========

Modify the AUTOEXEC.BAT and PROTOCOL.INI files to properly bind TCP/IP to

the network card.

Before you begin, you need the latest Real Mode Microsoft TCP/IP driver.

For more information about downloading the file WFWTCP.EXE from any of

Microsoft's electronic services, please see the following article in the

Microsoft Knowledge Base:

   ARTICLE-ID: Q112578

   TITLE     : Creating a Setup Disk for the Updated WFW 3.11 TCP/IP

               Drivers

When you have downloaded this file, run WFWTCP.EXE on a blank floppy disk

to extract the necessary files.

Setup Instructions

------------------

1. Start Setup for the Microsoft Workgroup Add-On for MS-DOS and during

   Setup, select Other Protocol, specifying the path to where you have

   extracted the files in WFWTCP.EXE (for example, A:\).

2. When you have completed Setup (the message "Workgroup Add-On is now

   installed on your computer" appears), press F3 to quit Setup.

3. Edit C:\AUTOEXEC.BAT. It should contain, in order, the following lines:

      C:\WRKGRP.DOS\net start NETBIND   (previously just NET START)

      C:\WRKGRP.DOS\umb

      C:\WRKGRP.DOS\tcptsr

      C:\WRKGRP.DOS\tinyrfc

      C:\WRKGRP.DOS\nmtsr.exe

      C:\WRKGRP.DOS\emsbfr.exe

      C:\WRKGRP.DOS\NET START   (you must add this line)

4. Edit PROTOCOL.INI from the path where you installed Microsoft Workgroup

   Add-On for MS-DOS. It should contain the following lines. Your own IP

   Address information will likely be different.

      [protman]

      DriverName=PROTMAN$

      PRIORITY=TCPIP   (Changed from =MS$NDISHLP)

      [TCPIP]

      DefaultGateway0=22 101 0 1   (you must add this line)

      SubnetMask0=255 255 0 0      (you must add this line)

      IPAddress0=22 101 47 173     (you must add this line)

      NBSessions=6                 (you must add this line)

      NetFiles=C:\WRKGRP.DOS       (you must add this line)

5. To ensure that sockets support is configured correctly, edit the

   TCPUTILS.INI file from the path where you installed Microsoft Workgroup

   Add-On for MS-DOS. It should contain the following entries as well as

   what is there by default.

      [TCPGLOBAL]

      username=<username>   (supply the user name for <username>)

      NetFiles=<path>       (supply the path for <path>, i.e. c:\net)

      hostname=<hostname>   (supply the host name for this computer

                            for <hostname>)

      drivername=GLOBAL$

6. Save the changes to AUTOEXEC.BAT, PROTOCOL.INI, and TCPUTILS.INI and

   restart the computer.

Example Files

-------------

Please note that your directory structure, network card, and IP addresses

will differ from those listed here. These files were created on a PC using

an Intel EtherExpress 16/16TP running MS-DOS version 6.2 and the Microsoft

Workgroup Add-On for MS-DOS, version 3.11, with Microsoft TCP/IP as the

only protocol.

Example CONFIG.SYS

   DEVICE=C:\DOS\SETVER.EXE

   DEVICE=C:\DOS\HIMEM.SYS

   DOS=HIGH

   FILES=30

   SHELL=C:\DOS\COMMAND.COM C:\DOS\  /p

   DEVICE=C:\WRKGRP.DOS\IFSHLP.SYS

   LASTDRIVE=Z

Example AUTOEXEC.BAT

   C:\DOS\SHARE.EXE

   @ECHO OFF

   PROMPT $p$g

   PATH C:\DOS;C:\WRKGRP.DOS

   SET TEMP=C:\DOS

   C:\DOS\DOSKEY

   C:\WRKGRP.DOS\net start NETBIND

   C:\WRKGRP.DOS\umb

   C:\WRKGRP.DOS\tcptsr

   C:\WRKGRP.DOS\tinyrfc

   C:\WRKGRP.DOS\nmtsr.exe

   C:\WRKGRP.DOS\emsbfr.exe

   C:\WRKGRP.DOS\NET START

Example PROTOCOL.INI

   [network.setup]

   version=0x3110

   netcard=ms$ee16,1,MS$EE16,1

   transport=tcpip,TCPIP

   lana0=ms$ee16,1,tcpip

   [MS$EE16]

   TRANSCEIVER=Twisted-Pair (TPE)

   IOCHRDY=Late

   IOADDRESS=0x310

   IRQ=3

   DriverName=EXP16$

   [protman]

   DriverName=PROTMAN$

   PRIORITY=TCPIP

   [TCPIP]

   DriverName=TCPIP$

   BINDINGS=MS$EE16

   LANABASE=0

   DefaultGateway0=22 101 0 1

   SubnetMask0=255 255 0 0

   IPAddress0=22 101 47 173

   NBSessions=6

   NetFiles=C:\WRKGRP.DOS

Example TCPUTILS.INI

   [tcpglobal]

   drivername=GLOBAL$

   [sockets]

   drivername=SOCKETS$

   bindings=TCPIP_XIF

   numsockets=4

   numthreads=32

   poolsize=3200

   maxsendsize=1024

   [telnet]

   drivername=TELNET$

   bindings=TCPIP_XIF

   nsessions=0

   max_out_sends=0

Example SYSTEM.INI

   [network]

   filesharing=yes

   printsharing=yes

   autologon=yes

   computername=MYPC

   lanroot=C:\WRKGRP.DOS

   username=MYUSERID

   workgroup=THEWRKGRP

   reconnect=yes

   directhost=no

   dospophotkey=N

   lmlogon=1

   logondomain=THEDOMAIN

   preferredredir=full

   autostart=full,,server

   maxconnections=8

   [network drivers]

   netcard=exp16.dos

   transport=tcpdrv.dos,nemm.dos

   devdir=C:\WRKGRP.DOS

   LoadRMDrivers=yes

   [386Enh]

   device=vsockets.386

   device=vbapi.386

   TimerCriticalSection=5000

   UniqueDosPSP=TRUE

   PSPIncrement=2

STATUS

======

Microsoft has confirmed this to be a problem in Workgroup Add-On for MS-

DOS, version 3.11. We are researching this problem and will post new

information here in the Microsoft Knowledge Base as it becomes available.

For a related article regarding Windows for Workgroups version 3.11 and the

real mode TCP/IP protocol as the only protocol, please see the following

article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q114839

   TITLE     : Net Start Fails When TCP/IP is the Only Protocol

Additional reference words: 3.11

KBCategory: kbnetwork kbfasttip

KBSubcategory: nttcp


TCP/IP-32 May Fail on Token Ring Network with Source Routing

Article ID: Q122317

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft TCP/IP-32

 - Microsoft Windows For Workgroups 3.11

----------------------------------------------------------------------

SYMPTOMS

========

If Microsoft TCP/IP-32 and IPXODI are loaded on a token ring network with

source routing enabled, the TCP/IP-32 utilities, such as PING, may fail to

locate hosts on the network.

CAUSE

=====

This problem occurs due to incorrect configuration of ROUTE.COM (Novell's

IBM-Token-Ring Source Routing Driver with DOS ODI) and incorrectly

configured NET.CFG file.

RESOLUTION

==========

To correct this problem:

1. Copy the ROUTE.COM file to a boot disk from the Novell DOS ODI

   Workstation Services disk.

2. Add the following two lines in the AUTOEXEC.BAT after LANSUP.COM or

   TOKEN.COM and before the protocol stack:

      ROUTE BOARD = 01

      ROUTE BOARD = 02

   NOTE: The BOARD parameter does not refer to the physical NIC. Instead,

   it refers to the Frame specified in the NET.CFG file.

3. Add the following two lines in the NET.CFG file (if it is not already

   present):

      Frame Token-Ring

      Frame Token-Ring SNAP

The Novell products discussed here are manufactured by Novell, Inc., a

vendor independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

Additional reference words: prodtcp32 3.11

KBCategory: kbnetwork kb3rdparty kbfasttip

KBSubcategory: nttcp


Err Msg: Hard Drive Partition... w/Quantum 540 MB IDE Drive

Article ID: Q122381

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you upgrade or install Windows NT version 3.5 on a Dell Dimension XPS

P60 PCI computer with a Quantum 540 megabyte (MB) IDE hard disk drive, the

following error message may appear:

   Hard drive partition containing the free space selected for

   installation is not accessible to the computer's startup program.

CAUSE

=====

This problem occurs if the hard disk drive does not support Logical Block

Addressing (LBA) mode. LBA is supported on Quantum IDE hard disk drives

with the BIOS revision starting with the letters EC.

WORKAROUND

==========

To correct this problem:

1. Verify the BIOS revision of the hard disk drive starting with the

   letters EC. Call Dell Technical Support at (800) 624-9896 for more

   information.

2. Back up all contents on the hard disk drive. Go to the system CMOS

   configuration and change the hard disk drive information from AUTO to

   1024 cylinders, 16 heads and 63 sectors.

3. Repartition the hard disk drive.

The third-party products discussed here are manufactured by vendors

independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

Additional reference words: prodnt 3.50 hd 3rdparty

KBCategory: kb3rdparty kberrmsg kbfasttip

KBSubcategory: nthw


Err Msg: Mail Could Not Read the Entire Message...

Article ID: Q122385

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

 - Microsoft Mail for Windows NT, versions 3.2 and 3.2a

----------------------------------------------------------------------

SYMPTOMS

========

When a Windows NT version 3.5 Workstation or Server sends mail to or

receives mail from a Microsoft Mail client, you receive this error message:

   Mail System Error

   =================

   Mail could not read the entire message from the post office.

   Some parts of the message may be missing.

   Ask sender to resend the message.

CAUSE

=====

The Windows NT Workstation and Server Mail client incorrectly zeros out

some fields in the .MAI file.

RESOLUTION

==========

Microsoft fixed this problem in an updated version of the Windows NT file,

MSSFS32.DLL.

To Apply MSSFS32.DLL:

   1. Download the self-extracting archive file, MSSFS32.EXE.

   2. Copy the file to the WINNT\SYSTEM32 directory on your hard drive.

   3. Rename the original MSSFS32.DLL to MSSFS32.OLD.

   4. Type the command "MSSFS32.EXE" (without the quotation marks) and

      press ENTER.

   5. Restart your computer.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. An updated version of MSSFS32.DLL is now

available. However, the new file, MSSFS32.DLL has not been fully regression-

tested. Microsoft does not recommend implementing it without first testing

it in a trial environment. Use of the updated MSSFS32.DLL file is at your

own risk.

The self-extracting archive file, MSSFS32.EXE, containing the updated

MSSFS32.DLL and a README.TXT files, can be downloaded from the Microsoft

Software Library (MSL) on the following services:

 - CompuServe

      GO MSL

      Search for MSSFS32.EXE or S14980

      Display results and download

 - Microsoft Download Service (MSDL)

      Dial (206) 936-6735 to connect to MSDL

      Download MSSFS32.EXE

 - Internet (anonymous FTP)

      ftp ftp.microsoft.com

      Change to the SOFTLIB\MSLFILES directory

      Get MSSFS32.EXE

Additional reference words: prodnt 3.50 3.20 3.20a S14980

KBCategory: kbinterop kbfile kbfasttip

KBSubcategory: ntutil MailPCNT


README.TXT: TCP/IP-32 3.11a for Windows for Workgroups

Article ID: Q122544

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft TCP/IP-32 version 3.11a

----------------------------------------------------------------------

The following is the complete README.TXT file that accompanies Microsoft's

TCP/IP-32 3.11a update.

---------------------------------------------------------------------------

                 Microsoft TCP/IP-32 version 3.11a Update

---------------------------------------------------------------------------

1.0  Introduction.

2.0  Installation Instructions for TCP/IP-32 version 3.11a.

2.1  List of Bugs Fixed in TCP/IP-32 3.11a.

2.2  Descriptions of Bugs Fixed in TCP/IP-32 3.11a.

2.3  Support Options for Microsoft TCP/IP-32

1.0  Introduction

-----------------

TCP/IP-32 version 3.11a is an update to Microsoft's TCP/IP-32, a 32-bit

TCP/IP network protocol stack for Windows for Workgroups version 3.11. This

update is a complete refresh of TCP/IP-32 and contains all components of

the product.

2.0  Installation Instructions for TCP/IP-32 3.11a

--------------------------------------------------

If you are running a 3rd party TCP/IP product on your system, you must

remove it before installing Microsoft TCP/IP-32 version 3.11a. If you

experience difficulties with another vendor's product, remove the existing

TCP/IP stack, exit Network Setup completely, reboot your system, and then

proceed to add the Microsoft TCP/IP-32 version 3.11a drivers by following

the instructions below.

There are two ways you can install the TCP/IP-32 version 3.11a upgrade on

your computer. You can completely reinstall your TCP/IP-32 network protocol

stack with TCP/IP-32 3.11a, which will overwrite your previous TCP/IP

settings with default settings. Alternatively, advanced users can manually

copy just the updated binary files to the proper directories. This will

retain your TCP/IP-32 settings, but will not update the TCP/IP-32 version

number.

Complete Reinstall:

1. From the Network group, choose the Network Setup icon.

2. Choose the Drivers button (Under Network Drivers, you will see your

   Network Interface Card (NIC) and the network protocols used on that

   NIC).

3. Select TCP/IP-32 3.11.

4. Choose the Setup button, review and write down all of your TCP/IP-32

   configuration information.

5. Choose the Cancel button to return to the Network Drivers dialog box.

6. If TCP/IP-32 3.11 is your only network protocol, then temporarily add

   the NetBEUI network protocol by following these steps:

      A. Choose the Add Protocol button.

      B. Select Microsoft NetBEUI.

      C. Choose the OK button (Microsoft NetBEUI will appear under Network

         Drivers).

7. Select TCP/IP-32 3.11.

8. Choose the Remove button and then the Yes button to confirm.

9. Choose the Add Protocol button.

10.Select Unlisted or Updated Protocol and Choose the OK button.

11.In the Install Driver dialog box, enter the path to the updated TCP/IP-

   32 3.11a files (You should then see Microsoft TCP/IP-32 3.11a in the

   Unlisted or Updated Protocol dialog).

12.Choose the OK button (You should then see Microsoft TCP/IP-32 3.11a in

   the Network Drivers dialog box).

13.Choose the Setup button and configure TCP/IP-32 3.11a based on the

   information you wrote down in step 4.

14.If you added Microsoft NetBEUI as a network protocol in step 6 and do

   not want to keep it, select Microsoft NetBEUI, choose the Remove button

   and then the Yes button to confirm.

15.Choose the Close button to exit the Network Divers dialog box.

16.Choose the OK button to exit the Network Setup dialog box (Setup will

   modify system files).

17.Choose the OK button (Network Setup prompts you to reboot).

18.Choose the Restart Computer button (The TCP/IP-32 3.11a upgrade is now

   complete).

Manual Installation for Advanced Users:

1. Copy the following files to the C:\<win_root> directory:

   NOTE: By default, the Windows root directory referred to above is

   C:\WINDOWS. If you installed Windows into a directory other than

   C:\WINDOWS, copy these files to that directory.

   11/21/94  12:00a                39,771 WINSOCK.DLL

   11/21/94  12:00a                57,152 TELNET.EXE

   11/21/94  12:00a                 9,604 WSOCK.386

   11/21/94  12:00a                53,935 TRACERT.EXE

   11/21/94  12:00a                67,595 NETSTAT.EXE

   11/21/94  12:00a                33,227 NBTSTAT.EXE

2. Copy the following files into the C:\<win_root>\SYSTEM directory:

   11/21/94  12:00a                89,545 VNBT.386

   11/21/94  12:00a                18,295 WSTCP.386

   11/21/94  12:00a                 9,604 WSOCK.386

2.1  List of Bugs Fixed TCP/IP-32 3.11a

---------------------------------------

NOTE: Use the Qxxxxxx number that precedes the title of the bug fix to

query the Microsoft Knowledge Base to find an article about that bug.

Q121317: TCP/IP-32 version 3.11 Does Not Include Terminal Font

Q120051: DNS Reverse Name Resolution Requests Are Incorrect

Q120052: NBT Query Can Hang Computer or Drop Back To MS-DOS

Q122293: LMHOSTS Lookup Can Cause Intermittent System Pauses

Q119575: TCP/IP-32 Winsock Stops FD_READ Notification

Q119918: Winsock: Accept() Sockets Are Unexpectedly Aborted

2.2  Description of Bugs Fixed in TCP/IP-32 3.11a

-------------------------------------------------

TCP/IP-32 version 3.11 Does Not Include Terminal Font:

   Beta versions of Microsoft TCP/IP-32 included a font named "Terminal"

   in the Telnet application. This font is not included in the released

   version of the TCP/IP-32 Telnet application.

DNS Reverse Name Resolution Requests Are Incorrect:

   TCP/IP-32 does not return the correct IP name when it queries the Domain

   Name Service (DNS) because it sends an improperly formatted query to the

   DNS.

NBT Query Can Hang Computer or Drop Back To MS-DOS:

   Your computer running Windows for Workgroups version 3.11 with TCP/IP-32

   network protocol stops responding (hangs) or drops back to MS-DOS when

   the 32-bit NetBIOS over TCP/IP (NBT) makes a query to the Domain Name

   Service (DNS).

LMHOSTS Lookup Can Cause Intermittent System Pauses:

   Your computer running Windows for Workgroups version 3.11 with TCP/IP-32

   intermittently stops responding (hangs) for about 20 seconds at a time.

   This occurs if TCP/IP-32 is installed as a non-default network protocol

   and the Enable LMHOSTS Lookup option in Network Setup is checked.

TCP/IP-32 Winsock Stops FD_READ Notification:

   FD_READ notification in a Winsock application may stop while the

   application is running.  This may cause data to be left in the input

   buffer, or, it may cause the application to hang. This occurs when the

   application disables and then re-enables FD_READ notification during a

   period of time while the Windows message queue is full.

Winsock: Accept() Sockets Are Unexpectedly Aborted:

   Occasionally, when you execute a PUT command from an FTP client, your

   session to the FTP server is aborted.

2.3  Support Options for Microsoft TCP/IP-32

--------------------------------------------

TCP/IP-32 version 3.11a is compatible with and supported exclusively on

Microsoft Windows For Workgroups 3.11.

Microsoft Support: Network Business Systems Products Support Options

The following support services are available from Microsoft for Microsoft

Business Systems products, including Microsoft Mail Server and its

gateways, SQL Server, LAN Manager, Windows NT, and SNA Server.

Electronic Services:

   CompuServe Information Service

   Microsoft forums are provided through CompuServe, (800) 848-8199,

   representative 230 (sales information only). Access is available 24

   hours a day, 7 days a week, including holidays.

   These forums enable an interactive technical dialog between users as

   well as remote access to the Microsoft KnowledgeBase of product

   information, which is updated daily. These forums are monitored by

   Microsoft support engineers for technical accuracy. If you are already a

   subscriber, type "GO <forum name>" at any !  prompt.

      MSCLIENT    Microsoft Network Client support

      WINNT       Microsoft Windows NT support

      MSSQL       Microsoft SQL Server support

      MSWRKGRP    Microsoft Windows for Workgroups support

      MSNETWORKS  Microsoft LAN Manager support

      MSAPP       Microsoft applications support

      MSWIN32     Information on Win32

      MSDR        Development-related discussion forum

      WINEXT      Support for extensions and drivers for Windows

      WINSDK      Support for Microsoft Windows Software Development Kit

   Microsoft Download Service

   Use the Microsoft Download Service (MSDL) to access the latest technical

   notes on common business system products support issues via modem. MSDL

   is at (206) 936-6735, available 24 hours a day, 7 days a week, including

   holidays (1200, 2400, or 9600 baud; no parity, 8 data bits, 1 stop bit).

   Internet

   Use the Internet to access the Microsoft Driver Library and Microsoft

   KnowledgeBase. The Microsoft Internet FTP archive host FTP.MICROSOFT.COM

   (ip address 198.105.232.1) supports anonymous login. When logging in as

   anonymous, please offer your complete e-mail name as your password.

Telephone Support:

   Microsoft FastTips

   An interactive, automated system providing support at no charge through

   toll lines and accessed by touch-tone phone. FastTips provides fast

   access to answers to common questions and a library of technical notes

   delivered by phone recording or fax. FastTips is available 24 hours

   a day, 7 days a week, including holidays. Microsoft's Business Systems

   Products FastTips telephone number is (800) 936-4400.

   Priority Telephone Support

   Get technical support from a Microsoft engineer. Microsoft offers pay-

   as-you-go telephone support from a Microsoft engineer, available 24

   hours a day, 7 days a week, except holidays. Choose from the following

   options:

      Per Incident: Dial  (900) 555-2100.  $150.00 per incident.

      (Charges appear on your telephone bill.)

      Per Incident: Dial  (800) 936-5900.  $150.00 per incident.

      (Charges billed to your Visa, Master Card, or American Express.)

      10-pack:  Ten incidents for $995 prepaid.

Additional Information:

For additional information about Microsoft support options or for a list

of Microsoft Solution Providers, call Microsoft Support Network Sales and

Information Group at (800) 936-3500, Monday through Friday, 6:00 A.M. to

6:00 P.M., Pacific time, excluding holidays.

This list includes only domestic support programs.

Microsoft's customer support services are subject to Microsoft's then-

current price, terms, and conditions.

Additional reference words: prodtcp32 1.00 3.11 3.11a wfw

KBCategory: kbreadme kbfixlistTCP/IP-32a kbfasttip

KBSubcategory: ntdistrib nttcp


Err Msg: Error 692: Hardware Failure in Port or Attached....

Article ID: Q122839

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you dial a Remote Access Services (RAS) server in Windows NT, the

modem starts to initialize and the following error message may appear:

   Error 692: Hardware failure in port or attached device.

CAUSE

=====

This error message occurs if RAS cannot correctly communicate with the

modem. There are several possible causes:

 - The modem is turned off or malfunctioning. Try resetting the modem.

 - The serial cable is incorrect. If you suspect this is the case, refer

   to the "Cabling Requirements" section in Remote Access Help for more

   information about requirements for correct cabling.

 - The serial cable is loose. If this is the case, remove the cable and

   then reattach it.

 - You are using a 9-to-25 pin adapter or a 25-to-9 pin adapter for the

   serial connection that is not wired correctly. For example, a 9-to-25

   adapter for a mouse would not properly work with a RAS serial setup.

 - The serial port or multi-port adapter on the RAS server or client may

   be malfunctioning. Replace the serial port or multi-port adapter.

 - The handshaking options for the modem need to be adjusted.

 - The modem is unsupported, or the chosen emulation may be incorrect.

   RAS uses a file called MODEM.INF in the %systemroot%\SYSTEM32\RAS

   subdirectory to send the right communication strings to the modem

   through the selected modem in RAS. Use a text editor, such as

   Notepad or Windows Write, with the No Conversion option selected to

   open the MODEM.INF file. Then find the modem you have selected in RAS

   and check the COMMAND_INIT string, which is the communication string

   RAS sends to set up the modem for communication. Refer to the

   "Modifying MODEM.INF" section in the RAS Online Help program and the

   modem documentation or check with the modem manufacturer for the

   correct communication string for your modem.

 - You are using an internal modem. Most internal modems that are listed in

   the MODEM.INF file are not tested and therefore not supported. Internal

   modems are only supported if the word "Internal" (without quotation

   marks) is explicitly mentioned as part of the modem name. Because

   internal modems provide their own serial hardware that could be faulty

   or incompatible, try an external modem in order to utilize the serial

   hardware on another communication (COM) port.

 - You are using a MultiTech MultiModem 224 or MT932BA. See the appropriate

   section below.

 - You are using a US-Robotics 14400 Sportster. See the appropriate

   section below.

If you are not using one of the above modems, or if you are using one of

them but have followed the procedures in this article without success, use

the steps in the next section to try to isolate the problem.

RESOLUTION

==========

You Are Using a MultiTech MultiModem 224 or MT932BA

---------------------------------------------------

In order to correct this problem for the MultiTech MultiModem 224 or

MT932BA modem, MultiTech Systems Technical Support recommends the

following:

1. Upgrade the firmware to the most current version. The current firmware

   versions recommended are 1.14 and 2.14. There are two different types

   of chip sets that can be used by the same modem:

      The 1.xx series is an AT&T Data Pump chip set.

      The 2.xx series is a Rockwell Data Pump chip set.

   To determine the type of chip set that is being used, start Terminal

   and type the following:

      ATI1 [ENTER] for the version.

      ATI2 [ENTER] for the modem model.

2. If the ECHO COMMAND is set to FALSE:

    - Set the DIP switch on the modem to enable ECHO COMMANDS.

      -and-

    - Add E1 to the modem's initialization string in the MODEM.INF file.

3. Call MultiTech Systems Technical Support at (800) 972-2439.

You Are Using a US-Robotics 14400 Sportster

-------------------------------------------

To work around this problem for a US-Robotics 14400 Sportster:

1. Configure the attached device as a Hayes Compatible 9600 modem in Remote

   Access Setup and run the RAS Client program again.

2. Configure the attached device as a US-Robotics 14400 Sportster again.

   From the Modem Settings dialog box in the RAS Client program, configure

   the initial speed to 19200 bps and run the program again.

3. For additional information, call US-Robotics at (800) DIAL-USR.

The third-party products discussed here are manufactured by vendors

independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

Additional reference words: prodnt 3.10 3.50

KBCategory: kb3rdparty kberrmsg kbfasttip

KBSubcategory: ntras ntconfig


System Stops Responding During Shutdown and Restart Process

Article ID: Q122940

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

After you install Windows NT version 3.5, your system may stop responding

(hang) when you select the Shut Down And Restart option. This behavior does

not occur if you select Shut Down. However, when you select Restart in the

Shutdown Computer dialog box, the same problem occurs.

CAUSE

=====

This problem occurs when the Windows NT version 3.5 Setup program calls the

computer BIOS to obtain computer configuration information. On several

computers, the BIOS returns invalid information for the number of

processors installed on the computer. For example, a multi-processor

Hardware Abstraction Layer (HAL) is installed instead of required uni-

processor HAL.

RESOLUTION

==========

To correct this problem, reinstall Windows NT version 3.5 and run Custom

Setup. Configure the Computer type for Standard PC instead of the one

selected by default. This forces the Setup program to install the uni-

processor HAL. Reinstalling Windows NT version 3.5 to the same location of

the previously installed one will update the HAL without losing any user

accounts and important Registry information.

Additional reference words: prodnt 3.50

KBCategory: kbsetup kbfasttip

KBSubcategory: ntsetup ntboot


How To Configure Windows NT as a Remote IP Router

Article ID: Q123024

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SUMMARY

=======

This article describes how to configure Windows NT Workstation or Windows

NT Server to serve as an IP router from a subnet to an Internet/enterprise

gateway using dual network interface cards (NICs). (When Windows NT has

more than one NIC installed it is referred to as a multi-homed system.)

HOW TO CONFIGURE WINDOWS NT AS AN IP ROUTER

===========================================

Install and bind TCP/IP to both NICs. Assign the correct IP address to each

NIC respective to the subnet in which it resides. Check that IP routing has

been enabled by using the IPCONFIG /ALL command.

EXAMPLE CONFIGURATION

=====================

In the following example you should configure the 199.55.10.1 NIC to a

default gateway of 199.55.10.252. The 212.56.11.1 NIC should be configured

with a blank default gateway:

   Multi-homed Windows NT 3.5 TCP/IP Workstation/Server

   ----------------------------------------------------

           |                             |

           |                             |

           |                             |

          NIC                           NIC

      212.56.11.1                   199.55.10.1

      -----------                   -----------

           |                             |

           |                             |

           |                             |

      Network ID:                   Router to Internet/

      212.56.11.0                   enterprise default

                                    gateway port address:

                                    199.55.10.252

The IPCONFIG /ALL command should display something similar to the

following:

Windows NT IP Configuration

        Host Name . . . . . . . . . : gha-1

        DNS Servers . . . . . . . . :

        Node Type . . . . . . . . . : Hybrid

        NetBIOS Scope ID. . . . . . :

        IP Routing Enabled. . . . . : Yes

        WINS Proxy Enabled. . . . . : No

        NetBIOS Resolution Uses DNS : No

Ethernet adapter Lance1:

        Description . . . . . . . . : DEC Etherworks Turbo Adapter

        Physical Address. . . . . . : 08-00-2B-30-D1-E0

        DHCP Enabled. . . . . . . . : No

        IP Address. . . . . . . . . : 199.55.10.1

        Subnet Mask . . . . . . . . : 255.255.255.0

        Default Gateway . . . . . . : 199.55.10.252

Ethernet adapter EE162:

        Description . . . . . . . . : Intel EtherExpress 16 Miniport

        Physical Address. . . . . . : 00-AA-00-44-B4-CB

        DHCP Enabled. . . . . . . . : No

        IP Address. . . . . . . . . : 212.56.11.1

        Subnet Mask . . . . . . . . : 255.255.255.0

        Default Gateway . . . . . . :

The ROUTE command is provided as an interface to manipulate the routing

table. You can use ROUTE PRINT, ROUTE ADD, ROUTE DELETE, and ROUTE CHANGE

to modify the routing table.

The ROUTE PRINT Command should show only one default gateway:

   Network Address   Netmask   Gateway Address   Interface     Metric

   0.0.0.0           0.0.0.0   199.55.10.252     199.55.10.1   1

A static route also needs to be added to the router at 199.55.10.252

providing a route back to the 212.56.11.0 network. Add the 199.55.10.1

gateway address as the static route to the 212.56.11.0 network. The method

of adding this static route will vary among routers.

Additional reference words: prodnt 3.50

KBCategory: kbnetwork kbfasttip

KBSubcategory: nttcp nthowto ntnetserv


RAS Error 652 with US-Robotics 14400 Sportster

Article ID: Q123168

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SYMPTOMS

========

After you configure a Remote Access Service (RAS) client system such as

Windows for Workgroups version 3.11 with a US-Robotics 14400 Sportster

modem for call-back from a RAS server, the modem fails to reinitialize in

call-back mode and the following error message appears:

   Error 652: Unrecognized text response received from the device.

   Make sure the device you selected in Setup matches your modem.

CAUSE

=====

This problem occurs because the RAS client software in Windows for

Workgroups version 3.11 does not keep the Data Terminal Ready (DTR) signal

state low long enough for the modem to release the line. In this case, DTR

was in the low state for approximately 1 millisecond. The US-Robotics 14400

Sportster modem requires the DTR to be in the low state for at least 5

milliseconds.

STATUS

======

Microsoft has confirmed this to be a problem in Windows for Workgroups

version 3.11. We are researching this problem and will post new information

here in the Microsoft Knowledge Base as it becomes available.

The US-Robotics 14400 Sportster modem is manufactured by US-Robotics, a

vendor independent of Microsoft; we make no warranty, implied or otherwise,

regarding this product's performance or reliability.

Additional reference words: prodnt 3.11

KBCategory: kbnetwork kberrmsg kbbug3.11 kbfasttip

KBSubCategory: ntras ntprotocol


Losing Connections with HP JetDirect Printers

Article ID: Q123297

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

----------------------------------------------------------------------

SYMPTOMS

========

Windows NT version 3.1 may lose connections with Hewlett-Packard (HP)

JetDirect printers. This can result in a continuous Online or Status

Unknown for the printer in Print Manager. The print queue then stops

responding (hangs) and does not restart until the server is restarted.

RESOLUTION

==========

To correct this problem, do the following:

 - Make sure the latest version of HPMON.DLL is loaded. Run Print Manager.

   Select any print queue using an HP JetDirect. From the Printer menu,

   choose Properties, and then choose Settings. Choose the About button to

   display the version information. It should be version A.00.14.

   NOTE: This is the version shipping with Windows NT version 3.5 and is

   available for Windows NT version 3.1 in Service Pack 3 or the HPMON.DLL

   provided in the HPMON.EXE Application Note, which is located in

   Microsoft Download Library (MSDL) and the Internet on FTP.MICROSOFT.COM.

 - Increase the DLC Timers settings located in Print Manager to be similar

   to the version information above. To adjust the DLC Timers, select a

   printer using a JetDirect, and then choose Properties from the Printer

   menu. Choose the Settings button, and then choose Options (do this from

   the server because HPMON.DLL cannot run remotely). The range for each of

   the three settings of the DLC Timers is 1 to 10. Try doubling each

   setting first, and then adjust them more if you need to. This affects

   HPMON as a whole for the server, so you only need to make this

   adjustment on one printer. Note: the new settings will not take affect

   until you restart the server.

 - HPMON by default uses windowing to communicate with the JetDirect card.

   This means HPMON will send say five packets to the JetDirect and only

   expect one acknowledgment for all five. Sometimes if the printer is slow

   to accept incoming data, the buffers on the JetDirect will become full

   and the JetDirect cannot accept all of the packets at once. The

   JetDirect will not send the acknowledgment and HPMON must attempt to

   synchronize between the two. Under stress, this causes problems because

   traffic increases between HPMON and the JetDirect with retransmissions.

   The connection may fail during this time. In cases like this, it is best

   to turn the windowing off. By doing so, HPMON will send one packet and

   wait for an acknowledgment before sending the second packet. This

   provides for much better error handling. While this change does affect

   the network speed to the printer, the speed is only moderately affected

   and is still much faster than printers can render the print. The above

   cases of flow control can actually be faster then with the

   retransmissions of failed windows of data.

   To disable windowing, you may modify the Registry. However, if you

   extract the new HPMON available on MSDL and the Internet with the "-D"

   (without the quotation marks) parameter, and then run the automated

   Install program for HPMON, you do not have to modify the Registry.

   WARNING: Using Registry Editor incorrectly can cause serious, system-

      wide problems that may require you to reinstall Windows NT to correct

      them. Microsoft cannot guarantee that any problems resulting from the

      use of Registry Editor can be solved. Use this tool at your own risk.

   1. Start REGEDT32.EXE and locate the following Registry subkey:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

         \Print\Monitors\Hewlett-Packard Network Port\Options

   2. From the Edit menu, choose Add Value. Enter "MaximumXmitsWindow"

      (without the quotation marks) in the Value Name field. Select

      REG_DWORD for the Data Type. Enter 1 in the Data field and choose OK.

   3. From the Edit menu, choose Add Value. Enter "MinimumXmitsWindow"

      (without the quotation marks) in the Value Name field. Select

      REG_DWORD for the Data Type. Enter 1 in the Data field and choose OK.

   4. Exit REGEDT32.

The HP JetDirect printer is manufactured by Hewlett-Packard Company, a

vendor independent of Microsoft; we make no warranty, implied or otherwise,

regarding this product's performance or reliability.

Additional reference words: prodnt 3.10 monitor printman

KBCategory: kbprint kbfasttip

KBSubcategory: ntprint