search for: laverenz

Hi, I successfully upgraded our servers to 3.06 last night and almost everything works great so far. One point that made me happy about 3.06 was this one: >From the Release Notes: * Ensure home directory service number is correctly reused (inspired by patches from Michael Collin Nielsen ). There still seems to be one small bug left: when a user logs out and in again within a short period

Hi all, when you join a linux server to an active directory with "realm" it uses "sssd" as default. This works well as long as you just want to be a simple domain member. As soon as you want a real member server, with acls for example, you need winbind instead of sssd. You can't even connect to or configure your server with "net rpc" without using winbind,

On 08/06/2019 21:32, Rowland penny via samba wrote: > On 08/06/2019 16:24, Uwe Laverenz via samba wrote: >> Hi all, >> >> when you join a linux server to an active directory with "realm" it >> uses "sssd" as default. This works well as long as you just want to >> be a simple domain member. >> >> As soon as you want a real...

On 08/06/2019 16:24, Uwe Laverenz via samba wrote: > Hi all, > > when you join a linux server to an active directory with "realm" it > uses "sssd" as default. This works well as long as you just want to be > a simple domain member. > > As soon as you want a real member server, with acls fo...

It seems like the files sent to the samba spool and then over to CUPS seem to stay in the /var/spool/samba directory indefinately. Is there a fix to this via a configuration, or just setting up a cron job to purge? Thanks

Hi, we have Samba 2.2.8a+LDAP 2.0.27 domain controllers running on our Debian servers and I'm preparing the update to Samba 3.0.0. Everything seems to work fine so far, except that I get some error messages that I don't understand. Could someone please explain them to me? Should I wait for the next Samba release before switching to 3.x? The error messages: When a user logs into the

My samba setup cannot handle files whose names contain german umlauts (????). The server is samba 2.2.8a-1 on Redhat 8.0 (from the binary RPM from the samba site), the client is running WinXP Home Edition. When I create a file whose filename contains umlauts on the samba share from the WinXP machine, the filename is displayed with question marks instead of the umlauts by ls on the linux machine,

...main above is two RHEL7.6 VMs with samba 4.10.4 and the rpms from there: http://nova.polymtl.ca/~coyote/dist/samba/samba-4.10.4/RHEL7 Regards, Vincent On Mon, 10 Jun 2019, Rowland penny via samba wrote: > On 08/06/2019 21:32, Rowland penny via samba wrote: >> On 08/06/2019 16:24, Uwe Laverenz via samba wrote: >>> Hi all, >>> >>> when you join a linux server to an active directory with "realm" it uses >>> "sssd" as default. This works well as long as you just want to be a >>> simple domain member. >>> >>&...

Hi, Before I file a bug report, I just wanted to check that samba is capable of serving files from a FAT32 partition. I have here an OpenBSD-4.2 i386 machine here with a second disk containting files that I will be sharing via both NFS and samba. The NFS share work great, but samba seg faults upon a windows client connecting. This occurs when using the OpenBSD package, and also when built from

Dear All, I am attempting to set up Samba 1.9.18p8 on a Sun E450 running Solaris 2.6. The Sun is configured as a NIS master serving a number of other Unix machines. It is our primary development platform acting as a NIS client and also has auto mounted home directories for users. Samba has been built using GCC 2.8.1 with the following options set: FLAGSM = -DSUNOS5 -DSHADOW_PWD -DAUTOMOUNT

Hi, I have just put Samba3alpha23 on my Suse 8.1 box and and implement the new goup structure in LDAP. All works fine expect when you log in a a user other than root on the windows box. The error is : [2003/04/08 13:30:19, 0] passdb/pdb_ldap.c:ldapsam_search_one_group(2198) ldapsam_search_one_group: Problem during the LDAP search: LDAP error: (Insufficient access)ldapsam_open: cannot access

Hi, I always prefer the Samba packages for Debian-Stable from the Samba-Team and I never had a problem so far (thank you, Simo!). Yesterday I updated from 3.0.22 to 3.0.23 in my LDAP-based network. I updated samba.schema, added "index sambaSID eq,sub" to my slapd.conf and ran slapindex. When I started slapd and samba afterwards, I saw error messages like these (from smbd.log):