w2k3 printing issue

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

we had a print server (W2K Advanced Server). Some domain systems
printed to this, without problem. By domain systems, I mean that a
server, in the domain, had a service (running as localsystem) which
was able to issue print jobs.

we upgraded the print server to a W2K3 Enterprise cluster on monday.

it seems now that services on servers, started as localsystem, can no
longer print to the print server. i re-started a service, running it
as a domain account.. and it worked.

any idea where they locked this down in W2K3 and how to un-lock it? i
have multiple systems w/ problems as a result

 

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

"" wrote:
> we had a print server (W2K Advanced Server). Some domain
> systems
> printed to this, without problem. By domain systems, I mean
> that a
> server, in the domain, had a service (running as localsystem)
> which
> was able to issue print jobs.
>
> we upgraded the print server to a W2K3 Enterprise cluster on
> monday.
>
> it seems now that services on servers, started as localsystem,
> can no
> longer print to the print server. i re-started a service,
> running it
> as a domain account.. and it worked.
>
> any idea where they locked this down in W2K3 and how to
> un-lock it? i
> have multiple systems w/ problems as a result

I’m not sure if this is the cause, but a difference between w2k and
w2k3 servers is that with w2k3 servers the ’anonymous logon’
security principal does not belong to everyone. You can do two things
to try if this is the problem:
* Assign anonymous logon the same permissions as everyone to the
printers
* Change the security policy on the w2k3 server called ’network
access - let everyone permissions apply to anonymous users’ to
enabled

I prefer to do the first as it only impacts the printer, against the
second that impacts the whole server

Hope this helps you. Good luck!

--
Posted using the http://www.windowsforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.windowsforumz.com/Active-Directory-w2k3-printing-issue-ftopict404684.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.windowsforumz.com/eform.php?p=1340897

 

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

ok i see how you do option #2....
i agree, option #1 sounds better... how do you go about that though?
Where would you assign priveleges to the anonymous login?

On 5 Aug 2005 00:38:37 -0400, Jorge_de_Almeida_Pinto
<UseLinkToEmail@WindowsForumz.com> wrote:

>"" wrote:
> > we had a print server (W2K Advanced Server). Some domain
> > systems
> > printed to this, without problem. By domain systems, I mean
> > that a
> > server, in the domain, had a service (running as localsystem)
> > which
> > was able to issue print jobs.
> >
> > we upgraded the print server to a W2K3 Enterprise cluster on
> > monday.
> >
> > it seems now that services on servers, started as localsystem,
> > can no
> > longer print to the print server. i re-started a service,
> > running it
> > as a domain account.. and it worked.
> >
> > any idea where they locked this down in W2K3 and how to
> > un-lock it? i
> > have multiple systems w/ problems as a result
>
>I’m not sure if this is the cause, but a difference between w2k and
>w2k3 servers is that with w2k3 servers the ’anonymous logon’
>security principal does not belong to everyone. You can do two things
>to try if this is the problem:
>* Assign anonymous logon the same permissions as everyone to the
>printers
>* Change the security policy on the w2k3 server called ’network
>access - let everyone permissions apply to anonymous users’ to
>enabled
>
>I prefer to do the first as it only impacts the printer, against the
>second that impacts the whole server
>
>Hope this helps you. Good luck!

 

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

got it working!
good call, thank you very much!! used option #1 and now the services
can print...



On Fri, 05 Aug 2005 09:28:24 -0400, BobMarley
<brianh*REMOVEFOREMAIL*@conterra.*REMOVE*.com> wrote:

>ok i see how you do option #2....
>i agree, option #1 sounds better... how do you go about that though?
>Where would you assign priveleges to the anonymous login?
>
>On 5 Aug 2005 00:38:37 -0400, Jorge_de_Almeida_Pinto
><UseLinkToEmail@WindowsForumz.com> wrote:
>
>>"" wrote:
>> > we had a print server (W2K Advanced Server). Some domain
>> > systems
>> > printed to this, without problem. By domain systems, I mean
>> > that a
>> > server, in the domain, had a service (running as localsystem)
>> > which
>> > was able to issue print jobs.
>> >
>> > we upgraded the print server to a W2K3 Enterprise cluster on
>> > monday.
>> >
>> > it seems now that services on servers, started as localsystem,
>> > can no
>> > longer print to the print server. i re-started a service,
>> > running it
>> > as a domain account.. and it worked.
>> >
>> > any idea where they locked this down in W2K3 and how to
>> > un-lock it? i
>> > have multiple systems w/ problems as a result
>>
>>I’m not sure if this is the cause, but a difference between w2k and
>>w2k3 servers is that with w2k3 servers the ’anonymous logon’
>>security principal does not belong to everyone. You can do two things
>>to try if this is the problem:
>>* Assign anonymous logon the same permissions as everyone to the
>>printers
>>* Change the security policy on the w2k3 server called ’network
>>access - let everyone permissions apply to anonymous users’ to
>>enabled
>>
>>I prefer to do the first as it only impacts the printer, against the
>>second that impacts the whole server
>>
>>Hope this helps you. Good luck!