Printing security problem



I have a strange problem on our Windows Server 2003 print server.

The server has a total of about 50 printers connected to it, four of them
being HP Laserjet 1022n, connected via standard TCP/IP ports.

When standard users (non-admin) try to print to these four printers, the
jobs spool fine in the queue, but there is no activity on the printer, and
the jobs get stuck in the queue with the status 'Printing'.

If I restart the spooler service, the jobs in the queue print just fine.

If I print to the same printer from the same computer as the above mentioned
example with the only difference being that it is my user account (domain
admin) that is logged in, everything works just fine.

It makes sense that the jobs print, when I restart the print spooler because
I can see in the event log that when I restart the spooler, the print jobs
are no longer owned by the user that submitted the job, but by the SYSTEM
account which also has adminstrative rights.

All the other printers on the server works just fine.

It doesn't remedy the issue to give standard users full rights to the
printer

I must conclude that this must be som kind of security rights issue since I
as administrator can print without problems and standard users cannot.

Can anyone give a hint to what I should do to remedy this situation

Best regards
Thomas Hansen, Denmark


.



Relevant Pages

  • Re: Windows 2008 Print Server
    ... appliances you may be able to backup the printers and drivers using Print ... Total Jobs Spooled 44,220 ... we will be decommissioning an old server which is an HP DL360G3 ... We are slowly starting to introduce Server 2008 into our environment. ...
    (microsoft.public.windows.server.general)
  • Re: SBS Server 2003 R2 Premium
    ... I was only thinking DHCP if you had two SBS boxes on the same LAN, so that's probably not an issue. ... Those directories should be empty unless there are jobs queued. ... I'm guessing that since all the client PCs are having this issue, if there are files that need to be deleted, they're on the server. ... Good thing I didn't put any money on this one - I would have bet on the leftover printers from the old server, ...
    (microsoft.public.windows.server.sbs)
  • Re: Shared network printer conflict problem?
    ... Make sure there are no stray files in the spool directory on the workstation ... Those directories should be empty unless there are jobs ... with users connecting to them through our SBS 2003 server. ... printers work but after a while a job will get stuck and all the other ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows 2008 Print Server
    ... even with 1 GIG adding 160 printers is not an issue ... appliances you may be able to backup the printers and drivers using Print ... Total Jobs Spooled 44,220 ... we will be decommissioning an old server which is an HP DL360G3 ...
    (microsoft.public.windows.server.general)
  • Re: !!HELP!! Pulling my hair on this one. Printer problems. Really need some help on this.
    ... Yes Larry I have already moved them off of the SBS server and onto a high ... When the printers were connecte they did show as being offline. ... have workstations connected are plugged into the same. ...
    (microsoft.public.windows.server.sbs)