search for: samba42

...= cluster-42 glusterfs:volume = gv0 glusterfs:logfile = /var/log/samba/gluster-gv0.log glusterfs:loglevel = 7 - ----------------- The share [daten] is pointing to the mountet glusterfs. Here is the part from /etc/fstab - ----------------- /dev/sda1 /gluster xfs defaults 0 0 samba42-1:/gv0 /glusterfs glusterfs defaults,_netdev,acl 0 0 - ----------------- The share [daten2] is using the vfs object glusterfs. If I try to connect to [daten] everything ist ok: - ----------------- root at samba42-fs2:/glusterfs# smbclient -U administrator //cluster-42/daten Enter administrator'...

...kernel share modes = No vfs objects = glusterfs glusterfs:volfile_server = cluster-42 glusterfs:volume = gv0 glusterfs:logfile = /var/log/samba/gluster-gv0.log glusterfs:loglevel = 7 - -------------------- And the connect: - -------------------- root at samba42-fs2:/glusterfs# smbclient -U administrator //cluster-42/daten2 Enter administrator's password: Domain=[EXAMPLE] OS=[Windows 6.1] Server=[Samba 4.2.0rc4-SerNet-Debian-6.wheezy] tree connect failed: NT_STATUS_BAD_NETWORK_NAME - -------------------- As I understoud, if you use vfs object glusterfs...

On 11/07/15 10:16, Rowland Penny wrote: > On 11/07/15 04:06, Lee Brown wrote: >> Hi Everyone, my first foray into Samba and AD both. >> >> Not sure if this is an OS or configuration problem. I've found similar >> issues, but nothing either recent enough (is related to samba 3) or >> close >> enough. >> >> FreeBSD-10.1-RELENG, Samba 4.2.2.

...ions of all files. We checked the bind9 config for the TKEY line. Everything is ok. The update works on the second DC without any error about the key. It's only one ADDC that makes the problem. The only differences we found was that the username on the working ADDC is in capital letters (CN=dns-SAMBA42) and on the non working ADDC in small letter (CN=dns-samba41). But on both systems it's the same inside the dns.keytab. (small =non working | capital = working). Any help? Stefan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: applicati...

....2. Right now I don't want to switch any of them to AD; I just want to keep running as I do now, but with a supported version. I've started from the simplest cases and so far I've been able to upgrade some servers with the following steps: _ stop Samba; _ uninstall samba36; _ install samba42; _ replace "samba_enable" with "samba_server_enable" in /etc/rc.conf; _ rename /usr/local/etc/smb.conf to /usr/local/etc/smb4.conf; _ move /usr/local/etc/samba/smbpasswd to /var/db/samba4/private; _ restart Samba. This worked on servers running on smbpasswd backend; however I...

...gt; config for the TKEY line. Everything is ok. The update works on >> the second DC without any error about the key. It's only one ADDC >> that makes the problem. The only differences we found was that >> the username on the working ADDC is in capital letters >> (CN=dns-SAMBA42) and on the non working ADDC in small letter >> (CN=dns-samba41). But on both systems it's the same inside the >> dns.keytab. (small =non working | capital = working). >> >> Any help? >> >> Stefan >> > > Have you set up 'failover' ? Th...

...cts = glusterfs > glusterfs:volfile_server = cluster-42 > glusterfs:volume = gv0 > glusterfs:logfile = /var/log/samba/gluster-gv0.log > glusterfs:loglevel = 7 > - -------------------- > > And the connect: > - -------------------- > root at samba42-fs2:/glusterfs# smbclient -U administrator > //cluster-42/daten2 > Enter administrator's password: > Domain=[EXAMPLE] OS=[Windows 6.1] Server=[Samba > 4.2.0rc4-SerNet-Debian-6.wheezy] > tree connect failed: NT_STATUS_BAD_NETWORK_NAME > - -------------------- > As I understo...

...switch any of them to AD; I just want to > keep running as I do now, but with a supported version. > > I've started from the simplest cases and so far I've been able to > upgrade some servers with the following steps: > _ stop Samba; > _ uninstall samba36; > _ install samba42; > _ replace "samba_enable" with "samba_server_enable" in /etc/rc.conf; > _ rename /usr/local/etc/smb.conf to /usr/local/etc/smb4.conf; > _ move /usr/local/etc/samba/smbpasswd to /var/db/samba4/private; > _ restart Samba. > > This worked on servers running on s...

...cked the bind9 config > for the TKEY line. Everything is ok. > The update works on the second DC without any error about the key. > It's only one ADDC that makes the problem. > The only differences we found was that the username on the working > ADDC is in capital letters (CN=dns-SAMBA42) and on the non working > ADDC in small letter (CN=dns-samba41). But on both systems it's the > same inside the dns.keytab. (small =non working | capital = working). > > Any help? > > Stefan > Have you set up 'failover' ? The records belong to whoever creates th...

...he TKEY line. Everything is ok. The update works on >>> the second DC without any error about the key. It's only one ADDC >>> that makes the problem. The only differences we found was that >>> the username on the working ADDC is in capital letters >>> (CN=dns-SAMBA42) and on the non working ADDC in small letter >>> (CN=dns-samba41). But on both systems it's the same inside the >>> dns.keytab. (small =non working | capital = working). >>> >>> Any help? >>> >>> Stefan >>> >> >> Have yo...

Hi, I have an issues that involves KDC, it is quite complex so I'll try to be really specific. I was running Samba42 with a secondary server replicating all was working fine. After we upgrade to Samba43 we start with the issues: 1. Replication wasn't working anymore error (WERR_LOGON_FAILURE) 2. Kerberos is also broken. On the Primary DC wouldn't allow me to to a kinit administrator error: krb5_get_ini...

On Tue, Jan 31, 2017 at 2:45 PM, Rowland Penny via samba <samba at lists.samba.org> wrote: >> /etc/resolv.conf: >> root at nickel:~ # cat /etc/resolv.conf >> nameserver 192.168.11.5 >> nameserver 192.168.1.4 >> domain mydomain.local >> > > I take it at least one of the above nameservers is the AD DC, is the > other another AD DC ? If it isn't,

Hi! the previous problems were solved (thank you, Rowland!), but few issues remains: I get such msg in log: 0. Is it possible to tell samba to output messages in logs as one line per message (even if it is long one?) 1. 2015/04/12 11:32:39.293583, 3] ../source3/smbd/msdfs.c:971(get_referred_path) get_referred_path: |shareX| in dfs path \FS\shareX is not a dfs root. (seems it is not