virtualbox.org

So, prior to a power outage, my Vbox VM (Ubuntu 16.04.3) IP was 192.168.0.9. My host is Win 7.

After the power came back on, the IP changed to 192.168.0.10! I have never seen one of my VM's IP change before! Never!

Now when I try to browse to 192.168.0.10, the browser tries to go to 192.168.0.9! Of course there is no longer a .9 IP.
FYI I have a webserver on multiple VM's and this is the only one I can't browse to. This happens in Firefox and Chrome.

I can ping .10 from the host just fine!
I can ping between this VM and other VM's.

I can browse to another VM.

I rebooted the host but that did not fix it.

Any ideas what is going on?

And I have been using Vbox a long time with no issues.

Rayj2016 wrote: I have never seen one of my VM's IP change before!

Are the IPs static or dynamic?
Wild guess? Dynamic. They will change. That's the idea...

I also rebooted the modem. That did not help.
The modem now seems to be dishing out new IPs? I know DHCP will dynamically reconfigure IP addresses but the IP's never seemed to change in the past. Only after this power failure we had, the IP's are now being
changed by DHCP.

My windows host LAN IP had been 192.168.0.2 what seems like forever, but now it is 192.168.0.4??

I have VM's with the same IP for months....and I power the LAN down every night. Like 192.168.0.29 is now 192.168.0.8 and I can no longer browse to it?
The error I am getting is: The server at 192.168.0.29 is taking too long to respond. WTF? I do an ifconfig on the VM and it says 192.168.0.8, yet the
browser thinks it is 192.168.0.29?

I manually changed this VM IP to 192.168.0.29. Now I can browse to it. Reboot this VM and the IP goes back to 192.168.0.8 and I cannot browse to it?


HELP!!!!

socratis wrote:

Rayj2016 wrote: I have never seen one of my VM's IP change before!

Are the IPs static or dynamic?
Wild guess? Dynamic. They will change. That's the idea...

They are on DHCP and I understand DHCP, yet the IP's have always stayed the same.
But the problem is the old IP is being retained somewhere because when I browse to the new IP, I get an error message about the old IP.

Ray

I play around a lot with VM's and have fired up plenty of them over the last year. They always got a DHCP IP and retained it.
In fact I am looking at a few of the VM's and they have their original IP addresses!

Rayj2016 wrote:They are on DHCP and I understand DHCP

No you don't. In particular you don't seem to understand the "D" part.

This is NOT a VirtualBox problem. VirtualBox has absolutely nothing to do with that, no matter what used to "work", or what you think might be working. There's a lease in the DHCP server. That hasn't expired, therefore making all your IPs look as occupied.

Shut down every computer and router in your house/work for 48 hours. The problem will be fixed.

I'm pretty sure I mentioned the D part. And I understand the difference between static and dynamic. My modem DHCP lease is set to 3600!
I have never...NEVER...did anything to the configuration of my modem/router. It dished out IP's as soon as I created a VM. And like I said,
I have never seen an IP change from then on. However a power failure today did something. I just don't know what.

And BTW, I never blamed Vbox. I just thought I'd post here for an explanation of why my IP"s are now all screwed up!
Shutting down my computers 48 hours is not an option. And it should not be.

Rayj2016 wrote:I just thought I'd post here for an explanation of why my IP"s are now all screwed up!

1) I already explained it to you, the leases have not been cleared/expired.
2) If you want to take out the "D" (ranDom) part, start assigning static IPs. That's not even up for discussion.
3) The VirtualBox forums are for VirtualBox problems. Not all computer related issues, it would be chaos otherwise.
4) The 48 hours suggestion was a tongue in cheek answer.