VBox 2.1.4 kills networking on host

[ddreier]

Since I upgraded to VirtualBox 2.1.4 on my Win XP Pro SP2 machine, every time I open virtualbox networking on the host completely stops working.

E.g. I loose access to the internet, and running 'ipconfig' literally returns nothing but "Windows IP Configuration".

Everything worked great in 2.1.2 and if there is a way to revert back to it, I'd be happy to wait for 2.1.5 to come out. I use a Netgear MA111 USB WiFi adapter, but I also tried it with a wired connection and got the same results.

[Sasquatch]

It's probably the new HIF driver that is being used. There were some installer issues due to that. Please disable the driver from the interfaces. You can do that at the same place as where you can configure the IP address of the interface.

[ddreier]

Ok, thanks, I'll do that.

There were some installer issues due to that.

I'm guessing that it has something to do with windows asking ~7 times for that 'Windows Logo' driver testing?

[Sasquatch]

No, it was because the installer aborted and rolled back changes. People weren't able to update to a newer version. But when they disabled the HIF driver to be installed, the setup didn't abort.

[ddreier]

I suppose I should have asked, is there a solution to this problem?

EDIT: Doing the whole, uninstall VB, install MS VPC, then re-install VB didn't fix the problem. I also happen to have a Realtek NIC, but it has the latest drivers a la MS Update.

[vbox4me2]

Msupdate does NOT always have the latest/best version, check with realtek's website(s).

[ddreier]

Ok, updated the driver (from Realtek) then rebooted, tried to install VB, but that failed, so I re-installed MS VPC, restarted, and successfully installed VB. Now, when ever I try to start a VM that is connected to a HIF I get a "VERR_INTNET_FLT_IF_NOT_FOUND" error.

[vbox4me2]

Some solutions for this:
http://www.google.nl/search?hl=nl&q=VER ... .org&meta=

[debianite]

I have vista 64bit host and I'm having tha same problem, uninstalling and reinstalling didn't solved it, is there any other solution?
Thanks.

[Sasquatch]

Ok, updated the driver (from Realtek) then rebooted, tried to install VB, but that failed, so I re-installed MS VPC, restarted, and successfully installed VB. Now, when ever I try to start a VM that is connected to a HIF I get a "VERR_INTNET_FLT_IF_NOT_FOUND" error.

Did you install the newer driver after you installed VB? If so, then it's possible that the HIF driver system isn't integrated in the new interface. When updating a driver in Windows, it will remove the interface with it's support and configuration, and create a new interface. Usually, it gets the same name, so the config which is stored in the registry (like IP address) is restored, but not the services for the said device. You can manually add the VB driver by hitting the Add button in the interface properties. After that, the error should go away.

[ddreier]

Did you install the newer driver after you installed VB? If so, then it's possible that the HIF driver system isn't integrated in the new interface. When updating a driver in Windows, it will remove the interface with it's support and configuration, and create a new interface. Usually, it gets the same name, so the config which is stored in the registry (like IP address) is restored, but not the services for the said device. You can manually add the VB driver by hitting the Add button in the interface properties. After that, the error should go away.

I updated the driver, then re-installed VB, since then I have "repaired" or uninstalled/re-installed VB twice, and it still hasn't fixed the problem. Also, I went into the properties of my WiFi NIC and "installed" the VB service on top of the one that was already there, and it still didn't fix the problem.

[debianite]

New release and same problem, the issue is still unsolved in VirtualBox 2.2.0

[debianite]

Bump!

[Sasquatch]

Bump!

Tried 2.2.2 yet?

[debianite]

Bump!

Tried 2.2.2 yet?

I'm on it!
As soon as i have tried it I'l report back.
thanks.