Netowrking playing up - 2.2.0 Vista Host, Ubuntu Guests - All sorts of wierd behavoir

[Stefan]

Hi there,

I have installed 2.2.0 r45846 and have been battling to set up a simple 4 node network for days now. My guest machines are Ubuntu 8 running on a Vista Ultimite host.

Netowrk adapters of guests set to connect to NAT I havde a Virtual Box Host only network on windows connections which seems to be doing nothing, it is given a 169 address and its properties freeze when I try and open it. A super frozen mode that task manager can't even handle. No matter what I do I cannot set static IPs (that work) and can only use DHCP which receives the same 10.0.2.15 on each VM (along with the other similar addresses mentioned in this that dont make much sense) and only allow me to connect to the internet from my hosts and occasionally ping eachother.. but they all have the same IP address so thats not too much to get excited about!

I have read through some other tickets, my question is: What do i do? Do i: a- re install VirtualBox? b- use the updated DLL files? c- roll back VirtualBox to the older version? d- download something else that will fix it that i've misses? e- forget virtual machines and buy 4 real ones f- none of the above

Congratulations on your sale to Oracle, lets hope they invest heavily in VirtualBox.

Your help is much appreciated.

Stefan

[Frank Mehnert]

Stefan, the host-only network problem is probably related to general installation problems of VirtualBox 2.2.0. As for the NAT problem: Keep in mind that each VM lives in their own NAT network. The default IP for the guest is 10.0.2.15, the host can be reached with 10.0.2.2. VMs which which are connected through NAT to the outside can talk to the host and to other remote hosts but they can never talk to each other. Having several VMs within the same NAT network is a planned feature. If you want to allow to talk VMs then you could enable an additional internal network to each VM. Or attach all VMs to the same host-only network but you said this didn't work. You might want to wait for the next maintenance release which is hopefully released within the next days.

[Stefan]

Thanks a lot for your swift response

Regards Stefan

[misha]

Re Host-Only adapter: it is only used for the host-only networking (i.e. host + one or more guests connected to one private virtuaal network) and is unrelated with NAT.

Re its 169 address and a limited network connectivity warning - this is a known issue (see #3670) we have a fix for it locally and I should be able give a test build with the fix soon.

What properties do you see frozen: is it a network connection properties or device properties? In any way I've no idea for now what makes it freeze since no VBox code is involved in displaying it. Do properties for other network adapters work OK for you?

[Stefan]

Frozen issue solved.. with a restart! Windows ay. Thanks

[Stefan]

Hi, ok thanks for the advice, I have enabled a second nic card on each guest and can now ping one VM from another.

For some reason though Eth0 has dissapeared from one of the guests. But this doesnt seem to be a big problem as it just starts from Eth1 (followed by Eth2). But its strange because it hasnt dissapeared from the other identical machine.

Whats more concerning is the fact that I have now lost my connection to the interenet and cannot figure out why?

Any ideas please?

Thanks Stefan.

[Stefan]

Just to confirm:

Ive enabled a second interface so i have

1 NAT 1 Internal Network

On each node, I cna ping nodes now.. but cannot access the outside

Stefan

[vasily Levchenko]

Replying to StefanDebattista:

Just to confirm:

Ive enabled a second interface so i have

1 NAT 1 Internal Network

On each node, I cna ping nodes now.. but cannot access the outside

what is route command output on you NAT machine and you internal network nodes?

Stefan

[vasily Levchenko]

no response