Troubleshooting with NCR: Timesaving Tips from NCR Experts

You need to demote the original PDC to the BDC. To demote the original PDC,follow these steps:

1. Go to Control Panel, Services;select Net Logon; and click Stop. Alternatively, go to the original BDC and stopthe NetLogon service at the DOS prompt, with the command

net stop netlogon

2. Click Start, Programs,Administrative Tools, and select Server Manager. Choose the machine name of theoriginal PDC and then select Demote To Backup Domain Controller from theComputer drop-down menu. Completing this step will change the original PDC to aBDC.

3. Go to Control Panel, Services;select Net Logon; and click Start. Alternatively, you can restart the NetLogonservice on the original BDC at the DOS prompt, with the command

net start netlogon

4. Resynchronize the domain fromServer Manager.

(You can promote the original PDC to PDC using Step 2. You need to demotethe current PDC to a BDC immediately after this step.)

If this process does not work (possibly because of securityID--SID--corruption), you can perform the following steps. However, try thisresolution as a last resort; Microsoft does not support it. Using the Registryeditor incorrectly can cause serious systemwide problems, and you may need toreinstall NT to correct them.

1. Physically go to the domaincontroller that you do not want to be the PDC, and log on as Administrator.

2. To start the Registry editor, clickStart, Run; enter regedt32 in the Open box; and click OK.

3. Select HKEY_LOCAL_MACHINESECURITY.By default, the Administrator has Special Access rights on the SECURITY key. Youneed to change these rights to Full Control. To make this change, implement thefollowing steps:

a. Select Security, Permissions from the menu bar.

b. Select the Administrator's name.

c. In the Type of Access drop-down box, choose Full Control andselect the Replace Permission on Existing Subkeys check box. Thisconfiguration gives the Administrator full control over the SECURITY key and allsubkeys.

d. Return the SECURITY key permissions to Special Access at the end of thisprocess. Select the Administrator's name, and under Special Access, Other,select WRITE DAC and READ CONTROL. Return to this step after changing theRegistry value in Step 5.

4. Select HKEY_LOCAL_MACHINESECURITYPolicyPolSrvRo.This key has the field : REG_NONE.Double-click this field to edit its values.

5. Change the value from 03000000 to02000000, and exit the Registry. Changing this value sets the machine as a BDCinstead of a PDC.

6. Reboot the server.

7. Resynchronize the domain, fromServer Manager.

This error probably occurs because you have the NT FTP service configured tooutput DOS-style directories, and Netscape uses UNIX conventions when itnavigates. This configuration explains why the error typically does not occurwhen your home directory is the root of a drive and you are accessing a file.

To fix this problem, you need to configure the service to output UNIX-styledirectories. Run regedt32 (the NT Registry editor) to add or modify theMsdosDirOutput Registry value at HKEY_LOCAL_MACHINE on SYSTEMCurrentControlSetServicesftpsvcParameters.

To add the value, follow these steps:

1. Select Edit, and then Add Value.

2. In the Value Name box, enter thename exactly as follows: MsdosDirOutput.

3. In the Data Type drop-down box, setthe data type to REG_DWORD.

4. Click OK.

5. When prompted for the string, enter0 for UNIX listings.

6. Click OK.

