similar to: Floating IP breaks AD replication

Maybe this is a stupid idea, but what we are doing here is using just the domain name for all sorts of services, i.e. LDAP. So instead of pointing a client to dc1.somedom.contoso.com or dc2.somedom.contoso.com, we point them to somedom.contoso.com which is then resolved to both and the client can pick. Best regards Johannes Am Mo., 23. Nov. 2020 um 17:02 Uhr schrieb Rowland penny via samba <

> we point them to somedom.contoso.com which is then > resolved to both and the client can pick I want to avoid Round-Robin DNS > You cannot use CTDB with AD DCs You can. /etc/ctdb/nodes 192.168.30.11 192.168.30.12 /etc/ctdb/public_addresses 192.168.30.10/24 ens18 /etc/ctdb/events/legacy/20.samba-ad.script #!/usr/bin/env bash function monitor_ldap() { ldbsearch -H

> Your DC's really should have fixed IP's Well, they have. But there are still projects which can not use multiple DNS Names. e.g. - https://gitlab.com/gitlab-org/gitlab/-/issues/139 - https://github.com/go-gitea/gitea/issues/6898 So I use an additional floating IP > I cannot recommend anyone using your method Why not? Even if AD replication is quite robust concerning multi

On 23/11/2020 16:50, Sven Wick via samba wrote: > >> You cannot use CTDB with AD DCs > You can. OK, I will change that to 'Do not use CTDB with Samba AD DCs' A cluster is where all the same data is stored on multiple computers but they act as if they were just one computer, which funnily enough is what Samba AD dc's do, so you are wrapping something that acts like one

I currently plan to move my storage to Gluster. One of the anticipated advantages is to have Gluster replicate data among physical nodes, i.e. if one node dies the file service can live on. AD for authentication also replicates nice on distinct physical nodes. So the remaining single point of failure is the samba file service. Is there something more intelligent than: if not \\severA\share

Setup a DC using 4.0.3 - all appears to go fine... Setup a second DC and everything works fine to here...but I'm not sure if replication is actually working or not. Here's what I get from ./samba-tool drs showrepl I've also done. [./samba-tool drs kcc -Uadministrator dc2.samba.somedom.local] in an attempt to fix the replication problem. (or what I think is a problem.) [The outbound

Hello, maybe there is someone they can help and answer a question why i get these network screen on my ctdb clusters. I have two ctdb clusters. One physical and one in a vmware enviroment. So when i transfer any files (copy) in a samba share so i get such network curves with performance breaks. I dont see that the transfer will stop but why is that so? can i change anything or does anybody know

Hai,   I was just reading : https://www.howtoforge.com/tutorial/ata-over-ethernet-aoe-on-debian-8-jessie/   I was wondering, anyone tried AoE for sysvol, so i dont needs replication anymore. Anyone Pro’s and Con’s ?    Or can anyone tell of sysvol is going to be replicated by samba so we dont need scripts anymore.     Greetz,   Louis

Hi, i need some help. We have two Networks. A CTDB Cluster and one domain controller in the same network. All other domain controller are outside this network. They are both connected with a firewall / router. We activated netbios over tcp on the other domain controllers outside but it seems that when we remove the single internal domain controller ctdb will not start with the following error.

I''ve been trying to install Ferret on RedHat 7.3, Ruby 1.8 (let me know if more details would be helpful) using the gem install. I''ve tried every version >10 and it installs, but I get errors: Building native extensions. This could take a while... In file included from q_filtered_query.c:1: search.h:683: array size missing in ''comparables'' make: ***

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 02.02.2015 um 13:30 schrieb Sven Schwedas: > On 2015-02-02 12:56, Lars Hanke wrote: >> I currently plan to move my storage to Gluster. One of the >> anticipated advantages is to have Gluster replicate data among >> physical nodes, i.e. if one node dies the file service can live >> on. >> >> AD for

Hi, on our samba 4 domain member server we use the vfs objects module 'recycle'. Unfortunately we ran into a strange permission problem with deleted folders. The newly created folders in the recycle folder have the wrong permission. The deleted file(s) itself has the correct group (rw) permissions. The shares correct permissions: getfacl Papierkorb/ # file: Papierkorb/ # owner: root #

Hi, we are in the process of testing a migration from our NT Classic Domain with OpenLdap to Samba AD. In our test setup migration of all accounts, groups and computer accounts went well using the classicupgrade path. Next step now is testing how to add a member server for file server services. We were able to get the server to join the domain and also idmapping works mostly as expected.

Hi Maxence, > Fyi, i've updated to 4.7.1, the dbcheck still not fix the broken links, > is the fix you talk about planned for a future release ? > > Our customer reported me, some users have issues when their logon server > is DC1 but not when it's DC2. > > On DC1 some users have access to all shares, some doesn't have any > access at all. actually this last

On Mon, 6 Nov 2017 11:39:50 +0100 (CET) Maxence SARTIAUX via samba <samba at lists.samba.org> wrote: > Hello. > > To follow-up this issue, since the upgrade, when i do a named reload > it crash, look like there's duplicated zones. > > Here's the log when i trigger a reload > > > nov 05 03:09:02 data.contoso.com named[2807]: received control >

Hello last week we updated three domain controllers (Sernet Samba) from 4.2 to 4.7, typical upgrade path (4.3->4.4->4.5->4.6->4.7), everything was ok. The next day we got a mail from the Sernet team informing they fixed a bug affecting the group memberships. https://bugzilla.samba.org/show_bug.cgi?id=13095 We've applied the update and few days after the update which should

Hi, I am in the middle of creating (or should that be re-creating) my test domain, creation of the first DC went without incidence, so I moved on to the second DC and this is where the problems started. I downloaded samba 4.3.1 and compiled it, I then setup bind9 etc and joined the new DC to the domain, everything seemed ok, so I then started testing DNS. This is where I found that my nice

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

Hi list, I've a strange issue with Windows 7 (also occurs on 8.1) when accessing shares on domain controllers. If I use IP address or in-domain FQDN (server.domain.name), all is right. If I use another DNS entry pointing to the same IP, share access fails with following message (translated from french) : \\somehost.somsuffix\someshare is not accessible. […] Invalid parameter Issue

Hello, is there a way to cluster samba4 with ctdb? The old [global] parameters of samba3 Will not work: Clustering=yes <--unknown with testparm Idmap backend= tdb2 <--unknown with testparm Greeetings Daniel ----------------------------------------------- EDV Daniel M?ller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 T?bingen Tel.: 07071/206-463, Fax: