INTERACT FORUM
Networks and Remotes => Media Network => Topic started by: bob on November 01, 2012, 10:08:39 am
-
We ran into this interesting problem.
Several of us are running VirtualBox on our PC's for testing. For some reason, MC in the host machine (not container) wasn't showing up on the LAN as a library server or as DLNA device.
The problem turned out to be rather esoteric. VirtualBox (as well as vmware) creates a virtual interface on your PC that shows up as an unidentified network. According to what we found, that means that when it's active (which is is by default) you have a public network firewall in Vista and Win7 (this blocks MC and other stuff by default).
I stumbled across this trying to debug the problem by disabling the VirtualBox adapter and restarting MC at which point Windows 7 popped up an unblock window!
Ran into a few references to fixing this on the net and figured they would be useful.
For VirtualBox: http://www.brokenwire.net/bw/Various/120/fix-virtualbox-causes-unidentified-network-on-vista-and-windows-7 (http://www.brokenwire.net/bw/Various/120/fix-virtualbox-causes-unidentified-network-on-vista-and-windows-7)
For VMWare: http://aspoc.net/archives/2008/10/30/unidentified-network-issue-with-vmwares-virtual-nics-in-vista/ (http://aspoc.net/archives/2008/10/30/unidentified-network-issue-with-vmwares-virtual-nics-in-vista/)
It appears that this would also apply if you have actual physical NICS and may apply with vlans.
-
It's always advisable with VirtualBox to not install host/bridged network adapters if you don't use them. They bite other programs too. Just untick them in the setup. If you have them already installed rerunning the installer and then unticking them will uninstall the adapters.
-
It's always advisable with VirtualBox to not install host/bridged network adapters if you don't use them. They bite other programs too. Just untick them in the setup. If you have them already installed rerunning the installer and then unticking them will uninstall the adapters.
True but in our case, we need the bridged adapter for our guest bottle because that's where MC for testing resides and we need to see it on the LAN (as well as the one on the host OS).
-
It's a vlan issue. VirtualBox creates in effect, a vlan before the virtual nic is passed to a VM *and* at the same mis-identifying the new virtual nic to the registry in the guest windows OS as well as in the host OS. I'm having the same problem at work with multiple Server 2010/2012 instances running on a single host machine.
Something changed in the past two iterations of VB. There are user complaints and problems all over their boards with no real workarounds.
-
This topic re-started my curiosity on this. Been working with setting up a custom configured internal network with the options available via vboxmanage. Still going to need at least a rudimentary DNS, thinking that using DHCP reservations and setting custom MAC addresses for each VM would be the way to go. Not too worried about swizzling custom MACs, there are plenty of prefixes from defunct card makers that can be used.
Section 8.8.2 in the current VBox manual is our starting point for all this.
-
(lack of) progress report....
Still fighting the vlan issues with VirtualBox. Haven't narrowed it do any further than that, we have a ticket open with Sun on the issue, sent them traces, haven't heard back.
If past releases are any indication, we're almost due for 4.3.14 to be released. The .14 and .16 releases are generally last-change bug fixes before the next major dot release comes out.