Joining client to Server in VirtualBox
up vote
2
down vote
favorite
Having installed the trial of Server 2012 and a copy of Win 7 Pro in VirtualBox, I now need to join them together so the client can be in the domain of the server. I need to deactivate dhcp within VirtualBox to do this but don't understand what the help file is trying to tell me...
Many thanks for any suggestions,
Al
networking virtualbox dhcp
asked Jul 9 '14 at 7:37
Alistair Green
1112
add a comment |
up vote
2
down vote
favorite
Having installed the trial of Server 2012 and a copy of Win 7 Pro in VirtualBox, I now need to join them together so the client can be in the domain of the server. I need to deactivate dhcp within VirtualBox to do this but don't understand what the help file is trying to tell me...
Many thanks for any suggestions,
Al
networking virtualbox dhcp
asked Jul 9 '14 at 7:37
Alistair Green
1112
You don't need to deactivate DHCP.
– Tanner Faulkner
Jul 9 '14 at 15:16
I was told that was a requirement if I wanted to use Server 2012 as the DHCP server...
– Alistair Green
Jul 9 '14 at 15:24
Well, yes, if you want to use a different DHCP server you'll need to deactivate the current one, but that has no impact on joining Windows 7 to a domain (barring any other network configuration issues).
– Tanner Faulkner
Jul 9 '14 at 15:25
Oh, right thanks. Yes I will want to use the Microsoft server for DHCP and DNS so I will need to deactivate the VirtualBox one, I just have no idea what the help files are trying to say to me in regard to this or the steps involved in adding this client to the Active Directory domain...
– Alistair Green
Jul 9 '14 at 15:34
Please try to change the VB network settings from NAT to bridged. It should work.
– Akash
Jun 2 '17 at 20:32
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
Having installed the trial of Server 2012 and a copy of Win 7 Pro in VirtualBox, I now need to join them together so the client can be in the domain of the server. I need to deactivate dhcp within VirtualBox to do this but don't understand what the help file is trying to tell me...
Many thanks for any suggestions,
Al
networking virtualbox dhcp
asked Jul 9 '14 at 7:37
Alistair Green
1112
Having installed the trial of Server 2012 and a copy of Win 7 Pro in VirtualBox, I now need to join them together so the client can be in the domain of the server. I need to deactivate dhcp within VirtualBox to do this but don't understand what the help file is trying to tell me...
Many thanks for any suggestions,
Al
networking virtualbox dhcp
networking virtualbox dhcp
asked Jul 9 '14 at 7:37
Alistair Green
1112
asked Jul 9 '14 at 7:37
Alistair Green
1112
asked Jul 9 '14 at 7:37
Alistair Green
1112
asked Jul 9 '14 at 7:37
Alistair Green
1112
asked Jul 9 '14 at 7:37
Alistair Green
1112
1112
You don't need to deactivate DHCP.
– Tanner Faulkner
Jul 9 '14 at 15:16
I was told that was a requirement if I wanted to use Server 2012 as the DHCP server...
– Alistair Green
Jul 9 '14 at 15:24
Well, yes, if you want to use a different DHCP server you'll need to deactivate the current one, but that has no impact on joining Windows 7 to a domain (barring any other network configuration issues).
– Tanner Faulkner
Jul 9 '14 at 15:25
Oh, right thanks. Yes I will want to use the Microsoft server for DHCP and DNS so I will need to deactivate the VirtualBox one, I just have no idea what the help files are trying to say to me in regard to this or the steps involved in adding this client to the Active Directory domain...
– Alistair Green
Jul 9 '14 at 15:34
Please try to change the VB network settings from NAT to bridged. It should work.
– Akash
Jun 2 '17 at 20:32
add a comment |
You don't need to deactivate DHCP.
– Tanner Faulkner
Jul 9 '14 at 15:16
I was told that was a requirement if I wanted to use Server 2012 as the DHCP server...
– Alistair Green
Jul 9 '14 at 15:24
Well, yes, if you want to use a different DHCP server you'll need to deactivate the current one, but that has no impact on joining Windows 7 to a domain (barring any other network configuration issues).
– Tanner Faulkner
Jul 9 '14 at 15:25
Oh, right thanks. Yes I will want to use the Microsoft server for DHCP and DNS so I will need to deactivate the VirtualBox one, I just have no idea what the help files are trying to say to me in regard to this or the steps involved in adding this client to the Active Directory domain...
– Alistair Green
Jul 9 '14 at 15:34
Please try to change the VB network settings from NAT to bridged. It should work.
– Akash
Jun 2 '17 at 20:32
You don't need to deactivate DHCP.
– Tanner Faulkner
Jul 9 '14 at 15:16
You don't need to deactivate DHCP.
– Tanner Faulkner
Jul 9 '14 at 15:16
I was told that was a requirement if I wanted to use Server 2012 as the DHCP server...
– Alistair Green
Jul 9 '14 at 15:24
I was told that was a requirement if I wanted to use Server 2012 as the DHCP server...
– Alistair Green
Jul 9 '14 at 15:24
Well, yes, if you want to use a different DHCP server you'll need to deactivate the current one, but that has no impact on joining Windows 7 to a domain (barring any other network configuration issues).
– Tanner Faulkner
Jul 9 '14 at 15:25
Well, yes, if you want to use a different DHCP server you'll need to deactivate the current one, but that has no impact on joining Windows 7 to a domain (barring any other network configuration issues).
– Tanner Faulkner
Jul 9 '14 at 15:25
Oh, right thanks. Yes I will want to use the Microsoft server for DHCP and DNS so I will need to deactivate the VirtualBox one, I just have no idea what the help files are trying to say to me in regard to this or the steps involved in adding this client to the Active Directory domain...
– Alistair Green
Jul 9 '14 at 15:34
Oh, right thanks. Yes I will want to use the Microsoft server for DHCP and DNS so I will need to deactivate the VirtualBox one, I just have no idea what the help files are trying to say to me in regard to this or the steps involved in adding this client to the Active Directory domain...
– Alistair Green
Jul 9 '14 at 15:34
Please try to change the VB network settings from NAT to bridged. It should work.
– Akash
Jun 2 '17 at 20:32
Please try to change the VB network settings from NAT to bridged. It should work.
– Akash
Jun 2 '17 at 20:32
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
Let's forget about DHCP for the moment. I don't have VirtualBox handy and have no memory of its DHCP settings.
It seems like the reason you're getting held up on DHCP is because you need to change the DNS settings to point to your Domain Controller. Yes, DHCP does hand out the DNS server addresses, but we can also override this.
On your Windows 7 machine, open up Network Connections. I find it's easiest to search for it in the Start Menu:
Right click on the connected network adapter and select Properties.
Select TCP/IPV4 and hit Properties.
Now select 'Use the following DNS server addresses' and punch in your Server's IP address. Leave the alternate blank (Since we only have one DNS server! Don't do this in a work environment.)
Now that our Windows 7 machine can contact the Domain Controller, we're ready to join to the domain. Open up System from the Control Panel and click Change Settings.
Punch another Change button (yay redundancy!).
Select Domain and type in the name of your domain.
It will prompt you for credentials. Punch in your Administrator creds and hit OK. Now reboot, and the PC is joined to the Domain.
answered Jul 9 '14 at 16:35
Tanner Faulkner
9,050134181
I get as far as this last step and when I OK after entering the domain I an error box appear saying "An AD DC for the domain could not be contacted"
– Alistair Green
Jul 9 '14 at 17:30
Ah, something is wrong with your network settings then. What are the IP addresses for both the server and the client? Are you sure they're both in the same network under Virtual Box?
– Tanner Faulkner
Jul 9 '14 at 17:47
No, the server is statically set to 10.1.10.2/24 whereas the client keeps getting set to 10.0.2.15 - presumably by the VirtualBox DHCP...
– Alistair Green
Jul 9 '14 at 18:26
Ah, so that's what we need to fix... Make sure you've got them both on the same 'virtual network' or whatever VirtualBox calls it, then set a static IP for the DC at 10.0.2.100 or something.
– Tanner Faulkner
Jul 9 '14 at 18:27
I'll give it a whirl, thanks for all your help - give me a minute...
– Alistair Green
Jul 9 '14 at 18:32
|
show 4 more comments
up vote
0
down vote
Sorted, the solution was to simply put both the Server 2012 machine and the Win 7 Pro client into "Internal" in Settings>Network. I still haven't got internet access on either machine but at least now I can get on with learning to administer the server and Active Directory. My host laptop has internet access.
Happy days!!! And it's my birthday, how cool is that!!!
answered Jul 11 '14 at 22:27
Alistair Green
1112
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Let's forget about DHCP for the moment. I don't have VirtualBox handy and have no memory of its DHCP settings.
It seems like the reason you're getting held up on DHCP is because you need to change the DNS settings to point to your Domain Controller. Yes, DHCP does hand out the DNS server addresses, but we can also override this.
On your Windows 7 machine, open up Network Connections. I find it's easiest to search for it in the Start Menu:
Right click on the connected network adapter and select Properties.
Select TCP/IPV4 and hit Properties.
Now select 'Use the following DNS server addresses' and punch in your Server's IP address. Leave the alternate blank (Since we only have one DNS server! Don't do this in a work environment.)
Now that our Windows 7 machine can contact the Domain Controller, we're ready to join to the domain. Open up System from the Control Panel and click Change Settings.
Punch another Change button (yay redundancy!).
Select Domain and type in the name of your domain.
It will prompt you for credentials. Punch in your Administrator creds and hit OK. Now reboot, and the PC is joined to the Domain.
answered Jul 9 '14 at 16:35
Tanner Faulkner
9,050134181
I get as far as this last step and when I OK after entering the domain I an error box appear saying "An AD DC for the domain could not be contacted"
– Alistair Green
Jul 9 '14 at 17:30
Ah, something is wrong with your network settings then. What are the IP addresses for both the server and the client? Are you sure they're both in the same network under Virtual Box?
– Tanner Faulkner
Jul 9 '14 at 17:47
No, the server is statically set to 10.1.10.2/24 whereas the client keeps getting set to 10.0.2.15 - presumably by the VirtualBox DHCP...
– Alistair Green
Jul 9 '14 at 18:26
Ah, so that's what we need to fix... Make sure you've got them both on the same 'virtual network' or whatever VirtualBox calls it, then set a static IP for the DC at 10.0.2.100 or something.
– Tanner Faulkner
Jul 9 '14 at 18:27
I'll give it a whirl, thanks for all your help - give me a minute...
– Alistair Green
Jul 9 '14 at 18:32
|
show 4 more comments
up vote
0
down vote
Let's forget about DHCP for the moment. I don't have VirtualBox handy and have no memory of its DHCP settings.
It seems like the reason you're getting held up on DHCP is because you need to change the DNS settings to point to your Domain Controller. Yes, DHCP does hand out the DNS server addresses, but we can also override this.
On your Windows 7 machine, open up Network Connections. I find it's easiest to search for it in the Start Menu:
Right click on the connected network adapter and select Properties.
Select TCP/IPV4 and hit Properties.
Now select 'Use the following DNS server addresses' and punch in your Server's IP address. Leave the alternate blank (Since we only have one DNS server! Don't do this in a work environment.)
Now that our Windows 7 machine can contact the Domain Controller, we're ready to join to the domain. Open up System from the Control Panel and click Change Settings.
Punch another Change button (yay redundancy!).
Select Domain and type in the name of your domain.
It will prompt you for credentials. Punch in your Administrator creds and hit OK. Now reboot, and the PC is joined to the Domain.
answered Jul 9 '14 at 16:35
Tanner Faulkner
9,050134181
I get as far as this last step and when I OK after entering the domain I an error box appear saying "An AD DC for the domain could not be contacted"
– Alistair Green
Jul 9 '14 at 17:30
Ah, something is wrong with your network settings then. What are the IP addresses for both the server and the client? Are you sure they're both in the same network under Virtual Box?
– Tanner Faulkner
Jul 9 '14 at 17:47
No, the server is statically set to 10.1.10.2/24 whereas the client keeps getting set to 10.0.2.15 - presumably by the VirtualBox DHCP...
– Alistair Green
Jul 9 '14 at 18:26
Ah, so that's what we need to fix... Make sure you've got them both on the same 'virtual network' or whatever VirtualBox calls it, then set a static IP for the DC at 10.0.2.100 or something.
– Tanner Faulkner
Jul 9 '14 at 18:27
I'll give it a whirl, thanks for all your help - give me a minute...
– Alistair Green
Jul 9 '14 at 18:32
|
show 4 more comments
up vote
0
down vote
up vote
0
down vote
Let's forget about DHCP for the moment. I don't have VirtualBox handy and have no memory of its DHCP settings.
It seems like the reason you're getting held up on DHCP is because you need to change the DNS settings to point to your Domain Controller. Yes, DHCP does hand out the DNS server addresses, but we can also override this.
On your Windows 7 machine, open up Network Connections. I find it's easiest to search for it in the Start Menu:
Right click on the connected network adapter and select Properties.
Select TCP/IPV4 and hit Properties.
Now select 'Use the following DNS server addresses' and punch in your Server's IP address. Leave the alternate blank (Since we only have one DNS server! Don't do this in a work environment.)
Now that our Windows 7 machine can contact the Domain Controller, we're ready to join to the domain. Open up System from the Control Panel and click Change Settings.
Punch another Change button (yay redundancy!).
Select Domain and type in the name of your domain.
It will prompt you for credentials. Punch in your Administrator creds and hit OK. Now reboot, and the PC is joined to the Domain.
answered Jul 9 '14 at 16:35
Tanner Faulkner
9,050134181
Let's forget about DHCP for the moment. I don't have VirtualBox handy and have no memory of its DHCP settings.
It seems like the reason you're getting held up on DHCP is because you need to change the DNS settings to point to your Domain Controller. Yes, DHCP does hand out the DNS server addresses, but we can also override this.
On your Windows 7 machine, open up Network Connections. I find it's easiest to search for it in the Start Menu:
Right click on the connected network adapter and select Properties.
Select TCP/IPV4 and hit Properties.
Now select 'Use the following DNS server addresses' and punch in your Server's IP address. Leave the alternate blank (Since we only have one DNS server! Don't do this in a work environment.)
Now that our Windows 7 machine can contact the Domain Controller, we're ready to join to the domain. Open up System from the Control Panel and click Change Settings.
Punch another Change button (yay redundancy!).
Select Domain and type in the name of your domain.
It will prompt you for credentials. Punch in your Administrator creds and hit OK. Now reboot, and the PC is joined to the Domain.
answered Jul 9 '14 at 16:35
Tanner Faulkner
9,050134181
answered Jul 9 '14 at 16:35
Tanner Faulkner
9,050134181
answered Jul 9 '14 at 16:35
Tanner Faulkner
9,050134181
answered Jul 9 '14 at 16:35
Tanner Faulkner
9,050134181
9,050134181
I get as far as this last step and when I OK after entering the domain I an error box appear saying "An AD DC for the domain could not be contacted"
– Alistair Green
Jul 9 '14 at 17:30
Ah, something is wrong with your network settings then. What are the IP addresses for both the server and the client? Are you sure they're both in the same network under Virtual Box?
– Tanner Faulkner
Jul 9 '14 at 17:47
No, the server is statically set to 10.1.10.2/24 whereas the client keeps getting set to 10.0.2.15 - presumably by the VirtualBox DHCP...
– Alistair Green
Jul 9 '14 at 18:26
Ah, so that's what we need to fix... Make sure you've got them both on the same 'virtual network' or whatever VirtualBox calls it, then set a static IP for the DC at 10.0.2.100 or something.
– Tanner Faulkner
Jul 9 '14 at 18:27
I'll give it a whirl, thanks for all your help - give me a minute...
– Alistair Green
Jul 9 '14 at 18:32
|
show 4 more comments
I get as far as this last step and when I OK after entering the domain I an error box appear saying "An AD DC for the domain could not be contacted"
– Alistair Green
Jul 9 '14 at 17:30
Ah, something is wrong with your network settings then. What are the IP addresses for both the server and the client? Are you sure they're both in the same network under Virtual Box?
– Tanner Faulkner
Jul 9 '14 at 17:47
No, the server is statically set to 10.1.10.2/24 whereas the client keeps getting set to 10.0.2.15 - presumably by the VirtualBox DHCP...
– Alistair Green
Jul 9 '14 at 18:26
Ah, so that's what we need to fix... Make sure you've got them both on the same 'virtual network' or whatever VirtualBox calls it, then set a static IP for the DC at 10.0.2.100 or something.
– Tanner Faulkner
Jul 9 '14 at 18:27
I'll give it a whirl, thanks for all your help - give me a minute...
– Alistair Green
Jul 9 '14 at 18:32
I get as far as this last step and when I OK after entering the domain I an error box appear saying "An AD DC for the domain could not be contacted"
– Alistair Green
Jul 9 '14 at 17:30
I get as far as this last step and when I OK after entering the domain I an error box appear saying "An AD DC for the domain could not be contacted"
– Alistair Green
Jul 9 '14 at 17:30
Ah, something is wrong with your network settings then. What are the IP addresses for both the server and the client? Are you sure they're both in the same network under Virtual Box?
– Tanner Faulkner
Jul 9 '14 at 17:47
Ah, something is wrong with your network settings then. What are the IP addresses for both the server and the client? Are you sure they're both in the same network under Virtual Box?
– Tanner Faulkner
Jul 9 '14 at 17:47
No, the server is statically set to 10.1.10.2/24 whereas the client keeps getting set to 10.0.2.15 - presumably by the VirtualBox DHCP...
– Alistair Green
Jul 9 '14 at 18:26
No, the server is statically set to 10.1.10.2/24 whereas the client keeps getting set to 10.0.2.15 - presumably by the VirtualBox DHCP...
– Alistair Green
Jul 9 '14 at 18:26
Ah, so that's what we need to fix... Make sure you've got them both on the same 'virtual network' or whatever VirtualBox calls it, then set a static IP for the DC at 10.0.2.100 or something.
– Tanner Faulkner
Jul 9 '14 at 18:27
Ah, so that's what we need to fix... Make sure you've got them both on the same 'virtual network' or whatever VirtualBox calls it, then set a static IP for the DC at 10.0.2.100 or something.
– Tanner Faulkner
Jul 9 '14 at 18:27
I'll give it a whirl, thanks for all your help - give me a minute...
– Alistair Green
Jul 9 '14 at 18:32
I'll give it a whirl, thanks for all your help - give me a minute...
– Alistair Green
Jul 9 '14 at 18:32
|
show 4 more comments
up vote
0
down vote
Sorted, the solution was to simply put both the Server 2012 machine and the Win 7 Pro client into "Internal" in Settings>Network. I still haven't got internet access on either machine but at least now I can get on with learning to administer the server and Active Directory. My host laptop has internet access.
Happy days!!! And it's my birthday, how cool is that!!!
answered Jul 11 '14 at 22:27
Alistair Green
1112
add a comment |
up vote
0
down vote
Sorted, the solution was to simply put both the Server 2012 machine and the Win 7 Pro client into "Internal" in Settings>Network. I still haven't got internet access on either machine but at least now I can get on with learning to administer the server and Active Directory. My host laptop has internet access.
Happy days!!! And it's my birthday, how cool is that!!!
answered Jul 11 '14 at 22:27
Alistair Green
1112
add a comment |
up vote
0
down vote
up vote
0
down vote
Sorted, the solution was to simply put both the Server 2012 machine and the Win 7 Pro client into "Internal" in Settings>Network. I still haven't got internet access on either machine but at least now I can get on with learning to administer the server and Active Directory. My host laptop has internet access.
Happy days!!! And it's my birthday, how cool is that!!!
answered Jul 11 '14 at 22:27
Alistair Green
1112
Sorted, the solution was to simply put both the Server 2012 machine and the Win 7 Pro client into "Internal" in Settings>Network. I still haven't got internet access on either machine but at least now I can get on with learning to administer the server and Active Directory. My host laptop has internet access.
Happy days!!! And it's my birthday, how cool is that!!!
answered Jul 11 '14 at 22:27
Alistair Green
1112
answered Jul 11 '14 at 22:27
Alistair Green
1112
answered Jul 11 '14 at 22:27
Alistair Green
1112
answered Jul 11 '14 at 22:27
Alistair Green
1112
1112
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f778790%2fjoining-client-to-server-in-virtualbox%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 don't need to deactivate DHCP.
– Tanner Faulkner
Jul 9 '14 at 15:16
I was told that was a requirement if I wanted to use Server 2012 as the DHCP server...
– Alistair Green
Jul 9 '14 at 15:24
Well, yes, if you want to use a different DHCP server you'll need to deactivate the current one, but that has no impact on joining Windows 7 to a domain (barring any other network configuration issues).
– Tanner Faulkner
Jul 9 '14 at 15:25
Oh, right thanks. Yes I will want to use the Microsoft server for DHCP and DNS so I will need to deactivate the VirtualBox one, I just have no idea what the help files are trying to say to me in regard to this or the steps involved in adding this client to the Active Directory domain...
– Alistair Green
Jul 9 '14 at 15:34
Please try to change the VB network settings from NAT to bridged. It should work.
– Akash
Jun 2 '17 at 20:32