host lost all network access

[jeebc]

So, I was trying to run a VBOX image from another computer, copied it to this computer who had VirtualBox installed, but failed to launch the image.

Sine the version of VB was rather old, I decided to get the latest version (4.3.24), and try with that.

When installing, he's asking for hardware related things, which I thought : well, what harm can that do ?

Well, my Windows completely lost ALL network capabilities, including internet access. Quite pissed by this ...

I was fiddling along quite some time (since copying images doesn't really work great, which will be cause of another thread). That problem still exists, by the way, checked with the new version.

But now, how do I get around this ? What has VirtualBox messed up ?

[aleksey-vb]

It is hard to tell what went wrong from the information you have provided. What's is the version of Windows on your host? Do you have the installation log named VBoxInstallLog.txt under <your_user_dir>\AppData\Local\Temp\VirtualBox? Did you try to unbind "VirtualBox Bridged Networking Driver Miniport" from your network adapter on its properties page?

[jeebc]

It is hard to tell what went wrong from the information you have provided.

Well, I guess you know the installation of this software better than me, so that would assume the info given is not really worthless. I did mention the version of VB, and the platform I'm on. Maybe I didn't specify the version of it though, which is 7 (Windows 7, 64-bit).

What went wrong ? Well, I lost all network functionality.
You know that the installation mentions there will be an interruption in network ? Well, after that I never regained network functionality. And no error was spawn, or I would have stated.

[jeebc]

Did you try to unbind "VirtualBox Bridged Networking Driver Miniport" from your network adapter on its properties page?

I have no clue what that is

[jeebc]

Do you have the installation log named VBoxInstallLog.txt under <your_user_dir>\AppData\Local\Temp\VirtualBox?

No

> dir C:\*VBoxInstallLog*.txt /S /B
File Not Found

[aleksey-vb]

Please, post the output of "ipconfig /all" and "netstat -r" commands. If you do not want to share this information with the rest of the world, send it to me in a private message. I do have VirtualBox 4.3.24 installed on Windows 7/64-bit host and have no trouble with host networking there. There is something specific about your host. Another possibility is that your host is out of LUIDs for network interfaces, if you have been installing/uninstalling VirtualBox lots of times. Could you check if there are any LUID-related errors with "findstr /i luid C:\Windows\inf\setupapi.dev.log"? Another way to check is to issue "Get-ItemPropery "hklm:\System\CurrentControlSet\Services\NDIS\IfTypes\6" in PowerShell and look for the value of "IfUsedNetLuidIndices". The value should be reasonably small, not something like "FFFFFFFFFFFFF...".

[jeebc]

Please, post the output of "ipconfig /all" and "netstat -r" commands. If you do not want to share this information with the rest of the world, send it to me in a private message. I do have VirtualBox 4.3.24 installed on Windows 7/64-bit host and have no trouble with host networking there. There is something specific about your host.

I can no longer do, since the issue was so fatal, it needed to be fixed ASAP.

I have the most common setup in the world : a router connected to the internet, my machine connected to that router.

BTW, this is my extremely exotic setup, I've changed some values with *

> ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : ****::****:***:****:******
IPv4 Address. . . . . . . . . . . : 192.168.***.***
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.***.***

Ethernet adapter VirtualBox Host-Only Network:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : ****::****:****:****:*******
IPv4 Address. . . . . . . . . . . : 192.168.**.*
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Tunnel adapter isatap.{**********-****-****-*****-************}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter isatap.{**********-****-****-*****-************}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :


>

[jeebc]

Another possibility is that your host is out of LUIDs for network interfaces, if you have been installing/uninstalling VirtualBox lots of times. Could you check if there are any LUID-related errors with "findstr /i luid C:\Windows\inf\setupapi.dev.log"? Another way to check is to issue "Get-ItemPropery "hklm:\System\CurrentControlSet\Services\NDIS\IfTypes\6" in PowerShell and look for the value of "IfUsedNetLuidIndices". The value should be reasonably small, not something like "FFFFFFFFFFFFF...".

What is LUID ?
What is PowerShell ?

[jeebc]

Looks similar to this thread ; viewtopic.php?f=6&t=66105&start=15

[joeller]

Looks similar to this thread ; viewtopic.php?f=6&t=66105&start=15

Actually I saw nothing in that thread that resolved the issue, which I am also having.

[noteirak]

What is LUID ?

A way to uniquely identify drivers on the system, it's just an internal ID. The value itself is not important. What is important is that you could run out of them (there is a maximum number of them) which would block further drivers.
More info here.

What is PowerShell ?

A script language. In this case, you can open a command prompt to type commands with that language. In your start menu, just type "Powershell", then you can start a prompt and type in the given command.

[Rootman]

Just a wild guess.

RIGHT click the NETWORK icon and choose PROPERTIES

Select CHANGE ADAPTER SETTINGS on the left

Click ADVANCED off the MENU

Select ADVANCED SETTINGS

Make sure the hosts NIC is FIRST on the CONNECTIONS list, this means "try this interface first". If it's NOT first, make it first. At least IPV4 must be chosen in the bindings list.

It should not take a reboot, but if still no connectivity reboot.

I actually had another interface (non VB realted) seize the #1 spot before and had the same results, could not connect to the internet.

[joeller]

RIGHT click the NETWORK icon and choose PROPERTIES

Are you referring to the windows Network Icon in the system tray? If so I will try that when I get home and let you know.

[Rootman]

Are you referring to the windows Network Icon in the system tray? If so I will try that when I get home and let you know.

I was referring to the one on the desktop (if visible) or in Windows Explorer but you can get there by RIGHT clicking the tray icon too and selecting OPEN NETWORK AND SHARING CENTER.