virtualbox.org

Hi,

I am using VirtualBox 4.2.16 on Windows 7 64 Host. I created two Windows 7 64 bit vms, and configured them to use "Internal Network". Name of the internal network used for both virtual machines is 'GAME'. But when I ping one virtual machine from another virtual machine, it fails (I tried it both ways, and it failed both ways ). Do I have to change any other settings to enable these two virtual machines to talk to each other?

Thanks,
Amruth Kumar Juturu.

Ping is not a good way to test network connectivity with modern systems - most built-in firewalls block ping by default. You will need to disable the firewalls or modify them to allow ping.

BillG wrote:most built-in firewalls block ping by default

That's a bit too sweeping. There's really only one company out there that thinks blocking pings is a great way to help users. But yes, the OP would be certainly affected

Thank you. My bad. I should have checked firewall myself first.

Hey ..
I am using two VMs as RHEL6 on ubuntu 13.04 host.
I am unable to communicate from One VM to another VM.
As i read in other posts that i enabled network adapter and selected internal network in both VMs...But when i started those VMs..First VM network is connecting and giving me 10.0.2.16 ip address.
But the second one is not allowing me to connect with eth0. I found it loading and loading....

So...what should i do now..???
Please guide me....


Thanks
Varun

10.0.2.16 sounds like a NAT IP address to me. Are you sure that the NIC is set to internal networking? Are both vms using the same internal network (the default is intnet)?

If you have not set up the internal network to use DHCP you may need to configure the NICs in the vms to use static IP addresses in the same IP subnet. I don't know what redhat does by default. (Windows would use APIPA which would work in this case).

Hi..
I have installed two VMs named server106 and server206.
Both are RHEL6.
In server106, I have enabled two adapters. One is NAT and another one is Internal network and named "intnet".
After booting it, i am getting connected with eth1 and i am getting ip "192.168.122.106"

In server206, i have done the same configuration.
But it is not letting me to connect with eth1 that is internal network connection named "intnet". Its loading and loading......
And i have tried it with different name "intnet206"...still it is loading and loading...

I went on following file and i got the following output :
vim /etc/sysconfig/network-scripts/ifcfg-eth1

O/P :
DEVICE="eth1"
HWADDR="08:00:27:24:AE:7D"
NM_CONTROLLED="yes"
ONBOOT="no"

I have changed ONBOOT to yes and restarted the system but still it loading and loading....i am unable to connect with that eth1..

Please guide me...
What should i do now...

That sounds like a problem with the OS in the vm. How did you create them? Is vm2 a clone of vm1?

If it is not a clone, I would delete it and start again. Recreate the vm and reinstall the OS.

When you get the NIC working you will have to use the same network name on both vms. If you use different network names, the machines will not be in the same network.

I'm also using Windows 7 x64 as Host. I have (2) 32-bit VMs setup (successfully pinging each other) using XP with SP3 and Server 2003 R2 32-bit. Here's how I did it:

1. Firewalls turned off in both VMs guests.

2. Successfully used VirtualBox DHCP to assign IPs to both VMs. To make this work, as mentioned above, used command-line as such:
vboxmanage dhcpserver add --netname intnet --ip 192.169.56.1 --netmask 255.255.255.0 --lowerip 192.168.56.150 --upperip 192.168.56.160 --enable

You can, of course, use whatever ip addresses you want, these are just the ones I happened to use while testing this out.

To view your settings after setting up a DHCP server for "Internal Network", just use command-line: vboxmanage list dhcpservers

3. Next, turn off all VM guests, then go into the VirtualBox Manager. For each VM guest, go under "Machine|Settings|Network", put a check in the box beside "Enable Network Adapter"; set adapter to "Internal Network"; set Name to "intnet", or whatever name you used above in the command-line that followed "--netname"; set Promiscuous Mode to "Allow All", just in case; be sure "Cable connected" is checked. Again, do this for *both* vm guests, or however many beyond 1 you're using.

