virtualbox 6.0.4 guest not receiving ip in bridged network

[BONappetite]

Hi everyone, I have a Windows 10 host and guest and when using the bridged adapter the guest does not receive an ip address! I have seen people have this issue on previous builds but that thread was closed as it was supposedly fixed. please let me know what I can do to fix this. or if you need more details.

Thanks

[andyp73]

What is the guest adapter bridged to? Is it to a wireless or wired interface on the host? Bridging to a wireless interface may not work - it is outside of the spec and requires some magic within the drivers that not everyone implements.

The VBox.log file from the guest may also give us some clues as to what is going on. Can you zip it and attach it here.

Regards,

Andy.

[BONappetite]

It's a wireless network card

[socratis]

It's a wireless network card

Then, as Andy explained, you may be out of luck, nothing that you can do, if it's your router and/or the specific wireless card. It may or may not work. Some combinations of Routers/Access Points, WLAN cards and drivers work, some don't. See: Bridging & Wifi - Supported hardware and add your experience. For example, it works fine in my home, but not in my office. Same laptop, same VM. Try to see if it works either with wired bridged or with NAT.

BTW, you seem to have a hardening problem with your Nvidia drivers:

00:00:05.005172 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll:
	rc=VERR_CR_PKCS7_KEY_USAGE_MISMATCH fImage=1 fProtect=0x0 fAccess=0x0
	\Device\HarddiskVolume3\Windows\System32\DriverStore\FileRepository\nvam.
	inf_amd64_1aae4f19e68d0780\nvinitx.dll: fKeyUsage=0x0, missing 0x1:
	\Device\HarddiskVolume3\Windows\System32\DriverStore\FileRepository\nvam.
	inf_amd64_1aae4f19e68d0780\nvinitx.dll

Please read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues for some generic guidelines/ideas on how to address this, because your 3D acceleration will fail to materialize, that's why your VM seems to fallback to the Intel GPU:

00:00:05.615692 OpenGL Info: Render SPU: GL_VENDOR:   Intel
00:00:05.615704 OpenGL Info: Render SPU: GL_RENDERER: Intel(R) HD Graphics 630

[BONappetite]

Then, as Andy explained, you may be out of luck, nothing that you can do, if it's your router and/or the specific wireless card. It may or may not work. Some combinations of Routers/Access Points, WLAN cards and drivers work, some don't. See: Bridging & Wifi - Supported hardware and add your experience. For example, it works fine in my home, but not in my office. Same laptop, same VM. Try to see if it works either with wired bridged or with NAT.

Thanks, what's interesting to me is that it used to work and stopped!

And I just tried a wired connection and it did work

BTW, you seem to have a hardening problem with your Nvidia drivers:

Thanks you very much, I have been trying to find a sollution since I installed on this PC VB, I hope this works!

[socratis]

Thanks, what's interesting to me is that it used to work and stopped!

Then it could be an updated driver, firmware, or a combination, can't really tell (unfortunately)...

[BONappetite]

Please read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues for some generic guidelines/ideas on how to address this, because your 3D acceleration will fail to materialize, that's why your VM seems to fallback to the Intel GPU:

I tried to follow that post and couldn't fix it. should I rather open a new thread on this or you want to answer here? please let me know if you need more info

[socratis]

should I rather open a new thread on this or you want to answer here?

Thanks for asking! Not a lot of people do, they tend to dump all their issues in one thread, and at the end the title of the thread has nothing to do with the original problem!

But there's nothing to discuss actually. It is what is is; your drivers are rejected. You need to address that by finding a suitable version from the vendor that doesn't have that problem. You'll know that you've solved it when there are no more references of rejected drivers in the VBox.log. I already showed you the strings to look for...