similar to: Samba-4.3.11 Roaming profiles on FreeBSD10.3

On Fri, July 29, 2016 02:58, L.P.H. van Belle wrote: > I sniped the best parts, and added comment. > >   > >> > >> The situation is that assigning a new user the profile: > >> //DC/PROFILES/%USERNAME%  does not produce anything on the DC's > >> filesystem.  > > Correct that only dan when you first login with the user and then > logoff. >

I am unable to get roaming profiles to work. I have turned on debugging and I believe that I have narrowed down where in the log file the problem is reported. However, I do not possess the knowledge necessary to understand what is going on. The situation is that assigning a new user the profile: //DC/PROFILES/%USERNAME% does not produce anything on the DC's filesystem. However, using the

I am familiar with the contents of https://wiki.samba.org/index.php/Samba_%26_Windows_Profiles#Profile_share_using_POSIX_ACLs. Reading that given my set up (Samba-4.4.3_1 on FreeBSD10.3 and ZFS); and given that smbd -b | grep HAVE_LIBACL produces nothing; I infer that setting up roaming profiles using Windows ACLs are not going to work. I am correct? Which implies that I will have to use the

We have set up a Samba-4.3 AD-DC on a FreeBSD-10.3 BHyve guest configured with UFS stoarge. The samba_server is provisioned and we can join the Domain and configure the server remotely using MMC snap-ins running on a MS Win-v7Pro workstation. We are at the point where we are implementing roaming profiles. We have followed the instructions found at:

I am seeing these in smb.log and each time I do it appears that the user in question is unable to retrieve their roaming profile. Does anyone know what is going on and more importantly, how to cure it? . . . [2017/03/28 16:24:37.426162, 0] ../source3/smbd/oplock.c:713(oplock_timeout_handler) Oplock break failed for file Administrator/AppData/Roaming/Microsoft/Internet Explorer/Quick

This problem has several elements but it did not evidence itself until we moved from a MicroSoft AD-DC to a Samba AD-DC. The environment is is a FreeBSD-10.3 Bhyve VM hosted on a 16 core host also running FreeBSD-10.3. The version of Samba is 4.3.11 obtained through FreeBSD ports. The AD clients are all running MSWin7pro patched up-to-date. Roaming profiles are in use. We have an intermittent

On Wed, March 15, 2017 22:31, Andrew Walker wrote: > What does your smb.conf look like? Are you using ACLs? If so, post > 'getfacl' output for the problem directory (ie 'getfacl > /mnt/tank/foo'). > Thank you for your reply. Here is the requested information. getfacl /var/samba4/BROCKLEY-2016/PROFILES/byrnej.V2 # file: /var/samba4/BROCKLEY-2016/PROFILES/byrnej.V2 #

We have recently converted our users from a Windows2000Advanced Server AD-DC to a Samba-4.3.11. AD-DC. For the most part this went very well, saving only for the degree of ignorance respecting things MicroSoft evidenced by myself. However, one of our users persistently reports difficulties with their roaming profile. Specifically, their Firefox profile. This did not occur before the change-over

On Mon, April 3, 2017 14:13, Rowland Penny wrote: > > Try following this wiki page: > > https://wiki.samba.org/index.php/Roaming_Windows_User_Profiles > > Rowland > I have, several times, read the aforementioned reference. I followed it, as it existed at the time, to the best of my understanding when I set up the domain in October 2016. Roaming profiles have been working

On Tue, October 11, 2016 19:06, Jeremy Allison wrote: > > > This doesn't sound like a Samba problem. If access for that user > was completely cut off, or got authentication errors, that sounds > like us. But > > "FF stops responding to javascript > calls and generally slows down to an unacceptable degree." > > doesn't sound like something a remote

