similar to: Samba 4.0.5 git. Printer sharing broken?

Hai Manu, > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Manu > Baylac via samba > Verzonden: vrijdag 3 november 2017 20:21 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Unable to upload printer drivers > > Hello Louis and list, > > > Le 03/11/2017 à 10:25, L.P.H. van Belle via samba a écrit :

Hi, I have a question about printer drivers management in Samba4 (Samba version 4.7.6, Ubuntu 18) I use MMC to add new drivers to an existing cups printers, and some of them are simply refused. I know the samba4/cups server is operationnal as i'm able to add new printers or drivers to it through MMC. I guess it's not a permission problem on the server as i perform the operation as

Hi all, i get struck with nearly the same problem as here : https://lists.samba.org/archive/samba/2016-December/205088.html excepted the NT_ error. And the thread ends suddenly without solution. And i tested all that Louis and Rowland proposed. Printer server as domain member but here with rid backend. Debian stretch : samba 4.5.12 (debian package), also tested with 4.6.7 and 4.6.8 (Louis

Hai Manu, Well, i can say... Its not you.. I did the following as test. Startup 2 pc's X64 w7 + w10 Open printer manager tool and connect to the server. Steps done. Create a new printer in cups. => after 15 min, in both pc's the new printer is shown correctly. Test 1 and 2. samba 4.6.8 and 4.6.9 own packages. W7, setup/upload/delete of an HP LaserjetII driver ( a original

Hi, As you all know, CentOS 7 is shipping PHP 5.4, which is OK in some situations. Unfortunately, some applications like OwnCloud require a more recent version of PHP. Up until recently, I've been using PHP 5.6 packages from the Webtatic repository. Despite the bad press this third party repo seems to have, it has been working perfectly for me for a few years. Here's the PHP 5.6 packages

On Tue, Nov 17, 2015 at 08:49:54PM +0000, Richard W.M. Jones wrote: > There was a copy and paste error. It should have read: > > $ md5sum viostor/2k8/amd64/* viostor/w7/amd64/* > d1132fbd27c98f25ea71a6eb4037b2f8 viostor/2k8/amd64/viostor.cat > defccbe48aca1cd97fee4d7b16053b72 viostor/2k8/amd64/viostor.inf > 6da6120368c097806e4ac7fc6b940810 viostor/2k8/amd64/viostor.pdb >

Hi I have a printer connected to a Samba4 AD machine. I set it up using CUPS. It works fine. Is there a howto as to what I need to add to smb.conf to be able to print from windows boxes connected to the domain? Thanks Steve

Hey all, One of that last pieces to be put in place before my site goes live on Samba4 as AD is printer support. Now I've seen https://wiki.samba.org/index.php/Samba_AD_DC_HOWTO#Step_13:_Setup_a_Printer_share and at one point had Group Policy that was deploying a printer on CUPS using AD authentication/Samba shares. However, we found out that when Windows machines printed to this printer, it

I think one - maybe final? - problem. How can I tell the difference between drivers for "client" versions of Windows (eg. Windows 7) and server versions of Windows (eg. Windows 2008 Server)? It seems in many or most cases the drivers are identical, eg: $ md5sum viostor/2k12/amd64/* viostor/w8/amd64/* bbe250c13bf891fd7292ccab9908a63a viostor/2k12/amd64/viostor.cat

Hi Achim, thank you for your effort! I did a couple of tests, from W8.1 with x64 driver which where rather old and therefore disignated for W7x64. But this went stale as well. Therefore I'll give it a try by using a W7-WS for uploading the drivers. Franz >>> Achim Gottinger <achim at ag-web.biz> 06.06.2017 15:27 >>> Hmm after another try an windows 7 client 32 and

Moved the hdd of my DC over to nicer P4 machine. It started as expected. (I have resolved the eth0 driver issue that happens with Debian/Ubuntu servers when you move a functional hdd to a different machine.) Then I decided to change the static ip address of the DC from 192.168.**.54 to 192.168.**.51. That went as expected, except it seems my W7 client cannot connect to my domain, now. It says

Hi I have folder redirection working fine in XP. I see that W7 has taken the same configuration as I made in XP. Here is a screenshot: http://dl.dropbox.com/u/45150875/gpo.png Unfortunately, on w7, whilst the roaming profile is correctly set, there is no folder redirection. Nothing appears in the \\hh1\USERS folder for the user who has logged in. Upon opening the GPO editor as Administrator

W7 client domain member? yes. Logged in as domainAdministrator? yes. "SeDiskOperatorPrivilege" set? yes Read "/Setup_and_configure_file_shares_with_Windows_ACLs"? yes. --- ------------------------- Bob Wooden of Donelson Trophy 615.885.2846 (main) www.donelsontrophy.com [2] "Everyone deserves an award!!" On 2015-01-28 10:40, Marcel de Reuver wrote: >

On 30/01/15 20:48, Bob of Donelson Trophy wrote: > > > Okay, added 'gidNumber: 10000' to the domain users group on DC1. (Was > within my range 500-40000.) > > getnet passwd [user] returns nothing on DC1. > > W7 client still a "no". > > And now? > > Have you tried getent on the member server ? Lets forget W7 for the moment, get the Unix

First, I am sorry. I should know this by now. Last week had an issue with W7 client could not update. I made some adjustments to get W7 updated. Now I am having an issue with update resolution. (Run apt-get update and repositories cannot be find, etc.) So, this tells me that I have messed up my dns resolution. All clients (W7 & linux) point to my DC for DNS nameserver. All clients (W7

Hi Bob, Set the rights like this. > /home 775 > > /home/samba 775 > > /home/samba/DT***RM 775 > > /home/samba/DT***RM/profiles 777 for the profiles, after you set the rights in windows, user profiles folders wil be created with the correct rights. and only accessable by the user.. and from here you shoule be able to set the correct rights. Can you give it a try?

Hai Manu, Can you post the output of: getfacl /var/lib/samba/printers And getfacl /var/lib/samba/printers/x64 And run net rpc rights list accounts -Uadministrator These are often forgotten or wrong set. NT Authority\SYSTEM NT Authority\Authenticated Users Set on the share AND folder rights. Share: SYSTEM: Full control. Share: Verified users: Full controll Folder security: SYSTEM:

Hello, i got some clients (WINDOWS7 and WINDOWS10) to connect to samba shares. OS is openSUSE 12.2; 13.1; 42.1 Samba-Version: 3.6.7; 4.1.22; 4.2.4 smb.conf is shown below. The samba setup is a workgroup setup, the W7-clients are set up to the workgroup 'workgroup'. No further changes are made to the W7-clients. samba setup: groupadd workgroup chgrp -R workgroup /srv/samba chmod -R 770

Le 25/11/2019 ? 09:15, L.P.H. van Belle via samba a ?crit?: > I tested Friday also with a W7 pc. > Not working, im try to see what i can do today on this problem. > > Greetz, > > Louis Hi Louis, Thanks for your help. I'm still investigating on it, but sadly i cannot upgrade to 4.11 as those servers cannot reach external repositories for security reasons (those servers