Simon Xu <[email protected]> wrote: > On 2015/9/15 22:41, [email protected] wrote: >> Simon Xu <[email protected]> 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. > > No, dhcp server is disabled. And the issue still exists when I don't > use .100 for the VM.
File a bug with packet traces as captured in the guest. -uwe _______________________________________________ vbox-dev mailing list [email protected] https://www.virtualbox.org/mailman/listinfo/vbox-dev
