similar to: Cloning from a backup: unable to reach any KDC in realm

On Fri, 2019-11-15 at 20:16 +0000, Don Kuenz via samba wrote: > > Greetings, > > This post pertains to a Disaster Recovery (DR) scenario on a Samba > 4.8 > server. The DR server was provisioned as a standalone host, on a > network isolated from the Production Server (PS). > The DR's /var/db/samba4 directory, which contains the private > directory, was then

On 15/11/2019 20:16, Don Kuenz via samba wrote: > > Greetings, > > This post pertains to a Disaster Recovery (DR) scenario on a Samba 4.8 > server. The DR server was provisioned as a standalone host, on a Just what do you mean by 'provisioned as a standalone host' ? Do you mean 'samba-tool domain provision --server-role=standalone' ? Rowland

Greetings, The process to join a new samba 4.6 DC to an existing samba 4.1 DC repeatedly caused: samba_dnsupdate --verbose --all-names to fail on the new DC with: Failed to connect host x.x.x.x on port 49152 - NT_STATUS_CONNECTION_REFUSED Noted: both samba versions are obsolete and will be updated post haste. Regardless, samba_dnsupdate was accidentally invoked on the new DC while the

Rowland penny via samba <samba at lists.samba.org> wrote: > On 11/11/2019 01:22, Don Kuenz via samba wrote: >> >> Error occurs on FreeBSD 12.1 >> >> ------------------------------------------------------------------------ >> samba-tool domain provision --use-rfc2307 --interactive >> Traceback (most recent call last): >> File

Rowland penny wrote: > On 11/11/2019 01:22, Don Kuenz wrote: >> >> Error occurs on FreeBSD 12.1 >> >> ------------------------------------------------------------------------ >> samba-tool domain provision --use-rfc2307 --interactive >> Traceback (most recent call last): >> File "/usr/local/bin/samba-tool", line 33, in <module>

Andrea Venturoli wrote: > Don Kuenz wrote: > >> Samba 4.8. It turns out that both the FreeBSD bin and source packages >> are broke. Fully functional, error free binaries were eventually created >> by manually installing about a dozen requisite packages, one at a time >> along the way, whenever make halted on an error. >> To add to a difficult day, something

Rowland Penny via samba <samba at lists.samba.org> wrote: > On 09 Dec 2016 21:52:39 UTC > Don via samba <samba at lists.samba.org> wrote: > >> Greetings, >> >> The backup and restore Samba AD DC section of SambaWiki [1] refers to >> ./source4/scripting/bin/samba_backup . Although my recent version of >> samba_backup uses tdbbackup on ldb files, it

Subject: Re: Is it possible to transfer a large, dynamic file in a piecemeal fashion? Yes it is. Don Kuenz via rsync <rsync at lists.samba.org> wrote: > Greetings, > > Is it possible to use rsync to transmit a large, dynamic 2TB file in a > piecemeal fashion during daylight hours over the course of a dozen days? > On a good day, about 200GB of data can be transferred before

Greetings, This post pertains to Samba version 4.16.8 on FreeBSD 13.1. When GPMC.MSC is invoked from within a Windows server domain member, it displays an inconsistency error: <https://attachments.samba.org/attachment.cgi?id=8386> <https://bugzilla.samba.org/show_bug.cgi?id=14927> # samba-tool ntacl sysvolreset # samba-tool ntacl sysvolcheck ERROR(<class

An old, standalone Samba 4.1 DC was originally provisioned with --use-rfc2307. When a new Samba 4.7 DC was joined to the original domain --option='idmap_ldb:use rfc2307 = yes' was not used. How do you correct this oversight? Is it possible to remove the new Samba 4.7 from the original domain and then join it to the original domain yet again but this time use

Greetings, Is it possible to use rsync to transmit a large, dynamic 2TB file in a piecemeal fashion during daylight hours over the course of a dozen days? On a good day, about 200GB of data can be transferred before rsync times out to enable a nightly local backup to complete. The local backup changes a few 512 byte blocks in the 2TB file. That's why the 2TB file is dynamic. As an

On 28/05/2020 05:14, Don Kuenz via samba wrote: > > Greetings, > > bind914-9.14.6 and bind-tools-9.14.6 were built and installed on a new > FreeBSD 12.1 samba DC. Then a prebuilt samba410-4.10.13 package was > installed. Both bind-dns/named.conf and BIND9_DLZ libs are missing. Is this using the ZFS filesystem ? If so, how ? What do you mean by 'a prebuilt

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

im betting here on a smb.conf that was not 4.6 compliant. port 49152 is not related i my opinion. is there a firewall running? the dynamic port range changed from a low range to high. Greetz Louis Op 17 mrt. 2019, om 22:36, Rowland Penny via samba <samba at lists.samba.org> schreef: On 17 Mar 2019 20:44:12 UTC Don Kuenz via samba <samba at lists.samba.org> wrote:

I have some problem whit Kerberos. OS: FreeBSD 5.3 Domain: W2k3 native mode. 1)I am Installing Heimdal 0.6.1 over port. Config /etc/krb5.conf %/usr/local/bin/kinit ivan ivan@NKMK.RU's Password: kinit: krb5_get_init_creds: Response too big for UDP, retry with TCP 2)Compile and install Heimdal 0.6.4 over source %/usr/local/bin/kinit ivan ivan@NKMK.RU's Password: kinit:

You probably want --inplace for this rather than partial. The upside of --partial is that the existing file isn't replaced until there is a complete file to replace it with. The downside is building up that entire new file. On 09/05/2017 12:01 AM, Don Kuenz via rsync wrote: > Subject: Re: Is it possible to transfer a large, dynamic file in a piecemeal fashion? Yes it is. > > Don

I am in the process of trying to setup a Samba 4.0.6 AD DC on Fedora 18, but dnsupdate is not updating the DNS records since I changed the addresses that I have assigned to my NICs. At first I thought the internal server didn't want to work, so I tried getting things setup with Bind (which is working just not with Samba yet). I am wanting to replace our Windows Server 2003 with RHEL 7 (or

>From searching the web, I found that many people have encountered this problem. The fixes the suggested don't seem to work for me... My smb.conf file looks like this [global] workgroup = OURDOMAIN security = ADS realm = OURDOMAIN.com password server = OURSERVER encrypt passwords = yes add user script = /usr/sbin/useradd %u hosts allow = 192.168.X. 127. winbind uid = 10000-20000 winbind

Hello all, this is with Samba 3.3.4 on FreeBSD, built locally from ports. The server is joined to a Windows 2008 AD domain. I'm only using winbind, because all I need are users and groups; this isn't a file server. As far as I can tell, it is actually working fine; winbindd can get all the required information from the DC. The NetBIOS name of the domain is MYDOMAIN, the DNS name is

I had freshly installed an Ubuntu Server 12.04lts and Samba 4.0.1 using the internal DNS. I followed the official HowTo until "kinit administrator at DOMAIN.LOCAL" It didn't work (cannot contact any kdc...) A "netstat" showed that "avahi-daemon" was running at: 807/avahi-daemon: r udp 0 0 10.0.0.20:389 0.0.0.0:* After removing that package