virtualbox.org

Adapter (VBox bridge) seems to be "physically" (virtual physically) connected, and it uses the same ethernet cable and port as the host system. The host system gets an IP address without any problems, but not the VM.

That problem happened suddely, a hours ago there wasn't a problem like that.

Maybe it's not a Virtual Box problem, but windows 10 has updated itself in the background?? And that is the reason for that behavior?

-> Logs are attached.

-> The virtual machine is Debian 10 "Buster" with all most current updates installed.

Thank you very much for your feedbacks! :-)

I looked at the logs but could not see where the problem was indicated. Please zip and post the VM's .vbox file, as well as the output of these commands:

In the host:
ipconfig /all

In the VM:
ifconfig
or
ip address

VBox.log.1.txt wrote:

00:00:02.905811 [/Devices/e1000/0/Config/] (level 4)
00:00:02.905812   CableConnected <integer> = 0x0000000000000000 (0)

You seem to have unplugged the virtual Ethernet cable.

Thank you very much; then, it must be a mistake of our employee...

I never saw that option - with the network connection settings (we use a bridge - same subnet and adapter / physical cable like the win10 host system)

How to re-connect that "virtual cable"? Is there an option in the VM menu on top of the VM window?

Is is that what you meant? (It's on my PC not on the employees one)

Good eye, fth0! (as usual... )

Yes,Jmar, that is the correct spot to re-connect the cable.

Thx!!!

jmar83_the2nd wrote:Is is that what you meant?

Yes. Alternatively, in the status area at the bottom right of the VM window, there's a network icon with a drop down menu.

Thx!! :-)