Hi every one,
I am New to virtual Box, My Requirement is to create a Windows server 2003 Network. with One Domain Controller and 2 Domain Members.
For that, I installed 3 virtual windows 2003 server GUest Operating systems. I named them as WSDC , WSDM1, WSDM2.
WSDC for Domain Controller
WSDM1 for Domain Member 1
WSDM2 for Domain Member 2
1)In the Networks, I Checked Only adapter 1 as Internal Network with name as "intnet" For 3 machines.
2)I Installed Active Directory Domain Controller, in WSDC.
3)I configured the IP addresses in 3 machines as..
for WSDC,
TCP/IP Protocols:
IP address: 192.1681.100
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
Preferred DNS server: 127.0.0.1
For WSDM1,
TCP/IP Protocols:
IP address: 192.1681.101
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
Preferred DNS server: 192.1681.100
For WSDM2
TCP/IP Protocols:
IP address: 192.1681.102
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
Preferred DNS server: 192.1681.100
When I try to add the WSDM1 and WSDM2 to Domain, It is not getting Connect. Its Showing the Error as like "Unable to reach the domain"
Please Guide me, Where i went wrong, When i configured the Same Protocols with same configuration in Vm ware using NAT it Gets Connected Successfully. But here
in Virtual Box, I Tried with Both "NAT" Network and "internal" networks, but no use.
Please Give me a Solution For this.
Unable to Configure Network for ws2003
-
socratis
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Unable to Configure Network for ws2003
The default range for internal networking is 192.168.50.###. Did you change the "intnet" settings or did you decide that 192.168.1.### looked better? Unless you can fix basic connectivity problems (like ping) you will not be able to move to more advanced topics, such as joining a domain.VirtualRush wrote:Internal Network with name as "intnet" For 3 machines
...
IP address: 192.1681.100
You may want to try "NAT Network" mode which is different from "NAT" mode. For more information, see Chapter 6.2. Introduction to networking modes.VirtualRush wrote:I Tried with Both "NAT" Network and "internal" networks
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
VirtualRush
- Posts: 2
- Joined: 16. Feb 2015, 08:05
Re: Unable to Configure Network for ws2003
hello,
Thanks for your reply, I tried changing the ip with in the limit you mentioned. Even though i didn't get that.
Thanks for your reply, I tried changing the ip with in the limit you mentioned. Even though i didn't get that.
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Unable to Configure Network for ws2003
I'm going to assume the '1681' in Rush's posts is a typo. ( I don't think the IP address settings window will allow that high of a number to be entered or used...) It would be 192.168.1.###, similar to the gateway values.
Rush, you should be able to connect the three guests with internal networking. Take a look at the manual, section 6.5. According to the manual, there's no DHCP server on an internal network, unless you turn it on. Static IP's in the guests should work fine without a DHCP server. Make sure the internal network name is spelled the same in all three guests - merely spelling the name differently will make a new entirely separate internal network, and the guest on that network won't connect to the others. Check that each guest is set to respond to PINGs in the guest OS, then try pinging from each guest to the other two. If you have good pings, then the network is good and Virtualbox has done its job. After that, it's just setting up a Windows domain, which would then be something for Google & Bing to help you with.
Rush, you should be able to connect the three guests with internal networking. Take a look at the manual, section 6.5. According to the manual, there's no DHCP server on an internal network, unless you turn it on. Static IP's in the guests should work fine without a DHCP server. Make sure the internal network name is spelled the same in all three guests - merely spelling the name differently will make a new entirely separate internal network, and the guest on that network won't connect to the others. Check that each guest is set to respond to PINGs in the guest OS, then try pinging from each guest to the other two. If you have good pings, then the network is good and Virtualbox has done its job. After that, it's just setting up a Windows domain, which would then be something for Google & Bing to help you with.