Page 1 of 1
[2.2.0] Problems with host-only network and dhcp
Posted: 16. Apr 2009, 15:45
by D4r
Hi,
I just downloaded the new version of virtualbox (2.2.0).. everything went fine, but when i started the guest the first time i noticed a strange problem and i can't figure out how to solve it.
Pratically, if i set a static ip on the guest (Windows XP SP3) everything works as intended, but if i set it to obtain an ip via dhcp it sets the ip as "192.168.56.101" (it should be instead like "192.168.0.x").
If i run ipconfig /all i see that the dhcp server is set to "192.168.56.100" instead of "192.168.0.4"
This is very strange because we don't use such type of network and all worked fine with the previous version 2.1.4
This is what i did:
- Updated VB to 2.2.0
- Re-Created a bridged network between the server and the host-only network card (win 2003 R2 SP2)
- Ran the virtual machine
Can you help me please?
Thank you.
Re: [2.2.0] Problems with host-only network and dhcp
Posted: 16. Apr 2009, 15:56
by Perryg
If you are using Bridged in the guest you should not need the host -only connection as it will use the IP range you are seeing. Drop the second adapter and see if this helps.
Re: [2.2.0] Problems with host-only network and dhcp
Posted: 20. Apr 2009, 10:52
by D4r
Sorry, but i don't understand what you mean... drop what adapter?
This is the result i wish to achieve:
Host (win2003): static ip set to 192.168.0.11 (255.255.255.0)
Guest (wiXP): automatic ip (through DHCP) -> 192.168.0.x (255.255.255.0)
As i said in my first post, it worked fine with 2.1.4 (using a bridged network), now it doesn't.
Where am i wrong?

Re: [2.2.0] Problems with host-only network and dhcp
Posted: 20. Apr 2009, 12:02
by vbox4me2
D4r wrote:This is what i did:
- Re-Created a bridged network between the server and the host-only network card (win 2003 R2 SP2)
For what reason did you do this? Bridge mode (used to be Host interface networking) is enough.
Re: [2.2.0] Problems with host-only network and dhcp
Posted: 20. Apr 2009, 17:21
by Sasquatch
D4r wrote:Sorry, but i don't understand what you mean... drop what adapter?
This is the result i wish to achieve:
Host (win2003): static ip set to 192.168.0.11 (255.255.255.0)
Guest (wiXP): automatic ip (through DHCP) -> 192.168.0.x (255.255.255.0)
As i said in my first post, it worked fine with 2.1.4 (using a bridged network), now it doesn't.
Where am i wrong?

You mis-interpreted the new networking options. Please read the manual again, Host-Only is added in 2.2.0 and Host Interface is renamed to Bridged.
Re: [2.2.0] Problems with host-only network and dhcp
Posted: 20. Apr 2009, 18:05
by mrui
Good afternoon.
I have the same problem since I've installed the 2.2.0 version. Yes you were right when you said that we didn't properly read the manual, but the names were so close that I didn´t detected the difference. The problem that I have now is that when I try to select the attached Bridged Network it always tell me that there is an error "no bridged network adapter is selected” but it does not let me select anything, it doesn’t show any adapters to select. On the manual is only “Finally, select desired host interface from the list at the bottom of the page, which contains the physical network interfaces of your systems”. But there is nothing on the bottom of the page, just the error message. If I open the extended settings dialog I have the same problem, there is no options to select on the Bridged Network Adapter.
What do we have to do to configure this, what steps do I need to do? Am I missing something?
Thank You for your help
Re: [2.2.0] Problems with host-only network and dhcp
Posted: 20. Apr 2009, 18:14
by Perryg
In the VBox gui when you are in the network settings look to the right of the Attached to: and you should see a little screw driver. Click that and you should see your selectable adapter.
If you do not see this something happened during install/upgrade.
Reinstall VBox 2.2 (as admin) and select the repair option.
Re: [2.2.0] Problems with host-only network and dhcp
Posted: 20. Apr 2009, 18:54
by mrui
It worked perfectly. You can't imagine how many atempts I made these last four days to solve this problem. I tried everything, well not everything I didn't remember to install the VirtualBox again...
By the way I needed (at least I think I need) this network setting because I'm using a Windows 7 (32bits) guest system on a Windows Vista 64bits host, to be able to connect to my workplace using a Cisco VPN connection, that doesn't work on 64 bits systems.
Thank you again,
Mário Pereira