StatusReported to Engineering
For the purpose of explaining this issue, there are 3 ways to load a print manager on NetWare:
1. NDPSM .MyPrintManager.Organization.OU
2. NDPSM .MyPrintManager.Organization.OU /IPADDRESS=[An IP Address bound to the server]
3. NDPSM .MyPrintManager.Organization.OU /DNSNAME=[A DNS Name used for the server or Print Service]
The way in which the Print Manager is loaded will dictate:
a. The name of the iPrint printer installed to the
b. How the iPrint printer installed to the workstation communicates with the Print Server (IP Address or DNS Name).
There is a feature in the iPrint client that looks up the way the Print Manager is loaded (by IP Address or DNS Name) and auto corrects the iPrint printer installed to the Windows workstation to reflect the administrator's choice (IP or DNS). This auto-remove/auto-install of the iPrint printer works unless the ShortInstallName feature is being implemented. The bug is being investigated by Novell.
Explanation on the ShortInstallName
The ShortInstallName feature is enabled in sys:\Apache2\htdocs\ippdocs\iprint.ini. Change ShortInstallName = DEFAULT to ShortInstallName = [WhateverName]. Making this feature take effect will require the printer to be reinstalled to the workstation. Instead of the name in the Windows Printers folder displaying like:
[pa_name] on [ipp://IPorDNS]
The name will display as:
[pa_name] on [WhateverName]
This can shorten the length of the printer name a lot, especially if a DNS name is being used.