Hello
I would like to create own Windows network laboratory = Windows server + Windows client in one domain. How should I set network for it, both guests can ping and see each other? It would be great also to have internet connection for both of them.
When I use default NAT, both guests have internet connection, but they have also the same IP address.
I tried to use NAT network with my own IP address range, but guests were not able to ping each other.
Thanks for help
Ales
How to set network for Window server and client?
-
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: How to set network for Window server and client?
Start by reading Chapter 6. Virtual networking. If you have any questions afterwards, feel free to ask.
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.
-
BillG
- Volunteer
- Posts: 5106
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: How to set network for Window server and client?
If you want to run it as a lab, the domain should be in its own network using its own IP subnet. I use an internal network.
If you want the domain to have Internet access, it gets harder. You need a virtual router to route the internal network to your physical network. In addition there are several steps you need to take to get it working, but they are not related to virtual machines or virtual networks. They are the result of the way Active Directory uses DNS and also apply if you use physical machines and networks to run a domain.
If you want the domain to have Internet access, it gets harder. You need a virtual router to route the internal network to your physical network. In addition there are several steps you need to take to get it working, but they are not related to virtual machines or virtual networks. They are the result of the way Active Directory uses DNS and also apply if you use physical machines and networks to run a domain.
Bill
Re: How to set network for Window server and client?
Hello guys
Of course I already read Chapter 6 - Virtual networking.
Thank you Bill, Internal network is working for me now.
Yesterday I tried this option, but I create a new name of
network and it did not work. Today, when I tried it again
with default "intnet" network it works!
Thanks again
Of course I already read Chapter 6 - Virtual networking.
Thank you Bill, Internal network is working for me now.
Yesterday I tried this option, but I create a new name of
network and it did not work. Today, when I tried it again
with default "intnet" network it works!
Thanks again