VirtualBox

Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#14869 closed defect (duplicate)

windows 10.0.10586: Failed to open the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter'

Reported by: jamesr Owned by:
Component: network/hostif Version: VirtualBox 5.0.10
Keywords: Cc:
Guest type: other Host type: Windows

Description

I'm trying to solve a problem that I haven't found a proper solution for on the internet. Problem is I'm trying to install laravel homestead virtual machine in virtual box in windows 10.0.10586. I currently use virtual box 5.0.10.

Error text: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

What I have tried to according to searches on google:

Enable Virtual technology and Intel VT-d feature in BIOS
Updating VirtualBox Host-Only Ethernet Adapter
Installing virtual box, while running in Administrator mode
Installing homestead in commando prompt, while running in Administrator mode
Added Virtualbox as an exception in AVG anti virus FREE 2015.
activate/deactivate Host-Only Ethernet Adapter

Attachments (18)

deactivating-host-only-network.jpg​ (30.0 KB ) - added by jamesr 8 years ago.
DSC_0135.JPG​ (375.9 KB ) - added by jamesr 8 years ago.
Enabling virtualization
homestead.jpg​ (147.3 KB ) - added by jamesr 8 years ago.
installing-homestead
virtualbox - error.jpg​ (21.2 KB ) - added by jamesr 8 years ago.
virtual-box-error
updating-driversoftware-internet.jpg​ (63.8 KB ) - added by jamesr 8 years ago.
updating-drivers
virtualbox.jpg​ (268.7 KB ) - added by jamesr 8 years ago.
homestad-cant-start-up
Vboxhardening.log​ (254.6 KB ) - added by jamesr 8 years ago.
Vbox hardening log on homestead
homestead-2015-11-25-09-41-12.log​ (32.3 KB ) - added by jamesr 8 years ago.
Vbox.log
vbox.log.txt​ (32.3 KB ) - added by jamesr 8 years ago.
vbox log in txt format
problem.txt​ (393 bytes ) - added by jamesr 8 years ago.
problem description
VBoxInstallLog.txt​ (439.7 KB ) - added by jamesr 8 years ago.
creating2hostonlyadapter.jpg​ (14.5 KB ) - added by jamesr 8 years ago.
couldnotfindvboxNetFltOSInitInstance.jpg​ (361.8 KB ) - added by jamesr 8 years ago.
Could not find vboxNetFltOSInitInstance
hostonlyifs.jpg​ (50.3 KB ) - added by jamesr 8 years ago.
hostonlyifs
whatiscaptured.jpg​ (39.7 KB ) - added by jamesr 8 years ago.
what is captured
plentyofhost-only-networks.jpg​ (94.5 KB ) - added by jamesr 8 years ago.
plenty of host only network created
anothererror.jpg​ (203.2 KB ) - added by jamesr 8 years ago.
anothererror
NDIS6notenabled.jpg​ (133.6 KB ) - added by jamesr 8 years ago.
NDIS 6 not enabled

Change History (35)

by jamesr, 8 years ago

Attachment: deactivating-host-only-network.jpg​ added

by jamesr, 8 years ago

Attachment: DSC_0135.JPG​ added

Enabling virtualization

by jamesr, 8 years ago

Attachment: homestead.jpg​ added

installing-homestead

by jamesr, 8 years ago

Attachment: virtualbox - error.jpg​ added

virtual-box-error

by jamesr, 8 years ago

Attachment: updating-driversoftware-internet.jpg​ added

updating-drivers

by jamesr, 8 years ago

Attachment: virtualbox.jpg​ added

homestad-cant-start-up

by jamesr, 8 years ago

Attachment: Vboxhardening.log​ added

Vbox hardening log on homestead

by jamesr, 8 years ago

Attachment: homestead-2015-11-25-09-41-12.log​ added

Vbox.log

by jamesr, 8 years ago

Attachment: vbox.log.txt​ added

vbox log in txt format

by jamesr, 8 years ago

Attachment: problem.txt​ added

problem description

comment:1 by Frank Mehnert, 8 years ago

VERR_INTNET_FLT_IF_NOT_FOUND often means that the installation of the network filter driver was not successful. This is most likely a problem when you install VirtualBox on your host. You might want to enable the logging of the installer, see here.

in reply to:  1 comment:2 by jamesr, 8 years ago

Replying to frank:

VERR_INTNET_FLT_IF_NOT_FOUND often means that the installation of the network filter driver was not successful. This is most likely a problem when you install VirtualBox on your host. You might want to enable the logging of the installer, see here.

Hi Thank you for answering. I now attached VboxInstallLog.txt to this ticket, which should be the log from when I installed virtualbox.

