Virtual Machine in VM Workstation networking conflict

Recently I upgraded my lab environment to VMware Workstation 11. After the upgrade I turned on the machines from hibernation and everything was working correctly. The next day after I rebooted all my machines all my member servers could not connect to the domain controller. Al my machines are connected trough the NAT network, and DHCP on VMware Workstation is disabled.

In my Windows Server 2012 R2 guest OS for my domain controller I’ve configured a static IP address as displayed in the picture below:

2015-04-30 10_24_48-DC01 - VMware Workstation

With this configuration my domain should work. Just to be sure I also ran an ipconfig /all from the prompt. This command gave the following output:

2015-04-30 10_23_23-DC01 - VMware Workstation

The above image shows that although there is a static IP address configured somehow it still places a DHCP request because autoconfiguration is enabled. Because there is no DHCP server active in this vLan Windows is presented with a Automatic Private Internet Protocol Addressing (APIPA) address. I found this behavior to be very annoying because now my virtual domain was not working. So I consulted my good friend Google and came up with a solution.

First we need an elevated command prompt to start working towards a solution.

2015-04-30 10_36_46-DC01 - VMware Workstation


show inter

set interface 14 dadtransmits=0 store=persistent

During the execution of these commands you will receive a message that there is now a PowerShell cmdlett for these commands. For now I will stick to the command prompt code.
As a last step for this change you need to disable the DHCP client for this network interface.2015-04-30 10_35_46-DC01 - VMware Workstation


Now when I execute an ipconfig I see the correct IP Address:


Geef een reactie

Het e-mailadres wordt niet gepubliceerd. Vereiste velden zijn gemarkeerd met *