search for: crcomp

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

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

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

Andrew Bartlett wrote: > Don Kuenz 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,

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

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

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