similar to: FSMO DC giving curious log output

Hello Community, im joining several macintosh workstations to my samba AD. First of all, it works pretty well and im able to authenticate/login my AD user on a mac. Server: Ubuntu 16.04 SAMBA: 4.7.7 First: Everytime when a mac starts up, some log entries are shown in log.samba. Looks like (Its not a flood, about 4 messages for each client): [2018/04/19 14:35:04.645001, 0]

Hi guys, I'm having a struggle with Dynamic DNS updates. When i join a Windows machine to the domain the host name get registered. When I change the IP the A-record gets deleted and nothing more happens. I'm using the internal dns with Samba 4. Any help or advice would be much appreciated. log: Replicated 0 objects (0 linked attributes) for CN=Configuration,DC=corp,DC=lo [2013/02/28

DNS is suddenly not working properly for some machines. We had a bunch of machines that were joined to the domain, but the computer name was wrong. To fix this, we unjoined the machines and deleted the computer accounts out of Samba (because renames while joined will leave LDAP attributes with the previous machine name and there will be connectivity problems for some reason), and we deleted them

This looks like a resolving misconfiguration. Post your smb.conf and resolv.conf and hosts and ( if used bind, the bind config ) Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > lingpanda101 via samba > Verzonden: donderdag 19 april 2018 16:28 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Samba

Not sure about the high CPU load, but you have the [netlogon] share twice in your smb.conf. Your first matches mine, have you added the second yourself? The second one looks weird with 2 path definitions. Cj Tibbetts schreef op do 18-12-2014 om 08:59 [-0700]: > New to linux and new to Samba so any direction in troubleshooting would be > helpful. Here is what I have so far. > > Within

Yes, you re right. Im using the *Samba Internal DNS Back End*. This is my config: # smb.conf [global] netbios name = DC1 realm = DOMAIN.DE workgroup = DOMAIN dns forwarder = <IP FIRST DNS SERVER> <IP SECOND DNS SERVER> server role = active directory domain controller idmap_ldb:use rfc2307 = yes log level = 3 tls

We are using samba 4.1.9 complied from source. We have been running as an AD DC for 5 months. Lately, we have noticed that samba processor seem to consume the entire system, using all cpu cycles. This happens within about 30 minutes of starting or restating the samba daemons. When Samba slows down, the first issue that comes up is that dns name resolutions time out for any client asking for

>>> I am running samba 4.1.9 compiled with internal dns. Please upgrade first to the latest samba version before be can investigate whats going on. The lastest is 4.1.14 now and lots have happend in betweeen. Greetz, Louis >-----Oorspronkelijk bericht----- >Van: ricky.nance at gmail.com >[mailto:samba-bounces at lists.samba.org] Namens Ricky Nance >Verzonden:

New to linux and new to Samba so any direction in troubleshooting would be helpful. Here is what I have so far. Within a half an hour of a reboot of the server my cpu reaches high numbers and becomes slow to respond on all actions. With my limited understanding I have used vmstat to observe the system. I noticed is that the numbers of forks grows from 1-2k to 43k within 30 minutes after reboot. I

Here is the information requested it took 3 days before results came samba-tool dbcheck finished with this error root at ham1:/usr/local/samba/bin# time ./samba-tool dbcheck --cross-ncs Checking 212687 objects ERROR(<type 'exceptions.MemoryError'>): uncaught exception - File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/__init__.py", line 175, in _run

On Tue, Aug 29, 2017 at 6:55 PM, lingpanda101 <lingpanda101 at gmail.com > wrote: > I can confirm they work on 4.6.7. I do recall they have worked for > several prior versions as well. I can't seem to get PTR records to > register though. > > The refused request doesn't necessarily mean it's not working. Windows > will send an un-secure request first,

Hello, I am wondering if this is preferred at this iteration in development. If so, what would be the best way to continue? To build a VM server and have that do file serving, then migrate file serving from the old ad, then join the new VM to the ad server? Vice versa? My reasoning; running sernet (Version 4.0.12-SerNet-Ubuntu-8.precise) with Ubuntu 12.0.2 and since deployment in three different

On 18/12/14 16:19, Germ van Eck wrote: > Not sure about the high CPU load, but you have the [netlogon] share > twice in your smb.conf. Your first matches mine, have you added the > second yourself? > The second one looks weird with 2 path definitions. > Cj Tibbetts schreef op do 18-12-2014 om 08:59 [-0700]: >> New to linux and new to Samba so any direction in troubleshooting

Hi, i need help with strange problem. I installed Fedora 28 to test Samba 4 AD DC with MIT Kerberos with Windows 10 and Windows 7 clients and i can't run GPOs for machines. GPOs for users works. On Fedora 27 is the same problem. After couple of hours changing settings I make a new installation of Debian 9.4 and everything works "out of the box". I set all like here:

Hi team, I recently upgrade some servers from v4.3.5 (affected by https://bugzilla.samba.org/show_bug.cgi?id=11520 ) to v4.5.8 (default in Debian Stretch) and was expecting secure DNS updates to be working again, but they are not. My logs show the same issues reported on bug 11520: [2017/08/29 15:21:01.990467, 2] ../source4/dns_server/dns_update.c:773(dns_server_process_update) Got a dns

Apparently I forgot I had this particular problem and that I had a work-around: https://lists.samba.org/archive/samba/2023-November/247069.html But yeah...disjoining a computer, *and* deleting the computer account *and* deleting the record out of DNS is still causing problems on various servers I manage. Currently on version 4.17.12-Debian The Windows event log says the DNS server refused the

Hi Denis, Thanks for taking the time to answer. Yes, I may have been wrong with --forced-sync and --full-sync since the start but in fact I wanted to make sure to force replication between the servers. Here is what I have noticed: - replication works from dc00 -> dc00 but not from dc01 -> dc00: [root at dc00 ~]# samba-tool drs replicate DC01 DC00 dc=ad,dc=lasthome,dc=solace,dc=krynn

Hello, I have errors like below every day at midnight. Anyone have an idea? samba4 AD version : 4.18.11 OS : Rocky Linux 8.9 Mar 18 00:00:00 <dc> samba[1253835]: [2024/03/18 00:00:00.114303, 1] ../../source4/dns_server/dns_query.c:1141(dns_server_process_query_got_auth) Mar 18 00:00:00 <dc> samba[1253835]: dns_server_process_query_got_auth: Failed to add SOA record:

On Fri, 22 Mar 2024 14:45:31 +0000 Kamal Chikh echioukh via samba <samba at lists.samba.org> wrote: > Hello, > > I have errors like below every day at midnight. Anyone have an idea? > > samba4 AD version : 4.18.11 > OS : Rocky Linux 8.9 > > Mar 18 00:00:00 <dc> samba[1253835]: [2024/03/18 00:00:00.114303, 1] >

Hi all, I'm running in circles trying to debug replication failures on samba 4.7.6: dc00 : is a VM on KVM host (attached to a bridge on local LAN) dc01 : is a similarly configured VM on another KVM host. I've forcibly demoted and re-promoted dc01 but I still cannot get automatic replication to work: root at dc00 ~]# samba-tool drs showrepl Krynn\DC00 DSA Options: 0x00000001 DSA