Forum Thread: Hiya, New to NullByte Forum, Been Watching Youtube Vlogs, Installed VirtualBox, Tried Kali, Installed Parrot Security

So i managed as a complete newbee to get the VM installed on my coreduo dell running the dell Windows 10 Home, using Realtek RTL8812au adapter without issues until i imported Kali and Parrot. So when the VM Box starts (Version 6.0.14) these machines disconnect my adapter. Now, when I first imported Buscador (weeks ago) and the adapter worked when i powered on that, but with the two newer machines I cannot get the adapter connected. The USB disconnects the Realtek 8812 and it no longer shows up as a connected device on the Host. I have to shut down any machine then get out of VirtualBox for it to reappear as a connected device in Windows, then reconnect to my network. I tried everything i could in the Adapter settings, NAT, Bridged, even Not Attached hoping the Kali or Parrot would then realize it but it dont work.

I read a lot of threads on the issue. I tried the >Device>USB>attach Realtek NIC - NOTHING WORKS.

So I get a "Failure to Attach" error most times "INVALIDARP" and the popup bar at the top says "Realtek 8812 is busy with another call request" Also in the Failure details an error code and "Console Wrap Error"

whatever that is.

Nothing i have done works, i even tried to mess with the VBox tools and Network settings and Adapters but i didnt go too far (i hope) so as i cant fix all that.

What should i do?
Is there any new wisdom on this issue?
I see a lot of dudes are having this issue.

After all, the reason for the Kali and Parrot were to use injection with the adapter, so if i cant get it running whats the use, i have three new OS in my VM that are now worthless if i cannot fix it.

Any help brothers would be appreciated.

1 Response

It sounds like there might be some compatibility issues between your Realtek 8812au adapter and the virtual machines you are trying to run. Here are a few things you can try to resolve the issue:

Update VirtualBox: Make sure you are running the latest version of VirtualBox. Older versions may have compatibility issues with certain hardware.

Check adapter settings: In VirtualBox, go to the settings for each virtual machine and check the network adapter settings. Make sure the adapter is set to "Bridged" mode, and that the correct network adapter is selected in the drop-down menu.

Check host network settings: In Windows 10, go to "Network and Sharing Center" and click on "Change adapter settings". Make sure the Realtek adapter is enabled and that it is set to "Obtain an IP address automatically".

Check USB settings: In VirtualBox, go to "Devices" and select the Realtek adapter from the USB menu. Make sure that the adapter is set to "Enabled" and that it is selected for the virtual machine you are running.

Try a different adapter: If none of the above steps work, you may need to try a different network adapter that is known to be compatible with VirtualBox and your virtual machines.

If you continue to have issues, you can also check the VirtualBox documentation and forums for more information on troubleshooting network adapter issues.

Share Your Thoughts