similar to: Join Samba to Windows with error DsReplicaSync

Hi, i've three samba DC's with BIND9_DLZ backend . The DNS queryes is erratic, sometimes from pc lan the DNS resolution work fine and on another occasion give timeout or fail My DC's are: [............] [root at sambadc03 ~]# host -t A mydomain.com mydomain.com has address 10.13.250.128 mydomain.com has address 10.13.250.110 mydomain.com has address 10.13.250.111 mydomain.com has

Well, if I eliminate the ipv6.disable-1 from the kernel command line everything works fine. So I don't think it is a samba config issue per se, unless of course I need something specific for kpasswd5 port 464, but in any case. This AD server is a Fedora 41 box running root at ad:~# uname -ra Linux ad.example.com 6.11.10-300.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Nov 23 00:51:20 UTC 2024

On Fri, 2024-05-03 at 09:34 +0100, Rowland Penny via samba wrote: > On Fri, 03 May 2024 10:11:48 +0200 > PaLi via samba <samba at lists.samba.org> wrote: > > > Hello > > > > I'm not able to connect to Samba AD domain by realm. > > > > sudo realm join OFFICE.COMPANY.COM -U administrator > > > > Password for administrator: > >

In your situation on Fedora you are not using the Samba buildin Heimdal KDC but the MIT KDC that might explain some differences between Rowland and you. Regards Christian Am 11. Januar 2025 21:18:23 MEZ schrieb Gregory Carter via samba <samba at lists.samba.org>: >I have resolved this issue last night. > >The issue wasn't the ipv6.disable=1, it was a separate difference

I noticed that kpasswd5 (port 464) isn't showing up on subnets where IPv6 is not allowed. So I cannot do any joins for these Linux boxes. Is there a Global switch I can use for samba to just startup and listen on IPV4 only? It seems inconsistent as all the other services don't seem to be affected by this switch and appropriately bind to the interface. How do I get kpasswd5 up on IPV4

I have resolved this issue last night. The issue wasn't the ipv6.disable=1, it was a separate difference in the config files. I was using: > bind interfaces only = yes > interfaces = 127.0.0.1 192.168.1.40 Mainly due to the fact that I plan on adding more ethernet interfaces later to the mail server, and I wanted to insure the configuration was explicit on what

On Fri, 10 Jan 2025 15:07:34 -0700 Gregory Carter <gjcarter2 at gmail.com> wrote: > Well, if I eliminate the ipv6.disable-1 from the kernel command line > everything works fine. So I don't think it is a samba config issue > per se, unless of course I need something specific for kpasswd5 port > 464, but in any case. > > This AD server is a Fedora 41 box running I

I had configured Samba AD's with Bind9_DLZ in all DC. But for some reason (i couldn't determine) three (sambadc02,03,04) AD's responded very slowly . So change to Samba_Internal backend into the servers with problem and works fine. sambadc01 -> with FSMO roles - Bind9_DLZ sambadc02 -> Samba_Internal sambadc03 -> Samba_Internal sambadc04 -> Samba_Internal My question is:

On Fri, 03 May 2024 10:11:48 +0200 PaLi via samba <samba at lists.samba.org> wrote: > Hello > > I'm not able to connect to Samba AD domain by realm. > > sudo realm join OFFICE.COMPANY.COM -U administrator > > Password for administrator: > See: journalctl REALMD_OPERATION=r41422.307314 > realm: Couldn't join realm: Failed to join the domain > >

Hi Rowland, 1. Thanks for you clarification ;) 2. About, my old DLZ configuration is: Versions: bind-9.11 - S.O Centos 7.8 This was the sambadc04 with the old bind dlz backend . [..........] [root at sambadc04 ~]# cat /etc/sysconfig/named |grep -v '^#' NAMED_RUN_CHROOTED="no" OPTIONS="-4" [..........] The /etc/named.conf [..........] acl "trusted" {

