Guest boot fail with Bridged Adapter

[PhilDunphy]

I have a RHEL 6 (64bit) VM I've imported on my Win7 host. If I add a bridged adapter to it so I can get to it without port forwarding, it will not start (works fine with NAT only). I've tried this with 4.2.18 and 4.3.0. The error I get is VERR_SUPDRV_COMPONENT_NOT_FOUND:

Waiting for VM "RHEL64" to power on...
VBoxManage.exe: error: Failed to open/create the internal network 'HostInterfaceNetworking-Intel(R) Centrino(R) Advanced-N 6205' (VERR_SUPDRV_COMPONENT_NOT_FOUND)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component Console, interface IConsole

I've tried this with my wireless card and my wired network connection. Same result both ways, as well as for the different adapter types. I've uninstalled VBox and reinstalled. Same result.

[noteirak]

In the NIC properties, can you check that there is a Virtualbox Bridged filter, at the same level as TCP/IP & Client for Windows network, and that the filter is checked?

[PhilDunphy]

Yes, I have the VirtualBox Bridged Networking Driver (checked) in each of my host NICs (wired and wireless), along with Client for Microsoft Networks, VMware Bridged Adapter, McAfee NDIS Intermediate Filter, QoS Packet Scheduler, and File and Printer Sharing for Microsoft Networks. Plus IPv{4,6} and Link-Layer Topology Mapper and Responder.

[noteirak]

There are known compatibility issues with antivirus and other virtualization products.
Could you try desintalling and reinstalling virtualbox after removing the vmware & mcafee products?

[macka]

Were you able to resolve this, as I am also not able to use the Bridged Adaptor / to multiple wireless adapters

[PhilDunphy]

No, I was not able to resolve this. I could not try disabling AV (corporate machine) and have not tried uninstalling vmware (though I may try that later). I ended up using NAT and port forwarding to get what I needed. Sub-optimal, but working.