Unless you're using the vagrant-windows plugin, its not going to set the static IP for you. Vagrant-windows will handle this for you (with VirtualBox) by running the appropriate netsh commands.
On Wednesday, January 15, 2014 2:53:39 PM UTC-8, Nicholas Chappell wrote: > > Pretty much what the title says. > > At first, I thought it was because of a lack of UAC/admin privs, but I > noticed when booting the VM that I would get the little pop-up balloon in > the lower right saying that a new network adapter was added. I presume this > means that Vagrant was able to successfully create the adapter? > > If I go into the Network and Sharing Center in the Control Panel and set > the static IP there by hand, everything works (can ping the VM on the > host-only address from other VMs and the host machine). The VM can reach > the Internet through the VirtualBox NAT adapter just fine. > > Host-only adapters/addresses on Linux VMs work just fine. > > Any ideas as to why Vagrant can't set the static IP automatically? > > VirtualBox version: 4.3.6 > Vagrant version: 1.4.3 > OS X 10.9.1 host, Windows Server 2008 R2 w/SP1 as the guest. > > Would debug output from `vagrant up` be helpful? > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
