Click here to get back home

Printing security problem
 Home | NewsGroups | Search | About
Login Password
Register Now!
 microsoft.public.windows.server.security    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content
Subject Author Date
Printing security problem Thomas Hansen 10-29-2007
Posted by Thomas Hansen on October 29, 2007, 4:51 am
Please log in for more thread options
 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



Posted by NeilH on October 29, 2007, 5:38 am
Please log in for more thread options
 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..

> 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
>
>



Posted by Thomas Hansen on October 29, 2007, 5:51 am
Please log in for more thread options
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

> 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..
>
>> 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
>>
>>
>
>



Posted by NeilH on October 29, 2007, 6:56 am
Please log in for more thread options
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..

> 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
>
> > 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..
> >
> >> 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
> >>
> >>
> >
> >
>
>



Posted by Thomas Hansen on December 15, 2007, 8:40 am
Please log in for more thread options
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


>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
>


Similar ThreadsPosted
xp to win2k3 printing problem July 27, 2006, 5:00 am
printing security July 26, 2006, 7:50 am
printing security May 17, 2007, 1:44 pm
RE: Security Problem... April 16, 2007, 7:46 pm
No more printing November 10, 2005, 3:39 pm
Problem Security on object in AD!!! February 27, 2006, 7:57 am
Folder security problem April 6, 2006, 1:27 am
Domain Printing February 7, 2006, 11:48 pm
Strange folder security problem October 4, 2006, 3:45 pm
MSMQ 2003 Security Problem December 10, 2007, 10:40 am

Our other projects:

Art Dolls, Fairies and Mermaids - Sunnyfaces.net

Roy's Linux, Programming and Search Engines messages

1-Script XML SitemapXML Sitemap