Similar to this SU question: "Network is unreachable" when attempting to ping google, but internal addresses work
Actually, it's pretty much the same base issue. I went through that thread trying to find a solution, I changed my resolv.conf:
before:
domain [my work domain]
search [my work domain]
nameserver [my gateway]
nameserver [my gateway2]
I changed it to:
after:
domain [my work domain]
search [my work domain]
nameserver 8.8.8.8
nameserver 8.8.4.4
However, any time I reboot the computer the resolv.conf gets overwritten to the previous version (the 'before' above).
The issues began after I installed virtualbox additions, X server and (specifically) LXDE:
Cat of apt history.log:
Start-Date: 2014-08-21 10:03:42
Commandline: apt-get install virtualbox-guest-utils virtualbox-guest-dkms
Install: x11-xkb-utils:amd64 (7.7+1, automatic), libxaw7:amd64 (1.0.12-2, automatic), xfonts-utils:$
End-Date: 2014-08-21 10:03:56
Start-Date: 2014-08-21 10:18:39
Commandline: apt-get install lxde
Install: desktop-base:amd64 (7.0.3, automatic), libgoa-1.0-0b:amd64 (3.12.4-1, automatic), lxmenu-d$
End-Date: 2014-08-21 10:21:52
Start-Date: 2014-08-21 10:26:40
Commandline: apt-get upgrade
Upgrade: libio-socket-ssl-perl:am
ifconfig on the guest:
root@Peridot:~# ifconfig
eth0 Link encap:Ethernet HWaddr 08:00:27:89:c9:20 og
inet addr:172.31.2.102 Bcast:172.31.2.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe89:c920/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2281 errors:0 dropped:1 overruns:0 frame:0
TX packets:463 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:266507 (260.2 KiB) TX bytes:120554 (117.7 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:240 (240.0 B) TX bytes:240 (240.0 B)
The adapter in VBox is a bridged adapter directly onto my ethernet connection; as are my other 2 VMs (which work)
Other SU questions I've tried:
"connect: Network is unreachable" in VirtualBox VM
