similar to: ACLs and winbind

Hello, I have a Samba/OpenLDAP domain (PDB+BDC) and a member Samba server hosting homes and profiles which is identifying users with nss_ldap and is issuing some strange ldap searches. I have these messages in my slapd logs: conn=14143 op=2 SRCH base="ou=XXX" scope=1 deref=0 filter="(&(objectClass=posixAccount)(uid=domain\5Cuser))" conn=14143 op=2 SRCH attr=uid

Hello, I have a centOS 5.5 box acting as as a PDC with samba 3.4.9 and openldap 2.4.22. Then I joined the domain with a centOS box (samba 3.4.17) which hosts the homes and profiles. I have no problem with XP clients. I can join a windows 7 client to my domain but it is unable to load the profile when logging in. See below a level 2 log.smdb from the file server when I log in with a domain

Hi, i'm probably not the first but i have found no concrete information about my problem... lots of information, nothing helped.. :S so, here's the thing.. i'm running a samba-3.0.22-13.16 server on SLES 9 kernel 2.6.16.21-0.8-default as an nt domain controller, there was a migration to Linux for the workstations so i had to implement WINBIND + PAM_MOUNT. after searching for the

Hm, I thought this to be the very TLD that is specifically assigned for local networks with no plans to become Internet-wide. What is the recommended TLD for such networks then? Dňa 20. 2. 2019 o 11:33 Rowland Penny via samba napísal(a): > On Wed, 20 Feb 2019 11:17:05 +0100 > "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > >> Hai, >>

Harry, Thank you. Unfortunately we don't have the choice of upgrading LDAP due to distro not supporting the newer version. However we have managed to get it to work. A lot of fiddling around. I do have another question though ;). Now that we have LDAP replicating, how do I transfer the "samba classic " PDC role to our BDC. I have read that using the domain master=yes in smb.conf

Hello, I'm trying to run a program called "elektronisches gesangbuch" under wine. Nearly everything works fine, but i get the following error during application startup: fixme:font:WineEngRemoveFontResourceEx :stub fixme:font:CreateScalableFontResourceA (0,"y:\\.wine\\drive_c\\eg2\\fonts\\Capella.fot","y:\\.wine\\drive_c\\eg2\\fonts\\Capella.ttf",(null)): stub

Am 26.04.2018 um 20:07 schrieb Harry Jede via samba: > No, i have created 2 users with same sid. > > root at capella:~# pdbedit -Lv | grep "User SID" | sort|uniq -d > root at capella:~# > > root at capella:~# pdbedit -L|grep Failing > ldapsam_getsampwsid: More than one user with SID [S-1-5-21-3958726613-3318811842-4132420312-21010]. Failing. count=2 >

Am 10.04.2018 um 18:46 schrieb Rowland Penny via samba: > Thanks for the updates, I just wish more people would report errors & > typo's I can send some more, this time from classicupgrade. Again I do not want to do these changes myself, a samba expert should have a look. Feedback for wiki page Migrating_a_Samba_NT4_Domain_to_Samba_AD_(Classic_Upgrade) Tried on Devuan 1 with

Hello all, I have several Samba4 DCs that host various production shares. I need one share, however, available as a read-only guest share (anonymous) that will be used as a software distribution share point. I have been unable to make it work (the servers prompt me for a valid username and password on that share). I have done some googling and it seems that this functionality might be

Hi! I'm experiencing problems with access to one of shares on server with Samba working as PDC for windows clients, after I upgraded Samba from 3.0.22 to 3.0.23 (this problem also present in 3.0.23a). There are config section for this share: ---------------------------------------------------------------- [domain] comment = Domain users exchange share path =

The function 'pchisq' from the 'stats' library gives a wrong result if the argument equals exactly zero: # Upper tail of central 1-df chi^2 distribution > pchisq(1 , 1, ncp=0, lower.tail = F, log.p = FALSE) [1] 0.3173105 > pchisq(0.5 , 1, ncp=0, lower.tail = F, log.p = FALSE) [1] 0.4795001 > pchisq(0.01 , 1, ncp=0, lower.tail = F, log.p = FALSE) [1]

Dear All I'm about migrating Samba 2.2.8 to 3.0.13 on Sparc, Solaris 8. Compilation and Installation without any problem. Runs fine with exception of 2.2.8-user validation in the domain (no problems with validation of WXP- and W2K-Client Machines, newly set users (./smbpasswd -a username) works perfectly ). I simply have copied smbpasswd 2.2.8 to the diferent directory of Samba 3.0.13.

I forget the correct terminology, but anyway, sumthin struck me while getting help for sorting out my previous problem. Among other things (apart from doing the gigs with my computer) I use the G4s (and soon hopefully 1 of those nice dual G4s we just got) to record tracks of the different ppl & bands on our course (which is BTEC Popular music btw) using Pro Tools. Since Vorbis has the

Hello, I did the steps described below and I have a problem with machine RIDs. When I first join a machine, samba adds to my sambaDomainName ldap entry a sambaNextRid attribute with a value of 1000. Now samba uses this value (incremented each time) to give its RID to the machine. This is going to be a real problem as my current samba computes RDIs as 1000+2*UID. FWIW I'm using

Dear all, I'm rather new to glusterfs but have some experience running lager lustre and beegfs installations. These filesystems provide active/active failover. Now, I discovered that I can also do this in glusterfs, although I didn't find detailed documentation about it. (I'm using glusterfs 3.10.8) So my question is: can I really use glusterfs to do failover in the way described

Back again with another oops, which looks suspiciously similiar to the one i posted some days ago (https://listman.redhat.com/pipermail/ext3-users/2002-May/003587.html). Jun 11 12:11:30 castor kernel: Assertion failure in journal_write_metadata_buffer() at journal.c:406: "buffer_jdirty(jh2bh(jh_in))" ksymoops 0.7c on i686 2.4.18-4custom. Options used -V (default) -k

Hi Stefan, I think what you propose will work, though you should test it thoroughly. I think more generally, "the GlusterFS way" would be to use 2-way replication instead of a distributed volume; then you can lose one of your servers without outage. And re-synchronize when it comes back up. Chances are if you weren't using the SAN volumes; you could have purchased two servers

Am Dienstag, 13. März 2018, 11:21:17 CET schrieb Praveen Ghimire: > Harry, > > Thank you. > > Unfortunately we don't have the choice of upgrading LDAP due to distro > not supporting the newer version. However we have managed to get it > to work. A lot of fiddling around. > > I do have another question though ;). Now that we have LDAP > replicating, how do I

Hi Alex, Thank you for the quick reply! Yes, I'm aware that using ?plain? hardware with replication is more what GlusterFS is for. I cannot talk about prices where in detail, but for me, it evens more or less out. Moreover, I have more SAN that I'd rather re-use (because of Lustre) than buy new hardware. I'll test more to understand what precisely "replace-brick"

Hello, I plan to update my samba-3.0.22/openldap-2.3.24 to samba-3.0.34/openldap-2.4.15 and I'm currently testing it. This is on FreeBSD. My idea is : 1) slapcat the openldap server and save the various tdb files. 2) deinstall samba and openldap and wipe out the bdb files 3) install the newer versions 4) slapadd to the new openldap server This seems to work in my test lab. During my tests I