Busting my head (and other valuable parts of my body) getting Bridged networking in virtual WindowsXP (Windows 7 doesn't have this issue) with Linux host because I needed it to have DHCP IP and make it available to my home network, basic websites would load and others would time out. Also accesing the machine via SAMBA would cause errors once in a while. Using standard NAT would work and resolve websites immediately, but the machine would get IP assigned by host machine and would not be seen to the rest of the home network and completely invisible in router.
Sunday, October 6, 2013
VirtualBox Bridged Networking and MTU Problem in a Windows Guest
Busting my head (and other valuable parts of my body) getting Bridged networking in virtual WindowsXP (Windows 7 doesn't have this issue) with Linux host because I needed it to have DHCP IP and make it available to my home network, basic websites would load and others would time out. Also accesing the machine via SAMBA would cause errors once in a while. Using standard NAT would work and resolve websites immediately, but the machine would get IP assigned by host machine and would not be seen to the rest of the home network and completely invisible in router.
Labels:
bridged,
Debian,
dhcp,
Linux,
mtu,
nat,
networking,
virtual,
virtualbox,
windows
Subscribe to:
Posts (Atom)