Virtualbox 3.0, NAT Networking not working

[wilbur.harvey]

Jaunty, 64-bit host, Windows 7 guest

When I use the bridged adapter the networking works as expected.
When I try to use NAT, I cannot make a network connection from the guest to anything.

[Sasquatch]

Any additional information for us to work with? You did read the Forum Posting Guide when you made the other posts, right?

[wilbur.harvey]

Forum posting guides?

1 item per post - YES
Did I check the 5 other items posted since V3.0 was released to see if my V3.0 issues was listed - YES
The title clearly states the issue

If there is any other information that would be helpful to resolve the issues, I am happy to provide it.

[Sasquatch]

The guide clearly states that topics with only "it's not working, help" won't get you anywhere. You have to provide us info on your Host, it's network, the Guest, it's settings, there are plenty of things you can provide as information.

[wilbur.harvey]

Ok,

I am not sure where to begin.

My host is Jaunty (9.04) Ubuntu, 64-bit. Intel i7 processor, 12GBytes ram, MSI X58 Platinum mother board with two GigE interfaces, one disabled in the BIOS.
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
The host is an SSD boot drive, with Raid5 main filesystem.
The file system is EXT4.
Host has a fixed (not DHCP) address (10.14.0.50).
Guest has a fixed address.

From the vbox-install.log
Building module:
cleaning build area....
make KERNELRELEASE=2.6.28-13-generic -C /lib/modules/2.6.28-13-generic/build M=/var/lib/dkms/vboxnetflt/2.2.4/build.....
cleaning build area....


My guest is Windows 7 RC, 32-bit.
The guest is a dynamic, expandable 40GByte drive.

The Attached VirtualBox.xml file is after I reverted back to V2.2.4, but I didn't make any changes to the configuration and the same problems exists in V2.2.4.

The Windows guest claims that it received some network data, but that no packets are sent out ever, when the network interface is NAT. When it is BRIDGED everything seems to work fine.

I don't know where there might be any log files that could help.

My first question is, has anyone tried the configuration of VirtualBox 3.0 with Linux host, NAT and Windows 7? Maybe the problem would be easy to see?

[Sasquatch]

Aha, here is your problem:

Guest has a fixed address.

Why did you set that for static? Haven't you searched the forums for possible issues with NAT why it wouldn't work? Static on NAT == death. Simple as that. It needs DHCP. It's called NAT for a reason, it's a separate network, just like how your own home network isn't a part of the internet, or your company/school network.

[wilbur.harvey]

I am sorry I didn't catch that.
I hadn't realized that the networking had changed at the same time as I upgraded the version of VirtualBox and assumed that the new version of VirtualBox was the problem.

Not very good scientific method on my part.

Any clues on the copy/paste problem in VirtualBox 3.0?

[Sasquatch]

Nope, don't use 3.0.0 yet. Please open a new topic for it, but do check if one already exists. It might have a solution there and it saves a lot of trouble when having one topic, instead of several topics with the same issue.

[davoura]

I am having a similar problem.

I am using VirtualBox 3.0.2 on Ubuntu 9.04 AMD64, 4 GB RAM, dualcore AMD CPU.

When using older versions everything worked fine, but when I installed the new version, I have a problem with all new virtual machines having no Internet access. The existing VMs can all still access the Internet, and the settings are all the same, using NAT on the PCnet-FAST III adapter.

Every time I try to install a new OS as a VM, it cannot connect to the Internet and thus the installation fails for every guest OS (all Linux guests, such as Mint and Fedora).

I tried changing the network settings within VirtualBox but it made no difference, such as using Bridged Networking instead of NAT, and the settings in File menu/Preferences/Settings/Network. There was already an IP address in Adapter tab (set to 192.168.56.1), and DHCP is enabled with IP set to 192.168.1.1

[Sasquatch]

Have you tried other NIC types? It wouldn't be the first time that switching to an Intel adapter fixes the problem.

For the Host-Only adapter, the IP address of 192.168.56.1 is fine, but the DHCP settings should have the same range, not 1.1 at the end. That will conflict with your existing network (if it uses the 192.168.1.0 range).

[davoura]

Yes, I tried the other NIC types.

The weird thing is, is that existing VMs created in an earlier VirtualBox can all connect to the Internet perfectly okay. Only when I create new ones do I have a problem.

[davoura]

For the Host-Only adapter, the IP address of 192.168.56.1 is fine, but the DHCP settings should have the same range, not 1.1 at the end. That will conflict with your existing network (if it uses the 192.168.1.0 range).

So are you saying that the first IP address is what connects to my existing real LAN, and not that of the virtual machine on the virtual network? The way this is set up in Virtual Box is very confusing.

[Sasquatch]

For the Host-Only adapter, the IP address of 192.168.56.1 is fine, but the DHCP settings should have the same range, not 1.1 at the end. That will conflict with your existing network (if it uses the 192.168.1.0 range).

So are you saying that the first IP address is what connects to my existing real LAN, and not that of the virtual machine on the virtual network? The way this is set up in Virtual Box is very confusing.

You're confusing yourself. The adapter type Host-Only is self-explaining. It's a network that contains communications between the Host and VM only. Everything else that is accessible from your Host, like your router, other machines and internet, are NOT a part of the Host-Only network, thus inaccessible. If you put your Host network information to be propagated to your VMs on the H-O network, it will cause problems if they want to access other parts by using a different network adapter.

To make your VM a part of your physical network, use Bridged.