Maybe a tough one…

Home Forums Virtualization Microsoft Hyper-V Technology Maybe a tough one…

Viewing 1 post (of 1 total)
  • Author

  • shmengie

    Hi there:

    I’ve got an HP GL370 with 5 physical NICs running 2K8 R2. I’ve installed Hyper-V and have set up several VMs without issue. All these VMs share the same virtual and physical NICs because they’re all on the network. So far, so good. So…

    I have set up a new VM (W7, just for light-duty code compiling, but needs to talk to an outside host) in the DMZ. I created a new virtual NIC, and mapped that to it’s own, separate physical NIC. This is where the trouble begins…

    The host box (the 2K8 install), has some code on it that needs to talk to another box on the domain. It does that just fine, until I enable the NIC that’s in the DMZ. Then, I can’t get to the other box. Can’t ping it; nothing. It’s like the DMZ’d NIC is superceding the network NIC.

    It’s possible (likely?) that there’s a tick box or radio button that I’ve overlooked, or don’t understand.

    I know it’s tough from here, but can anyone advise on how these two networks can peacefully co-exist?


Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.

Don't leave your business open to attack! Come learn how to protect your AD in this FREE masterclass!REGISTER NOW - Thursday, December 2, 2021 @ 1 pm ET

Active Directory (AD) is leveraged by over 90% of enterprises worldwide as the authentication and authorization hub of their IT infrastructure—but its inherent complexity leaves it prone to misconfigurations that can allow attackers to slip into your network and wreak havoc. 

Join this session with Microsoft MVP and MCT Sander Berkouwer, who will explore:

  • Whether you should upgrade your domain controllers to Windows Server
    2019 and beyond
  • Achieving mission impossible: updating DCs within 48 hours
  • How to disable legacy protocols and outdated compatibility options in
    Active Directory

Sponsored by: