virtualbox.org

Hello guys,
My first post here.

I've been successfully using the following VirtualBox configuration for months, maybe years now:
- Host: Windows 7 64bit
- Guest: Different distros of Linux, 64bit, especially Debian-based, usually Ubuntu family (desktop, server), sometimes Xubuntu or Lubuntu.
- Network #1: NAT (with default settings)
- Network #2: Host-only (with default settings); the internal DHCP would always assign the IPs: 192.168.56.101, .102, .103...
I cannot remember a single problem with host-only connection before (other than some networking/configuration problem that I caused myself).

Unfortunately, for a couple of days I haven't been able to connect from the host to the guest machines using Host-only network connection! I am not 100% sure, but it is very likely the problem begun with the upgrade of VirtualBox to 4.2.4.

This happens with all the guest machines. The guest machines are properly assigned IPs, just like this:

Code: Select all

eth0      Link encap:Ethernet  HWaddr 08:00:27:37:3e:11  
          inet addr:192.168.56.103  Bcast:192.168.56.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe37:3e11/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:96 errors:0 dropped:0 overruns:0 frame:0
          TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:15974 (15.9 KB)  TX bytes:8479 (8.4 KB)

eth1      Link encap:Ethernet  HWaddr 08:00:27:64:e6:0c  
          inet addr:10.0.3.15  Bcast:10.0.3.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe64:e60c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:180 errors:0 dropped:0 overruns:0 frame:0
          TX packets:193 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:117591 (117.5 KB)  TX bytes:20378 (20.3 KB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:84 errors:0 dropped:0 overruns:0 frame:0
          TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:8830 (8.8 KB)  TX bytes:8830 (8.8 KB)

The address 192.168.56.103 is properly resolved within the guest machine (for example when I type it in the guest OS browser's address or ping it from within the guest). But it doesn't work from outside, Windows 7 host cannot access the 192.168.56.103 address, cannot ping it. The problem is not helped with the installation of guest additions, installation of updates etc.

The NAT-based connection to the Internet from the guest machines works fine.

Are there any other people out there experiencing the same problem? Have you found any solution, yet?

Looking forward to any suggestions,
Thanks a lot!

What do you get with running "IPCONFIG /ALL" on the host?

Obviously you ought to see an address of 192.168.56.x on the host-only adapter, so that it is actually on the same subnet as your VMs. However, equally obviously it ought to be working and it isn't, so /something/ is wrong and this is an easy place to start looking.)

I can confirm this problem. After upgrading from 4.2.0 to 4.2.4, access from host to guest under Host-Only configuration is no longer working. The behavior is rather strange, just after starting the guest machine, access from host is okay, but after a little while, it is not. If I login into the guest machine and keep pinging the host, then accessing from the host to guest is avaliable again.

Hi, I just would like to ask if this issue has been solved already. I upgraded to 4.2.6 and the host-only is not working. Please advise.

Thanks in advance.

Hi, I just would like to inform you that I found the fix. Please follow the link: http://blog.techprognosis.com/2011/02/2 ... box-4.html

Regards.

The site Tech Prognosis is inaccessible to me due to security constraints in our organization. Could someone post a quick summary/guide as to what the solution was. I too have been having this problem since I upgraded.

This also seems to be the case in version 4.2.6 r82870

Well the link is not a fix, it tells you to use NAT instead of Host-only, and redirect you to the user manual...

A long series of "it doesn't work for me too" is not going to help anyone. Ken Hagan asked a sensible question right at the start of the thread, which neither the OP nor the also rans have answered, i.e. what is the output of ipconfig/all? Without basic diagnostics the problem cannot be solved.

ipconfig data from both host and guest would be useful (Linux guests would use ifconfig). Also, I would suggest picking one guest OS, since a vague selection of guest will result in a vague answer.

Hi,

I am also facing the same problem, I am running VBox 4.2.6 on Windows 7 64bit host. my "ipconfig /all" shows that

Ethernet adapter VirtualBox Host-Only Network:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
   Physical Address. . . . . . . . . : 08-00-27-00-84-82
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::75ed:2ef:b0a3:2a49%33(Preferred)
   Autoconfiguration IPv4 Address. . : 169.254.42.73(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 470286375
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-F1-64-FC-B8-AC-6F-C5-22-1E
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

So my host instead of using IP 192.168.56.1 it is assigned with 169.254.42.74. If I use DHCP instead of assigning static IP(192.168.56.1) my host is getting 192.168.56.102 and I am able to ping my guest at 192.168.56.101.

Anyone know why my host is picking 169.254.42.74 IP and how can I fix it?

It means that for some reason the Host-Only interface was not provided with an IP and therefore fell back on a static IP designed for that purpose.

What happens if you disable than re-enable the interface in the network & sharing center?

I am having a similar issue. Unable to install Oracle Virtual Box on my machine correctly. The VirtualBox Ethernet Adapters do not appear to be correctly installing. When I try to create a host-only network manually I get a Failed to create the host-only interface error. Once installed the adapter should be there automatically.

I have tried installing this by right clicking and running as administrator, installing as the admin user. Installing several different version of virtual boz. Repairing a current installation. There are no errors or prompts during virtual box installation letting me know that an issue has occurred.

For some reason I am not even getting the Virtual Box Ethernet Adapter to install on my machine (wont show up in ipconfig). I have gone to device manager and have pointed the adapter to the netadp inside the virtual box folder. I get an insufficient system resource error when I do that.

Any help is appreciated. I have search and tried several suggestions on this forum but still have had no luck! Thanks

I have accidently solved my problem today. It turns out I was using static IP configuration inside the GUEST with a globally started VirtualBoxDHCP server. After turning off the DHCP server from the HOST, all the networks are now imediatedly work. Hope this could help someone.

My config - windows 7 64 bit.
Loaded virtual box 4.3.12, PSoft 9.2 FS - oracle linux is the guest.

The Oracle linux uses dhcp.
ifconfig returns 192.168.56.101
Using the Host-Adapter Only/VirtualBox Host only.

From WIndows I cannot ping 192.168.56.101.
Cannot get to the PSOFT website at 192.168.56.101:8000

Solution - WIndows Control Panel - Networking.
There is a an adapter there when the VirtualBox is running called VirtualBox Host-only Network.
When I open it and look at the properties for TCP/IP it is set to static IP of 192.168.56.1
Change the setting to DHCP on THIS adapter and bada-bing all of a sudden it is working.

virtualbox.org

Host-only, no access, Win7 host, Linux guests, VB 4.2.4, 64b

Host-only, no access, Win7 host, Linux guests, VB 4.2.4, 64b

Re: Host-only, no access, Win7 host, Linux guests, VB 4.2.4,

Re: Host-only, no access, Win7 host, Linux guests, VB 4.2.4,

Re: Host-only, no access, Win7 host, Linux guests, VB 4.2.4,

Re: Host-only, no access, Win7 host, Linux guests, VB 4.2.4,

Re: Host-only, no access, Win7 host, Linux guests, VB 4.2.4,

Re: Host-only, no access, Win7 host, Linux guests, VB 4.2.4,

Re: Host-only, no access, Win7 host, Linux guests, VB 4.2.4,

Re: Host-only, no access, Win7 host, Linux guests, VB 4.2.4,

Re: Host-only, no access, Win7 host, Linux guests, VB 4.2.4,

Re: Host-only, no access, Win7 host, Linux guests, VB 4.2.4,

Re: Host-only, no access, Win7 host, Linux guests, VB 4.2.4,

Re: Host-only, no access, Win7 host, Linux guests, VB 4.2.4,