Originally Posted by Matir
There's a dozen different reasons that could cause this. When you say it doesn't have access to the internet -- does it get a virtual ip (usually 10.0.0.0/8 netblock) from the host? Can you resolve IPs with dig or host? Are there any firewall rules in place on either box? Is either box multi-homed (multiple network connections)? What guest OSes are you using? Are you using NAT for networking on both?
Let me start all over. Both host machines are running Lenny with custom kernels. The kernel configs are almost identical on both kernels. The guest OS on both machines is Windows 2000. Both machines have Atheros AR5212 based wifi connections with wpa_supplicant and dhclient3 on the ath5k driver in the kernel. The VirtualBox software on both machines was downloaded from source. One was compiled with kmk. On the other, the one that doesn't access the internet, I have tried both compiling with kmk and with fakeroot (the debian way). Running netstat -r on both guests (both machines) shows an ip address of 10.0.2.15. The routing looks the same on both. The /etc/network/interfaces files are the same on both machines with the exception of different static addresses on the ethernet cards joining them together this side of the ATT router. Both guests use the default network adapter with NAT. There are no firewalls in place. In both guests, nslookup tries to go through 10.0.2.3. One works, the other doesn't.
That's kind of jumbled, I guess. Sorry. But it does pretty much describe what's going on. I have no compelling reason that these need to work. It's just a toy to play with for a few days till I get bored with it.