On the guest side networking settings:
Adapter 1 = eth0 = NAT (you already have this setup, that's why you always get internet)
Adapter 2 = eth1 = bridged, here is your problem, my guess is your HOST networking device are you bridged too is eth0 (that is why it works at work), but when you get home your wifi is NOT the HOST eth0 networking device, it is maybe wlan0, or eth1 depending on your computers NIC).
If your setup is how you described then you are not using vboxnet0 at all, that vbox networking interface is used only whey you do a 'host-only' Ethernet adapter setting for the guest.
What I dont understand is why you have NAT AND a bridged adapter?? It makes no sense to have both the way your setup is configured. If you use your virtual strictly for internal services (for instance hosting an iscsi volume, or maybe as an svn server local to your host computer only) then what you should do is NAT the first adapter (as you have), and then "Host-Only" the second guest adapter... This second adapter is not visible to the internet but is visible to both your host AND any other virtuals that are configured to share that host-only network. Your virtual will still be able to access the internet through NAT, but will be more secure because the internet wont be able to access it.
I would also ditch that virtual eth0.1 interface because I dont see a point in that either, and will most likely screw with your tcp/ip stack because it may get confused as to which interface to send requests out, since eth0.1 is same ip range as vboxnet0... bad idea. ( I think the technical term is multi-homing your network.. but im not 100% sure)
Let me know if this helps you... If your setup or reason for your virtuals is different, you could explain in more detail of their purpose and I could assist in suggesting the best network configuration setup.
This seems like a known bug : Ticket #12182 : Failed to create the host network interface.
The only claimed workaround is given by David.Requena :
In fact going back to 4.2.24 and creating some h/o adapter allows its
use after upgrading to any 4.3.x release. Said adapter can be removed
in 4.3.x but not modified. Under no circumstance can it be re-created.
Try going back to version 4.2.24 to create the adapter,
or wait for the bug to be fixed by the developers.
Be careful to fully uninstall the current VB version and ensure that all its devices are deleted
before installing version 4.2.24.
Best Answer
The thread Bridged Adapter problem suggests that the problem is the network MaxNumFilters limit in Windows.
By default, the MaxNumFilters value is 8. You can change it up to 14, using regedit in this location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network, value ofMaxNumFilters.Note: If you don't see MaxNumFilters, you can create it with the Type of REG_DWORD as shown below :
If after this change you still have the problem, then while leaving the value of MaxNumFilters as 14, uninstall VirtualBox, reboot, then reinstall it.