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.
A friend who happens to be a network administrator and Cisco/router person set up a system which demonstrates the problem and then sent me a solution:
You would think it would have been discussed out there more. Who
knows? I really think it's a combination of bugs. When you setup the
2nd router as a wireless bridge, the 1st router should only see the
MAC address of the 2nd router's WLAN. It should proxy-arp all clients
on its side. The logic of this is explained decently in sections 16.3
and 16.3.1 on this site:
http://lartc.org/howto/lartc.bridging.proxy-arp.html
At any rate, I have a workaround for you. On your 192.168.1.1 router,
go to Administration -> Scheduler. Enable "Custom 1" and put "arp -d
192.168.1.195" (your PogoPlug IP) in the Command Box without the quotes. Set it to execute every 3 minutes of every day. Shouldn't be
necessary, but it's been working for my FreeBSD box connectivity for
over 45 minutes.
Best Answer
There could be a number of reasons for your problems, and it's hard to say which. My advice when setting something like this up would be:
Don't bridge. That is principally for paralleled connections to the same LAN.
Use a cheap switch/hub instead of an X-over cable, which is not always reliable.
Buy an Ethernet wireless access point and connect this to a third hub socket. (or get a combined hub/AP) Configure it as a client of the WiFi network.
When wired, turn off the WiFi on the Win8 Computer. It will also get its Internet connenction via the hub/AP.
Share a folder on the serving computer, and if necessary create a user account to access it with, and assign share and filesystem permissions.
To avoid IP changes, either give the serving computer a static IP, or else give it a secured lease on the Internet router's DHCP.
Ensure that port 445 is open to LAN destinations on the serving computer's firewall.
On the client, create a batch file containing net use h: \192.168.1.23\sharename /user:username password
(where the ip is that of the serving computer) Run this batch file to connect to the share. Drive H: should then become the share on the client.
HTH.
Basically there are many ways to do these things, but experience shows that some work reliably, others less so. Often it's the old ways that work reliably ;)