similar to: Strange problem with ddns AAAA delete

On 10/12/15 14:00, Ole Traupe wrote: > > > Am 10.12.2015 um 14:38 schrieb Rowland penny: >> On 10/12/15 13:25, Ole Traupe wrote: >>> Is it possible that kdc server is always the SOA, at least if >>> derived from DNS and not specified *explicitly* in the krb5.conf? >>> >>> In my DNS-Manager console I find that >>> >>>

On 10/12/15 14:40, Ole Traupe wrote: > >>> However, my 2nd DC is not that new, I restarted it many times, just >>> again (samba service). No DNS records are created anywhere. >>> >>> If I go through the DNS console, in each and every container there >>> is some entry for the 1st DC, but none for the 2nd (except on the >>> top levels: FQDN

Hi I know that this has been addressed before but I couldn't find a solution. Summary: when attempting to write a dns record using nsupdate, nothing gets written to the zone due to the error: ; TSIG error with server: tsig verify failure Everything is working. We can login to the domain from the same client and we have sssd sending the dyndns update requests which also produce the same

I am also seeing this in smbd.log: [2020/07/03 09:20:18.211558, 1] ../../auth/kerberos/gssapi_helper.c:391(gssapi_check_packet) GSS VerifyMic failed: A token had an invalid MIC: unknown mech-code 2529638943 for mech 1 2 840 113554 1 2 2 [2020/07/03 09:20:18.211625, 0] ../../source4/auth/gensec/gensec_gssapi.c:1347(gensec_gssapi_check_packet)

Hello List, Hello Rowland :-) again I'm having problems with the DDNS. I did it as shown in the wiki. I took all teh scripts from the wiki the dhcp-dyndns.sh is Version: 0.8.9 I configured everything including the failover. When I start the two DHCP-Server everything is perfect. I see the right messages in the log, the two DHCP-Servers are talking to each other. When a Client ask for an

> So you never read this: > https://wiki.samba.org/index.php/Changing_the_DNS_Back_End_of_a_Samba_AD_DC > Which means that you probably never ran the aptly named > 'samba_upgradedns'Of course I ran this. Many times. I'm not stupid, Rowland. At least I can read:D If I've seen that Bind doesn't work, I had to change backend to internal DNS.I carefully read and made

Hello, At one point secure dynamic updates worked. Now I require 'allow dns updates = nonsecure' for dynamic updates to work. I can't seem to find any trace of updates being performed in the samba logs or Windows. I've hit a wall and can't seem to progress. Since I couldn't pull anything from the logs I decided to run 'nsupdate -g -d -D -L 10'. This was

Hello Hello I'm using samba4 rc1 since 2 months as PDC with samba4 internal DNS. Everything works but i can't ping domain clinets via its names. Clients are named as stacja00X.localdomain where X is station number. But even on SambaPDC i can't ping it with for exapmle: ping stacja003.localdomain or ping stacja003 nslookup says that there is no host like that. Funny becouse domain

On Thu, 10 Jan 2019 20:18:37 +0000 (UTC) Billy Bob <billysbobs at yahoo.com> wrote: > > > On Thursday, January 10, 2019 2:08 PM, Billy Bob via samba > <samba at lists.samba.org> wrote: > >Do you want to change your scripts to match my scripts as found on > >the wiki ? > >I know they work, well they have for me for the last 6 years. > >

Hello I'm using samba4 rc1 since 2 months as PDC with samba4 internal DNS. Everything works but i can't ping domain clients even from samba machine. Clients are named as station00x.domain.lan where x is station number. But even on SambaPDC i can't ping it with for exapmle: ping station004.domain.lan or ping stacja003. Nslookup says that there is no host like that. Funny becouse

On Thu, 10 Jan 2019 20:40:30 +0000 (UTC) Billy Bob <billysbobs at yahoo.com> wrote: > > > > On Thursday, January 10, 2019 2:33 PM, Rowland Penny via samba > <samba at lists.samba.org> wrote: > > >On Thu, 10 Jan 2019 20:18:37 +0000 (UTC)> > >Billy Bob <billysbobs at yahoo.com> wrote: > > > >>  > >> >

Hi, I used to upgrade/migrated samba 3.3.10 to samba 3.4.17 with LDAP backend in place, while upgrading the CentOS from 5.5 to 5.9. In place to retain the trust relationship. The users can able to login without re-authentication from existing machines. Tested 3 XPs, and 3 Win7 but it takes 5-8 mins to login compared to 1 win7 that was re-connected (disconnected from domain, restart, then rejoin

Hi all, I posted on both mailing as this seems to be (to me) an internal issue. As the 4.3.1 went out I decided to switch my DC from 4.3.0 to this new version. The process was to install Samba 4.3.1 on new systems, joining these Samba as DC, seizing FSMO roles, demote all 4.3.0. The few I tested until now is working except for DNS entries: samba_dnsupdate is not working as it tries to update

On Friday, January 11, 2019 1:39 PM, Rowland Penny via samba <samba at lists.samba.org> wrote:   > There doesn't seem to be anything really wrong there,the only really > difference between your named.conf and mine is that I have: >  >     dnssec-validation no; >     dnssec-enable no; >     dnssec-lookaside no; >     listen-on-v6 { none; }; >     listen-on port 53

"--seize" helped: root at pre01svdeb03:~# samba-tool fsmo show SchemaMasterRole owner: CN=NTDS Settings,CN=PRE01SVDEB03,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=pilsbacher,DC=at InfrastructureMasterRole owner: CN=NTDS Settings,CN=PRE01SVDEB03,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=pilsbacher,DC=at RidAllocationMasterRole owner:

The DDNS setup from the wiki uses the keytab of the seperate "Unprivileged user for TSIG-GSSAPI DNS updates via ISC DHCP server" you have to Check this one not the one which BIND uses. Regards Am 16.05.2018 um 12:45 schrieb Rowland Penny via samba: > On Wed, 16 May 2018 12:32:52 +0200 Stefan Kania via samba > <samba at lists.samba.org> wrote: > >> It's me

On 1/2/2018 1:51 PM, Rowland Penny wrote: > On Tue, 2 Jan 2018 13:38:52 -0500 > lingpanda101 via samba <samba at lists.samba.org> wrote: > > >> A few other observations while attempting to switch. >> >> * I do not have a dns.keytab file. Should I or is created after >> attempting to switch? > See my earlier post about samba_dnsupgrade. >

Dear list, one more problem. I've setup my host running a samba addc controller. Samba version is samba-4.11.6-r2. I've joined two win10 clients to my domain. One client has a static ip, the other one was configured to ask my dhcpd-daemon for an ip. Following the book from stefan kania, I modified my dhcpd.conf to execute some scripts I've found on ArchWiki to add my

It's me again :-) Now we have DDNS with DHCP running but we have a problem on one of our two DCs. Btw we used the setup and the script from wiki. Doing a "dhclient" on a host we are getting the following messages: ------------- Mai 16 12:13:28 samba41 dhcpd[3961]: Commit: IP: 192.168.0.249 DHCID: 1:50:5b:5d:1c:ab:aa Name: horst Mai 16 12:13:28 samba41 dhcpd[3961]: execute_statement

I've set up a lab for testing Samba 4.1 as an RODC emulating a satellite office setup, using the sernet packages on SLES11SP2. ## Problem 1 samba_dnsupdate is failing: ==> /var/log/samba/log.samba <== [2013/11/18 13:22:37.416193, 0] ../lib/util/util_runcmd.c:317(samba_runcmd_io_handler) /usr/sbin/samba_dnsupdate: ; TSIG error with server: tsig verify failure [2013/11/18