Re: "Access denied, unable to connect" viewing shared print queues
- From: "Steve M" <steve@xxxxxxxxxxxxxx>
- Date: Fri, 15 Apr 2005 08:15:53 -0400
I think I found it. The desktop group policy has "Access this computer from
the network" set to only Administrators. When I added Users it worked. So
the User needs to be able to access his own PC over the network. Who would
think.
Thanks for your help!
"Alan Morris(MSFT)" <alanmo@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:425eee8c$1@xxxxxxxxxxxxxxxxxxxxx
> not sure but it's a permissions issue. I'm just a spooler guy.
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Steve M" <steve@xxxxxxxxxxxxxx> wrote in message
> news:e7RYlbSQFHA.3716@xxxxxxxxxxxxxxxxxxxxxxx
> > So then why does the problem clear up if I give the user local
> > administrator
> > rights?
> >
> >
> > "Alan Morris(MSFT)" <alanmo@xxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:425ebd41$1@xxxxxxxxxxxxxxxxxxxxx
> >> this is an issue when the print spooler on the print server is getting
> >> access denied contacting the spooler service on the client machines.
> >>
> >> When the client opens the queue remotely the server connects to the
> >> client
> >> and displays the jobs in the queue. Since the server is blocked by the
> >> client, it post an access denied.
> >>
> >> --
> >> Alan Morris
> >> Windows Printing Team
> >> Search the Microsoft Knowledge Base here:
> >> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >>
> >> "Steve M" <steve@xxxxxxxxxxxxxx> wrote in message
> >> news:uGXP1MSQFHA.1472@xxxxxxxxxxxxxxxxxxxxxxx
> >> >I am having a problem where all non-administrators get an error
message
> >> > "Access denied, unable to connect" when they open up their network
> > printer
> >> > queue window. The clients are windows 2000 Pro machines and the
> >> > servers are windows 2000 domain controllers. They can print to the
> > shared
> >> > printers fine but they cannot see the print queue nor delete their
> >> > jobs. Domain admins can do this fine. The printers are installed on
> >> > Windows 2000 domain controllers with SP4. This is not a problem for
> >> > the
> >> > users if they install a printer on a windows 2000 member server. The
> >> > users
> >> > have a group policy that restricts security. Taking the PC's out of
> >> > the
> >> > group policy lockdown does fix the problem. So I am thinking there
is
> >> > something in the group policy on the desktops that is causing the
> > problem
> >> > but I haven't found out what setting is doing it. If a domain admin
> > logs
> >> > into the locked-down PC they do not get the error. Here are the
> >> > printer
> >> > configuration of the lockdown policy:
> >> >
> >> > Policy Setting
> >> > Allow printers to be published Disabled
> >> > Allow pruning of published printers Enabled
> >> > Automatically publish new printers in Active Directory
> >> > Disabled
> >> > Check published state Enabled
> >> > Computer location Disabled
> >> > Custom support URL in the Printers folder's left pane
Disabled
> >> > Directory pruning interval Not configured
> >> > Directory pruning priority Not configured
> >> > Directory pruning retry Not configured
> >> > Disallow installation of printers using kernel-mode drivers
> >> > Not
> >> > configured
> >> > Log directory pruning retry events Not configured
> >> > Pre-populate printer search location text Not configured
> >> > Printer browsing Not configured
> >> > Prune printers that are not automatically republished Not
> >> > configured
> >> > Allow Print Spooler to accept client connections Not
> >> > configured
> >> > Web-based printing Disabled
> >> >
> >> >
> >> > Any ideas?
> >> >
> >> >
> >>
> >>
> >
> >
>
>
.
- Follow-Ups:
- Re: "Access denied, unable to connect" viewing shared print queues
- From: Alan Morris\(MSFT\)
- Re: "Access denied, unable to connect" viewing shared print queues
- References:
- "Access denied, unable to connect" viewing shared print queues
- From: Steve M
- Re: "Access denied, unable to connect" viewing shared print queues
- From: Alan Morris\(MSFT\)
- Re: "Access denied, unable to connect" viewing shared print queues
- From: Steve M
- Re: "Access denied, unable to connect" viewing shared print queues
- From: Alan Morris\(MSFT\)
- "Access denied, unable to connect" viewing shared print queues
- Prev by Date: Application started from a "win services" doesn't see network pri
- Next by Date: Move PrintServer Queues toanother Drive
- Previous by thread: Re: "Access denied, unable to connect" viewing shared print queues
- Next by thread: Re: "Access denied, unable to connect" viewing shared print queues
- Index(es):
Relevant Pages
|
Loading