I have set up various VMs with Ubuntu 16.04 guests and Windows 10 hosts in different physical locations, nevertheless with a stable internet connection. Expecting the hosts to provide an IP address through Virtualbox to all these Virtual OSs, configured with a NAT network adapter (default settings), have a purpose to connect to a server.
For some reason this works perfectly okay for some Virtual OSs and I hope to be guided through a debug to solve this situation.
ip a
:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 08:00:27:a3:5b:03 brd ff:ff:ff:ff:ff:ff
inet6 fe80::6467:c72f:f210:ad4e/64 scope link
valid_lft forever preferred_lft forever
3: enp0s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 08:00:27:93:64:d0 brd ff:ff:ff:ff:ff:ff
/etc/network/interfaces
:
*NOTE: the following configuration is the same for all the OSs, which makes me think 'network manager' has nothing to do with the IP assigning procedure since most guests get their IPs, not sure though.
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet dhcp
I am currently stuck rebooting the guests that fail to get their IPs at their first try to get around the connection problem.