Re: Printing security problem

Hello Neil

And by group archives you mean previous messages in this newsgroup or?

You suggests an SMTP setting? I am open to any suggestions, but I don't see
SMTP having anything to do with printing.

Thomas

"NeilH" <neil@xxxxxxxxx> wrote in message
news:OPudq9gGIHA.3400@xxxxxxxxxxxxxxxxxxxxxxx
Try looking at the group archives!
I seem to remember that this started with SP2 and is something to do with
an
SMTP setting which I think should be off but is on by default?

Neil..

"Thomas Hansen" <t_hansen20@xxxxxxxxxxx> wrote in message
news:e%23i9zjgGIHA.4808@xxxxxxxxxxxxxxxxxxxxxxx
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: Printing security problem
    ... The server has a total of about 50 printers connected to it, ... the jobs get stuck in the queue with the status 'Printing'. ... It doesn't remedy the issue to give standard users full rights to the ...
    (microsoft.public.windows.server.security)
  • Re: RANT: Books with a spine
    ... >this....I had a tough time finding printers that would take the jobs. ... >process, quality control and all. ... >> If your book broke, it most probably was not sewn, or not sewn well. ...
    (rec.music.classical.guitar)
  • Re: RANT: Books with a spine
    ... >>jobs, and the like. ... Amazing that they didn't want the business! ... >>this....I had a tough time finding printers that would take the jobs. ... >>> If your book broke, it most probably was not sewn, or not sewn well. ...
    (rec.music.classical.guitar)
  • 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: print management
    ... "Robert Britton" wrote: ... >>> We have several HP JetDirect based print servers as well ... >>> networked printers with built in network adapters. ... I need the ability to have a night manager move jobs between printers ...
    (microsoft.public.win2000.printing)