similar to: rid backed not working

On 23/10/2019 16:49, Leszek Gubernat via samba wrote: > Hi All, > I'd like start using 'rid' idmap backed rather than 'tdb' on my member > servers to keep gidNumbers in sync across the realm INCLUDING the DC. You cannot, A DC uses idmap.ldb to store xidNumbers (which are in the 3000000 range), you cannot use the 'rid' or 'ad' backend on a DC. On a

I have a samba classic domain, called it "DomainA." All domain controllers and servers are running 3.6.25 on Solaris 11. The PDC and BDC use an LDAP backend for unix, samba and idmap data. Member servers use LDAP backend for unix accounts, so the underlying unix and group accounts are consistent. There is a trust relationship with Windows 2008 AD domain

Hi All, I've got a Samba4.5.15 server which acts both as an DC and a file server. I'd like to break the setup into two servers without forcing the users to redo their mappings and links which point the DC's name or fqdn. My idea is to rename the DC (hostname and netbios) and assign its old the another server with shares only. Is it possible to do it safely without disrupting the

I tried recreating the trusts. I start by setting up trusts on Windows side, using Active Directory Domains and Trusts on the DomainB AD server. . I specify the the samba domain (DOMAINB) but before I can even specify trust type or direction I get the following: Cannot continue Trust relationship can not be created… The local security authority is unable to obtain an RPC

On Wed, Nov 18, 2015 at 6:00 AM, Rowland Penny <rowlandpenny241155 at gmail.com > wrote: > On 18/11/15 10:27, Jeff Dickens wrote: > >> >> >> On Nov 18, 2015 4:35 AM, "Rowland Penny" <rowlandpenny241155 at gmail.com >> <mailto:rowlandpenny241155 at gmail.com>> wrote: >> > >> > On 17/11/15 23:09, Jeff Dickens wrote:

<20100926154324.GD21843 at redhat.com>; from Michael S. Tsirkin on Sun, Sep 26, 2010 at 17:43:24 +0200 > > > >It's vanilla 2.6.32.22, but I also reproduced this on Debian's 2.6.32-23 > > > >(based on 2.6.32.21). > > > > > > > >If offload is the only difference, I'll play with different offload > > > >options and check

<20100926154324.GD21843 at redhat.com>; from Michael S. Tsirkin on Sun, Sep 26, 2010 at 17:43:24 +0200 > > > >It's vanilla 2.6.32.22, but I also reproduced this on Debian's 2.6.32-23 > > > >(based on 2.6.32.21). > > > > > > > >If offload is the only difference, I'll play with different offload > > > >options and check

Hi Thomas, >----Messaggio originale---- >Da: thomas@kupper.org >Data: 22/01/2010 10.48 >A: "Leszek Ciesielski"<skolima@gmail.com> >Cc: "linux-btrfs"<linux-btrfs@vger.kernel.org> >Ogg: Re: mount command not honoring rootflags passed > > >On 22 Jan 2010, at 10:40, Leszek Ciesielski wrote: > >> On Fri, Jan 22, 2010 at 10:30 AM,

> > You are using Bind9 with flatfiles, this is NOT recommended. > If you are using the standard Ubuntu Bind9 package, you should be using > BIND9_DLZ and this stores the dns info in AD. > How did you provision the DC, was it with 'BIND9_FLATFILE' or > 'BIND9_DLZ' ? > If it was the later, just remove the 'wie' zone and its reverse zone > from the

Samba - General mailing list wrote > On Wed, 17 May 2017 04:26:16 -0700 (PDT) > artyom via samba &lt; > samba at .samba > &gt; wrote: > >> I use official manual from wiki.samba.org for install samba 4.6.3 >> (from source) with bind_dlz on bind 9.9.10 (from source too). My OS >> is Debian Jessie x64 8.8 netinst. I use >>

On 16.11.2015 14:44, Rowland Penny wrote: > On 16/11/15 13:25, Ole Traupe wrote: >> >> >> Am 16.11.2015 um 14:06 schrieb Viktor Trojanovic: >>> >>> >>> On 16.11.2015 13:48, Viktor Trojanovic wrote: >>>> See replies below >>>> >>>> On 16.11.2015 12:39, Rowland Penny wrote: >>>>> On 16/11/15 11:19,

On 16.11.2015 15:08, Rowland Penny wrote: > On 16/11/15 14:00, Viktor Trojanovic wrote: >> >> >> On 16.11.2015 14:44, Rowland Penny wrote: >>> On 16/11/15 13:25, Ole Traupe wrote: >>>> >>>> >>>> Am 16.11.2015 um 14:06 schrieb Viktor Trojanovic: >>>>> >>>>> >>>>> On 16.11.2015 13:48,

Ok, > I am getting the DNS register warning message on > *all* win clients, not just that one. Good info, so, this confirms its not a bug but an incorrect setting. Type ipconfig /all on a pc. Post the output, i suspect, incorrect dnsdomain or dns search domain. Also. Check if the PTR records are set to the correct server ips. This does not change on its own. Ldbsearch from below

Othere thing. IF you domain name is like domain.tld By default, Windows does not send updates to top-level domains. If thats the case you should change it to a single-lable dns. https://support.microsoft.com/en-us/kb/300684 Greetz, Louis > -----Oorspronkelijk bericht----- > Van: Viktor Trojanovic [mailto:viktor at troja.ch] > Verzonden: maandag 16 november 2015 15:45 > Aan:

Am 16.11.2015 um 14:06 schrieb Viktor Trojanovic: > > > On 16.11.2015 13:48, Viktor Trojanovic wrote: >> See replies below >> >> On 16.11.2015 12:39, Rowland Penny wrote: >>> On 16/11/15 11:19, Viktor Trojanovic wrote: >>>> So I ran a samba-tool ntacl sysvolcheck, and the following error >>>> message came up: >>>>

On Wed, 24 May 2017 11:36:07 +0200 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > No big change here ... > > I can: > > * logon as BUERO\root > > * connect to the shares on \\dc > > * test other users via smbclient (auth works for them) > > But: > > * login as BUERO\Administrator just sits there and waits for >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I try to set up a ADDC with bind9 and dhcp-Server for dynamic DNS-updates. I followd the wiki: https://wiki.samba.org/index.php/Configure_DHCP_to_update_DNS_records_wi th_BIND9 My problem is, that the PTR Record will not be updated, because the script is using the wrong reverse-zone: - --------------------- Dez 26 17:30:05 addc-01 named[512]:

This morning due a a power outage our samba servers crashed. All looked OK at reboot (at first) - users who had stayed logged in could still access shares. However users who tried to log back into the network got the "The trust relationship between this workstation and the primary domain failed" message. Removing a machine from domain and rejoining did not help. Servers are a

Hi! I have some problems with my new member server This is my schema: -Doman Controller name is ?DC01? and realm name is ?MYDOMAIN.LOCAL? ? WORKS! -Member server 1, name ?MEMBER1? ? WORKS! #net rpc rights list accounts ?Uadministrator MYDOMAIN\Domain Admins SeDiskOperatorPrivilege When I run this command works well and I can administrate my shares with ACL from

wel, i was thinking about the following.. AD backend: member1 = fileserver with only company data. linux and windows users. member4 = database server with linux and windows users, nfs-kerberos connected with member1. member5 = webserver server with linux and windows users, nfs-kerberos connected with member1. ( no external web server only internal ) RID backend: member2 = profiles and user