Last edited 8 years ago by jamesr (previous) (diff)

by jamesr, 8 years ago

Attachment: VBoxInstallLog.txt​ added

by jamesr, 8 years ago

Attachment: creating2hostonlyadapter.jpg​ added

comment:3 by jamesr, 8 years ago

It's creating 2 virtualbox host-only network adapters. Is that normal?

VirtualBox Host-Only Network

VirtualBox Host-Only Network #2

Last edited 8 years ago by jamesr (previous) (diff)

comment:4 by Aleksey Ilyushin, 8 years ago

Please follow these steps:

  1. Uninstall existing version of VirtualBox (it is needed to remove all existing host-only adapters);
  2. Download and install ​DebugView;
  3. Download and install build 104375; no additional driver tweaking please, use defaults;
  4. Provide the output of VBoxManage list hostonlyifs;
  5. Start DebugView, make sure 'Capture Kernel' and 'Enable Verbose Kernel Output' are checked, you should see some messages being captured;
  6. Start VM that fails with VERR_INTNET_FLT_IF_NOT_FOUND, reproduce the issue;
  7. Stop capture, find captured lines that start with 'vboxNetFltOsInitInstance:' and copy them here.

in reply to:  4 ; comment:5 by jamesr, 8 years ago

I followed the instructions and install build 104375.

  1. I tried running the command VBoxManage list hostonlyifs. Unfortunately, it returned 0 result. please see hostonlyifs.jpg.
  1. I started DebugView and made sure Capture Kernel and Enable Verbose Kernel Output was checked. please see whatiscaptured.jpg
  1. From commando prompt I run "homestead up", which tried to open connection to virtual machine homestead. This made an error - "VirtualBox Host-only Ether Adapter 3 could not be found". To be honest, I tried this some times and it created a new host only adapter every time. Please see plentyofhost-only-networks
  1. Then I tried to manually and start homestead virtual machine from Virtual box GUI, and that worked. Eventhough that works it still doesn't solve problem with host-only adapter.

  1. I'm not sure I used DebugView properly, but I couldn't find vboxNetFltOsInitInstance. Please see

couldnotfindvboxNetFltOSInitInstance.jpg

by jamesr, 8 years ago

Attachment: couldnotfindvboxNetFltOSInitInstance.jpg​ added

Could not find vboxNetFltOSInitInstance

by jamesr, 8 years ago

Attachment: hostonlyifs.jpg​ added

hostonlyifs

by jamesr, 8 years ago

Attachment: whatiscaptured.jpg​ added

what is captured

by jamesr, 8 years ago

Attachment: plentyofhost-only-networks.jpg​ added

plenty of host only network created

by jamesr, 8 years ago

Attachment: anothererror.jpg​ added

anothererror

in reply to:  5 ; comment:6 by jamesr, 8 years ago

Replying to jamesr:

I followed the instructions and install build 104375.

  1. I tried running the command VBoxManage list hostonlyifs. Unfortunately, it returned 0 result. please see hostonlyifs.jpg.
  1. I started DebugView and made sure Capture Kernel and Enable Verbose Kernel Output was checked. please see whatiscaptured.jpg
  1. From commando prompt I run "homestead up", which tried to open connection to virtual machine homestead. This made an error - "VirtualBox Host-only Ether Adapter 3 could not be found". To be honest, I tried this several times and it created a new host only adapter every time. Please see plentyofhost-only-networks
  1. Then I tried to manually and start homestead virtual machine from Virtual box GUI, and that worked. Eventhough that works it still doesn't solve problem with host-only adapter.

  1. I'm not sure I used DebugView properly, but I couldn't find vboxNetFltOsInitInstance. Please see

couldnotfindvboxNetFltOSInitInstance.jpg

in reply to:  6 ; comment:7 by jamesr, 8 years ago

Replying to jamesr:

Replying to jamesr:

I followed the instructions and install build 104375.

  1. I tried running the command VBoxManage list hostonlyifs. Unfortunately, it returned 0 result. please see hostonlyifs.jpg.
  1. I started DebugView and made sure Capture Kernel and Enable Verbose Kernel Output was checked. please see whatiscaptured.jpg
  1. From commando prompt I run "homestead up", which tried to open connection to virtual machine homestead. This made an error - "VirtualBox Host-only Ether Adapter 3 could not be found". To be honest, I tried this several times and it created a new host only adapter every time. Please see plentyofhost-only-networks.jpg
  1. Then I tried to manually start homestead virtual machine from Virtual box GUI, and that actually worked. Eventhough that works it still doesn't solve problem with host-only adapter.

  1. I'm not sure I used DebugView properly, but I couldn't find vboxNetFltOsInitInstance. Please see

