Displaying 4 results from an estimated 4 matches for "edv04k".
Did you mean:
edv03
2024 Oct 07
1
rpcclient setdriver fails with WERR_ACCESS_DENIED
...cera TASKalfa 5052ci NAEV]
CUPS-printers have been installed and are working when used
from our windows workstations with locally installed drivers.
root at serv00:# rpcclient -Uprtadmin%pass1 SERV00 -c enumprinters
flags:[0x800000]
name:[\\SERV00\]
description:[\\SERV00\,,Edv04K]
comment:[Edv04K]
But setting the driver fails:
root at serv00:# rpcclient -Uprtadmin%pass1 SERV00 -c 'setdriver Edv04K
"Kyocera TASKalfa 5052ci NAEV"'
result was WERR_ACCESS_DENIED
I assume this happens due to missing SePrintOperatorPrivilege for
user prtadmin.
But ho...
2024 Oct 08
1
rpcclient setdriver fails with WERR_ACCESS_DENIED
...PS-printers have been installed and are working when used
> from our windows workstations with locally installed drivers.
>
> root at serv00:# rpcclient -Uprtadmin%pass1 SERV00 -c enumprinters
> flags:[0x800000]
> name:[\\SERV00\]
> description:[\\SERV00\,,Edv04K]
> comment:[Edv04K]
>
> But setting the driver fails:
>
> root at serv00:# rpcclient -Uprtadmin%pass1 SERV00 -c 'setdriver Edv04K
> "Kyocera TASKalfa 5052ci NAEV"'
> result was WERR_ACCESS_DENIED
>
> I assume this happens due to missing SePrin...
2024 Oct 08
2
rpcclient setdriver fails with WERR_ACCESS_DENIED
...ed and are working when used
> > from our windows workstations with locally installed drivers.
> >
> > root at serv00:# rpcclient -Uprtadmin%pass1 SERV00 -c enumprinters
> > flags:[0x800000]
> > name:[\\SERV00\]
> > description:[\\SERV00\,,Edv04K]
> > comment:[Edv04K]
> >
> > But setting the driver fails:
> >
> > root at serv00:# rpcclient -Uprtadmin%pass1 SERV00 -c 'setdriver Edv04K
> > "Kyocera TASKalfa 5052ci NAEV"'
> > result was WERR_ACCESS_DENIED
> >
> > I...
2024 Oct 08
1
rpcclient setdriver fails with WERR_ACCESS_DENIED
On Tue, 8 Oct 2024 14:58:11 +0200
Peter Koch via samba <samba at lists.samba.org> wrote:
> Hi Rowland,
>
> Thanks very much for your quick response.
>
> > Have you tried the command with a member of Domain Admins instead of
> > Administrator ?
>
> I just did and I now feel that something is wrong with
> our Administrator-account.
Probably not.