• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Server 2008 R2 & HyperV Network

sonoma1993

Diamond Member
In server 2008 R2 enterprise editition when using Hyper V. When you assign a network card for hyperv to use for the different vms. Should you assign a static IP to that network card or is it better to leave it for DHCP?
 
It depends on what you are looking to do. You can leave it as DHCP or static. If it is DHCP make sure that it has access to a DHCP server. Keep in mind that access to a DHCP server (or access to any server) will depend on whether you are using an external, internal or private network. Private the DHCP server will have to be another VM on the same host, Internal it can be another VM or the host and external it can be anything internal or external to the host that this machine has access to.



Hyper-V implements three types of virtual networks: external, private and internal. An external virtual network gives virtual machines direct access to a physical network adapters on the physical computer. In effect, the virtual network shares the physical network adapter with the parent operating system (the Windows Server 2008 originally installed on the computer). A private network is used to connect two or more virtual machines running on the same physical computer to one another. An internal network is just like a private network, except it includes the parent operating system as well.
 
Back
Top