Hi,
I installed the latest (2.04?) Virtualbox from Sun on a 64 bit Ubuntu 8.04 workstation and then installed XP. Miraculously, the network worked fine immediately, the immaculate installation! Then, I spent half a day installing Photoshop, Nero, Comodo firewall/AV, etc. Then I saved a snapshot. I did a samba mapping of my Ubuntu drive into xp and it worked fine (although I could not see my xp share in Ubuntu).

Suspend mode does not work (never fully wakes up, ~black screen, garbled contents, ...), so I have to turn it off every night. Today, all networking is gone in xp and windows is complaining that there is no firewall or a/v software.

I tried assigning a static ip address which (I think) is the same address it had when it worked:
ipconfig ->
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 10.0.2.15
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.2.2
I gave it the same dns servers that my real xp box uses.

I also tried disabling and then enabling it again in dhcp mode to perhaps get a new dhcp lease. The ipconfig shows all zeros.

I can't get to the internet or see my Ubuntu shares so I can't get anything in or out of xp_in_a_box.

Is there a manual setup routine to get me back on the net?

Thank you,

BrianP

First: there's an easier way to share files with your virtualbox host. From the virtualbox control window, see settings -> shared folders for the XP host. As for the rest of it, I'm not clear on what went wrong, or to what extent you're having trouble.


...but it sounds like this might be relevant: http://www.virtualbox.org/ticket/1660

I ran into much the same networking problem on one of my Lenny machines with Win2K. Curiously, the my other machine works with no problem. After trying all sorts of crap with bridging and so on, I managed to get networking to work again after setting the DNS Server Address for the network device from within the Win2K guest. Be sure the network device is set as NAT in the VirtualBox configuration.

If networking is broken, have you tried removing the adapter and restarting the host to get it re-installed? ...I'm not convinced man-handling a virtual adapter which (as QB02 mentioned) typically uses NAT through virtualbox is the proper course for resolution.

Secesh, just as a note to you, on my machine I did that removal and reinstall dance several times to no effect. I still don't know why the one won't just simply work properly, but it won't.

That's interesting. Thanks for the bump. I haven't been using virtualbox very long. ...long enough to know I like it a lot for desktop virtualization, and also long enough to notice it's not free from quirks. I guess in that case: I gots nothing!