similar to: enumerating group members with nss_winbind (4.0.9 as AD DC)

My samba thinks its own groups don't exist. Background: I had a samba3 server operating as a NAS with some desktops joined to the domain. I'm migrating it to samba 4.0.9 as an AD domain. Users can log in and browse their home share -- but the other shares aren't working. They're per-project shares set up to allow that project's group access, and to forcibly make all files

Using samba 4.0.9 as an AD DC (no other domain servers). Since my UIDs and GIDs have changed, I was doing cleanup: find /srv/svn/ -xdev '(' -nouser -o -nogroup ')' -ls I noticed this was very slow -- iostat reported only about 2tps and 50kB/s to my disks. So I timed it with nsswitch.conf users & groups set to "files" vs. "files winbind": # with

Dear R-devel: The following code seems to allow one function to permanently modify a calling function. I did not expect this would be allowed (short of more creative gymnastics) and wonder if it is really intended. (I can see other ways to accomplish the intended task of this code [e.g. via match.call instead of substitute below] that do not trigger the problem, but I don't think that is

Every 10 minutes, my samba 4.0.9 (active directory domain controller) is logging messages like these :- 2014-01-07T14:26:09.896260+11:00 gumbo samba[5198]: /usr/sbin/samba_dnsupdate: ; Communication with 127.0.1.1#53 failed: operation canceled 2014-01-07T14:26:09.896281+11:00 gumbo samba[5198]: /usr/sbin/samba_dnsupdate: could not talk to any default name server 2014-01-07T14:26:09.917096+11:00

Sunfreeware.com has compiled packages of Samba 3.4.2 with kerberos and ldap support included (if you also install the ldap and kerberos packages from sunfreeware.) However it does not include the nss_winbind.so.* or libnss_winbind.so.* files. Solaris does include nss_winbind.so already (since it is included with Samba 3.0.x) or I could compile it from the 3.4.x source code. But then I

Any hope getting an answer for this? If you do an ls -la in a directory that is part of a path of a share, you get the following error: ld.so.1: ls: fatal: relocation error: file /lib/nss_winbind.so.1: symbol socket: referenced symbol not found Killed So, for example, if you have a share: [monkey] comment = monkey path = /export/home/monkey #guest account =

hi all ! I have compiled Samba 2.2.2 for Solaris 7 ( Solaris 8 also ) but found out that the "nss_winbind" support is available in source-code, but not after compilation. The neccessary entries in the Makefile after "configre" are missing !! Why ? I have got it to run and it works fine with a small amout of groups. But deploying this samba/winbind version to a Windows

I've recompiled samba 2.2.3a and still any time I do a ls -l in a directory where there are files from a PC I get the error : ld.so.1: ls: fatal: relocation error: file /usr/lib/nss_winbind.so.1: symbol socket: referenced symbol not found If I shut off winbind or take winbind out for my /etc/nsswitch.conf file, I can get a directory listing and it lists the users ID that winbind assigned to

This patch attempts to address an issue some have reported where our nss_winbind is even slower than it's simple non-caching implementation needs to be. I think this comes from us not handling the BUILTIN domain properly, and so we constantly attempt to contact the DC, and then fail an internal validation step, throwing away that connection. I think this is also the cause of crashes folks

I ran some tests to see why getent passwd was not enumerating my domain users and discovered this: If I getent passwd <username> it returns the user information including the primary group defined in the Unix attributes. If I add a Unix GID in the idmap config range to the domain's Domain Users group and getent passwd, it returns all of my domain users with all of the Unix attributes as

Hi all, Is it a necessity to use the winbind nss module? I have run a few tests and having it enabled creates a massive bottleneck. It's not nss_winbind itself that is the bottleneck but something in the background (I'm guessing uid/rid->username code). If I disable winbind in nsswitch.conf what impact will it have? Will the system continue to work? eg: #nss_winbind enabled on

I had the same problem. You need to go into your Makefile and add the [LIBS] definition to the part where winbind.so is linked. Just take it on to the end of the line and run "make" and "make install" again. You might want to do a "make uninstall" and a "make clean" first. -Dan -----Original Message----- From: Jelmer Vernooij [mailto:jelmer@nl.linux.org]

OK, we're getting closer here I think. I repeated with -d 2 without much help. Here is -d 3, which may point us in the right direction. As I suspected, it seems to point to some corruption in the DNS still, perhaps? The key line seems to be here: Missing parent while attempting to apply records: No parent with GUID 60e25dda-6d35-4aab-bfa5-6137cb271e27 found for object remotely known as

You can test if winbind is able to resolve user IDs internally with "wbinfo -u". This uses the samba tool "wbinfo" to connect directly to the running winbind daemon and list all the Windows domain users. If that fails, then you have problems with the winbind daemon itself. The authentication between winbind and the PDC can be tested with "wbinfo -t", which is usually

I thought I had posted already, but my first message may have been confusing. Here is the output of the domain join: $ sudo samba-tool domain join redacted.domain.local DC -U"REDACTED\my.domain.admin" --dns-backend=SAMBA_INTERNAL Finding a writeable DC for domain 'redacted.domain.local' Found DC samba4dom.redacted.domain.local Password for [REDACTED\my.domain.admin]: NO DNS

Hi all, I'm seeing Dovecot include the string "MISSING_DOMAIN" in fetch envelope requests when an mailbox's `addr-spec` part does not have a `domain` part. For example: > C: a022 uid fetch 40 (envelope rfc822.header) > S: * 5 FETCH (UID 40 ENVELOPE ("Sat, 15 Aug 2020 12:53:05 +1000" > "test {{name}}" (("Michael Gratton" NIL

We have been experiencing a debilitating 'bug' in samba where something is causing a flood of the messages seen below in smbstatus and the network drives ( in our case N: ) on all clients become unresponsive. In fact, the entire client becomes unresponsive, essentially making them unusable until samba is restarted. We first saw this and connected it to the following open bug in samba

Hello, I have a quite unusual encoding problem (?). I call rsync with the following parameters: /usr/bin/rsync -a --delete --numeric-ids --delete-excluded \ --rsh="/usr/bin/ssh -o StrictHostKeyChecking=no -i \ /etc/rsnapshot_ssh_certs/mykey" \ --link-dest=/data/snapshots/hourly.1/folder/mail/ \ rsyncbackup at server:/var/backups/mail/. \

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, I think this is not the only time you guys ever seen that kind of mails. First of all, I did checked all that is to be checked before writing to list. wbinfo -u and wbinfo -g work flawless. Also wbinfo -a, so I can authenticate without problems. The setup is a normal trust setup where domain X (my domain) trusts domain Y (another company).

Hello, this is on Debian Jessie box, dovecot 2.2.27 from backports, imap-hibernate obviously enabled. I've been seeing a few of these since starting this cluster (see previous mail), they all follow the same pattern, a user who accesses their mailbox with both POP3 and IMAP deletes mails with POP3 and the IMAP (imap-hibernate really) is getting confused and upset about this: --- Apr 6