VirtualBox

Ticket #4119 (closed defect: worksforme)

Opened 5 years ago

Last modified 3 years ago

VERR_SUPDRV_COMPONENT_NOT_FOUND with bridged network

Reported by: jmccune Owned by:
Priority: major Component: network
Version: VirtualBox 2.2.2 Keywords:
Cc: Guest type: Windows
Host type: Windows

Description

I recently upgraded to Virtual Box 2.2.2 after fighting through some installation issues while my CheckPoint SecuRemote VPN client was installed into my Windows XP SP3 machine. The first issue was that the installer would always blue screen of death in the fw.sys immediately after popping up a dialog box that I needed to terminate the fwkern.exe process.

Both fw.sys and fwkern.exe are related to the CheckPoint VPN-1, so I completely uninstalled CheckPoint VPN-1, rebooted, completely un-installed the failed VirtualBox 2.2.2 installation, rebooted, then installed VirtualBox 2.2.2 successfully, rebooted, installed CheckPoint SecuRemote VPN-1 successfully, and rebooted again.

Upon launching Virtual Box, I deleted my windows guest entry and created a new one, selecting the old VDI disk. I set the network to Bridged to my wired ethernet adapter, and I receive "VERR_SUPDRV_COMPONENT_NOT_FOUND" consistently.

Attachments

WindowsVM-2009-05-28-12-33-38.log Download (31.5 KB) - added by jmccune 5 years ago.
VBox.log
OpenBSD-2009-07-25-20-00-40.log Download (30.9 KB) - added by mnieto 5 years ago.
VirtualBox 3.0.2 log. (bridge over wired connection)

Change History

Changed 5 years ago by jmccune

VBox.log

comment:1 Changed 5 years ago by mnieto

This seems not to be CheckPoint related. Without it, VirtualBox is also givin that error message when using a bridge attachment.

Changed 5 years ago by mnieto

VirtualBox 3.0.2 log. (bridge over wired connection)

comment:2 Changed 5 years ago by mnieto

BTW, version 2.2.4 is working ok.

comment:3 Changed 3 years ago by frank

  • Status changed from new to closed
  • Resolution set to worksforme

The reason was most likely that the Windows host driver for bridged networking / host-only networking was not properly installed. Uninstalling + re-installing VBox should solve the problem.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use