![]() ![]() Only when the domain is functional, set up a virtual router to connect your domain network to a physical network. Configure the local DNS ( and DHCP if you wish) and get your domain working locally. (This is just like setting up a physical domain on an isolated switch). Set up your domain machines on an internal virtual network. This DNS will lookup external calls on the client's behalf. The domain members should use the local DNS only. If you want access to resources outside the domain (such as the Internet), set a forwarder in the local DNS, do not put other DNS addresses in any domain member, not even as a secondary. An external DNS cannot resolve your local names. For the domain to work, all domain members must use the local DNS, so that local domain names can be resolved. That is fine in a workgroup situation but a domain will fail. Clients on any NAT network use the NAT router for DNS calls. This has nothing to do with VirtualBox - it applies to any Windows domain. If you really want to run a domain on this network, NAT is not a good choice. ![]() I repeated all three tests on a 6.1.6 host, all pings good every direction. I made another test on an Internal network with no DHCP, both XP guests set themselves APIPA addresses and could ping each other. I ran similar tests on a Host-Only network with DHCP enabled and could ping both guests and the host both ways all three OS's. Note the problem NAT network has when you change the IP address range after the NAT network has been used.įWIW I made the exact same test as listed above, on a 6.0.14 host, with XP guests, and had good pings all around. Then configure away for your DC lab experiments. Good ping means the NAT network is open for business. Ping the other guest's IP address in each guest. Ping 8.8.8.8 (Google's server) in each guest to test internet presence. The other guest should be IP 10.0.8.5, same numbers for the other settings. In each guest, edit the firewall to allow ICMP echo request (ping). For now, don't make any special role settings, just let the OS install to a basic setup. Don't re-use the old ones, we want fresh network stacks in factory configuration. (We need a new NAT network because the DHCP server for old NAT networks remains behind, set at the IP range settings the NAT network had when it was first used, and does not follow user-induced IP range changes to the NAT network, and remains ready to run on any other NAT network with the same name as the DHCP server). Make the Network CIDR: 10.0.8.0/24 (Note that if your physical LAN happens to be 10.#.#.anything, the NAT part of the NAT network may not work. Delete them all, and make a new NAT network. OK, let's do a standardized test: Go to the main Virtualbox window, File menu, Preferences, Network. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |