virtualbox.org

Hi guys! Sorry if i didn't Search properly, but i have to use my Phone to access this forum, so search is a little complicated.

My problem is, i installed virtualbox 4.0 in windows 7 64bit and set up a Android system. When i closed virtualbox my system lost network access and i wasn't able to restore it yet. my network device shows "no network access". i uninstalled and reinstalled network drivers several times and rebooted pc, but it did not help. i can't even access my router from pc. my phone connects to router and internet without problems though. settings on the router are unchanged.
what can virtualbox have messed up and how can
i fix it? any help is appreciated!


cheers
Qwer23

During the installation wizard it should have told you that if you continued on with the installation it would temporarily shut down your network.

Your situation is somewhat like mine. My post is just a few down from yours. It seems VirtualBox might have a problem here. I am using a different host and guest than yourself. My adapters never did install. I have tried several ways to get these network drivers install, but have still not found a solution.

I have no knowledge on Android. I be keeping an eye on your post to see it sheds some light on my problem.

You might want to tell everyone your settings for the network adapter in VB's Setting Tab.

NatDomain

@windowsuser:
right, i know. but what exactly does virtualbox do when it disables my network and how can i restore it?

See if this helps
Check your network adapter properties for "VirtualBox Bridged Networking Driver" and uncheck it.

Wufdog wrote:See if this helps
Check your network adapter properties for "VirtualBox Bridged Networking Driver" and uncheck it.

This worked for me. I had the same problem on Windows 8. It seems the VirtualBox Host-Only network adapter hides or disables my real ethernet adapter and prevents it from being recognised or used to create a network. The associated network disappears and it becomes unusable. Unchecking this entry in the adapter properties seems to fix the issue, though it may cause other issues if you need the functions it provides, I guess.