7. From Control Panel, Services, stopand restart your FTP Server service (you don't need to reboot).

If you're running Internet Information Server (IIS), you don't need tomodify the Registry. To make this change, start IIS, click the FTP serverproperties, go to the Directories tab, and select UNIX under Directory ListingStyle.

During the replacement or installation of a software component (such as SQLServer or Systems Management Server--SMS), the files needed for the upgrade comefrom the application source, which may predate the service pack. During theapplication installation, some of the files the service pack installed may beoverwritten with older versions from the application source. Reapplyingthe service pack after an upgrade or software product installation will correctthis condition.

An incorrect version of BHNT.SYS causes this problem when you use theNetwork Monitor on a Windows NT Server 3.51 system with SMS 1.1. If NT isinstalled on a FAT partition and the Network Monitor is not startedautomatically, you can reapply the latest service pack to the system.Alternatively, you can perform the following steps:

1. Go to the system32directory, and find the file BHNT.SYS. Rename this file BHNT.OLD.

2. Go to the latest service pack,uncompress the BHNT.SYS file, and place the file in the system32 directory.

3. Reboot the system.

Win95 detects Plug and Play (PnP) devices, but NT 4.0 does not. Therefore,you must manually install the Sound Blaster card driver to use it.

Go to http://creative-ok.creaf.com/wwwnew/tech/ftp/ftp-sb16awe.html#ntand select the Creative Labs Sound Blaster 1.x, Pro, 16 driver from the list.Accept the default settings. To add the driver in NT, click Start, Settings,Control Panel, Multimedia. On the Devices tab, click Add. When you're prompted,shut down and restart the system.

If the system you're installing NT on does not support Logical BlockAddressing (LBA), make sure the partition where you want to install NT is lessthan 540MB. You may also be able to get an updated BIOS from your PCmanufacturer to include LBA.

If your system supports LBA, make sure that Auto Detect is not enabled. Getthe hard disk specifications for cylinders, heads, and sectors--this informationis usually on the label of the hard disk. In your hardware setup, configure yourcomputer to use a custom-defined hard disk with the cylinders, heads, andsectors to match your disk.

If you selected the uninstall option when you applied the service pack, youcan run Update.exe from the service pack and select Uninstall a previouslyinstalled Service Pack. If you cleared the uninstall option when youinstalled the service pack, the files you need for the uninstall aren'tavailable to you. To remove the unwanted service pack, execute the followingsteps:

1. On the same system, install NT 4.0in a new directory.

2. Apply SP3, and select the Uninstalloption. This step will create a hidden directory under your NT root directory,$NtServicePackUninstall$.

3. Copy the $NtServicePackUninstall$directory from the second install to the original .Boot the original install of NT, run Update.exe from SP3, and selectUninstall a previously installed Service Pack. This step will use the$NtService PackUninstall$ files to replace the current files. It will alsoremove all indications that you are running NT 4.0 SP3.

An error is in the %SystemRoot%System32Oemnxppp.inf file that NTinstallation supplies. It does not include the option to add PPTP to aMicrochannel Architecture (MCA) server. Edit the Oemnxppp.inf file to addMCA to the [PlatformsSupported] section as follows:

[Identification]

OptionType = NetTransport

[PlatformsSupported]

ISA

MCA

EISA

"Jazz-Internal Bus"

[Options]

RASPPTP

.

.

.

Multiple SCSI adapters using the same IRQ may cause your problem. Althoughsharing IRQs is legal, you need to dedicate an IRQ to the controller connectedto the SCSI hard disk that NT boots from. Also, be sure to disable the BIOS onthe controllers that are not connected to this disk.

You're on the right track. Some applications can have files on the drivethat your system is still accessing. The drive might have launched theapplication and the application is still open, the application might have leftsome files open, or the application might have created shares that othercomputers access.

If the error still occurs after you shut down all possible services andapplications, try the following steps to eliminate the possibility of anapplication accessing the volume:

1. Log on as Administrator. InAdministrative Tools, Disk Administrator, select the stripe set and click Tools,Assign Drive Letter. Select Do not assign a drive letter.

2. Reboot the server.

3. After logging on, go to DiskAdministrator. Select the stripe set volume, and while pressing the Ctrl key,select Free Space on the replaced drive. Click Fault Tolerance, Regenerate, tobegin regeneration of the stripe set.

4. After regeneration, select thestripe set and click on Tools, Assign Drive Letter. Reassign the original driveletter to the volume.

5. Reboot the server.

You have the clients configured to print directly to the HP JetDirect portand not to the NT shared printer, so the first client to access the printer isin control until the client is rebooted. To fix this problem, you need to removethe DLC protocol and the HP JetAdmin software from each client.

To remove the DLC protocol, go to Control Panel, Network; select the DLCprotocol, and click Remove. Repeat these steps for the HP JetAdmin software.Click OK, and reboot the client. Connect each client to the NT shared printer inControl Panel, Printers.

The user account does not have permissions to the %SystemRoot%System32 directory.To fix this problem, go to the %SystemRoot%System32 directory.You will find that the user accounts that are causingthe shutdowns have restricted permissions. This situation prevents NT fromexecuting. Change the permissions to give all users Read and Execute permissionson the NT files.

Ntbackup.exe in the Spanish version of NT 4.0 is causing this problem.Fortunately, a fix is already available for it. Apply Service Pack 2 (SP2) orSP3 for NT 4.0, or expand Ntbackup.ex_ from SP2 and replace the original filewith the new expanded one.