[vbox-dev] Host-only network not working for the VM that boot up first
Valery Ushakov
uwe at stderr.spb.ru
Tue Sep 15 14:41:07 UTC 2015
Simon Xu <xu.simon at oracle.com> wrote:
> I'm having a problem with Windows 10 and Virtualbox 5.0.4 (102546). In
> my setup, host-only network doesn't work for the VM that first boot up,
> the VM uses static IP for host-only NIC, e.g. 192.168.56.100, now if you
> ping this IP from Windows, it just timeouts. Now if you start the
> second VM with static IP (say 192.168.56.101) for host-only NIC, you can
> ssh from Windows to this VM, and host-only networking between
> 192.168.56.100 and 192.168.56.101 works fine.
Isn't .100 address used by the DHCP server for the host-only network?
I.e. you have an address conflict.
> Is there a better, once-and-for-all, workaround to fix it?
Don't use .100?
-uwe
More information about the vbox-dev
mailing list