search for: 5052ci

Displaying 4 results from an estimated 4 matches for "5052ci".

Did you mean: 5052
2024 Oct 07
1
rpcclient setdriver fails with WERR_ACCESS_DENIED
...c printer download with our samba 4.19.4 fileserver which is a domain member of our samba 4.18.2 AD. printer drivers have been installed on the fileserver: root at serv00:# rpcclient -Uprtadmin%pass1 SERV00 -c enumdrivers [Windows x64] Printer Driver Info 1: Driver Name: [Kyocera 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] comm...
2024 Oct 08
1
rpcclient setdriver fails with WERR_ACCESS_DENIED
...fileserver which is a domain member of > our samba 4.18.2 AD. > > printer drivers have been installed on the fileserver: > > root at serv00:# rpcclient -Uprtadmin%pass1 SERV00 -c enumdrivers > [Windows x64] > Printer Driver Info 1: > Driver Name: [Kyocera 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\] > desc...
2024 Oct 08
2
rpcclient setdriver fails with WERR_ACCESS_DENIED
...f > > our samba 4.18.2 AD. > > > > printer drivers have been installed on the fileserver: > > > > root at serv00:# rpcclient -Uprtadmin%pass1 SERV00 -c enumdrivers > > [Windows x64] > > Printer Driver Info 1: > > Driver Name: [Kyocera 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] > > n...
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.