Hello Alex, When you use NAT networking, the guest gets its IP address from VirtualBox's internal DHCP server, not from your router's server. scp on the guest connecting to the host should work regardless of your ISP's setup, as through NAT, the guest sees anything the host does, and the host just sees the guest (in fact, VirtualBox) as a local application. Therefore, assuming your host's IP is 192.168.1.20, you can do
scp file [EMAIL PROTECTED]: from the guest and that will copy file from the guest to alex's home directory on the host. The host will just see a local application connecting to a local server, so firewalls should not play any role. Regards, Michael Alex Baer wrote: > Hi, > > I have the very same problem, even the IP address of my guest is identical > to yours. > > My environment is: > > VirtualBox OSE 1.3.3 running on Slackware 11 as host, with a guest running > Windows XP Media Center Edition. I configured NAT for the guest network > connection. > > My naive expectation was that the guest would now get just a new IP address > within my home network from my router/switch. But instead it got 10.0.2.15 > from ... s o m e w h e r e ...? > > I too can surf the internet and use WindowsUpdate and so on. I just cannot > connect to my host, as I would have to tunnel my ISPs firewall then from > the outside. Not sure if I have the skills to do this... ;-) > > I think it's possible to set up the guest OS with a fixed IP address > manually, but I tend to think there must be a cleaner way. > > Solution of this issue is vital, as only then I can use scp to transfer data > between host and guest, for backing up data created on the guest, eg. > Without some reliable way of exchanging data I am hesitating to actually > use the guest for production. > > Thanks for any help! > > Alex _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
