Opened 9 years ago
Closed 8 years ago
#14604 closed defect (obsolete)
Bridged networking not working since 5.0.0
Reported by: | Griffino | Owned by: | |
---|---|---|---|
Component: | network/hostif | Version: | VirtualBox 5.0.4 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Windows |
Description
I am running a Windows 7 host and have VBox 5.0.4 and both Windows 10 and Fedora 22 guests but ever since going to VBox 5 only NAT networking is working. I have been watching and upgrading VBox to see if it is fixed but still no go. I have even tried creating a new Fedora VM but it will not start if I have anything other than NAT networking. Most of the bug tracks I see are with a Windows 10 Host but I am Windows 7? I get: Failed to open a session for the virtual machine Linux test.
Failed to open/create the internal network 'HostInterfaceNetworking-Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)' (VERR_INTNET_FLT_IF_NOT_FOUND).
Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).
Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
If I switch to NAT, no errors at all. Could you please help.
Attachments (3)
Change History (26)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
VirtualBox Graphical User Interface, Version 5.0.6 r103037
I have tried removing all networks and creating them again, tried uninstall and install "as administrator", tried workaroud mentioned above, yet, it does not work. Bridged Network still fails with the message:
Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller' (VERR_INTNET_FLT_IF_NOT_FOUND). Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).
Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Any help on the issue, please?
EDIT:
Resolved by installing:
v.4.2.32
comment:3 by , 9 years ago
Dudes, thanks for the reply but it did not work. Is there an clean/full uninstall that I could try a complete clean out to see if that does the trick. It's just that it looks like not everyone is having this issue? Regards, Griffino
follow-up: 5 comment:4 by , 9 years ago
This has been an issue for me with bridged networking ever since the 5.x betas which introduced NDIS6, and still with 5.0.6: https://forums.virtualbox.org/viewtopic.php?f=15&t=67405
Running the installer with: VirtualBox-xxxx.exe -msiparams NETWORKTYPE=NDIS5 makes bridged networking work again - obviously, with the old drivers.
In case it helps, here is the output of 'VBoxManage list bridgedifs' when working:
Name: Broadcom NetLink (TM) Gigabit Ethernet GUID: 6241bc8f-c18a-4ed6-8d29-075760f5bbe2 DHCP: Enabled IPAddress: 192.168.0.2 NetworkMask: 255.255.255.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: bc:5f:f4:5b:66:98 MediumType: Ethernet Status: Up VBoxNetworkName: HostInterfaceNetworking-Broadcom NetLink (TM) Gigabit Ethernet
comment:5 by , 9 years ago
Thanks for the reply but it does not seem to have worked for me. I did as you suggested with 5.0.6 and it is still running the NDIS6.20 driver. I also tried uninstalling VBox and reinstalling with the parameter and still it has the NDIS6.20? Output of the VBoxManage list bridgedifs commend shows:
c:\Program Files\Oracle\VirtualBox>VBoxManage list bridgedifs Name: Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20) GUID: a9b43af4-63b3-4757-b18d-b1ec3cbff346 DHCP: Enabled IPAddress: 192.168.200.3 NetworkMask: 255.255.255.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 6c:f0:49:ef:11:3a MediumType: Ethernet Status: Up VBoxNetworkName: HostInterfaceNetworking-Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20) Name: Bluetooth Device (Personal Area Network) #5 GUID: f8126122-4dc8-454a-a9fc-230d8a8239b1 DHCP: Enabled IPAddress: 169.254.84.83 NetworkMask: 15.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:20:ed:36:c7:4d MediumType: Ethernet Status: Down VBoxNetworkName: HostInterfaceNetworking-Bluetooth Device (Personal Area Network) #5 c:\Program Files\Oracle\VirtualBox>
Any suggestions...am I doing it wrong? Kind regards, Griffino
follow-up: 8 comment:6 by , 9 years ago
The parameter has to be used on the command line with the installer, not the main program; and when installing it, not repairing it. I had to uninstall and reinstall myself.
I don't think the mention of "NDIS 6.20" refers to VMware's filter driver, but to that of the network card. Does bridged networking actually work now that you've reinstalled, or is it still broken?
comment:7 by , 9 years ago
Hi guys,
Not sure that I should create a new ticket, but I see the same problem on Mac OS X host. Only NAT Network is working since 5.0. No Bridged networking, No Host-Only networking (that for me is more needed).
Downgraded to 4.3.30
comment:8 by , 9 years ago
Replying to GreenReaper:
The parameter has to be used on the command line with the installer, not the main program; and when installing it, not repairing it. I had to uninstall and reinstall myself.
I don't think the mention of "NDIS 6.20" refers to VMware's filter driver, but to that of the network card. Does bridged networking actually work now that you've reinstalled, or is it still broken?
I did do an uninstall and reinstalled with that parameter but still no go. I have now upgraded the host to Win 10 and then did an uninstall/install with the parameter and using 5.0.8 in the hope it would resolve it but still no joy. With bridging I still get: Failed to open/create the internal network 'HostInterfaceNetworking-Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
and c:\Program Files\Oracle\VirtualBox>VBoxManage list bridgedifs on the host shows:
Name: Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20) GUID: a9b43af4-63b3-4757-b18d-b1ec3cbff346 DHCP: Enabled IPAddress: 192.168.200.3 NetworkMask: 255.255.255.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 6c:f0:49:ef:11:3a MediumType: Ethernet Status: Up VBoxNetworkName: HostInterfaceNetworking-Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20) Frustrating, the only thing that works is NAT or host only. Regards, griffino
comment:9 by , 9 years ago
I had the same problem with Windows 10 1511 and VirtualBox 5.0.10 r104061, I fix this issue enable VirtualBox NDIS 6 Bridged Networking Driver in VirtualBox Host-Only Ethernet Adapter.
by , 9 years ago
Attachment: | Sem título.png added |
---|
comment:10 by , 9 years ago
Could you try build 104592? If the problem still there, please provide the output of 'VBoxManage list bridgedifs' and 'VBoxManage list hostonlyifs'.
comment:11 by , 9 years ago
Unfortunately this build does not resolve the issue. Here is the requested output:
Name: Broadcom NetLink (TM) Gigabit Ethernet GUID: 6241bc8f-c18a-4ed6-8d29-075760f5bbe2 DHCP: Enabled IPAddress: 192.168.0.2 NetworkMask: 255.255.255.0 IPV6Address: fe80:0000:0000:0000:c5f0:287a:0543:0862 IPV6NetworkMaskPrefixLength: 64 HardwareAddress: bc:5f:f4:5b:66:98 MediumType: Ethernet Status: Up VBoxNetworkName: HostInterfaceNetworking-Broadcom NetLink (TM) Gigabit Ethernet
Name: VirtualBox Host-Only Ethernet Adapter GUID: c0e737bf-b0dc-49f0-979e-9dca5c76f24d DHCP: Disabled IPAddress: 192.168.56.1 NetworkMask: 255.255.255.0 IPV6Address: fe80:0000:0000:0000:6db9:41ed:da53:0334 IPV6NetworkMaskPrefixLength: 64 HardwareAddress: 0a:00:27:00:00:00 MediumType: Ethernet Status: Up VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter
comment:12 by , 9 years ago
GreenReaper, please provide VBox.log (from VM folder) and VBoxSVC.log (from .VirtualBox folder) files as well.
comment:13 by , 9 years ago
GreenReaper, thanks for the logs! May I ask you to go extra mile and do the following?
- Download and unpack DebugView;
- Run DebugView.exe as Administrator, make sure 'Capture Kernel' and 'Enable Verbose Kernel Output' are checked;
- Go to "Network Connections" and disable "Broadcom NetLink (TM) Gigabit Ethernet" adapter;
- Re-enable it back (you should see a message starting with vboxNetLwfWinAttach in DebugView);
- Start VM that fails with VERR_INTNET_FLT_IF_NOT_FOUND (you should see several messages starting with vboxNetFltOsInitInstance);
- Post the lines that I mentioned above here.
Thanks in advance!
comment:14 by , 9 years ago
I installed the build concerned on Windows Vista SP2 x86 with all components selected while running DebugView as administrator with the specified options enabled.
I did not see any messages regarding "vboxNetLwfWinAttach" on installation, even though I have kernel debugging enabled. Indeed, there was no debug output at any time mentioning "vboxNet".
Removed unrelated read-only issue due to Paragon ExtFS
I received the normal error [Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).], with the following debug output
vboxdrv: E960A000 VMMR0.r0 [1744] supR3HardenedScreenImage/NtCreateSection: rc=Unknown Status -608 (0xfffffda0) fImage=1 fProtect=0xf fAccess=0x2 \Device\HarddiskVolume4\Windows\System32\drivers\atikmdag.sys: [1744] [1744] supR3HardenedScreenImage/NtCreateSection: cached rc=Unknown Status -608 (0xfffffda0) fImage=1 fProtect=0x2 fAccess=0x6 cHits=1 \Device\HarddiskVolume4\Windows\System32\drivers\atikmdag.sys [1744] supR3HardenedScreenImage/NtCreateSection: cached rc=Unknown Status -608 (0xfffffda0) fImage=1 fProtect=0x2 fAccess=0xf cHits=2 \Device\HarddiskVolume4\Windows\System32\drivers\atikmdag.sys [1744] supR3HardenedScreenImage/NtCreateSection: cached rc=Unknown Status -608 (0xfffffda0) fImage=1 fProtect=0x2 fAccess=0x6 cHits=3 \Device\HarddiskVolume4\Windows\System32\drivers\atikmdag.sys vboxdrv: E9709000 VBoxDDR0.r0 vboxdrv: E972D000 VBoxDD2R0.r0
VBox.log shows the following output:
00:00:02.048503 IntNet#0: szNetwork={HostInterfaceNetworking-Broadcom NetLink (TM) Gigabit Ethernet} enmTrunkType=3 szTrunk={\DEVICE\{6241BC8F-C18A-4ED6-8D29-075760F5BBE2}} fFlags=0x14000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false 00:00:02.048538 VMSetError: F:\tinderbox\win-rel\src\VBox\Devices\Network\DrvIntNet.cpp(1753) int __cdecl drvR3IntNetConstruct(struct PDMDRVINS *,struct CFGMNODE *,unsigned int); rc=VERR_INTNET_FLT_IF_NOT_FOUND 00:00:02.048545 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-Broadcom NetLink (TM) Gigabit Ethernet' 00:00:02.048570 VMSetError: F:\tinderbox\win-rel\src\VBox\Devices\Network\DevVirtioNet.cpp(2080) int __cdecl vnetConstruct(struct PDMDEVINS *,int,struct CFGMNODE *); rc=VERR_INTNET_FLT_IF_NOT_FOUND 00:00:02.048573 VMSetError: Failed to attach the network LUN 00:00:02.048581 PDM: Failed to construct 'virtio-net'/0! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found. 00:00:02.049264 TxTimer stats (avg/min/max): 0 usec -1 usec 0 usec 00:00:02.049671 GIM: KVM: Resetting MSRs 00:00:02.050723 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to open/create the internal network 'HostInterfaceNetworking-Broadcom NetLink (TM) Gigabit Ethernet' (VERR_INTNET_FLT_IF_NOT_FOUND). 00:00:02.050735 Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)}, preserve=false aResultDetail=0 00:00:02.050881 Console: Machine state changed to 'PoweredOff' 00:00:02.055027 Power up failed (vrc=VERR_INTNET_FLT_IF_NOT_FOUND, rc=E_FAIL (0X80004005))
DriverView shows the following VirtualBox drivers as "loaded":
Name Address End Address Size Loads Index File Type Description Version Company Product Name Modified Created Filename Service Name Display Name VBoxNetAdp6.sys 0xF2110000 0xF212D000 0x0001d000 1 162 Network Driver VirtualBox NDIS 6.0 Host-Only Network Adapter Driver 5.0.51.4620 Oracle Corporation Oracle VM VirtualBox 12/9/2015 10:02:38 AM 12/9/2015 10:02:38 AM C:\Windows\system32\DRIVERS\VBoxNetAdp6.sys A VBoxNetAdp VirtualBox NDIS 6.0 Miniport Service VBoxNetLwf.sys 0xF212D000 0xF215B000 0x0002e000 1 163 Network Driver VirtualBox NDIS 6.0 Lightweight Filter Driver 5.0.51.4620 Oracle Corporation Oracle VM VirtualBox 12/9/2015 10:02:38 AM 12/9/2015 10:02:38 AM C:\Windows\system32\DRIVERS\VBoxNetLwf.sys A VBoxNetLwf VirtualBox NDIS6 Bridged Networking Service VBoxDrv.sys 0xF202E000 0xF20F3000 0x000c5000 1 161 System Driver VirtualBox Support Driver 5.0.51.4620 Oracle Corporation Oracle VM VirtualBox 12/9/2015 10:03:04 AM 12/9/2015 4:15:16 PM C:\Windows\system32\DRIVERS\VBoxDrv.sys A VBoxDrv VirtualBox Service VBoxUSBMon.sys 0xF200D000 0xF202E000 0x00021000 1 160 System Driver VirtualBox USB Monitor Driver 5.0.51.4620 Oracle Corporation Oracle VM VirtualBox 12/9/2015 10:02:38 AM 12/9/2015 4:15:14 PM C:\Windows\system32\DRIVERS\VBoxUSBMon.sys A VBoxUSBMon VirtualBox USB Monitor Driver
VirtualBox's NDIS6 Bridged Networking Driver is ticked in the Local Area Connection's settings dialog.
comment:15 by , 9 years ago
I get this same error message with VirtualBox 5.0.10 on Windows 10 build 10586.29 x64.
The steps in https://www.virtualbox.org/ticket/14604#comment:1 did not help.
I've had to revert to VirtualBox 4.3.34 to get working again.
comment:16 by , 9 years ago
jstangroome, would you be willing to follow steps in comment 13? I must warn you that those won't help you either, but they may provide valuable information.
GreenReaper, I installed Vista SP2 from scratch, but couldn't reproduce the issue. The fact that you see no lines starting with vboxNet in DebugView most probably means that something prevents the bridging filter to attach to your physical adapter's stack. If you are willing to do more experiments you can install WinDbg (comes as a part of Windows WDK, look for 'Standalone Debugging Tools for Windows' section, uncheck all installation options except 'Debugging tools'), enable local kernel debugging, set up symbols paths as described here, make sure you use "run as administrator" to start WinDbg, select Kernel Debug
, Local
, then do !ndiskd.miniports
, click on the miniport that corresponds to Broadcom NetLink (TM) Gigabit Ethernet
, scroll to section BINDINGS
, subsection Filter list
and click on the module under VirtualBox NDIS Light-Weight Filter-XXXX
and upload/post WinDbg output here.
comment:17 by , 9 years ago
As it happens I had all that installed already for some reason. :-)
When I have it in a working state (i.e. -msiparams NETWORKTYPE=NDIS5)
There are no bound filters on "Broadcom NetLink (TM) Gigabit Ethernet"
"VBOXNETFLT" is the only item on the "Open List" beneath it within that section.
There is a separate "Broadcom NetLink (TM) Gigabit Ethernet - VirtualBox Bridged Networking Driver Miniport" (VBoxNetFlt.sys)
When I uninstall and reinstall without -msiparams:
There are still no bound filters on "Broadcom NetLink (TM) Gigabit Ethernet".
The open list is as follows:
Open List Open Protocol Context TCPIP6 b1cdc480 aea22670 b1be3590 TCPIP b24b5680 ae9f3160 b214dd70 RSPNDR b0248800 b0b13e70 b2d67008 LLTDIO b0248150 b0b473a8 b21504c8
I don't see the "VirtualBox NDIS Light-Weight Filter" anywhere.
There is no separate bridged adapter, just the VirtualBox Host-Only Ethernet Adapter (VBoxNetAdp6.sys) that was also there with NDIS5.
comment:18 by , 9 years ago
Indeed, the ones you have listed are protocols, not filters. I guess you have an older version of WinDbg. I am pretty sure that versions that come with WDK 8.1 and 10 do list filters. You may also try !ndiskd.filter
.
comment:19 by , 9 years ago
I have reinstalled using the 8.1 SDK, which provides WinDbg 6.3.96000.17298 X86.
The resulting output is the same. There is a filter list for the adapter; the problem is it's empty.
lkd> !ndiskd.miniports VBoxNetAdp6.sys, v1.0 b1112438 NetLuidIndex 14, IfIndex 34, VirtualBox Host-Only Ethernet Adapter asyncmac.sys, v0.0 b04fe438 NetLuidIndex 1, IfIndex 7, RAS Async Adapter rassstp.sys, v0.0 afdd81d0 NetLuidIndex 5, IfIndex 10, WAN Miniport (SSTP) raspptp.sys, v0.0 b2d92438 NetLuidIndex 1, IfIndex 3, WAN Miniport (PPTP) raspppoe.sys, v0.0 afffb438 NetLuidIndex 0, IfIndex 4, WAN Miniport (PPPOE) ndiswan.sys, v0.0 b0075468 NetLuidIndex 0, IfIndex 5, WAN Miniport (IPv6) b118f470 NetLuidIndex 3, IfIndex 6, WAN Miniport (IP) b2e81470 NetLuidIndex 13, IfIndex 11, WAN Miniport (Network Monitor) rasl2tp.sys, v0.0 b2a41340 NetLuidIndex 0, IfIndex 2, WAN Miniport (L2TP) k57nd60x.sys, v1.0 afbb82f8 NetLuidIndex 17, IfIndex 27, Broadcom NetLink (TM) Gigabit Ethernet tunnel.sys, v1.0 b0a730e8 NetLuidIndex 2, IfIndex 30, Microsoft Direct Point-to-point Adapater afdd70e8 NetLuidIndex 8, IfIndex 26, 6TO4 Adapter lkd> !ndiskd.miniport afbb82f8 MINIPORT Broadcom NetLink (TM) Gigabit Ethernet Ndis Handle afbb82f8 Ndis API Version v6.1 Adapter Context b02e0000 Miniport Driver b1067010 - k57nd60x.sys v1.0 Ndis Verifier [No flags set] Media Type 802.3 Physical Medium 802.3 Device Path \??\PCI#VEN_14E4&DEV_16B1&SUBSYS_96B11849&REV_10#4&2b8260c3&0&00E4#{ad498944-762f-11d0-8dcb-00c04fc3358c}\{6241BC8F-C18A-4ED6-8D29-075760F5BBE2} Device Object afbb8240 MAC Address bc-5f-f4-5b-66-98 STATE Miniport Running Device PnP Started Datapath Normal Interface Up Media Connected Power D0 References 5 User Handles 0 Total Resets 0 Pending OID None Flags 2c452218 ↑ BUS_MASTER, 64BIT_DMA, SG_DMA, DEFAULT_PORT_ACTIVATED, SUPPORTS_MEDIA_SENSE, DOES_NOT_DO_LOOPBACK, MEDIA_CONNECTED PnPFlags 00610021 ↑ PM_SUPPORTED, DEVICE_POWER_ENABLED, RECEIVED_START, HARDWARE_DEVICE, NDIS_WDM_DRIVER BINDINGS Filter List Filter Filter Driver Context No filters are bound Open List Open Protocol Context TCPIP6 af698008 aea22670 b1ba0008 TCPIP b0638b60 ae9f3160 af421008 RSPNDR af4fec50 b0b13e70 b1910008 LLTDIO af3eaac8 b0b473a8 af027cb8
However, !ndiskd.filter did produce some output:
lkd> !ndiskd.filter b08433f8 - VirtualBox NDIS Light-Weight Filter afee3a38 - QoS Packet Scheduler Filter b00da828, Miniport b2e81470 - WAN Miniport (Network Monitor) Filter b00c4c10, Miniport b118f470 - WAN Miniport (IP) Filter b00c3c10, Miniport b0075468 - WAN Miniport (IPv6) lkd> !ndiskd.filterdriver b08433f8 FILTER DRIVER VirtualBox NDIS Light-Weight Filter Ndis Handle b08433f8 Ndis API Version v6.0 Driver Version v0.0 Driver Object b02319f0 Filter Type MODIFYING_FILTER Run Type OPTIONAL_FILTER Class compression References 1 FILTERS Filter _ [No filter instances were found] HANDLERS Filter Handler Function pointer Symbol (if available) SetOptionsHandler 0 SetFilterModuleOptionsHandler 0 AttachHandler f2101bb0 DetachHandler f2101e20 RestartHandler f2101f90 PauseHandler f2101ed0 SendNetBufferListsHandler f2102670 SendNetBufferListsCompleteHandler f21027a0 CancelSendNetBufferListsHandler 0 ReceiveNetBufferListsHandler f2102810 ReturnNetBufferListsHandler f21029e0 OidRequestHandler f2101660 OidRequestCompleteHandler f21017c0 DirectOidRequestHandler 0 DirectOidRequestCompleteHandler 0 CancelDirectOidRequestHandler 0 DevicePnPEventNotifyHandler 0 NetPnPEventHandler 0 StatusHandler f2102470
comment:20 by , 9 years ago
OK. After all this, I figured it out: there was a broken or incompatible filter driver/service, "Virtual Machine Network Services", which I believe was installed by VirtualPC.
Uninstalling this from a Network Connections property dialog instantly enabled the bridged filter driver, with associated debug messages, !ndiskd.filter status, etc. Even better, the VM now works! :-)
Sorry for putting you through all this fuss, but hopefully it may help anyone else in this situation.
Note that disabling the above service is insufficient to fix the problem - it must actually be uninstalled.
follow-up: 22 comment:21 by , 9 years ago
I had the same issue with running a Windows 10 host and a Windows Server 2008 Guest. The error which I receive is the same but perhaps the root cause is different. I found another solution to solve my issue. I had to change a setting of the "VirtualBox Host-Only" network connection to fix the issue.
Go to Configuration Settings, Network connections and open properties of "VirtualBox Host-Only Network". Check the "VirtualBox NDIS6 Bridged Networking Driver" if it is unchecked. After this modification, I was able to start the Guest without receiving the error message.
comment:22 by , 9 years ago
Bingo, Filip - I followed these instructions to check the NDIS6 item in the network adapter properties, and it fixed my issues.
Replying to Filip:
I had the same issue with running a Windows 10 host and a Windows Server 2008 Guest. The error which I receive is the same but perhaps the root cause is different. I found another solution to solve my issue. I had to change a setting of the "VirtualBox Host-Only" network connection to fix the issue.
Go to Configuration Settings, Network connections and open properties of "VirtualBox Host-Only Network". Check the "VirtualBox NDIS6 Bridged Networking Driver" if it is unchecked. After this modification, I was able to start the Guest without receiving the error message.
comment:23 by , 8 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
This is probably the same problem as in #11371.
Can you, please, try the following workaround? Open
Network and Sharing Center
and go to theChange adapter settings
in the sidebar. Right-click on the host-only adapter in the list of adapters and thenConfigure
button ->Driver
tab ->Update driver
button. SelectBrowse my computer ...
and in the next dialog selectLet me pick ...
. You should see the list with just host-only driver in it. Select it and click next. After the driver is updated, please try using host-only network in a VM again.