Printing security problem

[Thomas Hansen]

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

[NeilH]

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_han...@hotmail.com> wrote in message
news:e%23i9zjgG...@TK2MSFTNGP05.phx.gbl...

[Thomas Hansen]

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" <ne...@nospam.uk> wrote in message
news:OPudq9gG...@TK2MSFTNGP03.phx.gbl...

[NeilH]

Yes, previous messages in this newsgroup.

Sorry but I don't fully remember the details, but a few weeks ago someone
sent out a message which detailed what was the problem and how to sort it
out.

Below is the text from a message. I can't confirm the details are correct
but it is worth trying. Also I can't tell you who sent it as the person
decided not to provide any name

=Go to TCP/IP port settings on the print server, uncheck the SNMP Status
Enabled box. The printers are not replying to the SNMP =packets to sent from
the print server and thus the print server believes their status is offline.
Unchecking the box will disable this test =and printers will show online.
Simple fix to a real headscratcher.

Neil..

"Thomas Hansen" <t_han...@hotmail.com> wrote in message

news:OPpA8EhG...@TK2MSFTNGP02.phx.gbl...

[hjacobson]

The symptoms described by Thomas Hansen at the top of this thread are
identical to what I witness.

Unfortunately SNMP is not enabled for any of my 1022n printers (per
NeilH below). I wish that were the case; below would be a solution to
a chronic nagging problem!

A google groups search for 1022n and Windows Server 2003 brings up
this thread only.

I'll do variants of the search however anything else comes to mind?

Thank you,
Harry

[mine...@yahoo.com]

> > Neil..- Hide quoted text -
>
> - Show quoted text -

I experienced this exact problem. Only Admins could print--user jobs
would only go through after restarting the print spooler service on
the server. I first thought it was due to the drop to the printer
being quite long and through a small switch, but upon moving it to a
drop near the server room, I determined that this was not the case. I
disabled SLP and mDNS through the web config and then rebooted the
printer. Since then, all users have been able to print without any
problems. Hope this is helpful.

[Thomas Hansen]

I came up with a solution that completely solved the problem.

Instead of using the original driver that shipped with the LaserJet 1022n, I
am now using the HP Laserjet III driver that comes with Windows. This driver
works perfect with the 1022n but without all the troubles of the other
driver.

And as a bonus the printer now also works with our printing account system.

I hope that this solution might help others in the same situation.

Regards
Thomas Hansen

"Thomas Hansen" <t_han...@hotmail.com> skrev i meddelelsen
news:e%23i9zjgG...@TK2MSFTNGP05.phx.gbl...

[slee...@gmail.com]

This works great and its simple. On the server Change this setting.
Go to the 1022n printer properties, Configure tab, and make sure
status messaged are OFF. No need to change anything else.