search for: corporatedatacenter

Displaying 7 results from an estimated 7 matches for "corporatedatacenter".

2020 Apr 29
3
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
On 29/04/2020 10:58, Olaf Dreyer via samba-technical wrote: > > I run a setup with two Samba DC (currently samba 4.12.2 on debian 10 > VMs). I started with a Windows 2003 DC but the last Windows DC has > been removed a few years ago from this setup. this is really the wrong list for this, so i have CC'ed the samba mailing list, please reply there. You say you started with Win
2020 Apr 29
3
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
...,DC=ForestDnsZones,DC=omtn,DC=de > dn: > DC=_ldap._tcp.dc._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de > dn: > DC=_ldap._tcp.b66950c4-e9b8-4bc9-b625-5b7d8a36f903.domains._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de > dn: > DC=_ldap._tcp.CorporateDataCenter._sites.gc._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de > dn: > DC=7abd666f-d3bc-4e8f-9ff3-cf3abd802ee5._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de > dn: > DC=_ldap._tcp.gc._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de >...
2020 Apr 29
2
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
...crosoftDNS,DC=ForestDnsZo > > > nes,DC=omtn,DC=de > > > dn: > > > DC=_ldap._tcp.b66950c4-e9b8-4bc9-b625- > > > 5b7d8a36f903.domains._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestD > > > nsZones,DC=omtn,DC=de > > > dn: > > > DC=_ldap._tcp.CorporateDataCenter._sites.gc._msdcs,DC=omtn.de,CN= > > > MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de > > > dn: > > > DC=7abd666f-d3bc-4e8f-9ff3- > > > cf3abd802ee5._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones, > > > DC=omtn,DC=de > > > dn: > > >...
2020 Apr 29
0
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
...tn,DC=de >> dn: >> DC=_ldap._tcp.dc._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de >> dn: >> DC=_ldap._tcp.b66950c4-e9b8-4bc9-b625-5b7d8a36f903.domains._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de >> dn: >> DC=_ldap._tcp.CorporateDataCenter._sites.gc._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de >> dn: >> DC=7abd666f-d3bc-4e8f-9ff3-cf3abd802ee5._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de >> dn: >> DC=_ldap._tcp.gc._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC...
2020 Apr 29
0
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
...dcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de dn: DC=_ldap._tcp.dc._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de dn: DC=_ldap._tcp.b66950c4-e9b8-4bc9-b625-5b7d8a36f903.domains._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de dn: DC=_ldap._tcp.CorporateDataCenter._sites.gc._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de dn: DC=7abd666f-d3bc-4e8f-9ff3-cf3abd802ee5._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de dn: DC=_ldap._tcp.gc._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de dn: DC=_tcp.CorporateDa...
2020 Apr 30
0
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
...C=ForestDnsZo >>>> nes,DC=omtn,DC=de >>>> dn: >>>> DC=_ldap._tcp.b66950c4-e9b8-4bc9-b625- >>>> 5b7d8a36f903.domains._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestD >>>> nsZones,DC=omtn,DC=de >>>> dn: >>>> DC=_ldap._tcp.CorporateDataCenter._sites.gc._msdcs,DC=omtn.de,CN= >>>> MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de >>>> dn: >>>> DC=7abd666f-d3bc-4e8f-9ff3- >>>> cf3abd802ee5._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones, >>>> DC=omtn,DC=de >>>> dn: >...
2020 Apr 30
2
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
On 30/04/2020 11:44, Olaf Dreyer wrote: > Hi, > > I restored the last backup with the 4.11.6 setup. This is working fine > and i can confirm that my AD is set up with a single forwarding zone, > there is no _msdsc zone. On this 4.11.6 setup also the Windows DNS > Tool does not complain. When upgrading to 4.12.2 DNS administration > fails again with