Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to add Additional Domain Controller #2071

Closed
lukewowo opened this issue Aug 4, 2021 · 3 comments
Closed

Unable to add Additional Domain Controller #2071

lukewowo opened this issue Aug 4, 2021 · 3 comments
Assignees
Labels
Reason: Invalid Indicates that an issue or pull request is no longer relevant Status: Nothing to do Indicates that work won't continue on an issue or pull request Type: Configuration Mistake Indicates that an issue is caused by a configuration mistake

Comments

@lukewowo
Copy link

lukewowo commented Aug 4, 2021

Installed a new Zentyal 7.0.4 twice, and the same results happen when trying to add an Additional Domain Controller to an existing Zentyal 6.2 domain.

image

@imrelaszlo
Copy link

Maybe this problem is related to my topic: #2051

@thctlo
Copy link

thctlo commented Sep 23, 2021

+1 thats simply wrongly written, making it confusing and prone to errors.

DOMAINNAME should be DNS-DOMAINNAME .. ( the "right" part of the hostname.FQDN )
HOSTNAME should be : SERVER-HOSTNAME .. ( the "left" part of the hostname.FQDN )

NETBIOS-DOMAIN = ADDOM or old school .. NT4DOM ( can be anything, but you can follow this rule. )
internal.domain.tld, then INTERNAL is often used at NETBIOS-DOMAINNAME
NETBIOS-HOSTNAME = SERVER-HOSTNAME

please read this one
https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/naming-conventions-for-computer-domain-site-ou
There are much more restritions then people think, if you want to setup correctly.

@brunolorente
Copy link
Member

Hi @thctlo fixed!

@brunolorente brunolorente self-assigned this May 4, 2022
@brunolorente brunolorente added Reason: Invalid Indicates that an issue or pull request is no longer relevant Type: Configuration Mistake Indicates that an issue is caused by a configuration mistake Status: Nothing to do Indicates that work won't continue on an issue or pull request labels May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Reason: Invalid Indicates that an issue or pull request is no longer relevant Status: Nothing to do Indicates that work won't continue on an issue or pull request Type: Configuration Mistake Indicates that an issue is caused by a configuration mistake
Projects
None yet
Development

No branches or pull requests

4 participants