[Resolved] Windows 10 - Host Only Adapters

Discussions related to using VirtualBox on Windows hosts.

[Resolved] Windows 10 - Host Only Adapters

Postby Darkwing Duck » 12. Aug 2019, 19:09

NICs.jpg
NICs
NICs.jpg (30.27 KiB) Viewed 818 times
Hi

I'm using Windows 10 Professional as Host and Virtual Box Version 6.0.10 r132072 (Qt5.6.2)
Fact is, I installed Virtual Box as Administrator.
I'm not sure about this, but there was an windows update a few days agoo.
Before 3 Host Only Devices exist, now they where gone.
I reinstalled VirtualBox - no help
When I create an Host only Adapter and try to use it on Guest I run into:
Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).
Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).
Fehlercode:E_FAIL (0x80004005)
Komponente:ConsoleWrap
Interface:IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

The log reads:
00:00:02.250219 NAT: DNS#0: 192.168.2.1
00:00:02.251004 E1000#1: Chip=82540EM LinkUpDelay=3000ms EthernetCRC=on GSO=enabled Itr=disabled ItrRx=enabled TID=disabled R0=enabled GC=enabled
00:00:02.251127 IntNet#0: szNetwork={HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter} enmTrunkType=4 szTrunk={VirtualBox Host-Only Ethernet Adapter} fFlags=0x8000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:02.251193 VMSetError: F:\tinderbox\win-6.0\src\VBox\Devices\Network\DrvIntNet.cpp(1768) int __cdecl drvR3IntNetConstruct(struct PDMDRVINS *,struct CFGMNODE *,unsigned int); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:02.251217 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter'
00:00:02.251250 VMSetError: F:\tinderbox\win-6.0\src\VBox\Devices\Network\DevE1000.cpp(7986) int __cdecl e1kR3Construct(struct PDMDEVINS *,int,struct CFGMNODE *); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:02.251252 VMSetError: Failed to attach the network LUN
00:00:02.251262 PDM: Failed to construct 'e1000'/1! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found.
00:00:02.264183 AIOMgr: Async flushes not supported
Darkwing Duck
 
Posts: 8
Joined: 16. Mar 2017, 04:15

Re: Windows 10 - Host Only Adapters

Postby mpack » 12. Aug 2019, 19:23

VERR_INTNET_FLT_IF_NOT_FOUND happens when you bridge to a device that doesn't exist, AFAIK it has nothing to do with host-only networking (hostinterfacenetworking != hostonlynetworking).

Windows 10 feature updates sometimes rename physical NICs, i.e. <whatever> becomes <whatever>#2. That would certainly break bridged networking.

In any case the cure is to use the VM settings | Network panel to reselect the NIC you want to bridge to.
mpack
Site Moderator
 
Posts: 29817
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Windows 10 - Host Only Adapters

Postby Darkwing Duck » 12. Aug 2019, 20:12

NIC2.jpg
Selected NICs
NIC2.jpg (56.27 KiB) Viewed 808 times
Thanks.

I checked that one, and as far as I can see, the correct interface is selected.
I even dropped and recreated it. :(
Darkwing Duck
 
Posts: 8
Joined: 16. Mar 2017, 04:15

Re: Windows 10 - Host Only Adapters

Postby mpack » 13. Aug 2019, 09:59

It looks like I was wrong before: looking more closely it does seem that the VM is configured for host only networking. Obviously it isn't finding the "Host Only" virtual Ethernet cards on your host.

I recommend that you uninstall VirtualBox (this will not do anything to data, i.e. to your VMs). Then reinstall using "Run as administrator" to run the installer. Do this even if your user account already has admin rights. Make sure you are logged in as the final user while you do this.

p.s. I notice that you're showing me the configuration for virtual network adapter #2. What do you have for adapter #1? Is it possible that the error refers to adapter #1?
mpack
Site Moderator
 
Posts: 29817
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Windows 10 - Host Only Adapters

Postby Darkwing Duck » 13. Aug 2019, 17:28

Hi mypack, thanks a lot.

Well, I fixed this issue as You suggested. :D

I uninstalled VMBox and did an reboot.
The interfaces have been gone, as I expected.
Then, I did an installation "as admin", added 3 hostonly adapters.
After an reboot (just to make shure) the interface where visible.
I added them to the virtual maschine - and it works fine.
I'm a little bit suprised about this one.
Running under Windows 8, I never run into this error.

Regards
Christian
Darkwing Duck
 
Posts: 8
Joined: 16. Mar 2017, 04:15

Re: Windows 10 - Host Only Adapters

Postby Darkwing Duck » 14. Aug 2019, 18:48

I just noted a confusing fact.
I added 3 Host-Only NICs, which went fine.
They where listed as NICs on the host - looks fine....
Then I added them to the guest and tried to start the guest.
Guess what? Right, the NICs where not found, the guests did not came up. :shock: :shock:
So, I did an reboot of the host. :idea:
After this, the guests came up without any problem.
Darkwing Duck
 
Posts: 8
Joined: 16. Mar 2017, 04:15

Re: Windows 10 - Host Only Adapters

Postby socratis » 14. Aug 2019, 20:07

Marking as [Resolved].
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 25828
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Windows 10 - Host Only Adapters

Postby SirLouen » 5. Sep 2019, 17:49

Darkwing Duck wrote:So, I did an reboot of the host. :idea:


You did not even needed to do a host reboot. Just by disable and reenabling the interfaces in the Windows Network section

Here is my solution
viewtopic.php?f=6&t=94568&p=456926#p456926

Tried with two soft (Genymotion + Flywheel) and worked flawlessly with both
SirLouen
 
Posts: 8
Joined: 3. Aug 2010, 22:57
Primary OS: Ubuntu other
VBox Version: OSE Debian
Guest OSses: Linux and Windows Server


Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: artelogic.com, Martin and 51 guests