Check the VBox.log file for 'NAT:' entries. There is only one name server passed to the guest, perhaps this name server cannot resolve names.
On Wednesday 23 January 2008, Richard Cesar wrote: > Ah, yea that doesent work either, that was the reason I went to try a > traceroute/ping. When you open the browser and try to navigate to a page > It just hangs on what appears to be resolving the host. When I choose NAT > it takes a long time "waiting", if I choose HI in the network options it > goes immediately to an error page. > > On Jan 23, 2008 3:42 PM, Michael Thayer <[EMAIL PROTECTED]> wrote: > > Hello Richard, > > > > Try getting a page in a webbrowser using NAT. ping and traceroute will > > not work with the VirtualBox NAT implementation. > > > > Regards, > > > > Michael > > > > Richard Cesar wrote: > > > Hello, > > > > > > Pretty self explanitory from the post above, I have a windows > > > vista host running an XP guest, installation and everything went fine. > > > > Default > > > > > install did NAT for the internet, but I cant connect.. at all. I tried > > > > both > > > > > NAT and Host Interfaces, both failing. When I did HI I set media > > > > connection > > > > > to always on (read that it fixes it somewhere). No avail. With NAT > > > > selected > > > > > I did a traceroute to google (using their IP), and it showed it hitting > > > > only > > > > > 10.0.2.2. I am behind a router, but vista has no problem getting on > > > the internet by itself. Any Ideas? > > > > > > Richard > > > > _______________________________________________ > > vbox-users mailing list > > [email protected] > > http://vbox.innotek.de/mailman/listinfo/vbox-users -- Dr.-Ing. Frank Mehnert innotek GmbH, http://www.innotek.de
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
