virtualbox.org

So last night I had my virtaul network all setup. This morning I decided to decrease the amount of ram on my VM Server and it went to # so I started fresh plugged in the same IP as before and got nothing...I have now cleared out all of my IP leases so I wont run into a conflict left VirtualBox settings unchanged (besides adding a bridged adapter).


Here are my settings:
VM Host adapter = 192.168.56.1 (default)
I would like for my server to have a static IP of 192.168.1.100
My address pool will be 192.168.1.150

This is just a test environment so I can get more familiar with GPO's capturing and deploying images etc...

As a note, I did not change and IP settings on my main box since last night when I went to bed everything was perfect.

I wish I would have wrote down my settings last night before I deleted Virtualbox...

192.168.56.1 is the VBox host-only adapter. If you are using Bridged you don't even need this enabled in the guest settings.
You also don't want it to be the hosts default adapter if that is what you have now. Disabling that in the guest and a reboot of the host (cold boot, shut down) should clear this.

Perryg wrote:192.168.56.1 is the VBox host-only adapter. If you are using Bridged you don't even need this enabled in the guest settings.
You also don't want it to be the hosts default adapter if that is what you have now. Disabling that in the guest and a reboot of the host (cold boot, shut down) should clear this.

So completely disable VM box's adapter do a restart of my Host box should clear this...Should I delete it from within Virtualbox as well....Last night I swear I just plugged in 192.168.1.200 into the server and it worked

Steps I should do just so we are clear
Disable the VirtualBox adapter, restart my machine and then set the static IP in VirtualBox?

As I said in the VirtualBox settings for the guest, disable the host-only adapter and just leave the Bridged adapter.

If however you do not have the host-only adapter enabled in the guest settings then I would suggest that you disable/delete the host-only adapter in the VirtualBox preferences so it is not being used. Then cold boot the host.

That did not work.

OK on the host and from a command Windows type ipconfig /all and post the results here.

Also, post the guests log file (as an attachment)
See Online Users Manual for the location of the file.

Here is everything in a zip attachment

Two more things please:
From the guests command window post the results of ipconfig /all (hint if you right click the command window title bar and then click edit you can copy the text to a text file).

Also

From the hosts terminal/command window type VBoxManage showvminfo <VM Name> --details and post here. Replace <VM Name> with the actual name of the VM. Use " " if the name has a space in it.

Note if the host is Windows you need to be in the directory that has VBoxManage.exe for the command to work.

Here you go

I double checked my DHCP leases on my router and I have 192.168.1.100-192.168.1.253 open

Everything seems to be working as it should be. The guests is set to use 192.168.1.101
So what is not working for you?

You are not using DHCP so that will not matter if it is open, unless you have to use it to get a connection. If so you need to enable it in the guest network settings, but that is going to stop static addressing.

getting out to the net

From the guests command window can you ping yahoo.com and does it reply?
The ping 98.138.253.109 and see if that replies.

Here you go

If I click the red X it will set my IP back to dynamic

Then there is something wrong at the router. If the address will only work with DHCP you need to see how to set static addresses. Probably one that is not in the DHCP range.

Just so you know this has nothing to do with VirtualBox. Using Bridged the guest operates like another PC on the LAN.