dwinks wrote:So far I am rather impressed with Virtualbox, and especially like the ability to use my USB printer on guests.
However, I am running into one major issue (for me) that I can't seem to figure out.
When I installed Virtualbox, the virtual adapter popped up and I classified it as a "private network" in Vista. This is important, as it controls which of the firewall profiles gets implemented.
I can leave my computer unattended for a few hours, with no reboots or anything, and Virtualbox running a small testing server the whole time, and when I get back, the virtualbox network is classified as a "public network" again, and it also keeps saying "Unidentified network" in the network and sharing center, no matter how many times I change it.
One of the major issues this is causing for me is that while on any public networks, Vista seems to shut down UPnP and automatic registrations for applications in the firewall, so some of my software I use keeps getting cut off from inbound connections, which really sucks when I use those inbound connections to connect back to my server while I am out working.
If I can't get the virtual adapter to stay listed as a "private network" I'm afraid I might have to give up my lovely USB on my guests and switch back to stupid VMware. =(
Mate, I have a similar (probably exactly the same) issue. NAT is no good for me, as I need a real IP address both ways from guest to host. I've set up a Host Interface as per instruction, and if I tell Vista to bridge my connections with my local ethernet and the VirtualBox virtual adapter, the guest springs to life completely network wise. However, when I do this, anything with incoming connections on the host (I'll use my son's uTorrent as an example), refuses incoming connections within 10 minutes.
Mate, when you find the answer to this one please let me know. I currently bridge the connection before I use Virtualbox then unbridge when I've finished, but it is majorly annoying.