Page 1 of 1

Can't change IP of host-only network adapter

Posted: 1. Feb 2014, 13:40
by Hawkeye83
Hello!

I did quite some research on the topic, but couldn't find an answer yet. If I missed it, please kindly point me to the topic...

I have VirtualBox 4.3.6 on Win 8 64 bit as host.
When I change the host-only network adapter IP (under VBox -> File -> Preferences -> Network -> Host-only Networks) and set an IP address, the dialog accepts it but after saving and re-opening the Preferences, it gets back to an APIPA IP (169.254.x.x). Ipconfig also reveals that windows uses it's fallback.

Trying to change the adapter's settings in windows (network connections => VirtualBox Host-Only Network => Properties => IPv4) just gives an error saying "In order to configure TCP/IP a network adapter must be installed and active" (sorry, it's in German and I just translated it - see attachment).

Thanks for your help!
Simon

Re: Can't change IP of host-only network adapter

Posted: 1. Feb 2014, 13:53
by mpack
Please provide the output of "showvminfo" as described in:
Minimum information needed for assistance.

Re: Can't change IP of host-only network adapter

Posted: 1. Feb 2014, 14:10
by Hawkeye83
Sorry, my bad.
See attachment.

Guest is Win 2012 Server 64bit with Guest Additions installed

Simon

Re: Can't change IP of host-only network adapter

Posted: 1. Feb 2014, 17:04
by mpack
Ok, please show the result of "ipconfig /all", run on both the host and the guest.

Re: Can't change IP of host-only network adapter

Posted: 2. Feb 2014, 12:20
by Hawkeye83
Here are the ipconfig results of both host and guest.
Virtualbox Network config is attached as well.
Whenever I change the "adapter" settings in virtualbox, these can be saved but upon reopening these are reverted to the APIP address.

Thanks!
Simon

Re: Can't change IP of host-only network adapter

Posted: 2. Feb 2014, 12:22
by Hawkeye83
uhm... after numerous tries, it now worked!!! I have no idea why, but it's working now... =)
What I had to do (and I think I did it before, but still with V 4.3.4): Completely shut down all the VMs, close VirtualBox and then startup again.

So... I guess, case is closed!

Thanks for your support!