I am trying to replicate a samba-4.3 DC [192.168.8.65] to a newly joined samba-4.10 DC. I am using rsync as described in the samba wiki, excepting that I am using a remote shell (ssh) with the root user and password-less logins. When I run the command below from the 4.10 DC I get acl errors as shown below. rsync -XAavz --delete-after --rsh='ssh' [192.168.8.65]:/var/db/samba4/sysvol

FreeBSD-12.1p7 Samba-4.10.15 The user profiles were transferred from the existing Samba AD-DC to a new domain running on Samba-4.10. An ls on the original Samba (4.3.13) domain DC shows this: [root at SAMBA-01 ~]# ls -ld /var/samba4/BROCKLEY-2016/PROFILES/lyneak_hll.V2 drwxrwx---+ 16 BROCKLEY-2016\lyneak_hll BROCKLEY-2016\domain admins 512 Aug 12 17:07

On Tue, May 12, 2020 09:46, Rowland penny wrote: > One problem is that ZFS uses NFSv4ACLS and a Samba AD doesn't, it > expects POSIX ACLS, there also is a possibility that xattr may be > another problem. > > Try reading this: > > https://bugzilla.samba.org/show_bug.cgi?id=12912 > I have worked with Timur on this very problem in the past. And he has produced in

FreeBSD-11 Samba-4.3.5 I am having a problem with my roaming profile. Other users are not experiencing this, only my personal account is affected. The error is being reported in the event log as a 1521 permissions error. However, I cannot see how the permissions on the server could possibly been changed as I am the only one with access to that device. My roaming profile was working fine up to

At this point I have a DC2 joined to a DC1 that has all the FMSO roles. I have confirmed that 'samba-tool drs showrepl' on both DCs produces the expected results without error. I am now looking at sysvol replication. On FreeBSD the sysvol is located at /var/db/samba4/sysvol. Here is the problem. On DC1 I see this: [root at smb4-1 ~ (master)]# ll /var/db/samba4/sysvol total 1

I changed the entries in smb4.conf (smb.conf) to this: [global] . . . dns update command = /usr/local/sbin/samba_dnsupdate nsupdate command = /usr/local/bin/samba-nsupdate -d -g And this is what results when I run: samba_dnsupdate --verbose -d8 --all-names . . . update(nsupdate): SRV _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.brockley.harte-lyne.ca

I am testing DC administration using samba-4.10.15 on FreeBSD-12.1p6 and have run across this: [root at smb4-2 ~ (master)]# samba-tool domain join BROCKLEY.HARTE-LYNE.CA DC -U"BROCKLEY\administrator" INFO 2020-06-25 14:26:10,692 pid:47306 /usr/local/lib/python3.7/site-packages/samba/join.py #104: Finding a writeable DC for domain 'BROCKLEY.HARTE-LYNE.CA' INFO 2020-06-25

This is all the diagnostic information I can think of at the moment: [root at smb4-1 ~ (master)]# klist Credentials cache: FILE:/tmp/krb5cc_0 Principal: administrator at BROCKLEY.HARTE-LYNE.CA Issued Expires Principal Jul 2 10:35:11 2020 Jul 2 20:35:11 2020 krbtgt/BROCKLEY.HARTE-LYNE.CA at BROCKLEY.HARTE-LYNE.CA [root at smb4-1 ~ (master)]# grep nsup

> Could be because you added the wrong line to your smb4.conf (why does > freebsd call it smb4.conf ?), Why does freebsd put these things in /usr/local/etc/? Some questions have answers that are not worth the effort to know. > try: > nsupdate command = /usr/local/sbin/nsupdate -g I did catch that error earlier. But it makes no difference. samba_dnsupdate does not give any

Thank you for your patience. On Tue, June 30, 2020 16:48, Rowland penny wrote: > > From 'man smb.conf': > > nsupdate command (G) > > This option sets the path to the nsupdate command which is used for > GSS-TSIG dynamic DNS updates. > > Default: nsupdate command = /usr/bin/nsupdate -g > > dns update command (G) > > This