New
#21
In this case it's most likely that the virtual box is actually causing the issue. I've seen this happen before quite a few times although I'm not entirely sure what the virtual box Ethernet connection is being used for?
As a test I would enable DHCP on the Ethernet connection then uninstall V box and test for reliable connectivity over a time period.
It may also be worth typing the gateway IP of 192.168.0.1 into the IPv4 static settings for the Default Gateway of the Ethernet connection since it doesn't seem to be picking it up for some reason. This may be because the static IP info isn't entered correctly.
Try using a different version of Virtual box if the test proves correct.