Currently we have a mix of printers (HP, Xerox, Kyocera etc.) shared from NT4 and Windows 2000 servers.
We have noticed that when printing documents attached to Windows 2000 servers, the job spool size can increase up to 800% more than its NT4 counterpart for the same doucment. As an example, 1.25MB for a test page! As you can imagine printing even a 5 page document over the WAN now is a nightmare.
All printers in the company are mapped using standard file and print sharing (\\servername\printershare). Irregardless of which flavour of server these are hosted on. Workstations are NT4/XP.
All printers are setup on the servers using a mixture of Standard TCP/IP Printing and LPR under Windows 2000 and LPR under NT4.
I found that if I installed Print services for Unix on my XP machine, and added a printer locally as an LPR port, referencing it using <servername>:<queuename> my spool size reduced dramatically.
I find it surprising that mapping a printer using \\<servername>\<sharename> causes such an issue, and I am sure there is an explaination for it.
Short of creating login scripts specifcally to map users printers as local LPR ports I would like to find a solution that ties in the with the current way we work.
I have looked around technet - but to no avail. I am not a printer expert, so I may just be looking for the wrong thing.
Anyone else come across this problem?