similar to: Sysvol replication problem

Hello I am experiencing an strange issue when listing printers in the domain. It seems that the printer installed on workstation is registered on every restart without removing the old data . The outcome of this registration is that after few days I have "Printer" record along with few "Printer000xxx" records, and then I have to manually remove all these "new"

I'm testing a samba4 server join AD (had 1 win2003 dc) as dc. Version: Samba4 DC: samba 4.1.1 with ubuntu (172.16.3.8) Win2003 DC: Win2003 SP2 (172.16.3.3) AD domain name: dotest.com The samba server had joined to AD as DC. When win2003 dc online, it seems works fine. When I test win2003 dc online, simulate the win2003 DC was failue, found the samba4 DC can't work fine along. The AD

Hi everybody, I have yet another issue that I can't solve in my Samba4.0.10 AD DC. For some reason when I access sysvol share via domain name \\domain.local, every directory open waits for about 60 seconds. But when I open it directly on DC \\dc1.domainname.local, it works fine. Is anybody familiar with such issue, (domain was replicated from w2k3) and everything except this is working as

Hi I've just recreated whole environment and after DC provision ?group "domain users" has gid 100 getent passwd OFFICE\administrator:*:0:100::/home/OFFICE/administrator:/bin/bash OFFICE\guest:*:3000011:3000012::/home/OFFICE/guest:/bin/bash OFFICE\krbtgt:*:3000015:100::/home/OFFICE/krbtgt:/bin/bash OFFICE\dhcpduser:*:3000016:100::/home/OFFICE/dhcpduser:/bin/bash getent group ...

I forgot about ldbsearch. Here is a dump of xid numbers. root at dc01:~# ldbsearch -H /var/lib/samba/private/idmap.ldb | grep xidNumber xidNumber: 3000028 xidNumber: 3000013 xidNumber: 3000033 xidNumber: 3000003 xidNumber: 3000032 xidNumber: 3000023 xidNumber: 3000019 xidNumber: 3000010 xidNumber: 65534 xidNumber: 3000031 xidNumber: 3000022 xidNumber: 3000026 xidNumber: 3000017 xidNumber: 3000027

pam doesn't work. Samba Version 4.12.0rc4 openSUSE Leap 15.2 ./configure --with-ads --systemd-install-services --with-shared-modules=idmap_ad --enable-debug --enable-selftest --with-systemd # Global parameters [global] dns forwarder = 172.16.0.1 netbios name = WNETIN realm = WNETINFO.LAN server role = active directory domain controller workgroup =

Hello,     Looking up a users group membership I'm showing different results on each DC. UID and GID mapping appears consistent but not all group membership is displayed. I've verified idmap.ldb is backup up and copied over to the other DC's. I do notice when taking a hot backup of idmap.ldb, the file size is dramatically smaller than the original. Using Microsoft RSAT to view

Hi, I configured a share for home-directories on my Debian Samba PDC (4.1.9) and connected the share on another linux machine (terminal server) via /etc/fstab: //192.168.10.51/home /home/DOMAIN/ cifs credentials=/root/.smbcredentials,iocharset=utf8 0 0 The .smbcredentials file contains the Domain Administrators username/password. The share is mounted successfully,

Hello Pros and users of Puppet. I have two problems with the following modul setup: My first problem that i tried every combination of require,notify,subscribe for the mail sending exec but it runs every single time when i run the module no matter if the files changed or not. Second problem that puppet reports that snmpd was refreshed by two resource and restarted but actually it doesnt happen.

OK, I noticed that also, but why does everything return NT_STATUS_INVALID_SID? Even if I run "smbclient -L \\localhost -U adminnamehere" on the DC itself, I get the error. At this point we are looking at erasing every workstation, wiping the DC, and starting from scratch. It has been a week and not even rolling back to 4.4 fixed it. What should my next steps be? I attached the server