couldnotfindvboxNetFltOSInitInstance.jpg

Last edited 8 years ago by jamesr (previous) (diff)

in reply to:  7 comment:8 by jamesr, 8 years ago

Replying to jamesr:

Replying to jamesr:

Replying to jamesr:

I followed the instructions and install build 104375.

  1. I tried running the command VBoxManage list hostonlyifs. Unfortunately, it returned 0 result. please see hostonlyifs.jpg.
  1. I started DebugView and made sure Capture Kernel and Enable Verbose Kernel Output was checked. please see whatiscaptured.jpg
  1. From commando prompt I run "homestead up", which tried to open connection to virtual machine homestead. This made an error - "VirtualBox Host-only Ether Adapter 3 could not be found". To be honest, I tried this several times and it created a new host only adapter every time. Please see plentyofhost-only-networks.jpg
  1. Then I tried to manually start homestead virtual machine from Virtual box GUI, and that actually worked. Eventhough that works it still doesn't solve problem with host-only adapter.

  1. I'm not sure I used DebugView properly, but I couldn't find vboxNetFltOsInitInstance. Please see couldnotfindvboxNetFltOSInitInstance.jpg

comment:9 by Aleksey Ilyushin, 8 years ago

Could you check the properties of host-only connections if they have "VirtualBox NDIS6 Bridged Networking Driver" enabled? Your problem definitely looks like bridging filter is not bound to host-only adapters.

in reply to:  9 comment:10 by jamesr, 8 years ago

Replying to aleksey:

Could you check the properties of host-only connections if they have "VirtualBox NDIS6 Bridged Networking Driver" enabled? Your problem definitely looks like bridging filter is not bound to host-only adapters.

Of course! Seems like VirtualBox NDIS6 Bridged Networking Driver hasn't been enabled! Should I enable? - see NDIS6notenabled.jpg

by jamesr, 8 years ago

Attachment: NDIS6notenabled.jpg​ added

NDIS 6 not enabled

comment:11 by Valery Ushakov, 8 years ago

Component: network → network/hostif
Resolution: → duplicate
Status: new → closed

#14832

in reply to:  11 ; comment:12 by jamesr, 8 years ago

Replying to vushakov:

#14832

Why are you setting this as closed? this hasn't been solved yet. Why are you refering to this as a "duplicate" ?

your link solution doesn't solve my problem. I tried enabling it, but it doesnt solve the problem on my machine.

Last edited 8 years ago by jamesr (previous) (diff)

in reply to:  description comment:13 by jamesr, 8 years ago

Replying to jamesr:

I'm trying to solve a problem that I haven't found a proper solution for on the internet. Problem is I'm trying to install laravel homestead virtual machine in virtual box in windows 10.0.10586. I currently use virtual box 5.0.10.

Error text: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

What I have tried to according to searches on google:

Enable Virtual technology and Intel VT-d feature in BIOS
Updating VirtualBox Host-Only Ethernet Adapter
Installing virtual box, while running in Administrator mode
Installing homestead in commando prompt, while running in Administrator mode
Added Virtualbox as an exception in AVG anti virus FREE 2015.
activate/deactivate Host-Only Ethernet Adapter

NB! Vushakov closed this ticket without any explation. Problem hasn't been solved yet. I got no >explanation why its a duplicate.

in reply to:  12 ; comment:14 by Valery Ushakov, 8 years ago

Replying to jamesr:

Replying to vushakov:

#14832

Why are you setting this as closed? this hasn't been solved yet. Why are you refering to this as a "duplicate"?

Because it is a duplicate?

your link solution doesn't solve my problem. I tried enabling it, but it doesn't solve the problem on my machine.

Please, use the bug #14832 for further discussion.

in reply to:  14 comment:15 by jamesr, 8 years ago

Replying to vushakov:

Replying to jamesr:

Replying to vushakov:

#14832

Why are you setting this as closed? this hasn't been solved yet. Why are you refering to this as a "duplicate"?

Because it is a duplicate?

your link solution doesn't solve my problem. I tried enabling it, but it doesn't solve the problem on my machine.

Please, use the bug #14832 for further discussion.

Well, I disagree. bug 14832 solution didn't solve my problem at all. I don't like people closing tickets, when they can't even elaborate their choice of closing something not solved.

comment:16 by Aleksey Ilyushin, 8 years ago

So, did you try to enable 'VirtualBox NDIS6 Bridged Networking Driver' for all host-only adapters? Note that it is essential to enable them for each adapter, as each adapter has individual bindings.

comment:17 by Aleksey Ilyushin, 8 years ago

Please try build 104592. It should solve the issue.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
Contact – Privacy policy – Terms of Use