NDPS RPM fails after applying 4.83 SP1 for users and power users
(Last modified: 18Apr2003)
This document (10073624) is provided subject to the disclaimer at the end of this document.
fact
Novell Client 4.83 SP1 for Windows NT/2000/XP
Microsoft Windows XP Professional
Microsoft Windows 2000 Professional
symptom
NDPS RPM fails after applying 4.83 SP1 for users and power users
Power users unable to add printers after applying 4.83 SP1
Error: Windows error 5 being returned during the RPM process
NDPPNT.LOG shows a message similar to "NWDPPrtDownloadAndAddDriver2 failed for "<printerobject>", error = 0x0100000A othererror = 0x00000005"
DPRPMLOG.TXT shows a message similar to "Printer <printerobject>: Driver unsuitable for installation (WINDOWS (5) - Access is denied)"
The above errors are returned even if the Driver Signing Policy is set to "Ignore".
On Windows XP using the "Add Printer" wizard, you receive an error stating "You do not have sufficient access to your computer to connect to the selected printer".
fix
Fixed in the Novell Client 4.83 SP2 for Windows NT/2000/XP.
WORKAROUNDS:
For Windows 2000 workstations, you can modify the following registry entry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Driver Signing]
"Policy"=hex:00
Setting this value will temporarily work around the issue by causing the system driver signing policy to be "Ignore" rather than the default of "Warn". Note that a single-byte REG_BINARY value as shown must be used; a four-byte REG_BINARY or REG_DWORD will not be successful in working around this issue. Nor will setting the Windows driver signing policy to "Ignore" using the user interface in the System control panel work around this issue; setting the specific value shown above via the registry is required.
For Windows XP workstations, the only option at this time is to elevate the rights of the users to be Administrators on the local workstations.
This has been fixed in updated NDPS Client libraries for the 4.83SP1 client. These are the DP?WIN32.DLL and DPLRNAME.* dated 26AUG2002 or later and are available in NDPC4831.EXE. Please note that it is very possible that the digital signature error will pop up even with these new modules. However, the printer driver will be able to be installed.
BACKGROUND:
Prior to SP1 for the Novell Client 4.83 for Windows NT/2000/XP, users could receive the Windows digital signature warning when new printers were being installed to the local workstations. This would occur on Windows 2000 and Windows XP workstations depending upon the local workstation's effective driver signing policy. Please see TID10068087, Message: "This driver is not digitally signed!" for additional information.
SP1 includes a change designed to prevent the digital signature warnings from occurring during NDPS printer installations, without requiring that the Windows driver signing policy be turned off entirely on the workstation. However, when workstation users have only Power Users or restricted Users group rights, the Windows error 5 is returned during the attempted printer installation.
This can occur regardless of the Users or Power Users groups having been explicitly granted rights at a Windows level to install new printers, regardless of using the NDPS Remote Printer Management (RPM) feature which does not require the Windows user to have rights to install new printers, and regardless of the Windows driver signing policy having been set to "Ignore" by a workstation administrator (using the System control panel or a group policy).
For Windows 2000 users, setting the driver signing policy to "Ignore" using the specific registry value described above will work around the issue. For Windows XP users, the workstation user will need to have their Windows account rights elevated to Administrators or equivalent.
document
| Document Title: | NDPS RPM fails after applying 4.83 SP1 for users and power users |
| Document ID: | 10073624 |
| Solution ID: | NOVL81580 |
| Creation Date: | 17Aug2002 |
| Modified Date: | 18Apr2003 |
| Novell Product Class: | NetWare |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.