Hi All, since Friday I get a surprising error, when I try to replicate my domain-controllers. This is new! It worked before in any direction without any failures... When I replicate from dc2 to dc1 this runs also, without any failures: root at dc1:~# samba-tool drs replicate dc1 dc2 DC=mydomain,DC=uni-frankfurt,DC=de Replicate from dc2 to dc1 was successful. Only when I try to replicate from

Hello, I'm trying to setup a Samba 4 sever (Alpha 18) over Centos 6 32 bits. I have followed directions in http://wiki.samba.org/index.php/Samba4/HOWTO Everything has gone OK up to Step 9, Testing kerberos. kinit administrator at PDC.IESMSANTILLANA.LAN Returns (red color is mine, not from computer)... kinit: Server not found in Kerberos database while getting initial credentials If I try

Hello I'm not able to connect to Samba AD domain by realm. sudo realm join OFFICE.COMPANY.COM -U administrator Password for administrator: See: journalctl REALMD_OPERATION=r41422.307314 realm: Couldn't join realm: Failed to join the domain this is in journal: smbmem41.office.company.com realmd[211374]: adcli: joining domain office.company.com failed: Couldn't set password for

Hello, I am changing 2 x Gentoo/Samba 4.1 AD DCs for 2 x Ubuntu/Samba 4.7 AD DCs. I have joined the 2 new DCs and transferred the role to #3. I am performing sysvol replication from #3 to #4 quite happily with no errors. I have left them for 2 weeks. Windows desktops, etc. appear fine with no problems. I now want to demote and remove #1 and #2 from the domain and network. In preparation, I

On Sat, 6 Apr 2019 10:58:15 +0200 Martin Krämer via samba <samba at lists.samba.org> wrote: > Hello everyone, > > I have setup two Samba AD DC's running Debian 9 with BIND9_DLZ dns > backend. Both are running Samba 4.5.16 - I know it is already very > old version but this is the default one coming with debian stretch > repo. (I will upgrade to Debian buster - and with

On Fri, 25 May 2018 13:33:19 +0000 Paul Littlefield via samba <samba at lists.samba.org> wrote: > Hello, > > I am changing 2 x Gentoo/Samba 4.1 AD DCs for 2 x Ubuntu/Samba 4.7 AD > DCs. > > I have joined the 2 new DCs and transferred the role to #3. > > I am performing sysvol replication from #3 to #4 quite happily with > no errors. > > I have left them

The Samba ports are not filtered. The firewall is between STG-DC and SAMBADC (both of them sync correctly). The sync problems happen in VIG-DC3, which is behind the same firewall of STG-DC. Here's nmap output (SAMBADC is 172.16.50.9): root at vig-dc3:~# nmap -Pn 172.16.50.9 Starting Nmap 7.93 ( https://nmap.org ) at 2024-05-23 08:22 UTC Nmap scan report for SAMBADC.ugt.ldap (172.16.50.9)

On Wed, 10 Apr 2019 21:10:59 +0200 Martin Krämer <mk.maddin at gmail.com> wrote: > Thanks - think I will give it a try > I read the wiki page > https://wiki.samba.org/index.php/Idmap_config_rid and understood this > is a read only connection. For normal logon and use I think this is > absolutely enough. Only topic I am not sure of is password expiry... > - will people be

Dear useRs: I successfully model-based partitioned several datasets through the use of mob from the party package (thanks Achim et al. once again !!!). At times, however, the partitioning leads to terminal nodes in which the parameter estimates of the model are not significant (although the split points and in general the proposed segmentation both seem reasonable). As I do not seem to be able

On Sat, 6 Apr 2019 17:21:26 +0200 Martin Krämer <mk.maddin at gmail.com> wrote: > Hello Rowland, > > thanks for your help. > Below my comments > > See here: > > > > http://apt.van-belle.nl/ > > > From stability point of view I always had the best experience by > saying with the debian default repository. > Additionally as you have seen blow I