similar to: dns_tkey_negotiategss: TKEY is unacceptable

Hello! Output of command # 1 record dn: CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=MYDOMAIN cn: {31B2F340-016D-11D2-945F-00C04FB984F9} name: {31B2F340-016D-11D2-945F-00C04FB984F9} Referral # ref: ldap: //interno.mastersonda.com.br/CN=Configuration,DC=MYDOMAIN Referral # ref: ldap: //interno.mastersonda.com.br/DC=DomainDnsZones,DC=MYDOMAIN Referral # ref: ldap:

Hi, I try to switch from internal DNS to bind9 on an samba-ad-dc (sernet 4.1.23 on debian wheezy). I try to run samba_upgradedns --dns-backend=BIND9_DLZ and get an python error pointing to /usr/lib/python2.7/dist-packages/samba/provision/__init__.py line 271 Reading domain information Traceback (most recent call last): File "/usr/sbin/samba_upgradedns", line 261, in

On 30/12/15 18:19, Carlos A. P. Cunha wrote: > Hello! > I've got this error > dns_tkey_negotiategss: TKEY is unacceptable > > when running samba_dnsupdate --verbose > > With this error dynamic entries stopped working as Type A machines > that entered in the field or entry to a new DC. > > Already tried the step described here > >

On 30/12/15 18:19, Carlos A. P. Cunha wrote: > Hello! > I've got this error > dns_tkey_negotiategss: TKEY is unacceptable > > when running samba_dnsupdate --verbose > > With this error dynamic entries stopped working as Type A machines > that entered in the field or entry to a new DC. > > Already tried the step described here > >

Hello! Yes already tried this, both he always says that the account already exists even if it does not exist, it affects only dicamicas entries, entries staticas work and replication as well, but as dynamic are troubled by instances in Multiple Sites will have problems ... But some log or command that can help? Thanks Em 30-12-2015 18:38, Rowland penny escreveu: > On 30/12/15 19:57,

On 13/11/15 07:00, Achim Gottinger wrote: > > > Am 13.11.2015 um 07:11 schrieb Achim Gottinger: >> Hi, >> >> I try to switch from internal DNS to bind9 on an samba-ad-dc (sernet >> 4.1.23 on debian wheezy). >> I try to run >> >> samba_upgradedns --dns-backend=BIND9_DLZ >> >> and get an python error pointing to >>

On 18.07.2016 01:52, Achim Gottinger wrote: > > > Am 18.07.2016 um 01:02 schrieb Norbert Hanke: >> Hello, >> >> I'm trying to join a samba 4 DC to an already existing samba 4 DC, >> both with BIND9_DLZ. Samba is at version 4.4.5, bind is version >> 9.10.4-P1, all brand new. >> >> The existing DC runs fine, but the added DC refuses to update

Hello, I'm trying to join a samba 4 DC to an already existing samba 4 DC, both with BIND9_DLZ. Samba is at version 4.4.5, bind is version 9.10.4-P1, all brand new. The existing DC runs fine, but the added DC refuses to update its local bind database: every attempt to update the local DNS results in "update failed: NOTAUTH". AD replication works perfectly. Both systems are set

On 18.07.2016 22:48, Achim Gottinger wrote: > > > Am 18.07.2016 um 11:45 schrieb Norbert Hanke: >> On 18.07.2016 01:52, Achim Gottinger wrote: >>> >>> >>> Am 18.07.2016 um 01:02 schrieb Norbert Hanke: >>>> Hello, >>>> >>>> I'm trying to join a samba 4 DC to an already existing samba 4 DC, >>>> both with

Hello, we have the following problem with a ADDC Sernet 4.7.6-11 on CentOS 7.4. We have two DCs, replication is working fine. We use bind9 as dns-backend. When we do a "samba_dnsupdate --all-names" we get the following messages: ------------------- [root at dc1 ~]# samba_dnsupdate --all-names dns_tkey_negotiategss: TKEY is unacceptable dns_tkey_negotiategss: TKEY is unacceptable

James, I configured the account lockout policies by RSAT, GPEDIT.MSC. By GPEDIT.MSC I set the value = 10 attempts. Through the samba-tool, I used this command: # samba-tool domain passwordsettings set --account-lockout-threshold=11 INFO: Current debug levels: ... pm_process() returned Yes Module 'tombstone_reanimate' is disabled. Skip registration.lpcfg_servicenumber:

Hello, I am trying to change over from bind9 to internal dns. For some reason I keep getting the following error: Error parsing DNS data from '/opt/samba/private/dns/TH01.INET.zone' () I have inspected TH01.INET.ZONE but I could not find an error. I do not understand this error message. I am hoping someone could help me with this issue please. Your help will be very much appreciated.

Dear James, Thanks for the input. Even increasing from 5 to 10, the amount of times to miss the password and lock the account (after changing, I wheeled a gpupdate / force), if you miss 3 times the account is locked. I changed smb.conf log level to 9. I tried to unlock the account using the samba-tool command line, but without success, because I can only unlock using the RSAT. I get these

On 18.07.2016 20:10, Rowland penny wrote: > On 18/07/16 00:02, Norbert Hanke wrote: >> Hello, >> >> I'm trying to join a samba 4 DC to an already existing samba 4 DC, >> both with BIND9_DLZ. Samba is at version 4.4.5, bind is version >> 9.10.4-P1, all brand new. >> >> The existing DC runs fine, but the added DC refuses to update its >>

Am 13.11.2015 um 07:11 schrieb Achim Gottinger: > Hi, > > I try to switch from internal DNS to bind9 on an samba-ad-dc (sernet > 4.1.23 on debian wheezy). > I try to run > > samba_upgradedns --dns-backend=BIND9_DLZ > > and get an python error pointing to > /usr/lib/python2.7/dist-packages/samba/provision/__init__.py line 271 > > Reading domain information >

On 13/11/15 10:20, mourik jan heupink wrote: > Hi Rowland, Achim, list, > >> The search would probably be better something like this: >> >> res7 = >> samdb.search(expression="(name={31B2F340-016D-11D2-945F-00C04FB984F9})", >> base="CN=Policies,CN=System," + basedn, >>

On 30/12/15 19:57, Carlos A. P. Cunha wrote: > Hello! > Output of command > > # 1 record > dn: > CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=MYDOMAIN > cn: {31B2F340-016D-11D2-945F-00C04FB984F9} > name: {31B2F340-016D-11D2-945F-00C04FB984F9} > > Referral # > ref: ldap: //interno.mastersonda.com.br/CN=Configuration,DC=MYDOMAIN > Referral #

Hello Samba-ers, I tried to continue my Samba setup after a long pause doing other stuff. To recall, I want to run two Samba DCs for one domain as virtual machines on two Windows systems (I switched from VirtualBox to Hyper V, which helps to run them automatically at system startup, but I don´t think that really matters). Both DCs shall use themselves as DNS server as the VPN in between is

On 13/11/15 12:45, Achim Gottinger wrote: > > > Am 13.11.2015 um 11:30 schrieb Rowland Penny: >> On 13/11/15 10:20, mourik jan heupink wrote: >>> Hi Rowland, Achim, list, >>> >>>> The search would probably be better something like this: >>>> >>>> res7 = >>>>

Hi at all, i´am using samba 4.3.4 as "ad", "migrated by classicupgrade" some time ago from an nt4-domain. By trying samba_upgradedns --dns-backend=BIND9_DLZ i get the following error: Traceback (most recent call last): File "/usr/sbin/samba_upgradedns", line 262, in <module> paths, lp.configfile, lp) File