similar to: AD file server

I have an existing install of Samba4 ( I think beta6 vintage ), which uses ntvfs and bind9. It's only providing AD and Group Policy. I have a seperate file server running 3.6.x. I want to add a server to the domain running the most recent RC. I know they are using internal by default and s3fs for the file shares on sysvol. Can s3fs coexist with ntvfs? Can the internal DNS coexist with

Okay I didn't read that. surprised that it should work with the databases as is. The dbcheck function was quite involved when it was run on the 4.5.5. update. On Thursday, 23 March 2017, 20:21, Ray Klassen <julius_ahenobarbus at yahoo.co.uk> wrote: After upgrade massive slowdown network wide. Does not make sense that it's the samba, but I've nothing left. Question

We are proud to announce another beta release of Samba 4.0, beta8 Specifically, this release addresses the panic on startup all users upgrading to beta7 experienced. What's new in Samba 4.0 beta8 ============================= Samba 4.0 will be the next version of the Samba suite and incorporates all the technology found in both the Samba4 alpha series and the stable 3.x series. The primary

We are proud to a announce another alpha release of Samba 4.0, alpha 21 What's new in Samba 4 alpha21 ============================= Samba 4.0 will be the next version of the Samba suite and incorporates all the technology found in both the Samba4 alpha series and the stable 3.x series. The primary additional features over Samba 3.6 are support for the Active Directory logon protocols used by

We had used Samba 4 alpha 17 for a long time and want to update our server now to Samba 4.0.x. The old Samba versions was using NTVFS and Samba 4.0.x is now using S3FS by default. So, what is the best practice now? Should we stay on NTVFS or should we switch to S3FS? The global part of our smb.conf looks like this: --- [global] interfaces = eth0 netbios name = PDC

I've been trying to run samba4 alpha11 on a FreeBSD 8.1 system as a domain controller but I'm having trouble starting the cldapd server. For some reason it won't bind to the specified address or interface whatever I specify in smb.conf. I managed running the provision script without any trouble but I have no clue how to solve this problem in order to start the samba server. bitrot#

I had 444 errors I didn't want to put them all up here. Maybe I missed a step, maybe it's an easy "oops you forgot to do this" I'm on ubuntu 10.10 amd64 server completely uptodate today. I followed the http://wiki.samba.org/index.php/Samba4/HOWTO My git is also today. == samba4.rpc.echo on ncacn_ip_tcp with validate and --option=socket:testnonblock=True

Hello to the Samba Mailing List, This is my first post, so please, should I commit any faux pas, nudge me in the right direction and I will adjust accordingly. I'm experiencing a complete failure of the PDC in a Samba 4 AD Domain I've deployed for a client. Samba failed a few days ago and I've been unable to resolve the issue on my own. Google searches are leading me in circles,

./configure --bundled-libraries && make ............ [3638/3880] Linking default/source4/lib/policy/py-policy.so [3639/3880] Linking default/source4/auth/ntlm/libauth4.so [3640/3880] Linking default/source4/ntvfs/libntvfs.so default/source4/ntvfs/sysdep/inotify_1.o: In function `inotify_setup': inotify.c:(.text+0x503): undefined reference to `inotify_init'

Okay, so I've just put the sernet repo file in my yum.repos.d directory and a yum update will elevate my samba server to the latest version. Is there any pitfall that is out there that I can avoid before yum updating. Centos 5.3 samba3-3.0.34-37 & related packages openldap-2.3.43-3.el5 & related packages I still have my samba3-3.0.34 packages squirreled away so I can force downgrade

Hi everyone After almost 2 days up-time with Samba 4, it failed again. This time it simply will not restart. The krb5.conf had got corrupted. I replaced it with this one from /usr/local/samba/private /etc/krb5.conf [libdefaults] default_realm = HH3.SITE dns_lookup_realm = false dns_lookup_kdc = true It starts up OK: samba -i -d 3 lpcfg_load: refreshing parameters from

On Mon, 05 Dec 2016 21:30:20 +1300 Andrew Bartlett <abartlet at samba.org> wrote: > On Mon, 2016-12-05 at 08:12 +0000, Rowland Penny via samba wrote: > > On Mon, 05 Dec 2016 21:07:48 +1300 > > Andrew Bartlett <abartlet at samba.org> wrote: > > > > > > > > > > > > > It is a lot of work to change the situation, even more so

Thanks a lot for the reference how to make the regtest. One last question please, if understand this correctly, the --use-ntvfs isnot available by default when installing the Debian package, so I need to compile samba with --with-ntvfs-fileserver to make the option available? On 11/14/19 8:52 AM, Andrew Bartlett wrote: > On Thu, 2019-11-14 at 07:30 +0000, Ghassan Elrayah wrote: >> Hi,

On Fri, 2 Sep 2016 13:03:05 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Fri, 2 Sep 2016 12:41:47 +0100 > Cameron Murdoch via samba <samba at lists.samba.org> wrote: > > > On 2 September 2016 at 12:21, Rowland Penny via samba > > <samba at lists.samba.org > > > wrote: > > > > > On Fri, 2 Sep 2016 11:51:02 +0100

Apologies if this post is inappropriate to this list; please redirect me if so. Our team uses ssh extensively for server access and maintenance (Debian). An issue is acting as root when operating, for example, over ansible and keeping a record of who performed the actions, something ssh certificates solves well. The problem is then to automate certificate issuance since it would be pretty

On Mon, 05 Dec 2016 07:50:23 +1300 Andrew Bartlett <abartlet at samba.org> wrote: > On Sun, 2016-12-04 at 11:43 +0000, Rowland Penny via samba wrote: > > On Sun, 4 Dec 2016 12:11:17 +0100 > > Marc Muehlfeld via samba <samba at lists.samba.org> wrote: > > > > > > > > Hi Scott, > > > > > > Am 02.12.2016 um 06:55 schrieb Scott

Hi all, I am in the process of finding the best way to use Samba4 as an AD under FreeBSD and ZFS. The following is based on own research, google, mail archives, a bit of source code etc. So please correct me if I am wrong. 1. ZFS is using NFSv4 ACLs. 2. NFSv4 ACLs are modelled with NTFS (Windows) ACLs in mind. 3. Samba4 started with a new ntvfs file server but that was abandoned (or

On Mon, 2017-01-30 at 08:42 +0000, Rowland Penny wrote: > On Mon, 30 Jan 2017 15:44:15 +1300 > Andrew Bartlett <abartlet at samba.org> wrote: > > > On Sun, 2017-01-29 at 22:43 +0000, Rowland Penny via samba wrote: > > > On Sun, 29 Jan 2017 17:07:39 -0500 > > > Sonic <sonicsmith at gmail.com> wrote: > > > > > > > On Sun, Jan 29,

Hi again, it seems that the configure option (--with-ntvfs-fileserer, --enable-developer) are not available on samba-4.11.2. I get the following error: + --enable-developer --with-ntvfs-fileserver --sysconfdir=/etc/samba/ --mandir=/usr/share/man/ --sbindir=/usr/sbin/ --bindir=/usr/bin/ --without-systemd --with-statedir=/var/lib/samba --with-cachedir=/var/cache/samba

Hi, I am trying to get some integration tests running in CI with a software uses samba4 AD for authentication. So basically I would like spin up a build and provision a samba4 AD with some test users and groups non-interactively and test commits and pull requests against the AD. On 11/14/19 8:16 AM, Andrew Bartlett wrote: > On Thu, 2019-11-14 at 06:19 +0000, Ghassan Elrayah via samba wrote: