After switching a virtual machine from NAT to BRIDGED mode, I ran in the following issue:
https://www.virtualbox.org/ticket/9112 related to NAT forwards.
I wasn’t able to restore the original settings via GUI – which didn’t ever show the forwards.
I solved simply removing the nats with vboxmanage.
# for svc in {apache,proftpd}/{HostPort,GuestPort,Protocol}; do
vboxmanage setextradata ubuntu VBoxInternal/Devices/pcnet/0/LUN#0/Config/$svc;
done
If you use putty on virtualbox, you’ll surely notice that the mouse pointer become almost invisible whenever you put it on the putty window.
A simple solution: just go to ControlPanel->Mouse->Pointer and change the default “select text” one  to a more visible one (like beam_r.cur).
Enjoy,
R.
When you run apache into VirtualBox, it’s unreachable from outside.
You have to tell to your PC to listen on the net and forward the request to the VM.
This nice post explains how.
Server web virtuale con VirtualBox, port forwarding
Anyway latest vbox have the nice Bridged Interface which should solve the issue!
A common issue with virtual environments (rdesktop, virtualbox, &co) is to have a common storage between real and virtual systems.
With vbox you can easily share a folder between guest and real host once you have installed Guest Additions. So
With rdesktop simply add the following parameter to
share a local directory with your remote host
# rdesktop winhost -r disk:Home=/home/rpolli