4. Vbox documentation mentioned that if you create a DHCP server for "Internal Network", it's always set off by default, so it's probably good to go ahead and enable it while you're at it.

I was mixed up in thinking that the GUI that has Host-Only DHCP was somehow broken. I kept assuming the DHCP stuff there would work with "Internal Network," but it never would. Hmmmm. But, It finally hit me when, after running the vboxmanage command in #2 above, that the DHCP settings under VirtualBox Host-Only Ethernet Adapter *might* only be for VirtualBox Host-Only Ethernet Adapter - slow learner on this one here... but, I suddenly noticed (upon checking it) that the command above didn't change anything for the DHCP server settings under VirtualBox Host-Only Ethernet Adapter.... Wait a minute - Too much tunnel vision while working on this, but it finally clicked - ya gotta use the command-line in #2 above to setup a *different* DHCP server to use "Internal Network". Granted, the documentation didn't really spell that out anywhere clearly that I could find, I guess it just kind of hit me. There doesn't appear to be anywhere in the VirtualBox Manager window that it bothers showing you anything about this hidden DHCP server - at least, that I could find - but it actually exists, somewhere in the nether-regions of VirtualBox.

5. Now, inside each VM guest you're setting up, you should be able to just leave the networking protocols in their defaults. Each VM guest should have successfully connected to the VirtualBox "Internal Network" DHCP server and been assigned an IP address within the range you specified in step #2 above. In my case, one was assigned 192.169.56.150 and the other was assigned 192.168.56.151. I also noticed in the documentation that there was this sentence: "After this, VirtualBox will automatically start the DHCP server for given internal or host-only network as soon as the first virtual machine which uses that network is started." So, I shut down both VM guests completely and brought each back up (didn't do a restart, just shut down - too frustrated with this not working for many hours).

Lastly, to check the default in each VM guest, quickest route is just to double-click the network icon in the Windows taskbar, then click Properties, then Internet Protocol (TCP/IP). Under Windows 7, that would be "Internet ProtocOl Version 4 (TCP/IPv4)". Not sure how that's labeled in Vista or Windows 8. At any rate under that just be sure "Obtain an IP address automatically" is selected, "Object DNS server address automatically" is selected, and under the Advanced button and WINS tab, that NetBIOS setting is set to "Default:". This is of course assuming that you don't want any VM guests in your "Internal Network" connecting with the Host (in the instructions above, your "Internal Network" will be *completely* self-contained. You won't be able to ping the VirtualBox Host-Only Ethernet Adapter, nor the Host OS (Win7 x64 in my case, like akjuturub04's) - I also have my host OS setup with a static IP address, but this is for needing to connect to my home computer from a location away from home.

But, back on topic, the VMs *should* be able to ping each other successfully. Mine have been able to ping each other successfully - I did this several times, because I couldn't believe it was working - after completing the steps above. Again, one VM is XP/SP3 (32-bit), and the other VM is Server 2003 R2 (also 32-bit). In that respect I differ from akjuturub04's setup, but I'm looking at doing 2 64-bit VM guests like he's doing. I'll add a note back to this posting later as to how that goes.

Ok, on an extra note, I went into the network settings for Server 2003 R2 32-bit and changed it to a static ip of 192.168.56.130 and a subnet mask of 255.255.255.0. I also set NetBIOS to "On". I left the gateway blank, and I left the DNS servers blank. Server 2003 R2 (32-bit) then assigned itself as the primary DNS server. I can still ping each VM guest from the other VM guest (the dhcp 192.168.56.150 to the static ip 192.168.56.130 and vice-versa). No problems either direction.

Additionally, I might throw together a small program (that I'll upload/post here) for graphically viewing and setting up DHCP for the "Internal Network" network adapter, at least so that folks (myself included) have a quicker option for setting that up, rather than trying to dig command-line stuff out of the documentation. It'll just be a simple standalone GUI. That'll probably be done in the next 3 or 4 days. It'll likely be posted on SourceForge, but I'll upload a copy here as well. This will be for Windows only right now, but I may try something for Linux too.