[SOLVED]Network settings are changed every time on startup

[joerch]

Hello,

I have some trouble with the new version of virtualbox. After upgrading from VirtualBox-4.1.6-74713-Win to VirtualBox-4.1.10-76836-Win I have to type the IP adress in the global settings again. The Host-Only-Adapter has the ip 192.168.56.1 and in the global settings I have typed this address too.

After starting virtualbox again, there is a different ip address. In the VirtualBox.xml is the ip address as mentoined above. So whenI have to work with virtualbox, I always have to change the ip address in the global settings back to 192.168.56.1 .

What can I do?

With kind regards

Joerch

Host win7

[mpack]

What "global settings" are you referring to? You mention both Host Mode IP address and global IP address. Are you using both terms to refer to the same thing?

If yes, then I find that v4.1.10 on my system is using 192.168.56.1 as the host address for host-only networking. I agree that in past versions I think I've seen this number jump around, but I didn't write down the details, I just fixed them. I think the last number has sometimes been 100, with guests getting 101, 102 etc.

[joerch]

To be more clearly:

these are the settings for the "VirtualBox Host-Only Network" in the networksettings of win7. See attached file win7nwtwork.png

And here are the settings of virtual box as they have to be, but this is changed after every restart manually. See attached file vbox_settings.png

[Perryg]

I remember seeing this on a Windows host before. I fixed it by deleting the host only adapter (in the preferences) and creating a new one with the proper addresses. Just changing it would not save on boot.

[joerch]

I have tried this. Deleting it form VirtualBox. Deleting it on the networkconfiguration of win7. With reboot, without reboot.

No chance. When I start virtualbox for the first time after reboot, I have a new ip address in the virtualbox configuration.

[mpack]

Do you have admin rights on this PC?

Have you done anything strange, like trying to use Windows bridged feature (not to be confused with the VirtualBox Bridged Adapter feature) to bridge to the host-only NIC?

[joerch]

Yes, i have admin rights. And no, i only updated from a previous version of virtualbox.

It worked with the previous version

Joerch

[joerch]

does anybody have a solution for my problem?

[Perryg]

There was some work done in the host-only area and a new version is available. 4.1.12. I would upgrade and see if that fixes your issue.

[mswvette]

I am having the same issue with 4.1.12r77245 It saves the dhcp settings but not the ip. I also had trouble when delete it and creating a new one.

I just created a second host only adapter and was able to set the values.

I had the problem on the previous release and also created a second host only adapter but when I upgraded to 4.1.12 my second adapter was deleted and I got errors saying the second adapter did not exist when I started a vm. The second adapter was removed from the vm.

[joerch]

With updating to 4.1.12r77245 the problem is solved

[offler]

Sadly i'm using 4.2r81870

The stupid thing changed from 192.168.56.1 to 169....

I change it back to 192.168.56.1 in global setting and every restart i have the wrong adress again.

Also this thread is a year old, I think it is the same problem, it maybe just only be solved / appear again by accident ?


---
The main problem is, that it has taken literally days to perfectly put a network simulator to work in virtualbox - and it only really works in actual state with actual ip adresses. Therefore the changed ip address is a really show stopper. (changing the general network adapter each time is a short, but overall time consuming task)