Sign in
 
HomeWindows 8Windows 7Windows VistaWindows XPMDOPWindows IntuneLibraryForums
Windows Client > Windows 7 IT Pro Forums > Windows Virtual PC and XP Mode > Client VM's not getting IP address from DHCP VM

Answered Client VM's not getting IP address from DHCP VM

    •  
      Sunday, August 23, 2009 4:36 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Hi, i have a VM with Windows Server 2008 which is installed as a DC, second VM with Windows Server 2008 running DHCP and NPS and a third VM with Windows Vista. The Vista VM is not picking up IP address from the DHCP VM. If i give a static IP address to the Vista VM, then it is able to communicate with the other 2 VM's. I am using Windows 7 with Windows Virtual PC as the virtualisation software. Any pointers on this would be highly appreciated.
       

    Answers

    • Friday, October 02, 2009 12:19 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote
      It seems Virtual PC has a built-in DHCP server, which offers 169.254.0.x addresses. Strange, because this address range should be used as APIPA range, not to be offered by DHCP. The virtual machine sends out its DHCP discover packet, and receives an offer from the address 169.254.0.1. (Strange again, this address cannot be pinged.) This offer arrives sooner as the offer (if any) made by the DHCP server running on the virtual server system, and is accepted by the client operating system.

      Microsoft's representative suggested to create a loopback adapter on the host, as a workaround. Then, in the settings, bind the network adapter of the virtual machine to the loopback adapter. It works.
      mz
       

    All Replies

    • Monday, August 24, 2009 11:26 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I have the same problem Goldy; I've just left it static IP (nice). Whatever they're using as a controller for the "Internal Network" option must be killing the DHCP requests from the client.

      VDI for the win!
       
    • Friday, October 02, 2009 12:19 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote
      It seems Virtual PC has a built-in DHCP server, which offers 169.254.0.x addresses. Strange, because this address range should be used as APIPA range, not to be offered by DHCP. The virtual machine sends out its DHCP discover packet, and receives an offer from the address 169.254.0.1. (Strange again, this address cannot be pinged.) This offer arrives sooner as the offer (if any) made by the DHCP server running on the virtual server system, and is accepted by the client operating system.

      Microsoft's representative suggested to create a loopback adapter on the host, as a workaround. Then, in the settings, bind the network adapter of the virtual machine to the loopback adapter. It works.
      mz
       
    • Saturday, October 17, 2009 3:32 PM
       
       Proposed Answer
      Sign In to Vote
      0
      Sign In to Vote
      It's not killing requests, it's just replying faster than your DHCP server in the network. You can simply deny DHCP replies from 169.254.0.1 on a firewall and you'll get what you want - see http://anderwald.info/windows/windows-virtual-pc-built-in-dhcp-server-and-isa-2004/
      • Proposed As Answer by Kocureq Saturday, October 17, 2009 3:32 PM
      •  
       
    • Saturday, April 03, 2010 4:18 AM
       
       Proposed Answer
      Sign In to Vote
      2
      Sign In to Vote

      Instead of installing a loopback adaptor, another way is to simply disable the DHCP option by modifying the option.xml in 

      C:\user\<username>\appdata\local\microsoft\windows virtual pc

      change the boolean value of <dhcp> in the <internal network>portion from true to false will do the trick.

      Hope it helps

      • Proposed As Answer by Kocureq Sunday, June 13, 2010 7:13 PM
      •  
       
    • Sunday, April 04, 2010 12:28 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

        Goldy,

         How is the networking configured? Are the vms all in the same virtual network? Is the DHCP server authorized in AD?

        169.254.x.y addresses do not come from a DHCP server. They are APIPA addresses which are assigned by the OS itself. (You can disable this in the registry). This happens if the machine is set up to get its network config automatically but no DHCP server can be found (ie no replies received when a dhcp discover broadcast is sent).

      http://www.petri.co.il/whats_apipa.htm

       

       

      Bill
       
    • Sunday, June 13, 2010 7:14 PM
       
       
      Sign In to Vote
      1
      Sign In to Vote
      Too bad you didn't do any research before answering. As MVP, you have a lot of influence on people's thoughts and opinions. There IS a DHCP server in VirtualPC, assigning addresses from APIPA range.