Opened 6 years ago
Closed 6 years ago
#18279 closed defect (duplicate)
VM does not automatically reconnect to server after a temporary network disturbance
Reported by: | MSKS | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 6.0.0 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Windows |
Description
Hello,
After updating my laptop from Windows 7 to Windows 10 and using exactly the same VM (Windows 7 guest) I am facing a known I think VirtualBox issue:
In Bridged Adapter Networking mode, after a temporary network disturbance, e.g. start an endless ping and break temporarily the Ethernet connection by unplugging/plugging in the UTP cable, the connection to server does not restore automatically as it did with a Windows 7 host.
I use one of the workarounds reported in the past to restore the connection, without stopping the guest: in VirtualBox Manager, under the Network settings for the guest, I detach the Bridged Adapter (Attached to : None) -> Apply and then back to Bridged Adapter. Attached you can find the ping log from the guest machine as well as the VBoxBugReport logs.
This is a very annoying bug as I usually change between servers under the same guest and I always have to perform the workaround above to restore connectivity.
Note that the same issue under Windows 10 host applies both for VirtualBox 5.1 and 6.0 from where the logs are.
Happy New Year to All!
Attachments (2)
Change History (4)
by , 6 years ago
Attachment: | 2019-01-04-11-40-24-bugreport.tgz added |
---|
by , 6 years ago
Attachment: | Win7_Guest_ping.log added |
---|
comment:1 by , 6 years ago
comment:2 by , 6 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Replying to MSKS:
If it's a known issue, you should comment on the ticket that this is reported, not open a duplicate...
Duplicate of #15308.