Error The current printer driver is not compatible with a policy enabled on your computer that blocks Windows NT 4.0 or Windows 2000 kernel mode drivers

Error The current printer driver is not compatible with a policy enabled on your computer that blocks Windows NT 4.0 or Windows 2000 kernel mode drivers

Release

Windows 2003 server SP2,Windows XP

Problem

When you install printer drivers , you may receive the following error message and cannot install printer.

“Unable to Install Printer. The printer driver is not compatible with a policy enabled on your computer that blocks Windows NT 4.0 drivers. If you want to use this driver, contact your system administrator about disabling this policy”

Solution

This behavior occurs because Windows does not support Kernel mode print drivers by default.

For windows XP

Open the group policy editor by typing gpedit.msc on RUN prompt and locate the path

Under Local Computer Policy, double-click Computer Configuration. Double-click Administrative Templates, and then double-click Printers.Right-click Disallow installation of printers using kernel mode drivers, and then click properties.On the Setting tab, click Disabled, and then click OK.

If you enable this the installation of kernel-mode printer drivers will be prevented.

For updating group policy use gpupadte /force command in command prompt

For windows 2003 server

Open the group policy editor by typing gpedit.msc on RUN prompt and locate the path

Under Local Computer Policy, double-click Computer Configuration. Double-click Administrative Templates, and then double-click Printers.Right-click Disallow installation of printers using kernel mode drivers.

or

Default Domain Controller Policy / Computer Configuration / Administrative Templates / Printers / Disallow installation of printers using kernel-mode drivers. And then click properties.On the Setting tab, click Disabled, and then click OK.

For updating group policy use gpupadte /force command in command prompt

Server not booting due to active directory corrupt

Problem:      Error shows as " security accounts manager initialization failed because of the following error: Directory Services cannot start. Error status 0xc00002e1. "

Causes:                    This problem occurs because one or more of the following conditions are true:

Ø  The NTFS file system permissions on the NTDS folder are too restrictive.

Ø  The drive letter of the volume that contains the Active Directory database has changed.

Ø  The Active Directory database (Ntds.dit) is corrupted.

Ø  The NTDS folder is compressed.

Scenario:        Customer is having Windows 2000 server and four clients of Windows XP. All these machines are connected in network via workgroup. While powering on – server not booting with the error denoted above.



Solution:     
To avoid reinstallation of operating system, we can demote as member server.

1.       Restart/ Start the server in Directory services restore mode

2.       Login with username and password given in time of Active directory installation.

3.       Start à Run à Regedit

4.         Change from old  "ProductType"="LanmanNT" to new "ProductType"="ServerNT" in the following path [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ProductOptions]

5.       Restart the Server

If need to reconfigure Active directory configuration

6.       delete the folder "NTDS".( c:\winnt\ntds )

7.       Reconfigure the domain &rejoin the clients again.

Add/Remove programs applet shows blank

Add/Remove programs applet shows blank

Release

Windows 2003 server

Problem

          While opening the Add/Remove programs its shows nothing. No programs are listed on the control panel applet.

Solution

  To solve this issue, open the command prompt by typing the cmd on the Run prompt.

Type the command

   regsvr32 mshtml.dll and press enter. If it is succeeded it will shows the result as

dllregisterserver in mshtml.dll succeeded.

Then enter the following command regsvr32 shdocvw.dll –I and press enter. Confirm the dll succeeded message.

 Finally  execute the regsvr32 shell32.dll –I command.

Restart the computer.

                               ****************

Network and Dial-Up Connections Icons May Be Missing

After you click Start, point to Settings, and then double-click Network and Dial-up Connections, or Right-Click My Network Places on the desktop and select properties, you may experience one or more of the following symptoms:

• The network adapter has a resource conflict with another device, causing the Local Area Connection icon not to be displayed. Note that Device Manager may incorrectly show the device to be working properly.
• The Local Area Connection icon may be missing.
• The Make New Connection icon may be missing.
• When you double-click Make New Connection, you may receive the following error message:

Unable to create the specified connection. This can be caused by insufficient memory or not enough disk space.

CAUSE

This behavior can occur because of one or more of the following reasons

This behavior can occur because of one or more of the following reasons:

• The Plug and Play service is not running, causing the Local Area Connection icon to not be displayed.
• The Remote Procedure Call (RPC) service is not running, causing the Make New Connection icon to not be displayed.
• You used the Dcomcnfg.exe tool to change DCOM default settings, causing the error message listed earlier in this article to be displayed.
• One of the following network dlls is not properly registered.
• Netcfgx.dll
• Netman.dll
• Netshell.dll

• The Network Connections service is disabled or is not started, causing the Local Area Connection icon to not be displayed.

RESOLUTION

To resolve this behavior, use the appropriate method: Verify That the Device R...

To resolve this behavior, use the appropriate method:

Verify That the Device Resources Are Correct

To resolve this behavior:

1. Obtain the network adapter configuration utility from the manufacturer of the network adapter. Typically, you must boot the computer from an MS-DOS or Windows 95/98 Startup disk to run these utilities.
2. If the network adapter uses jumpers for its settings, verify that the settings do not conflict with another device and manually change them to a resource setting that is not currently in use.
   
   NOTE: You may need to remove all devices except the NIC and add them back one at a time to determine which device the network adapter conflicts with.

Start the Plug and Play Service

To resolve this behavior:

1. Click Start, point to Programs, point to Administrative Tools, and then click Computer Management.
2. Double-click Services and Applications, click Services, and then double-click Plug and Play.
3. In the Startup type dialog box, click Automatic, click OK, and then restart your computer.
   
   NOTE: If the Local Area Connection icon is still missing, press F5 several times to refresh the screen. Also, you may try restarting your computer in Safe Mode with Networking.

Start the RPC Service

To resolve this behavior:

1. Click Start, point to Programs, point to Administrative Tools, and then click Computer Management.
2. Double-click Services and Applications, click Services, and then double-click Remote Procedure Call (RPC).
3. In the Startup type dialog box, click Automatic, click OK, and then restart your computer.
   
   NOTE: If the RPC Service is disabled, you may need to use the Recovery Console. In Recovery Console, run Enable RPCSS Service_Auto_Start, and then restart your computer.
   
   NOTE: If the Make New Connection icon is still missing, press F5 several times to refresh the screen. Also, you may try restarting your computer in Safe Mode with Networking.

Reset Default DCOM Permissions

To work around this problem:

1. Click Start, click Run, type dcomcnfg, and then click OK.
2. On the Default Properties tab, click any setting other than Anonymous in the Default Impersonation Level box. The default setting is Identify.

Register the Following Dlls

1. Click Start, click Run, and then type cmd.exe on the Open line.
2. Type the following lines, and then press ENTER after you type each line:

3.     regsvr32 netshell.dll

4.     regsvr32 netcfgx.dll

5.     regsvr32 netman.dll

6. Restart the computer.