similar to: Samba4 DNS errors from latest git

Hi, I upgraded my Samba 4.5.16 installed (by apt-get) on Debian 9.9 to Samba 4.10 through the Van Belle repository (apt.van-belle.nl). apt-get install -t stretch-samba410 samba attr winbind libpam-winbind libnss-winbind libpam-krb5 krb5-config krb5-user bind9 ctdb ldb-tools smbldap-tools ufw glusterfs-common libcephfs1 The packages "bind9 ctdb ldb-tools smbldap-tools ufw glusterfs-common

Hi, I have a problem. After several tests with Samba4, put into production. With one week working began to fill the files with HD / usr/local/samba4/var/cores/smb. I went into that directory and deleted some files to free up space. More Samba4 now no longer starts the ldap. When I start giving the error: [root @ new-lost sbin] #. / samba-i-M single-d 1 Samba version 4.1.0pre1-GIT-05a5974

Hello. I'm trying to perform a classic upgrade from Samba 3.6.6 with LDAP backend on Debian to 4.1.6 on Ubuntu on a new machine. The samba-tools creates the following *smb.con*f: *# cat /etc/samba/smb.conf** *[global] workgroup = SOMEDOM realm = somedom.local netbios name = SOMEDOM server role = member server passdb backend = samba_dsdb server

I am working on a FreeBSD jail (12.1p4) using samba410. I have joined this service to our existing Samab DC DOMAIN using samba-tool domain join. This worked as far as I can tell. I have these entries in smb4.conf # BOF # Global parameters [global] netbios name = SAMBA-02 realm = BROCKLEY-2016.HARTE-LYNE.CA server role = active directory domain controller workgroup = BROCKLEY-2016

Hello. On several FreeBSD 11.2/amd64 servers, I've got a jail dedicated to running Samba as an AD DC. Some days ago I upgraded one of them from 4.8.7 to 4.8.9 and suddenly everything stopped working. Since it was a production box, I immediately restored the whole jail from a backup, with no chance to better investigate. Today, with more time, I tried on another server and again I run

Hey All, I don't know what's wrong, or what I may have done wrong, but I THOUGHT I followed all the correct steps to setup samba, and it's not working. Here's what I did: D/L latest samba code (4.13.1) & extract install dependencies ./configure --prefix=/usr/local --enable-fhs (enable-fhs was required to get configure to run through completely) make make install cp

See Inline LPHvBvs> Hi Gregory, LPHvBvs> On the questions. >> Is there a good reason to avoid Samba internal DNS? LPHvBvs> No, imo not, but i only use bind9_dlz because i need bind in my lan for other setups also. LPHvBvs> I just used my RSAT on my win7 64b, but at my point it works fine. LPHvBvs> I do have questions to get a better impression of the setup. LPHvBvs>

Dear samba-mailinglist, We're using samba 4.0.5 as an active directory domain controller. We used to set up some file shares on basis security=user in the old samba version. I was able to set up the shares as they used to be . My Question: How can I set up "wich user kan read/write which share?" Do I have to do this in den Active Directory or in smb.conf? This maybe a trivial

On Wed, July 22, 2020 14:48, Rowland penny wrote: > On 22/07/2020 19:40, James B. Byrne via samba wrote: >> >> On Wed, July 22, 2020 12:35, James B. Byrne wrote: >>> FreeBSD-12.1p7 jail running Samba-4.10.15 on ZFS. >>> >>> When I run 'samba-tool domain backup offline targetdir=/tmp' I see this: >>> >>> running backup on dirs:

FreeBSD-12.1p7 jail running Samba-4.10.15 on ZFS. When I run 'samba-tool domain backup offline targetdir=/tmp' I see this: running backup on dirs: /var/db/samba4/private /var/db/samba4 /usr/local/etc Starting transaction on /var/db/samba4/private/secrets At which point samba-tool enters a permanent wait state. 86064 root 1 52 0 131M 78M wait 3 0:01 0.00%

I keep getting errors in my logs about can not bind to address *.*.*.*:53 address in use.. what did i do wrong in the setup of my server or domain? attached logs and smb.conf along with the output from my provision command. Jeffrey D. Means meaje at meanspc.com Owner / CIO for MeansPC http://www.meanspc.com/ Custom Web Development For Your Needs. (970)308-1298 - The

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

Release Announcements --------------------- This is the first release candidate of Samba 4.0.0! This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. What's new in Samba 4.0.0rc1 ============================= Samba 4.0 will be the next version of the Samba

Release Announcements --------------------- This is the first release candidate of Samba 4.0.0! This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. What's new in Samba 4.0.0rc1 ============================= Samba 4.0 will be the next version of the Samba

On 23/07/2020 18:12, James B. Byrne via samba wrote: > > On Thu, July 23, 2020 16:16:30, Mani Wieser wrote: > >>>> ../../source4/nbt_server/interfaces.c:228(nbtd_add_socket) >>>> Failed to bind to 127.0.162.1:137 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED >> check where has port 137 occupied > There is nothing listening on 137 > > [root at smb4-2 ~

Hello everyone ! Well, I'm setting up a 'new' box with samba 4.9.3 on Ubuntu 18.04 Idea is to use Host OS for Domain Controler (dc1.smb.domain.tld) and a LXC container (ubuntu 18.04 too) as Domain Member with File Server (fs.smb.domain.tld). Administration through Windows OS will be done with a Qemu KVM. Bad thing is that I get : > Failed to bind to 0.0.0.0:53 TCP -

?Ok, so now : Content of /etc/hosts 127.0.0.1 localhost 172.31.6.15 adc1.transmitcorp.com adc1 Now, stop samba. Cleanup current data and now setup samba and provision again. cleanup /var/lib/samba /var/cache/samba Rename smb.conf Then provision again, the base is wrong so the AD-DB has wrong data. > > I removed smb.conf from /etc/samba > un the interactive

Try this. systemctl stop smbd nmbd winbind systemctl disable smbd nmbd winbind systemctl mask smbd nmbd winbind systemctl unmask samba-ad-dc systemctl enable samba-ad-dc systemctl start samba-ad-dc Reboot server. Check again. > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Lionel Monchecourt via samba

On 23/07/2020 18:36, Jeremy Allison wrote: > On Thu, Jul 23, 2020 at 06:31:09PM +0100, Rowland penny via samba wrote: >> On 23/07/2020 18:12, James B. Byrne via samba wrote: >>> On Thu, July 23, 2020 16:16:30, Mani Wieser wrote: >>> >>>>>> ../../source4/nbt_server/interfaces.c:228(nbtd_add_socket) >>>>>> Failed to bind to

So, I setup Samba on Ubuntu 18.04, using the packaged Samba version. [Thanks Rowland/Louis et al.] I'm doing some testing/tinkering using FreeNAS as a share, using the AD as the authentication back-end. As part of that process, you need to add a computer account and change some security settings. I setup RSAT and can see the AD tree, and add users etc. When I try to switch to advanced view