Displaying 20 results from an estimated 20000 matches similar to: "Samba-4.3 FreeBSD-10.3 Roaming Profiles and User Home Drive Shares"
2016 Jul 29
0
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.
>
2016 Aug 01
0
Samba-4.3.11 Roaming profiles on FreeBSD10.3
Hai James,
>I deliberately switched the PROFILES share with the USERS share in order to >test whether or not there was something obviously wrong with either the >share definition or the permissions. I understand that one must first >press on the ok button to trigger the event.
For a USER Home dir yes, but profiles no.
You can do that but that wont help much.
Pressing OK
2017 Apr 03
1
Unable to load roaming profiles samba-4.3 FreeBSD
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
2017 Mar 16
0
Permissions problem with 1 user
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
#
2020 Jul 09
1
sysvol permissions
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
2020 May 09
1
rsync replication acl error
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
2020 May 13
0
rsync replication acl error
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
2020 Jul 03
0
samab-4.10 nsupdate
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
2020 Jul 02
0
samab-4.10 nsupdate
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
2020 Jun 30
0
samab-4.10 nsupdate
> 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
2020 Jun 25
0
samba-4.10.15 - Unable to demote secodary DC
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
2020 Jul 02
1
samab-4.10 nsupdate
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
2020 Jul 07
0
How to delete an unwanted NS record
On 07/07/2020 20:00, James B. Byrne via samba wrote:
> I have this on the DC smb4-1.brockley.harte-lyne.ca:
>
> samba-tool dns query localhost brockley.harte-lyne.ca brockley.harte-lyne.ca
> ALL -U administrator
> Password for [BROCKLEY\administrator]:
> Name=, Records=6, Children=0
> SOA: serial=7, refresh=900, retry=600, expire=86400, minttl=3600,
>
2020 Jul 08
0
How to delete an unwanted NS record
On 07.07.2020 22:14, Mani Wieser via samba wrote:
>
> On 07.07.2020 21:14, Rowland penny via samba wrote:
>> On 07/07/2020 20:00, James B. Byrne via samba wrote:
>>> I have this on the DC smb4-1.brockley.harte-lyne.ca:
>>>
>>> samba-tool dns query localhost brockley.harte-lyne.ca
>>> brockley.harte-lyne.ca
>>> ALL -U administrator
2020 Jul 07
3
Can someone explain why host reports no SOA record for domain on DC?
[root at smb4-1 ~ (master)]# samba-tool dns query localhost brockley.harte-lyne.ca
brockley.harte-lyne.ca ALL -U administrator
Password for [BROCKLEY\administrator]:
Name=, Records=4, Children=0
SOA: serial=3, refresh=900, retry=600, expire=86400, minttl=3600,
ns=SMB4-1.brockley.harte-lyne.ca., email=hostmaster.brockley.harte-lyne.ca.
(flags=600000f0, serial=110, ttl=3600)
NS:
2020 Jun 30
3
samab-4.10 nsupdate
I have a dc configured to use the samba internal dns service. The version of
samba I am using is 4.10.15 packaged for FreeBSD. Its build options state
this:
BIND911 : off
BIND916 : off
, , ,
GSSAPI_BUILTIN : on
GSSAPI_MIT : off
LDAP : on
. . .
NSUPDATE : off
My smb4.conf file contains this:
[global]
bind interfaces only = Yes
dns forwarder =
2020 Jul 07
2
How to delete an unwanted NS record
I have this on the DC smb4-1.brockley.harte-lyne.ca:
samba-tool dns query localhost brockley.harte-lyne.ca brockley.harte-lyne.ca
ALL -U administrator
Password for [BROCKLEY\administrator]:
Name=, Records=6, Children=0
SOA: serial=7, refresh=900, retry=600, expire=86400, minttl=3600,
ns=SMB4-1.brockley.harte-lyne.ca., email=support.harte-lyne.ca.
(flags=600000f0, serial=110, ttl=3600)
2020 Jun 05
1
(no subject)
Previously, when I did this:
>> samba-tool dns query localhost brockley.harte-lyne.ca brockley.harte-lyne.ca
>> ALL -U administrator
Then I saw this:
>> Password for [BROCKLEY\administrator]:
Now I see this:
>> samba-tool dns query localhost brockley.harte-lyne.ca brockley.harte-lyne.ca
>> ALL -U administrator
>> Cannot do GSSAPI to an IP address
>>
2020 Jul 07
2
How to delete an unwanted NS record
On 07.07.2020 21:14, Rowland penny via samba wrote:
> On 07/07/2020 20:00, James B. Byrne via samba wrote:
>> I have this on the DC smb4-1.brockley.harte-lyne.ca:
>>
>> samba-tool dns query localhost brockley.harte-lyne.ca
>> brockley.harte-lyne.ca
>> ALL -U administrator
>> Password for [BROCKLEY\administrator]:
>> ?? Name=, Records=6, Children=0
2020 Jul 02
0
samab-4.10 nsupdate
On Thu, July 2, 2020 14:47:42 UTC, Rowland penny wrote:
> Looks like you need to recompile nsupdate, you need GSSAPI.
>
> Failing that, try adding:
>
> dns update command = /usr/sbin/samba_dnsupdate --use-samba-tool
>
> To your DC's smb.conf
Further investigation has uncovered (for me) the cause of this error:
/usr/local/bin/samba-nsupdate: cannot specify -g or -o,