Any chance of making this into a Novell TID somewhere?. I had to sift
through lots of stuff to come up with the following solution.

Issue: (All server netware 6.5 Sp2 edir
After a tree merge, the servers from the old tree could no longer use
imanager to configure print driver profiles.
A login prompt would come up with the old tree name displayed as
the "realm". This could not be changed. Authentication was impossible.

-Change this file: sys:\apache2\iprint\ipp.conf. The following line will
have the old treename. Change it to the new as shown.
AuthName "NewTreeName"
-Stop Apache : ap2webdn
-Stop Tomcat : tc4stop
-Stop LDAP : unload nldap
-Copy sys:\public\rootcert.der from a server that always had the correct
tree name to the server in question. Overwrite the current rootcert.der.
ALTERNATIVE: Export the Self signed certificate from ConsoleOne and use
that instead. (Open CA object in .security container Select Certificates \
Self Signed Cert. Do not export private key.

-Look at SSL Certificate objects in the container related to the servers
that this issue affected. ConsoleOne SSL Certificate... Certificates tab
shows that the certs are issues by old tree name.
-Deleted "SSL Certificate*" objects from container where issue arises.
-Run PKIDIAG on server in question. Set option 4 to fix and run it. This
will recreate the SSL objects based on the rootcert.der file.
-Then (From TID 10082626) -
Use ConsoleOne
-- Delete the LDAP Group Object. Delete the LDAP server object.
- Re-create the Group object by right-clicking on the Container that holds
the NCP server object, select new object and select LDAP Group Object. You
can ignore for now the message about obsolete syntax mappings. Accept the
message about the need to have a LDAP server object in the group. Give the
server group a descriptive name such as LDAP Group - Servername. Click on
OK about the need to have a LDAP server in the group.
- Re-create the LDAP server object by right-clicking on the NCP server
objects container as above, new object and select LDAP Server object.
Again a descriptive name is helpful such as LDAP Server - Servername. Also
select Define Additonal Properties so we do not have to open the object
after creation to do the following. On the General Tab use the selector to
associate the Host Server (NCP Server object) to this newly created LDAP
Group. Do the same on the next line to associate the LDAP group you
created before to this LDAP server object. Click apply and ok.
-Start Apache : ap2webup
-Start Tomcat : tomcat4
-Start LDAP : load nldap
All should now work OK.
No reboot necessary.