Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I have set up 3 printers, two on a JetDirect 500X and one has its own network card, to an NT server. Whenever a domain user (not me as Admin) prints, a while later the USER: SYSTEM prints (I am auditing to see who prints and see both print jobs) the same thing, which has nailed some people doing embarrassing things, but I can't seem to stop it. Any ANY ideas???? HELP!!

This is what I could find in Microsoft's Technet Knowledgebase:
After you install Service Pack 3 on a computer running Windows NT 4.0,
Hewlett-Packard (HP) printers may function erratically. They may start printing
multiple copies of jobs, multiple or duplicate separator pages, or print
separator pages even though none are selected.
CAUSE
=====
SP3 overwrites the Hprasddui.dll and Hprasdd.dll files installed with HP
drivers.
RESOLUTION
==========
Reinstall the latest version of the Hewlett Packard printer driver to ensure
that the Hprasddui.dll and Hprasdd.dll files are replaced.

2 of 3 printers are brand new, and they have been installed using their own disks. All three do this. I can see them in the spool folder--a second copy just sitting there waiting for me to reboot the server and then they print again. Also, have SP6 installed. Tried changing spooling folders, same thing. Shows a job in the queue, but when you look at the printer, it says "PRINTED"...but still prints again. The two files still in the spool folder are a .shd file and a Shockwave Flash object...what does THIS mean?????? What does Shockwave have to do with printing???

I am not sure what this means. The reference I posted was all I could find on Microsoft's Technet CD. I have not encountered a problem like yours before.
Did this occur only after you enabled auditing or was it happening before that and you are using auditing to track the problem ?
Is Event Viewer showing any error messages under System or Application logs ?

It turns out that, while I gave everyone in my domain "Print" permissions, I deleted the "Creator owner" user because I was
afraid it would give anyone who found the printers on the wider network permission to print on them, which was not true (bear with me--I'm pretty new to this!) If "Creator Owner" is deleted, it seems the users have no rights to manage documents which means they do not self-delete and when I logged in as admin they had stayed in the queue, so they printed again and then deleted because I was the only one left with "Manage Documents" permissions. WHY this happens--why they would actually PRINT again when they have already printed (and show as printed in the queue) I cannot fathom...but they do.

![]() |
Driver Files for NT4
|
dll register server error
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |