Active Directory domain in home network - how to add computer
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I had used AD domain before, but the domain was set up already, so I do not have much hands-on experience with setting up everything from scratch, and I am still new to networking side of things, so please bear with me.
Now, I am trying to play the system at home, where I can have the liberty of trying things without worrying about breaking things, but with limited hardware resources.
I have now set up a 2008R2 domain controller with DNS + dhcp. I then tried to join a windows 7 PC to the domain - it failed. I wonder if anyone can shed some light on my set up...
----- here is my set up ------
I have 1 PCs at home, home1. I have set it to use static ID addresses, 192.168.1.15. This is the host computer on which I installed a guest VM - 2008 R2.
Router config:
Router IP: 192.168.1.1
Subnet Mask: 255.255.**248**.0 (will use 192.168.2 network for the AD domain)
DHCP: I did not disable DHCP, but set its IP range to 192.168.1.2 ~ 99, i.e. only dish out IP addresses to network 192.168.1.
I then created a 2008 R2 VM, win-DC.
ID & basic settings
Static ID: 192.168.2.99
subnet mask: 255.255.**252**.0
Default gateway: 192.168.1.1
Preferred DNS server: 127.0.0.1
Alternate DNS servr: 208.67.222.222 (open dns)
Computer name: win-dc
primary DNS suffix of this computer: home.internal
((so after reboot, full computer name is win-dc.home.internal))
DNS settings:
I added DNS role as part of dcpromo. The A record of the server in the forward lookup zone (home.internal) is added, and the reverse one (PTR) record is created. I cannot upload image, but basically in the left pane under reverse lookup zones, I have: 2.168.192-in-addr-arpa. In the left pane, I have 192.168.2.99, a PTR type, point to "win-dc.home.internal."
Added dhcp role. DHCP settings:
A very basic one: ip range : 192.168.2.101 ~ 150
I then created a OU, named PCGroup. Another OU, named AdminStaff.
After all these, I try to connect a windows 7 x64 (client1) to the domain:
I added WDS on this server, so that I can use WDSUtil to add this device using mac address.
Boot up the client1.
Changed it from WORKGROUP to domain "home.internal"
I then got an error: the dns servers used by this computer for name resolution are not responding. This computer is configured to use dns servers with the following ip address: (none)
So I manually configured it to use the above server (ip) as the DNS server, 192.168.2.99.
Tried to join again. Same error, but this time it mentioned the IP addr of my win-dc server.
Note that the client1 is plugged in the router using ethernet cable, not over wifi.
I did notice that it got an IP of 169.234.199.183. It must be getting this IP from the router DHCP . -- I've seen people trying AD domain in home network saying that they disabled DHCP completely. But is this related? Do I must disable DHCP in the router? How can I make client1 join to the AD domain and use DHCP on the server?
Presumably the 1st blocking hurdle is that client1 cannot resolve the server name from ip. But where did I got it wrong?
I have run nslookup on the server:
nslookup
server win-dc
set querytype=NS
.
It seems all right: name is resolved to win-dc.home.internal, IP is 192.168.2.99. When running set querytype=NS followed by '.', I got the list of non-authoritiative answer from name server f.root-servers.net to c.root-servers.net, and ip addresses of them in the reverse resolution.
dns home-networking active-directory windows-domain
asked Sep 16 '13 at 20:59
user2654478user2654478
243
|
show 2 more comments
I had used AD domain before, but the domain was set up already, so I do not have much hands-on experience with setting up everything from scratch, and I am still new to networking side of things, so please bear with me.
Now, I am trying to play the system at home, where I can have the liberty of trying things without worrying about breaking things, but with limited hardware resources.
I have now set up a 2008R2 domain controller with DNS + dhcp. I then tried to join a windows 7 PC to the domain - it failed. I wonder if anyone can shed some light on my set up...
----- here is my set up ------
I have 1 PCs at home, home1. I have set it to use static ID addresses, 192.168.1.15. This is the host computer on which I installed a guest VM - 2008 R2.
Router config:
Router IP: 192.168.1.1
Subnet Mask: 255.255.**248**.0 (will use 192.168.2 network for the AD domain)
DHCP: I did not disable DHCP, but set its IP range to 192.168.1.2 ~ 99, i.e. only dish out IP addresses to network 192.168.1.
I then created a 2008 R2 VM, win-DC.
ID & basic settings
Static ID: 192.168.2.99
subnet mask: 255.255.**252**.0
Default gateway: 192.168.1.1
Preferred DNS server: 127.0.0.1
Alternate DNS servr: 208.67.222.222 (open dns)
Computer name: win-dc
primary DNS suffix of this computer: home.internal
((so after reboot, full computer name is win-dc.home.internal))
DNS settings:
I added DNS role as part of dcpromo. The A record of the server in the forward lookup zone (home.internal) is added, and the reverse one (PTR) record is created. I cannot upload image, but basically in the left pane under reverse lookup zones, I have: 2.168.192-in-addr-arpa. In the left pane, I have 192.168.2.99, a PTR type, point to "win-dc.home.internal."
Added dhcp role. DHCP settings:
A very basic one: ip range : 192.168.2.101 ~ 150
I then created a OU, named PCGroup. Another OU, named AdminStaff.
After all these, I try to connect a windows 7 x64 (client1) to the domain:
I added WDS on this server, so that I can use WDSUtil to add this device using mac address.
Boot up the client1.
Changed it from WORKGROUP to domain "home.internal"
I then got an error: the dns servers used by this computer for name resolution are not responding. This computer is configured to use dns servers with the following ip address: (none)
So I manually configured it to use the above server (ip) as the DNS server, 192.168.2.99.
Tried to join again. Same error, but this time it mentioned the IP addr of my win-dc server.
Note that the client1 is plugged in the router using ethernet cable, not over wifi.
I did notice that it got an IP of 169.234.199.183. It must be getting this IP from the router DHCP . -- I've seen people trying AD domain in home network saying that they disabled DHCP completely. But is this related? Do I must disable DHCP in the router? How can I make client1 join to the AD domain and use DHCP on the server?
Presumably the 1st blocking hurdle is that client1 cannot resolve the server name from ip. But where did I got it wrong?
I have run nslookup on the server:
nslookup
server win-dc
set querytype=NS
.
It seems all right: name is resolved to win-dc.home.internal, IP is 192.168.2.99. When running set querytype=NS followed by '.', I got the list of non-authoritiative answer from name server f.root-servers.net to c.root-servers.net, and ip addresses of them in the reverse resolution.
dns home-networking active-directory windows-domain
asked Sep 16 '13 at 20:59
user2654478user2654478
243
You need to install the DHCP role on your DC as it will assign an IP address from an address pool to a connecting device. Can you ping the server successfully?
– Yass
Sep 16 '13 at 21:08
@yassarikhan786 I did install DHCP role, and made it to dish out 192.168.2.101-150. I only tried ping on the server, since I cannot get client1 to connect to the domain. ping to the win-dc or to its ip all OK. Correct what I just said: I just ping the server from the host PC, worked , too
– user2654478
Sep 16 '13 at 21:12
If you have the DHCP role installed you need to disable your routers DHCP service.
– Yass
Sep 16 '13 at 21:15
@yassarikhan786 OK. I will try just that. thanks for looking into my post.
– user2654478
Sep 16 '13 at 21:16
No problem, glad I could help.
– Yass
Sep 16 '13 at 21:18
|
show 2 more comments
I had used AD domain before, but the domain was set up already, so I do not have much hands-on experience with setting up everything from scratch, and I am still new to networking side of things, so please bear with me.
Now, I am trying to play the system at home, where I can have the liberty of trying things without worrying about breaking things, but with limited hardware resources.
I have now set up a 2008R2 domain controller with DNS + dhcp. I then tried to join a windows 7 PC to the domain - it failed. I wonder if anyone can shed some light on my set up...
----- here is my set up ------
I have 1 PCs at home, home1. I have set it to use static ID addresses, 192.168.1.15. This is the host computer on which I installed a guest VM - 2008 R2.
Router config:
Router IP: 192.168.1.1
Subnet Mask: 255.255.**248**.0 (will use 192.168.2 network for the AD domain)
DHCP: I did not disable DHCP, but set its IP range to 192.168.1.2 ~ 99, i.e. only dish out IP addresses to network 192.168.1.
I then created a 2008 R2 VM, win-DC.
ID & basic settings
Static ID: 192.168.2.99
subnet mask: 255.255.**252**.0
Default gateway: 192.168.1.1
Preferred DNS server: 127.0.0.1
Alternate DNS servr: 208.67.222.222 (open dns)
Computer name: win-dc
primary DNS suffix of this computer: home.internal
((so after reboot, full computer name is win-dc.home.internal))
DNS settings:
I added DNS role as part of dcpromo. The A record of the server in the forward lookup zone (home.internal) is added, and the reverse one (PTR) record is created. I cannot upload image, but basically in the left pane under reverse lookup zones, I have: 2.168.192-in-addr-arpa. In the left pane, I have 192.168.2.99, a PTR type, point to "win-dc.home.internal."
Added dhcp role. DHCP settings:
A very basic one: ip range : 192.168.2.101 ~ 150
I then created a OU, named PCGroup. Another OU, named AdminStaff.
After all these, I try to connect a windows 7 x64 (client1) to the domain:
I added WDS on this server, so that I can use WDSUtil to add this device using mac address.
Boot up the client1.
Changed it from WORKGROUP to domain "home.internal"
I then got an error: the dns servers used by this computer for name resolution are not responding. This computer is configured to use dns servers with the following ip address: (none)
So I manually configured it to use the above server (ip) as the DNS server, 192.168.2.99.
Tried to join again. Same error, but this time it mentioned the IP addr of my win-dc server.
Note that the client1 is plugged in the router using ethernet cable, not over wifi.
I did notice that it got an IP of 169.234.199.183. It must be getting this IP from the router DHCP . -- I've seen people trying AD domain in home network saying that they disabled DHCP completely. But is this related? Do I must disable DHCP in the router? How can I make client1 join to the AD domain and use DHCP on the server?
Presumably the 1st blocking hurdle is that client1 cannot resolve the server name from ip. But where did I got it wrong?
I have run nslookup on the server:
nslookup
server win-dc
set querytype=NS
.
It seems all right: name is resolved to win-dc.home.internal, IP is 192.168.2.99. When running set querytype=NS followed by '.', I got the list of non-authoritiative answer from name server f.root-servers.net to c.root-servers.net, and ip addresses of them in the reverse resolution.
dns home-networking active-directory windows-domain
asked Sep 16 '13 at 20:59
user2654478user2654478
243
I had used AD domain before, but the domain was set up already, so I do not have much hands-on experience with setting up everything from scratch, and I am still new to networking side of things, so please bear with me.
Now, I am trying to play the system at home, where I can have the liberty of trying things without worrying about breaking things, but with limited hardware resources.
I have now set up a 2008R2 domain controller with DNS + dhcp. I then tried to join a windows 7 PC to the domain - it failed. I wonder if anyone can shed some light on my set up...
----- here is my set up ------
I have 1 PCs at home, home1. I have set it to use static ID addresses, 192.168.1.15. This is the host computer on which I installed a guest VM - 2008 R2.
Router config:
Router IP: 192.168.1.1
Subnet Mask: 255.255.**248**.0 (will use 192.168.2 network for the AD domain)
DHCP: I did not disable DHCP, but set its IP range to 192.168.1.2 ~ 99, i.e. only dish out IP addresses to network 192.168.1.
I then created a 2008 R2 VM, win-DC.
ID & basic settings
Static ID: 192.168.2.99
subnet mask: 255.255.**252**.0
Default gateway: 192.168.1.1
Preferred DNS server: 127.0.0.1
Alternate DNS servr: 208.67.222.222 (open dns)
Computer name: win-dc
primary DNS suffix of this computer: home.internal
((so after reboot, full computer name is win-dc.home.internal))
DNS settings:
I added DNS role as part of dcpromo. The A record of the server in the forward lookup zone (home.internal) is added, and the reverse one (PTR) record is created. I cannot upload image, but basically in the left pane under reverse lookup zones, I have: 2.168.192-in-addr-arpa. In the left pane, I have 192.168.2.99, a PTR type, point to "win-dc.home.internal."
Added dhcp role. DHCP settings:
A very basic one: ip range : 192.168.2.101 ~ 150
I then created a OU, named PCGroup. Another OU, named AdminStaff.
After all these, I try to connect a windows 7 x64 (client1) to the domain:
I added WDS on this server, so that I can use WDSUtil to add this device using mac address.
Boot up the client1.
Changed it from WORKGROUP to domain "home.internal"
I then got an error: the dns servers used by this computer for name resolution are not responding. This computer is configured to use dns servers with the following ip address: (none)
So I manually configured it to use the above server (ip) as the DNS server, 192.168.2.99.
Tried to join again. Same error, but this time it mentioned the IP addr of my win-dc server.
Note that the client1 is plugged in the router using ethernet cable, not over wifi.
I did notice that it got an IP of 169.234.199.183. It must be getting this IP from the router DHCP . -- I've seen people trying AD domain in home network saying that they disabled DHCP completely. But is this related? Do I must disable DHCP in the router? How can I make client1 join to the AD domain and use DHCP on the server?
Presumably the 1st blocking hurdle is that client1 cannot resolve the server name from ip. But where did I got it wrong?
I have run nslookup on the server:
nslookup
server win-dc
set querytype=NS
.
It seems all right: name is resolved to win-dc.home.internal, IP is 192.168.2.99. When running set querytype=NS followed by '.', I got the list of non-authoritiative answer from name server f.root-servers.net to c.root-servers.net, and ip addresses of them in the reverse resolution.
dns home-networking active-directory windows-domain
dns home-networking active-directory windows-domain
asked Sep 16 '13 at 20:59
user2654478user2654478
243
asked Sep 16 '13 at 20:59
user2654478user2654478
243
edited Sep 16 '13 at 21:15
user2654478
asked Sep 16 '13 at 20:59
user2654478user2654478
243
asked Sep 16 '13 at 20:59
user2654478user2654478
243
asked Sep 16 '13 at 20:59
user2654478user2654478
243
243
You need to install the DHCP role on your DC as it will assign an IP address from an address pool to a connecting device. Can you ping the server successfully?
– Yass
Sep 16 '13 at 21:08
@yassarikhan786 I did install DHCP role, and made it to dish out 192.168.2.101-150. I only tried ping on the server, since I cannot get client1 to connect to the domain. ping to the win-dc or to its ip all OK. Correct what I just said: I just ping the server from the host PC, worked , too
– user2654478
Sep 16 '13 at 21:12
If you have the DHCP role installed you need to disable your routers DHCP service.
– Yass
Sep 16 '13 at 21:15
@yassarikhan786 OK. I will try just that. thanks for looking into my post.
– user2654478
Sep 16 '13 at 21:16
No problem, glad I could help.
– Yass
Sep 16 '13 at 21:18
|
show 2 more comments
You need to install the DHCP role on your DC as it will assign an IP address from an address pool to a connecting device. Can you ping the server successfully?
– Yass
Sep 16 '13 at 21:08
@yassarikhan786 I did install DHCP role, and made it to dish out 192.168.2.101-150. I only tried ping on the server, since I cannot get client1 to connect to the domain. ping to the win-dc or to its ip all OK. Correct what I just said: I just ping the server from the host PC, worked , too
– user2654478
Sep 16 '13 at 21:12
If you have the DHCP role installed you need to disable your routers DHCP service.
– Yass
Sep 16 '13 at 21:15
@yassarikhan786 OK. I will try just that. thanks for looking into my post.
– user2654478
Sep 16 '13 at 21:16
No problem, glad I could help.
– Yass
Sep 16 '13 at 21:18
You need to install the DHCP role on your DC as it will assign an IP address from an address pool to a connecting device. Can you ping the server successfully?
– Yass
Sep 16 '13 at 21:08
You need to install the DHCP role on your DC as it will assign an IP address from an address pool to a connecting device. Can you ping the server successfully?
– Yass
Sep 16 '13 at 21:08
@yassarikhan786 I did install DHCP role, and made it to dish out 192.168.2.101-150. I only tried ping on the server, since I cannot get client1 to connect to the domain. ping to the win-dc or to its ip all OK. Correct what I just said: I just ping the server from the host PC, worked , too
– user2654478
Sep 16 '13 at 21:12
@yassarikhan786 I did install DHCP role, and made it to dish out 192.168.2.101-150. I only tried ping on the server, since I cannot get client1 to connect to the domain. ping to the win-dc or to its ip all OK. Correct what I just said: I just ping the server from the host PC, worked , too
– user2654478
Sep 16 '13 at 21:12
If you have the DHCP role installed you need to disable your routers DHCP service.
– Yass
Sep 16 '13 at 21:15
If you have the DHCP role installed you need to disable your routers DHCP service.
– Yass
Sep 16 '13 at 21:15
@yassarikhan786 OK. I will try just that. thanks for looking into my post.
– user2654478
Sep 16 '13 at 21:16
@yassarikhan786 OK. I will try just that. thanks for looking into my post.
– user2654478
Sep 16 '13 at 21:16
No problem, glad I could help.
– Yass
Sep 16 '13 at 21:18
No problem, glad I could help.
– Yass
Sep 16 '13 at 21:18
|
show 2 more comments
1 Answer
1
active
oldest
votes
you need to create the computer object (your vm) before it can join the domain
answered Sep 17 '13 at 7:38
KPSKPS
1892311
I have. I used wdsutil to add the device by MAC address into the domain. I will try disabling router dhcp first. But thanks for the reply.
– user2654478
Sep 17 '13 at 20:07
add a comment |
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%2f646241%2factive-directory-domain-in-home-network-how-to-add-computer%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
you need to create the computer object (your vm) before it can join the domain
answered Sep 17 '13 at 7:38
KPSKPS
1892311
I have. I used wdsutil to add the device by MAC address into the domain. I will try disabling router dhcp first. But thanks for the reply.
– user2654478
Sep 17 '13 at 20:07
add a comment |
you need to create the computer object (your vm) before it can join the domain
answered Sep 17 '13 at 7:38
KPSKPS
1892311
I have. I used wdsutil to add the device by MAC address into the domain. I will try disabling router dhcp first. But thanks for the reply.
– user2654478
Sep 17 '13 at 20:07
add a comment |
you need to create the computer object (your vm) before it can join the domain
answered Sep 17 '13 at 7:38
KPSKPS
1892311
you need to create the computer object (your vm) before it can join the domain
answered Sep 17 '13 at 7:38
KPSKPS
1892311
answered Sep 17 '13 at 7:38
KPSKPS
1892311
answered Sep 17 '13 at 7:38
KPSKPS
1892311
answered Sep 17 '13 at 7:38
KPSKPS
1892311
1892311
I have. I used wdsutil to add the device by MAC address into the domain. I will try disabling router dhcp first. But thanks for the reply.
– user2654478
Sep 17 '13 at 20:07
add a comment |
I have. I used wdsutil to add the device by MAC address into the domain. I will try disabling router dhcp first. But thanks for the reply.
– user2654478
Sep 17 '13 at 20:07
I have. I used wdsutil to add the device by MAC address into the domain. I will try disabling router dhcp first. But thanks for the reply.
– user2654478
Sep 17 '13 at 20:07
I have. I used wdsutil to add the device by MAC address into the domain. I will try disabling router dhcp first. But thanks for the reply.
– user2654478
Sep 17 '13 at 20:07
add a comment |
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%2f646241%2factive-directory-domain-in-home-network-how-to-add-computer%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
You need to install the DHCP role on your DC as it will assign an IP address from an address pool to a connecting device. Can you ping the server successfully?
– Yass
Sep 16 '13 at 21:08
@yassarikhan786 I did install DHCP role, and made it to dish out 192.168.2.101-150. I only tried ping on the server, since I cannot get client1 to connect to the domain. ping to the win-dc or to its ip all OK. Correct what I just said: I just ping the server from the host PC, worked , too
– user2654478
Sep 16 '13 at 21:12
If you have the DHCP role installed you need to disable your routers DHCP service.
– Yass
Sep 16 '13 at 21:15
@yassarikhan786 OK. I will try just that. thanks for looking into my post.
– user2654478
Sep 16 '13 at 21:16
No problem, glad I could help.
– Yass
Sep 16 '13 at 21:18