Unable to join client pc to domain
ERROR: An attempt to resolve the DNS name of a domain controller in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain.
I have just installed a fresh windows server 2012 R2 and installed Active Directory. DNS is not installed in this server. Firewall is OFF. Domain is capita.com
Server IP settings are as follows:
ip address: 192.168.1.2
Subnet Mask: 255.255.255.0
Preferred DNS: 192.168.1.2
I have installed windows 7 Ultimate as client machine and IP settings are as follows:
IP address: 192.168.1.3
Subnet Mask: 255.255.255.0
Preferred DNS: 192.168.1.2
Firewall is OFF
Able to ping from server to client using ip address and from client to server as well. Unable to ping server using domain name (capita.com)
windows
asked Feb 19 at 12:36
Manoj ChoudharyManoj Choudhary
11
|
show 3 more comments
ERROR: An attempt to resolve the DNS name of a domain controller in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain.
I have just installed a fresh windows server 2012 R2 and installed Active Directory. DNS is not installed in this server. Firewall is OFF. Domain is capita.com
Server IP settings are as follows:
ip address: 192.168.1.2
Subnet Mask: 255.255.255.0
Preferred DNS: 192.168.1.2
I have installed windows 7 Ultimate as client machine and IP settings are as follows:
IP address: 192.168.1.3
Subnet Mask: 255.255.255.0
Preferred DNS: 192.168.1.2
Firewall is OFF
Able to ping from server to client using ip address and from client to server as well. Unable to ping server using domain name (capita.com)
windows
asked Feb 19 at 12:36
Manoj ChoudharyManoj Choudhary
11
If your AD server doesn't run DNS... then what device is the 192.168.1.2 DNS server, and have you configured the domain name in it according to MS requirements? What records does your zone file contain?
– grawity
Feb 19 at 12:46
Well, I saw a lot of videos on YouTube where only AD is installed in the server and client pc is added to the domain. 192.168.1.2 is my server 2012 with AD installed. Domain is configured according to MS requirements.
– Manoj Choudhary
Feb 19 at 12:58
But if you didn't install DNS on it, why are you trying to use it as a DNS server from your client? (dcpromo does install DNS by default because AD is very DNS-dependent, some YouTube videos might just forget to mention it.)
– grawity
Feb 19 at 13:10
Are you saying, without dns I will not be able to add the client into domain? I think 🤔 I should be able to.
– Manoj Choudhary
Feb 19 at 13:34
1
Starting when Active Directory was introduced with Windows 2000 a domain client will always use DNS to locate a domain controller, even when they are on the same subnet. Only with the older domain system was DNS optional. DNS does not have to be running on the domain controller but but must somewhere in the network and it must have a specific configuration. By default promoting a server to a domain controller will install a properly configured DNS server. Otherwise some manual configuration on the server will be necessary.
– LMiller7
Feb 19 at 15:45
|
show 3 more comments
ERROR: An attempt to resolve the DNS name of a domain controller in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain.
I have just installed a fresh windows server 2012 R2 and installed Active Directory. DNS is not installed in this server. Firewall is OFF. Domain is capita.com
Server IP settings are as follows:
ip address: 192.168.1.2
Subnet Mask: 255.255.255.0
Preferred DNS: 192.168.1.2
I have installed windows 7 Ultimate as client machine and IP settings are as follows:
IP address: 192.168.1.3
Subnet Mask: 255.255.255.0
Preferred DNS: 192.168.1.2
Firewall is OFF
Able to ping from server to client using ip address and from client to server as well. Unable to ping server using domain name (capita.com)
windows
asked Feb 19 at 12:36
Manoj ChoudharyManoj Choudhary
11
ERROR: An attempt to resolve the DNS name of a domain controller in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain.
I have just installed a fresh windows server 2012 R2 and installed Active Directory. DNS is not installed in this server. Firewall is OFF. Domain is capita.com
Server IP settings are as follows:
ip address: 192.168.1.2
Subnet Mask: 255.255.255.0
Preferred DNS: 192.168.1.2
I have installed windows 7 Ultimate as client machine and IP settings are as follows:
IP address: 192.168.1.3
Subnet Mask: 255.255.255.0
Preferred DNS: 192.168.1.2
Firewall is OFF
Able to ping from server to client using ip address and from client to server as well. Unable to ping server using domain name (capita.com)
windows
windows
asked Feb 19 at 12:36
Manoj ChoudharyManoj Choudhary
11
asked Feb 19 at 12:36
Manoj ChoudharyManoj Choudhary
11
asked Feb 19 at 12:36
Manoj ChoudharyManoj Choudhary
11
asked Feb 19 at 12:36
Manoj ChoudharyManoj Choudhary
11
asked Feb 19 at 12:36
Manoj ChoudharyManoj Choudhary
11
11
If your AD server doesn't run DNS... then what device is the 192.168.1.2 DNS server, and have you configured the domain name in it according to MS requirements? What records does your zone file contain?
– grawity
Feb 19 at 12:46
Well, I saw a lot of videos on YouTube where only AD is installed in the server and client pc is added to the domain. 192.168.1.2 is my server 2012 with AD installed. Domain is configured according to MS requirements.
– Manoj Choudhary
Feb 19 at 12:58
But if you didn't install DNS on it, why are you trying to use it as a DNS server from your client? (dcpromo does install DNS by default because AD is very DNS-dependent, some YouTube videos might just forget to mention it.)
– grawity
Feb 19 at 13:10
Are you saying, without dns I will not be able to add the client into domain? I think 🤔 I should be able to.
– Manoj Choudhary
Feb 19 at 13:34
1
Starting when Active Directory was introduced with Windows 2000 a domain client will always use DNS to locate a domain controller, even when they are on the same subnet. Only with the older domain system was DNS optional. DNS does not have to be running on the domain controller but but must somewhere in the network and it must have a specific configuration. By default promoting a server to a domain controller will install a properly configured DNS server. Otherwise some manual configuration on the server will be necessary.
– LMiller7
Feb 19 at 15:45
|
show 3 more comments
If your AD server doesn't run DNS... then what device is the 192.168.1.2 DNS server, and have you configured the domain name in it according to MS requirements? What records does your zone file contain?
– grawity
Feb 19 at 12:46
Well, I saw a lot of videos on YouTube where only AD is installed in the server and client pc is added to the domain. 192.168.1.2 is my server 2012 with AD installed. Domain is configured according to MS requirements.
– Manoj Choudhary
Feb 19 at 12:58
But if you didn't install DNS on it, why are you trying to use it as a DNS server from your client? (dcpromo does install DNS by default because AD is very DNS-dependent, some YouTube videos might just forget to mention it.)
– grawity
Feb 19 at 13:10
Are you saying, without dns I will not be able to add the client into domain? I think 🤔 I should be able to.
– Manoj Choudhary
Feb 19 at 13:34
1
Starting when Active Directory was introduced with Windows 2000 a domain client will always use DNS to locate a domain controller, even when they are on the same subnet. Only with the older domain system was DNS optional. DNS does not have to be running on the domain controller but but must somewhere in the network and it must have a specific configuration. By default promoting a server to a domain controller will install a properly configured DNS server. Otherwise some manual configuration on the server will be necessary.
– LMiller7
Feb 19 at 15:45
If your AD server doesn't run DNS... then what device is the 192.168.1.2 DNS server, and have you configured the domain name in it according to MS requirements? What records does your zone file contain?
– grawity
Feb 19 at 12:46
If your AD server doesn't run DNS... then what device is the 192.168.1.2 DNS server, and have you configured the domain name in it according to MS requirements? What records does your zone file contain?
– grawity
Feb 19 at 12:46
Well, I saw a lot of videos on YouTube where only AD is installed in the server and client pc is added to the domain. 192.168.1.2 is my server 2012 with AD installed. Domain is configured according to MS requirements.
– Manoj Choudhary
Feb 19 at 12:58
Well, I saw a lot of videos on YouTube where only AD is installed in the server and client pc is added to the domain. 192.168.1.2 is my server 2012 with AD installed. Domain is configured according to MS requirements.
– Manoj Choudhary
Feb 19 at 12:58
But if you didn't install DNS on it, why are you trying to use it as a DNS server from your client? (dcpromo does install DNS by default because AD is very DNS-dependent, some YouTube videos might just forget to mention it.)
– grawity
Feb 19 at 13:10
But if you didn't install DNS on it, why are you trying to use it as a DNS server from your client? (dcpromo does install DNS by default because AD is very DNS-dependent, some YouTube videos might just forget to mention it.)
– grawity
Feb 19 at 13:10
Are you saying, without dns I will not be able to add the client into domain? I think 🤔 I should be able to.
– Manoj Choudhary
Feb 19 at 13:34
Are you saying, without dns I will not be able to add the client into domain? I think 🤔 I should be able to.
– Manoj Choudhary
Feb 19 at 13:34
1
1
Starting when Active Directory was introduced with Windows 2000 a domain client will always use DNS to locate a domain controller, even when they are on the same subnet. Only with the older domain system was DNS optional. DNS does not have to be running on the domain controller but but must somewhere in the network and it must have a specific configuration. By default promoting a server to a domain controller will install a properly configured DNS server. Otherwise some manual configuration on the server will be necessary.
– LMiller7
Feb 19 at 15:45
Starting when Active Directory was introduced with Windows 2000 a domain client will always use DNS to locate a domain controller, even when they are on the same subnet. Only with the older domain system was DNS optional. DNS does not have to be running on the domain controller but but must somewhere in the network and it must have a specific configuration. By default promoting a server to a domain controller will install a properly configured DNS server. Otherwise some manual configuration on the server will be necessary.
– LMiller7
Feb 19 at 15:45
|
show 3 more comments
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%2f1407424%2funable-to-join-client-pc-to-domain%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%2f1407424%2funable-to-join-client-pc-to-domain%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
If your AD server doesn't run DNS... then what device is the 192.168.1.2 DNS server, and have you configured the domain name in it according to MS requirements? What records does your zone file contain?
– grawity
Feb 19 at 12:46
Well, I saw a lot of videos on YouTube where only AD is installed in the server and client pc is added to the domain. 192.168.1.2 is my server 2012 with AD installed. Domain is configured according to MS requirements.
– Manoj Choudhary
Feb 19 at 12:58
But if you didn't install DNS on it, why are you trying to use it as a DNS server from your client? (dcpromo does install DNS by default because AD is very DNS-dependent, some YouTube videos might just forget to mention it.)
– grawity
Feb 19 at 13:10
Are you saying, without dns I will not be able to add the client into domain? I think 🤔 I should be able to.
– Manoj Choudhary
Feb 19 at 13:34
1
Starting when Active Directory was introduced with Windows 2000 a domain client will always use DNS to locate a domain controller, even when they are on the same subnet. Only with the older domain system was DNS optional. DNS does not have to be running on the domain controller but but must somewhere in the network and it must have a specific configuration. By default promoting a server to a domain controller will install a properly configured DNS server. Otherwise some manual configuration on the server will be necessary.
– LMiller7
Feb 19 at 15:45