Implementing Shared Folders breaks network connection for Guest OS (Windows 7)

[Charles Allen]

Operating VirtualBox in Solaris 10, update 9, with Windows 7 SP1 as the Guest OS (guest additions are installed). When creating a shared folder to the Guest OS, all network connectivity is lost and does not return with the removal of the shared folder. Further, a simple reboot of the Guest OS will not fix the problem. Must completely shutdown Guest OS and restart before connectivity is restored. Even though network connectivity is lost, access to the shared folder is functional.

We are operating the Guest OS with a bridged adapter. Do not experience the problem when using a NAT network.

[Ramshankar Venkataraman]

The log indicates creation of DrvIntNet fails with VERR_INTNET_FLT_IF_BUSY possibly because one of the interface being already in use.

Is this the only user that uses bge0 for the VM?

Do you have multiple users that bridge over bge0 with VirtualBox VMs? If so, you will need to remove the access restriction across users explicitly for each VM.

For the Intel e1000g adapter (the one you're using):

VBoxManage setextradata <vmname> VBoxInternal/Devices/e1000/0/LUN#0/Config/RestrictAccess 0

For AMD pcnet adapter:

VBoxManage setextradata <vmname> VBoxInternal/Devices/pcnet/0/LUN#0/Config/RestrictAccess 0

[Ramshankar Venkataraman]

Is this issue still relevant with the latest VirtualBox?

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.