On Tue, 18 Jun 2024 15:25:03 +0200 PaLi via samba <samba at lists.samba.org> wrote: > > on DC - dc31: > ------------- > $ sudo samba-tool testparm > > INFO 2024-06-18 13:09:06,760 pid:31797 /usr/lib/python3/dist- > packages/samba/netcmd/testparm.py #96: Loaded smb config files from > /etc/samba/smb.conf > INFO 2024-06-18 13:09:06,760 pid:31797

Hello, I recently set up a new software to backup samba share. This software ( https://github.com/borgbackup/borg ) run on file server as root cron script during the night and save file on external NAS. The problem I have is that for each file copied from samba share to external NAS, winbindd log an error such this to samba.log.winbindd and /var/log/messages [2017/11/06 11:05:16.747449, 0]

Hi I use /usr/bin/rsync -XAavz --log-file /var/log/sysvol-sync.log --delete-after -f"+ */" -f"- *" /var/lib/samba/sysvol root at DC2:/var/lib/samba && /usr/bin/unison &> /dev/null and works ok but not working with crontab */5 * * * * root /usr/bin/rsync -XAavz --log-file /var/log/sysvol-sync.log --delete-after -f"+ */" -f"- *"

Hello, 1) fs acl support I use XFS I did the tests ( https://wiki.samba.org/index.php/File_System_Support ) and no errors [root at dc1ucp ~]# setfattr -n user.test -v test test.txt [root at dc1ucp ~]# setfattr -n security.test -v test2 test.txt [root at dc1ucp ~]# getfattr -d test.txt # file: test.txt user.test="test" [root at dc1ucp ~]# getfattr -n security.test -d test.txt # file:

Hello, I have this defined resource type which is working perfectly until I want an ssl an http vhost pointing to the same directory in which case the unique $servername variable became a singleton Do you have any idea how to get around this? I am pretty tired at the moment and cant think of any good solution. define vhost ($servername = "${hostname}.${domain}", $serveralias = [

Hello , ( samba 4.6.9 - centos 6 DC1 centos DC2 ) I tried to sync sysvol as described in https://wiki.samba.org/index.php/Rsync_based_SysVol_replication_workaround between two DC but rsync shows some errors like this rsync: set_acl: sys_acl_set_file(apam-ad.apam.it/Policies/{D725AAC4-27E8-46AC-918D-55B560988386}/Machine/Applications/{031B2C75-D832-429B-B4C4-226BAA665E3A}.aas,

Dear, I'm having trouble handling GPO's my DC. Environment: Samba 4.4.5, primary and secondary DC. I am not allowed to edit the GPO's. The problem occurred after I edit the Default GPO in the primary DC, and then run the rsync to synchronize between the DC's. The following errors arise when squeegee commands: Note: I hid the actual domain name. # samba-tool gpo aclcheck

Best guess.. Can you check this : ( from the wiki ) Good: rsync --dry-run -XAavz --delete-after --password-file=/usr/local/samba/etc/rsync-sysvol.secret rsync://sysvol-replication@{IP-of-you-PDC}/SysVol/ /path/to/your/sysvol/folder/ Wrong. rsync --dry-run -XAavz --delete-after --password-file=/usr/local/samba/etc/rsync-sysvol.secret rsync://sysvol-replication@{IP-of-you-PDC}/SysVol/*

On Fri, 3 Nov 2017 10:18:14 +0100 "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > Best guess.. > > Can you check this : > > ( from the wiki ) > Good: > rsync --dry-run -XAavz --delete-after > --password-file=/usr/local/samba/etc/rsync-sysvol.secret > rsync://sysvol-replication@{IP-of-you-PDC}/SysVol/ /path/to/your/sysvol/folder/

Hi, I would like to know which the best way to replicate Sysvol between my DC Samba 4 is with Rsync/Osync, as per the article below? https://wiki.samba.org/index.php/Bidirectional_Rsync/osync_based_SysVol_replication_workaround I have 3 Samba 4 DC. Regards, M?rcio Bacci