Environment
Novell iPrint Client 4.05
Novell NetWare 6.5 SP3
Situation
Error: "iPrint Client- You do not have sufficient privileges to fulfill the request."
Unable to access secure page https://ipaddress/ipps
Unable to install secure printer.
Error: "Winsock 10061." when uploading drivers to the broker.
Error: "Printer Authentication Failed. Do you want to try again?" after attempting to authenticate to create a Printer Driver Profile.
Resolution
1. Download and install the latest iPrint Plugin for
NetWare.
- Go to download.novell.com.
- Choose "iPrint" from the drop down list under "Product or
Technology"
- Important: Click the "View" button for Install
Instructions.
- Complete the installation of the new iPrint Plugin.
2. Install the latest iPrint client.
- Search Novell's File Finder for nipp.exe.
- Install this version of the iPrint client to the workstation
performing this iPrint/iManager operation.
Additional Information
For those receiving the 401 error when doing secure printing, the above fix (updating iprint plugin and client) will not help. The rest of this TID must be read and followed to resolve the problem. There are several reasons the LDAP authentication can fail:
b. CN doesn't equal the UID
c. Multiple Organization objects
4. Certificate Timeout
SYS:\Apache2\iprint\ipp.conf references the authenticating server
by DNS name. If the DNS lookup takes longer than expected, a 401
error will be returned.
5. Rootcert.der is corrupt
setting err = -5875. Error stack:
sslv3 alert bad certificate - SSL alert number 42
6. PHP is installed on the server.
PHP has a conf file that is loaded through the httpd.conf
file using an include statement. (include
sys:\Apache2\conf\mod_php.conf). The PHP apache configuration file
loads other NLMS, one of which is PHP_LDAP.NLM. PHP_LDAP and
AuthLDAP (AuthLDAP is used by iPrint) conflicts with each
other.
No code changes are planned to be made to address this error. Determine which condition is causing the 401 error in your environment and make the change suggested below to resolve the problem. The below suggestion numbers correlate to the above cause numbers:
1. Duplicate CN's
2. The uniqueID attribute is not set on the
user.
b. Choose "eDirectory Administration"
c. Choose "Create Object" - create a user that has no rights and no
password
e. Under the "Authentication Options", browse to the user created
in Step c. Click Apply.
Reason 2: CN doesn't equal the UID - Compare the CN value to the
uniqueID attribute by going to the properties of the user and
choosing the "Other" tab. If there is a difference, then change the
uniqueID value to match the CN.
to
AuthLDAPURL "ldaps://[IPorDNSofPrintServer]/???(objectClass=user)"
4. Certificate Timeout.
to
AuthLDAPURL ldaps://localhost/O=[OrganizationName]???(objectClass=user)
Use the word localhost. Restart Apache to make that take affect. (ap2webdn.ncf and ap2webup.ncf)
5. Resolve the certificate problem.
6. PHP is installed on the server.
a. If PHP is not needed on the server, simply comment out
b. Copy (not move) SYS:/PUBLIC/rootcert.der to
SYS:\PHP5\Certs\.
c. Change the value of the ldap.ssl_cert_dir variable in the
PHP.INI file
7. Use NWAdmin to upload drivers.
8. Install iPrint client version 3.x on administrator
workstations.
The iPrint client prior to version 4.x does not perform the
additional authentication to upload drivers to the Broker using
iManager. Novell does not recommend this as a solution, but as a
temporary workaround until the real cause and resolution is
determined. When using the 3.x iPrint client, the rights are
obtained through the Public trustee assignment to the XFER
directory.
How to export the Self Signed Certificate from ConsoleOne
- type PKIDIAG at the server console
- enter administrator username and password
- option 4
- option 6
- option 0
c. Select Certificates -> Self Signed Certificate
d. Do not export the private key.
e. Make a back up of SYS:\PUBLIC\RootCert.der
g. Copy new Self-signed certificate from c:\RootCert.der to SYS:\PUBLIC\RootCert.der
- Stop Tomcat: tc4stop
- Start Tomcat: tomcat4
- Start Apache: ap2webup
How to export the SSL
Certificate from ConsoleOne
- properties of the LDAP server object
- Select the SSL/TLS configuration tab
- Server Certificate will show which certificate is being
used.
b. To resolve the certificate problem:
- Delete the SSL Certificate that LDAP is using in
ConsoleOne.
- Manually recreate the Certificate.
- Right-click the container object
- Select New, Object, NDSPKI:Key Material
- Give the Certificate a name. This can be the same name as the
previous certificate or a different name.
- Creation Method should be standard
- Click Next, click Finish
- Go into the LDAP server object
- Select the SSL/TLS configuration tab
- Enter in the new certificate in the Server Certificate
field
- Go back to the General tab and click Refresh NLDAP Server
Now
- Click OK
How to capture an LDAP trace
using DSTrace:
1. Configure the LDAP Server Object
Using iManager:
a) Launch iManager (https://IPaddressOrDNS/nps/iManager.html)
b.) eDirectory Administration
c.) Modify Object
d.) Browse to container where the iPrint server resides, choose the"LDAP Server - [ServerName]" object.
e.) Go to the "Tracing" properties on this object.
Using ConsoleOne:
a.) Launch ConsoleOne
b.) Highlight the container that contains the iPrint Server
object.
c.) Right click the "LDAP Server - [ServerName]" object and choose
Properties.
d.) Click the "Screen Options" tab
Continued steps using Either ConsoleOne or iManager:
f.) Make sure all of the following options have check marks in
their boxes:
- Critical Error Messages
- Non-critical Error Messages
- Configuration Processing
- Informational Error Messages
- Search Response Summary
- Messages from LDAP Extended Operations
- Connection Information
- Server Console Messages for LDAP
g.) Click Apply
2. Configure DSTrace (Server Console):
a.) DSTRACE (this will load the NLM, and of note, none of the +
or - flags are case sensitive)
f.) Load NLDAP (doing this when the trace is on will help verify
LDAP is listening on it's ports)
g.) Duplicate the problem.
h.) DSTRACE OFF (turns off tracing to file and screen)
j.) Read the log file at SYS:\SYSTEM\DSTRACE.LOG file
How to capture debug Apache logs
1. Modify the following line in sys:\Apache2\conf\httpd.conf
LogLevel warn
2. Restart Apache:
3. Duplicate the problem
Formerly known as TID# 10097177