Networking Virtual Machines: Best Practices

Click For Summary

Discussion Overview

The discussion revolves around best practices for networking multiple Virtual Machines (VMs) to enable resource sharing and communication, particularly in the context of Active Directory. It includes considerations of different networking configurations and the implications of virtual environments.

Discussion Character

  • Technical explanation
  • Conceptual clarification
  • Debate/contested

Main Points Raised

  • Some participants inquire about standard methods for networking VMs, particularly in relation to sharing resources like Active Directory.
  • There is mention of using Docker containers as a potential model for networking, although it is unclear if this is the intended focus.
  • One participant suggests searching for specific virtualization technologies (e.g., VMware, Hyper-V) to find information on creating virtual networks or switches.
  • Another participant describes three types of virtual networks: Bridged, NAT, and Host-only, explaining that VMs can be assigned to these networks to enable communication.
  • It is noted that VMs can be added to a domain and function similarly to physical machines, provided they have access to a NIC and unique IP addresses.
  • Some participants emphasize that VMs should be hardware-agnostic, with the requirement that they have different IPs to avoid issues, and mention the use of bridged adapters.
  • One participant confirms that moving all VMs into the same domain has successfully facilitated their networking needs.

Areas of Agreement / Disagreement

Participants generally agree on the feasibility of networking VMs within the same domain and the importance of unique IP addresses. However, there are varying perspectives on the specifics of networking configurations and the relevance of different types of virtual networks.

Contextual Notes

Some assumptions about the networking environment and specific configurations are not fully explored, and the discussion does not resolve the nuances of different virtualization technologies or their implications for networking.

Who May Find This Useful

This discussion may be useful for IT professionals, system administrators, and anyone interested in virtual machine networking, particularly in relation to Active Directory and resource sharing.

WWGD
Science Advisor
Homework Helper
Messages
7,806
Reaction score
13,120
Hi just curious,
Are there standard methods for putting several Virtual Machines in a network?
 
Computer science news on Phys.org
Do you mean like Docker containers?
 
  • Like
Likes   Reactions: WWGD
jedishrfu said:
Do you mean like Docker containers?
Thanks, not sure exactly, but I am just looking to have them be able to share resources (I am thinking mostly Active Directory) and communicate with each other in general, as standard physical machines do.
 
There are three types of virtual networks: Bridged, NAT, and Host-only. When you create a new VM or add a NIC to an existing VM, you assign the NIC(s) to a virtual network, thereby giving it access to any other VMs configured on the same network.
 
  • Like
Likes   Reactions: WWGD
WWGD said:
Thanks, not sure exactly, but I am just looking to have them be able to share resources (I am thinking mostly Active Directory) and communicate with each other in general, as standard physical machines do.

Yes. You can put a VM on a network assuming the VM has access to a NIC card. That VM could be added to the domain, and you could log into that VM using accounts in the active directory for that domain. If you looked for computers on your domain, you would also find your VM. That VM would be able to access whatever resources a physical computer on that domain could access. It would be for all intents and purposes, just another computer on the domain.

There ARE differences. But, for the scope of your question - they aren't relevant.
 
  • Like
Likes   Reactions: WWGD
Thanks all, it seems like just moving all VMs into the same domain has done the job.
 
VMs are supposed to be agnostic to the hardware they are running on. As long as their ips are different, there should be no issue. Sometimes you'll have to use a bridged adapter through the host though.
 
  • Like
Likes   Reactions: WWGD
newjerseyrunner said:
VMs are supposed to be agnostic to the hardware they are running on. As long as their ips are different, there should be no issue. Sometimes you'll have to use a bridged adapter through the host though.
Thanks, Runner. Does the idea of having them in the same domain ( in windows) work in general too?
 
  • #10
WWGD said:
Thanks, Runner. Does the idea of having them in the same domain ( in windows) work in general too?
Yeah, part of my job is to manage some of my companies windows servers. I've virtualized all of them and they're all on the same domain.

As long as they each have their own ip and computer name. Ip you set in network and sharing, right click on the connection, properties, IPv4, properties. The computer name, right click on my computer and a select properties.
 
  • Like
Likes   Reactions: WWGD

Similar threads

Replies
5
Views
2K
  • · Replies 4 ·
Replies
4
Views
2K
  • · Replies 4 ·
Replies
4
Views
1K
  • · Replies 9 ·
Replies
9
Views
2K
  • · Replies 4 ·
Replies
4
Views
3K
Replies
13
Views
2K
  • · Replies 20 ·
Replies
20
Views
5K
  • · Replies 7 ·
Replies
7
Views
2K
Replies
5
Views
2K
Replies
5
Views
874