Forum archive
Access VM over network
(First, TKL is amazing. I had no idea it existed until a couple days ago. Awesome.)
Windows 2003 for host.
Rails TKL for guest.
VirtualBox 3.1.2 for VM.
Installed via the ISO: set up as a CD, booted to it, installed to hard drive. Straightforward.
DHCP gave me an address, using bridged networking. Great.
It didn't quite work, so I found this (/forum/support/20090707/network-interface-una...) which pointed me to resetting the udev rules and changing my adapter from eth1 to eth0. My host has multiple adapters, so I guess that's why that happened.
Now, I can ping the guest from the host. Webmin and webshell work. Sweet!
I can't get to the VM from a different computer on the network, though. I can get to the host (both from the network and from the guest) on its IP just fine, like I could before (it's our mysql & web & svn server).
No firewall on the host machine. We're all on the same subnet and using the same router/gateway.
Outgoing network connections from the guest work ok. I was able to update RubyGems and resolve DNS and ping google.
All of my experience with Ubuntu has been in shared hosting or VPS hosting, so I've never really messed with IP configurations.
I started to mess with NAT and port forwarding, but decided that was a road to avoid. Bridged networking looks like it should just work.
Any advice? If you need clarification or more infomation, lemme know. I don't know what diagnostic information would help y'all figure this out.
You are correct. You should not have to do NAT of forwarding with bridged networking. Your VM should be able to talk to the network directly.
We use CentOS for our hosts so I can't really say much about a Windows environment. It is very strange that connections are going outbound but not inbound.