Long delay opening Groupwise messages with iPrint printers installed.

Long delay opening Groupwise messages with iPrint printers installed.
Novell iPrint client version 1.10.00 or later is installed on the workstation.
The IPRINT.INI file on the server has changed.
The ShortInstallName within the IPRINT.INI changed from DEFAULT to something else.
The IPRINT.INI is configured to allow for user printers.
LAN traces show the ShortInstallName being broadcast out via WINS, NDS, etc. in an attempt to resolve the name.
Initial request is slow; subsequent requests are fast.

The problem is resolved with iPrint client version 2.02 or later. iPrint client version 2.02 will be included with NW65SP1.EXE, NW6SP4.EXE, and NW51SP7.EXE, if and when those support packs become available. NOTE: If there are any iPrint printers that are currently installed on the workstation that are experiencing slowness, those iPrint printers will need to be removed and added back to the workstation before the issue will be resolved. Simply upgrading to iPrint client 2.02 will not fix the issue. The printers will need to be reinstalled to completely fix the problem.
The current work around is to change the ShortInstallName back to DEFAULT, uninstall your iPrint printers, and then reinstall them.
Potential workaround:If you have several print providers on your workstation, try to remove those print providers from your workstation. By reducing the number of print providers, you can potentially decrease the delay Windows incurs while it goes out and checks each one of the print providers.

User printers and ShortInstalledNameMUSTbe set in order for this problem to occur. If user printers are set or ShortInstallName is set, then the problem doesn't occur. The problem is caused by the Windows operating system. Windows will ask the iPrint print provider if a certain printer belongs to it. The iPrint print provider will respond if the printer belongs to it or not. If the iPrint print provider responds that the printer blongs to iPrint print provider, Windows should give the request to the iPrint print provider. Instead Windows asks the other print providers installed on the workstation if they know about this iPrint printer. That is what is causing the delay. If you take a LAN trace, you will see LAN traffic trying to resolve the ShortInstallName.
Clients prior to iPrint client version 1.10.00 use the IPP URL for printer names. It is very easy to have a long IPP URL as the printer name. Some older applications do not show the full printer name. Therefore, there was a need to shorten the printer name. That feature was included in the 1.10.00 version of the iPrint client. That version of the iPrint client shipped with NW6SP3.EXE and NW51SP6.EXE.

Formerly known as TID# 10082641