virtualbox.org

No custom settings were used. The wizard did everything because as our first experience with Virtual Box that is all we knew how to do.

Well all I can tell you is that is not the default settings. I posted them way back in the topic. Since it is not I have no idea what happened.

Yes as I noted in my post before last, we used the settings that you provided. We followed you instructions. And we ended up with a guest with no IP address and which could not be PINGed from the host and which could not PING the HOST. Is it certain that these are the default settings for version 4.1.8? Also it sounds from your post when you add a Network adapter, that it should automagically be created with those default settings. But when we did that it did not even create it with the DHCP server enabled.

Is there another way to add the Netadapter without recreating the Virtual Machine from scratch? If not how are we supposed to fix this?

I hate to sound like a broken record but the defaults should have been created as I indicated. If it does not then there must be a reason that I am unaware of. You should be able to create the adapter and the defaults should be right, but if not you can change them to be what ever you need. If the DHCP server is the only thing that was not enabled then enable it.

The only thing that I can think of that would cause this to fail would be the Windows host may not have released/deleted the host-only adapter when you told VirtualBox to delete it. This you should be able to see in the network section of the Windows host.

I just noticed you put the wrong numbers in.

7. Entered settings that perryG reported as being the default settings. 192.168.56.1 for IPv4 of adapter and 192.168.56.100 for DHCP server IPv4 255.255.255.0 for DHCP server mask, 192.168.56.1 as lower bound of DHCP server and 192.168.56.254 as upper bound DHCP Server.

The lower boundry for the IP address range is 101 not 1 (192.168.65.101)
If this was not a typo then it would have failed as that is the same value of the hosts IP address

Made change to lower bound see below for results.
So it appears that made the difference.

With la piece de resistance


"Hurray!!! Hurree!!! For Chef Boy-R-Dee!! YAAAAAAAAY!!"

Update:

Manually setting this on the host is not suggested as it probably will not be retained after a cold boot.

I did a cold boot (a 25 minute process on these Navy machines) and all the settings were retain. Cudos to perryG.

The issue is still happening. Vagrant, Docker machine are both having the same sort of issues as reported in this thread. I am using version 4.3.30 r1010610. I briefly installed a version of 5. That did not fix the issue and so I deleted it resinstalled 4 to even get the host adapter back and after that, I could ping from the host to the vm but not from the vm out.

I tried vagrant up and it worked the first time, but the second time i get
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 => 2200 (adapter 1)
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["modifyvm", "a287ddaf-9c20-48da-9284-c42254648f08", "--natpf1", "ssh,t cp,127.0.0.1,2200,,22"]

Stderr: VBoxManage.exe: error: A NAT rule of this name already exists
VBoxManage.exe: error: Details: code E_INVALIDARG (0x80070057), component NATEng ine, interface INATEngine, callee IUnknown
VBoxManage.exe: error: Context: "AddRedirect(Bstr(strName).raw(), proto, Bstr(st rHostIp).raw(), RTStrToUInt16(strHostPort), Bstr(strGuestIp).raw(), RTStrToUInt1 6(strGuestPort))" at line 1708 of file VBoxManageModifyVM.cpp

The only way I can see to get virtualbox back to the way it was running is to reimage my machine. Unless someone has a better idea or the problem has been solved and I am doing something incorrectly.

@echeadle2,

What makes you think this is a VirtualBox issue and not a vagrant one?
Plus the error looks more like NAT than it does host-only as this topic is discussing.