search for: cwing

...> > host -t SRV _ldap._tcp.pdc._msdcs.mad.mater.int > _ldap._tcp.pdc._msdcs.mad.mater.int has SRV record 0 100 389 bwing.mad.mater.int. > _ldap._tcp.pdc._msdcs.mad.mater.int has SRV record 0 100 389 awing.mad.mater.int. > _ldap._tcp.pdc._msdcs.mad.mater.int has SRV record 0 100 389 cwing.mad.mater.int. > > > What could have happened ? Just curious. There is a bug for this, whilst there is code to create the PDC_Emulators SRV record after the FSMO role is moved, there isn't any code to remove it, so you can end up up like yourself, with a record for every DC the P...

...ool. You posted this: host -t SRV _ldap._tcp.pdc._msdcs.mad.mater.int _ldap._tcp.pdc._msdcs.mad.mater.int has SRV record 0 100 389 bwing.mad.mater.int. _ldap._tcp.pdc._msdcs.mad.mater.int has SRV record 0 100 389 awing.mad.mater.int. _ldap._tcp.pdc._msdcs.mad.mater.int has SRV record 0 100 389 cwing.mad.mater.int. Which clearly shows you have three records for the PDC_Emulator DC and like that FSMO role, there can only be one, the DC that holds the role, you should delete the two incorrect ones. I have two DC's and this is the output from my domain: host -t SRV _ldap._tcp.pdc._msdcs.s...

On 14/04/2023 12:13, Lorenzo Milesi via samba wrote: > >> That all smells quite similar to what I were seeing >> here before, and what someone else were seeing too, >> all with 4.17[.4]. This famouse WERR_FILE_NOT_FOUND >> error too. > > We upgraded one more domain, and in the hope to avoid this error, we remained on 4.16. So we deployed a new 4.16.9 DC, joined,