isolating VM's for DHCP testing RRS feed

  • Question

  • Here is what I'm trying to do.

    I need to test interactions of a DHCP server on Sever 2012 with End Point Protection from Symantec, which blocks the DHCP. service

    I'm using Hyper-V on win10.

    I need to avoid collision with the local AD, and it's DHCP / DNS, so the test needs to be isolated from the LAN

    I created 2 VM, set them on the same 'internal' or 'private' virtual switch, and test.

    I installed Server2012 on one VM, attached it to an internal switch, and assigned it a fixed IP4, and then installed DHCP and DNS.

    When I attach a Win10 VM to the same virtual switch, it does not pick up an IP address from the VM DHCP server, and comes up with the default 169... IP address.

    the same result obtains on either internal or private virtual switch.

    What am I doing wrong?

    David L.

    Tuesday, May 2, 2017 8:32 PM


  • OK, my bad

    the issue is not in the switches, but in not adding a DHCP zone to the DHCP server, no zone, no service

    • Marked as answer by David Len Wednesday, May 3, 2017 3:12 PM
    Wednesday, May 3, 2017 3:12 PM