Does vbox have any resident part that is running even after closing all VMs ? Because the described problem went away only after rebooting the host. David
________________________________ From: [EMAIL PROTECTED] on behalf of Michael Thayer Sent: Sun 03-Jun-07 17:31 To: VirtualBox end user list Subject: Re: [vbox-users] Guest NAT networking does not work after netfailure Hello David, It sounds reasonable to post this to the bug tracker, as it definitely sounds like a bug. As for your last posting not being answered, I'm afraid that our resources are often rather stretched to keep up with all the user input we get, even when that input is useful and interesting (and obviously people from the user community answer or they not as they see fit). Please don't take it personally! Regards, Michael On Sunday 03 June 2007 15:29:38 David Balazic wrote: > I have vbox 1.3.8 on Windows XP SP2 > > I started a VM (with NAT networking), while the host had no network > connection. Then I connected the host and networking on the host worked. > > But in the guest it did not. > > It turns out, that outgoing TCP connections work, but only to numerical IP > addresses. DNS resolving on the other hand not. Tried a manual "nslookup > some.server.com" and it failed. > > The TCP/IP parameters in the VM wre correct : > - address 10.0.2.15 > - gateway 10.0.2.2 > - DNS server : 10.0.2.3 > > Regards, > David > > PS: Or should I post bugs diretcly to the bug system ? To my last post here > I received not a single reply. _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
<<winmail.dat>>
_______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
