Brideged Adaptor

[macka]

I have tried to use two different wireless adapters (see errors below), and both have failed

Windows 7 on HP, 64 bit

All worked fine, until I tried to upgrade to 4.2.18, but have tried installing versions 4.1.18, 4.2.10 and 4.2.18, and all have the same results. I am able to start the VM only when selecting NAT on all versions

Failed to open/create the internal network 'HostInterfaceNetworking-Intel(R) Centrino(R) Advanced-N 6205' (VERR_SUPDRV_COMPONENT_NOT_FOUND).

Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}

and

Failed to open a session for the virtual machine SYMC.

Failed to open/create the internal network 'HostInterfaceNetworking-Wireless N-300 USB Adapter WNA3100' (VERR_SUPDRV_COMPONENT_NOT_FOUND).

Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}

Thanks in advance for the help,

John

[mpack]

This looks like you did not install the host only networking driver. You need admin rights to install drivers on a 64bit host, so you need to use "Run as administrator" on the installer.

p.s. I've never encountered a 63 bit host before...

[socratis]

p.s. I've never encountered a 63 bit host before...

I think that no one has seen that yet ... except you. There's no mention in the post for 63 bits Tried an eye-exam lately?

[mpack]

p.s. I've never encountered a 63 bit host before...

I think that no one has seen that yet ... except you. There's no mention in the post for 63 bit

Well, not since the OP edited the post there isn't...

[macka]

Small minds amused over a typo

[mpack]

"Small minds"? If I was you I'd watch that tendency to abuse other participants if you ever want help here again. It was a small joke concerning a typo, I advise you to get over it.
(Site Moderator).

[macka]

Help and advise is what I needed, I did not realize the forum was for jokes, I am way over it.

[mpack]

You got your "help and advice" answer in the first sentence of my first reply. I note that you have not attempted to respond, nor have you closed the issue.

[macka]

I am still working on this, as I can not find a procedure to just install the host only driver, I have tried multiple versions of VB, but at this time it could be at the lower level. Being new to the forum, I will figure out how to close it

[macka]

The only setting that allows the VB to start is NAT, as previously I was using Bridged, which is the error messages I posted. During the install or upgrade of VB the additional interface never gets create, I see an unknown device via Device Manager (Hardware ID = sun_VBoxNetFltmp), and when trying to update the driver software for VirtualBox Bridged Networking Driver Miniport I get Insufficient system resources

I also see this error in the event log

Driver Management concluded the process to install driver FileRepository\vboxnetfltm.inf_amd64_neutral_ff1072753d9e3ba9\vboxnetfltm.inf for Device Instance ID ROOT\SUN_VBOXNETFLTMP\0001 with the following status: 0x5aa.

[mpack]

By "close the topic" I mean as in to bring closure. Basically, report back so that others know if the advice was successful.

You might also want to review this other recent thread.

[Perryg]

http://www.virtualbox.org/manual/ch12.html#idp58424832

[macka]

Perryg

Thanks, but the option to select the bridged adapters shows up in the "Networking" section of the VM settings, I am just not able to start the VM with it select, but only able if I select NAT, I am checking mpack other recent threads also

[macka]

This has been resolved, the fix was to re-image the host, thanks to all for your help