martin123 wrote:I moved the VMs to an external hard drive.
It's after moving the VMs that the internet access problem occurred.
Normally, simply moving the VM files from one drive to another will not damage anything in the VM.
However, if only the VM's drive file is moved, and a new VM is built around the drive file, the network setup may not match what the VM had originally.
How exactly did you move your VMs? And if you move a broken VM back to where it was before, does internet come back?
Also, let's look at the VM setup:
scottgus1 wrote:For one VM that is still working and one VM that has the problem, please provide the following:
1. Please right-click the VM in the main Virtualbox window's VM list, choose "Show in Explorer/Finder/File Manager". In the window that opens, zip the VM's .vbox file (not the .vbox-prev file), and post the zip file, using the forum's Upload Attachment tab. (Please make sure all file extensions are shown, so you will be able to see the .vbox extension easier.)
2. Start the VM from full power off, not save-state. If it is the failing VM. run until you see the problem happen. If it is the good VM, run until you can access the internet. Then shut down the VM from within the VM OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Please right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.
Further, please run and post the output of this on the host:
if Windows:
ipconfig /allif Mac, Linux:
ifconfig or
ip addressRun and post this in both working and failing Windows VMs:
ipconfig /allping 8.8.8.8