Specifically, VirtualBox is configured (via the old Docker-Machine program) with both a NAT adapter and a Host-Only networking interface. The IP used to communicate is assigned to the Host-Only Networking adapter. My understanding is that these should both be entirely local the the PC and unaffected by external networking conditions.
I believe to to be external because, basically, there used to be one PC that exhibited this problem. So we split half the workload to another PC *identically configured*, and the old PC is working fine. It gets the disconnections but without fail recovers. The new PC is exhibiting the behavior of the old PC, where it waits for some kind of user login to recover.
A little bit of network topology here...
Code: Select all
internet
|
? connected some way...
/ \
managed switch managed switch
/ \ / \
PC 1 ethernet device PC 2 ethernet device
The primary purpose of the PC is to communicate with that ethernet device. When it was one PC, it was PC1. We added PC2 to troubleshoot it and PC1 started being able to recover from the network issues, with PC2 acting how PC1 used to.
So again specifically, what kind of events could cause a VirtualBox Host-Only connections to stop working? Until a user logs into the PC via TeamViewer? I was thinking maybe some kind of gateway configuration issue or something? Something a managed switch could be doing? This area is not my expertise, so thanks for any pointers!