VirtualBox 4.3.18 NAT no longer works/broken

[Zovs]

About a month ago I upgraded to Virtual Box 4.3.18 and now all my virtual machines can no longer access the internet. Don't quite get why this upgrade is broken.

All 19 of my virtual machines can no longer access the internet, prior to upgrading to 3.18 Virtual Box worked great. Now it's just a waste of space for all 19 of the machines...

When will this bug be fixed and corrected?

[mpack]

I'm not aware of any such bug.

Instead of providing your diagnosis of the cause, I suggest that you describe the actual problem properly, including saying what VBox network mode you are using, and provide a VM log file too.

Minimum information needed for assistance.

[Zovs]

I have 19 different VMs, ranging from Windows 7 to varous flavors of Linux, everyone of these VMs no longer can access the internet. Previously all 19 VMs were able to access the internet just fine, the Host machine can access the internet just fine. But after I upgraded to 4.3.18, no more will any of the 19 VMs I have connect to the internet.

All 19 VM's depending on their guest OS will display a different message but it all amounts to the same.

Basically for the Windows 7 Profession 64 bit it says:

Windows Network Diagnostics
Your broadband modem is experiencing connectivity issues
Restart your broadband modem.
blah blah blah

Which is a false message, because A) Prior to upgrading to 4.3.18, this was never an issue. B) The Host is connected to the same modem and has no issues.

All the various Linux distros say the same thing. Like I said prior to be upgrading to 4.3.18 I have never had any issues what so ever using Virtualbox, now after applying the 4.3.18 upgrade its' completly broken all 19 VMs which previously worked just find before.

Using NAT, there is no VM log file.

[loukingjr]

Using NAT, there is no VM log file.

I coincidentally have 19 guests running in VB 4.3.18 all but a couple using NAT and they all connect. I'm not sure what you mean by no logs if you are using NAT. You should have 4 logs per machine assuming you launched each at least 4 times. What network setting one has wouldn't affect the logs.

[Zovs]

Where would the VirtualBox logs live?

There are none in the VM folders, and none on the Host system that I can find. So I don't' understand what you mean by VM logs? Do you mean the guest logs (irrelevant) or the host logs?

I have been using Virtualbox for a number of years and this is the very first upgrade that caused all 19 of the guest VMs to stop being able to connect. Obviously it was the upgrading from 17 to 18 that caused this issue.

[loukingjr]

The logs for each guest are in the Log folder in each VM's guest folder. Even if you couldn't find them, if you have VirtualBox open and right click on a guest's name it will have a "Show Logs" choice in the menu that opens.

It's hard to tell if the guest logs are irrelevant without seeing one.

[Zovs]

Thanks for pointing that out I was looking in the folder where I stored the vdi files:

Attached are two logs:

[loukingjr]

Looking at your log for W7 it looks like you are running into the hardening issues that are going on with VirtualBox on Windows hosts. I would roll back to VB 4.3.12 and wait until they are fixed.

[Zovs]

Thank you for looking at my logs!

Rolling back to 4.3.12

[Zovs]

Installed 4.3.12 and can now access the internet.

Thank you again!

Hopefully Oracle can fix this bug for 4.3.19

[michaln]

It won't get fixed unless it's reported. So please check viewtopic.php?f=6&t=64111 and add the relevant details.