Getting error "Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)" when booting VM

[Suraj]

Hello Experts,
I am getting below error when trying to boot my VM.Am also describing the error scenario below.Please do help me here.
Error:-
Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2' (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}

Error Scenario
1) Created a clone of an Oracle 6.7 Linux VM[Working without any issues on my same virtual box].I am using oracle virtual box Version 5.1.14 r112924 (Qt5.6.2)
A host only adapter configured and a static IP(192.168.56.1) has been configured for this adapter.I am able to access the VM guest from my host using this IP without any issues.
Screenshots below.

Step 1

Old1.jpg (63.38 KiB) Viewed 19700 times

host_onlyadapter1.jpg (62.94 KiB) Viewed 19700 times

2) Imported the clone to same virtual box and its is found booting up without any issues.
Same host only adapter used without any change.

3) New Host only adapter is created and assigned a new static IP(192.168.107.1)
This is used in the network settings of the imported appliance mentioned above in step 2.
However, i am getting the error "Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)" as stated above when booting up the appliance.
When the initial host only adapter is used instead of the newly created one,the appliance boots up without any issue.Screenshots below.

New_notworking1.jpg (66.24 KiB) Viewed 19700 times

If somebody knows any hint on what is happening here,it would be very much helpful.
Note:- I have done multiple pc restarts,disabled/enabled the host only adapter2 from control panel,toggled VirtualBox NDIS6 bridged networking driver property of this host by now

[mpack]

Please provide a VM log file. With the VM fully shut down, right click it in the GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.

[Suraj]

Hello mpack,
I am attaching the logs you requested.
You can find that in attached file VBOX_Log.zip.
Thanks for your attention in my issue over here.

VBOX_Log.zip

(32.68 KiB) Downloaded 158 times

Regards

[mpack]

00:00:02.816721 E1000#0 Chip=82540EM LinkUpDelay=5000ms EthernetCRC=on GSO=enabled Itr=enabled ItrRx=enabled R0=enabled GC=enabled
00:00:02.817109 IntNet#0: szNetwork={HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2} enmTrunkType=3 szTrunk={\DEVICE\{3878D680-62EA-466E-BD20-0C49CFA2054E}} fFlags=0x8000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:02.817240 VMSetError: F:\tinderbox\win-5.1\src\VBox\Devices\Network\DrvIntNet.cpp(1766) int __cdecl drvR3IntNetConstruct(struct PDMDRVINS *,struct CFGMNODE *,unsigned int); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:02.817305 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2'
00:00:02.817399 VMSetError: F:\tinderbox\win-5.1\src\VBox\Devices\Network\DevE1000.cpp(7833) int __cdecl e1kR3Construct(struct PDMDEVINS *,int,struct CFGMNODE *); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:02.817407 VMSetError: Failed to attach the network LUN
00:00:02.817454 PDM: Failed to construct 'e1000'/0! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found.

It seems to me this is likely to the same problem as discussed here (different cause, same problem): viewtopic.php?f=6&t=85910.

Certainly the host OS seems to have renamed the ethernet adapter for some reason.

[Suraj]

Hello mpack,
I am not sure i follow your last comment.
I had created a new Host only adapter(Created "Virtual Box Host-Only Ethernet Adapter #2" from Preferences section) so that it can be used exclusively for the new VM instance(Clone of an already existing VM also using a host only adapter["Virtual Box Host-Only Ethernet Adapter"])

Static IP's assigned to the Adapters are as below:-
Virtual Box Host-Only Ethernet Adapter -->> 192.168.56.1
Virtual Box Host-Only Ethernet Adapter #2-->192.168.107.1


Thanks for you time

Regards
Suraj

[mpack]

I mean that a new adapter has been renamed or created, and the new adapter does not have all of the same interfaces as the previous (working) adapter. I suggest that you look at the service list for each adapter on the Windows host and make sure they're the same. I suspect you'll find that a service has been left disabled (e.g. IPv4 or IPv6).