Join Computer to Domain in Windows
I'm a little confused, I've been playing around with a home lab, and I am looking to add a laptop to the domain that I have created for test purposes.
I have been reading some articles, and some of the just tell you to add the Device to the Domain, and others tell me to first change the adapter settings to point to the DNS server, then add the domain.
I am just trying to understand why there are differences?
Does it depend on the setup?
Regards.
windows windows-10 dns domain windows-server-2016
add a comment |
I'm a little confused, I've been playing around with a home lab, and I am looking to add a laptop to the domain that I have created for test purposes.
I have been reading some articles, and some of the just tell you to add the Device to the Domain, and others tell me to first change the adapter settings to point to the DNS server, then add the domain.
I am just trying to understand why there are differences?
Does it depend on the setup?
Regards.
windows windows-10 dns domain windows-server-2016
What's provoking the question? What happens when you try it? Is it not working? Do you get an error message?
– Bill_Stewart
Feb 4 at 15:54
1
Windows Domain join is heavily reliant on DNS. If you aren't using your Windows Server to also do DHCP (and provide DNS) then your clients won't get the correct DNS server to allow the domain join to find your DC - thus you'll receive an error that the domain join couldn't find a DC. OR, you would need to manually configure your clients to use the DC as their primary DNS server, and then do the domain join. Been there, done that.
– Kinnectus
Feb 4 at 15:56
Thank you very much, that is a good explanation. I will have to manually configure the DNS, because I am still using my router as my primary DHCP.
– jimbob
Feb 4 at 16:13
If I wanted the server as the primary DHCP, would I have to disable DHCP on router in order to stop confusion?
– jimbob
Feb 4 at 16:26
add a comment |
I'm a little confused, I've been playing around with a home lab, and I am looking to add a laptop to the domain that I have created for test purposes.
I have been reading some articles, and some of the just tell you to add the Device to the Domain, and others tell me to first change the adapter settings to point to the DNS server, then add the domain.
I am just trying to understand why there are differences?
Does it depend on the setup?
Regards.
windows windows-10 dns domain windows-server-2016
I'm a little confused, I've been playing around with a home lab, and I am looking to add a laptop to the domain that I have created for test purposes.
I have been reading some articles, and some of the just tell you to add the Device to the Domain, and others tell me to first change the adapter settings to point to the DNS server, then add the domain.
I am just trying to understand why there are differences?
Does it depend on the setup?
Regards.
windows windows-10 dns domain windows-server-2016
windows windows-10 dns domain windows-server-2016
asked Feb 4 at 15:51
jimbobjimbob
228
228
What's provoking the question? What happens when you try it? Is it not working? Do you get an error message?
– Bill_Stewart
Feb 4 at 15:54
1
Windows Domain join is heavily reliant on DNS. If you aren't using your Windows Server to also do DHCP (and provide DNS) then your clients won't get the correct DNS server to allow the domain join to find your DC - thus you'll receive an error that the domain join couldn't find a DC. OR, you would need to manually configure your clients to use the DC as their primary DNS server, and then do the domain join. Been there, done that.
– Kinnectus
Feb 4 at 15:56
Thank you very much, that is a good explanation. I will have to manually configure the DNS, because I am still using my router as my primary DHCP.
– jimbob
Feb 4 at 16:13
If I wanted the server as the primary DHCP, would I have to disable DHCP on router in order to stop confusion?
– jimbob
Feb 4 at 16:26
add a comment |
What's provoking the question? What happens when you try it? Is it not working? Do you get an error message?
– Bill_Stewart
Feb 4 at 15:54
1
Windows Domain join is heavily reliant on DNS. If you aren't using your Windows Server to also do DHCP (and provide DNS) then your clients won't get the correct DNS server to allow the domain join to find your DC - thus you'll receive an error that the domain join couldn't find a DC. OR, you would need to manually configure your clients to use the DC as their primary DNS server, and then do the domain join. Been there, done that.
– Kinnectus
Feb 4 at 15:56
Thank you very much, that is a good explanation. I will have to manually configure the DNS, because I am still using my router as my primary DHCP.
– jimbob
Feb 4 at 16:13
If I wanted the server as the primary DHCP, would I have to disable DHCP on router in order to stop confusion?
– jimbob
Feb 4 at 16:26
What's provoking the question? What happens when you try it? Is it not working? Do you get an error message?
– Bill_Stewart
Feb 4 at 15:54
What's provoking the question? What happens when you try it? Is it not working? Do you get an error message?
– Bill_Stewart
Feb 4 at 15:54
1
1
Windows Domain join is heavily reliant on DNS. If you aren't using your Windows Server to also do DHCP (and provide DNS) then your clients won't get the correct DNS server to allow the domain join to find your DC - thus you'll receive an error that the domain join couldn't find a DC. OR, you would need to manually configure your clients to use the DC as their primary DNS server, and then do the domain join. Been there, done that.
– Kinnectus
Feb 4 at 15:56
Windows Domain join is heavily reliant on DNS. If you aren't using your Windows Server to also do DHCP (and provide DNS) then your clients won't get the correct DNS server to allow the domain join to find your DC - thus you'll receive an error that the domain join couldn't find a DC. OR, you would need to manually configure your clients to use the DC as their primary DNS server, and then do the domain join. Been there, done that.
– Kinnectus
Feb 4 at 15:56
Thank you very much, that is a good explanation. I will have to manually configure the DNS, because I am still using my router as my primary DHCP.
– jimbob
Feb 4 at 16:13
Thank you very much, that is a good explanation. I will have to manually configure the DNS, because I am still using my router as my primary DHCP.
– jimbob
Feb 4 at 16:13
If I wanted the server as the primary DHCP, would I have to disable DHCP on router in order to stop confusion?
– jimbob
Feb 4 at 16:26
If I wanted the server as the primary DHCP, would I have to disable DHCP on router in order to stop confusion?
– jimbob
Feb 4 at 16:26
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1401905%2fjoin-computer-to-domain-in-windows%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1401905%2fjoin-computer-to-domain-in-windows%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What's provoking the question? What happens when you try it? Is it not working? Do you get an error message?
– Bill_Stewart
Feb 4 at 15:54
1
Windows Domain join is heavily reliant on DNS. If you aren't using your Windows Server to also do DHCP (and provide DNS) then your clients won't get the correct DNS server to allow the domain join to find your DC - thus you'll receive an error that the domain join couldn't find a DC. OR, you would need to manually configure your clients to use the DC as their primary DNS server, and then do the domain join. Been there, done that.
– Kinnectus
Feb 4 at 15:56
Thank you very much, that is a good explanation. I will have to manually configure the DNS, because I am still using my router as my primary DHCP.
– jimbob
Feb 4 at 16:13
If I wanted the server as the primary DHCP, would I have to disable DHCP on router in order to stop confusion?
– jimbob
Feb 4 at 16:26