virtualbox.org

Running VBox on Win7 Home Premium 64-bit. Hosting a variety of clients - linux, Solaris, Win Server

Had the host only adapter set at 192.168.56.1 with mask of 255.255.255.0.
Have all my clients (which are emulating servers) binding eth0 to the host-only adapter, with fixed ip addresses beginning at 192.168.56.101

Decided to follow up on the nagging pop-up and upgraded from 4.2.16 to 4.2.18.
Now my host only adapter is set at 169.254.27.57 with a mask of 255.255.0.0

Where did VBox come up with that?
And why didn't it honor the existing setting?

What's worse, when I go to Settings -> Network to reset it, it seems to go through the motions (Windows ask for permission to allow it), but in the end, nothing changes.

Set the IP and the mask using the Virtualbox Manager, in the menu : File - Preference - Network.
Select the host-only interface, and click on the orage screwdriver on the right.

Virtualbox will automatically overwrite the interface config with the ones saved in Virtualbox, which is why they don't stick if you configure it via Windows directly.

noteirak wrote:Set the IP and the mask using the Virtualbox Manager, in the menu : File - Preference - Network.
Select the host-only interface, and click on the orage screwdriver on the right.

Virtualbox will automatically overwrite the interface config with the ones saved in Virtualbox, which is why they don't stick if you configure it via Windows directly.

That's exactly what I did.
I don't even know how one would "configure it via Windows directly".

I finally completely deleted the adapter (again, from the VBox management console) and recreated it, giving it the IP address and net mask I have been using all along. That worked until the next time I restarted the PC (host). I again deleted/recreated the adapter. We'll see how well that stuck when I get home this evening.

And to follow-up from my last post ... the IP address of the VBox adapter changed itself again.
Next attempt, I un-installed VBox 4.2.18, then installed v 4.2.16.
The install gave me a "cannot rename this connection" pop-up. When that completed, I had an adapter identified as "Ethernet adapter Local Area Connection 3:" with my original address of 192.168.56.1.

Vbox management console started, and -- without my telling it where they were located -- recognized the four vm's I had previously created. This surprised me, because they are not in the default location. Everything *seems* to be working now, except of course that the VBox adapter is not reported as such by ipconfig ..

This is all very strange.