[vbox-dev] NAT/slirp issue?
huisinro at yahoo.com
Thu Dec 18 18:06:51 PST 2008
Yes, you are right. From the vbox.log, I found those "NAT: DNS" lines, it indeed picked the wrong DNS server. It basically pick the DNS from the internal network, rather the interface that can browse internet.
I also verified that IE works from vm is using ip address directly, so it's purely DNS issue.
Perhaps, can perform some kind of checks, and pick the DNS that can resolve internet names?
--- On Thu, 12/18/08, Frank Mehnert <Frank.Mehnert at Sun.COM> wrote:
From: Frank Mehnert <Frank.Mehnert at Sun.COM>
Subject: Re: [vbox-dev] NAT/slirp issue?
To: vbox-dev at virtualbox.org
Date: Thursday, December 18, 2008, 9:30 AM
On Thursday 18 December 2008, Huihong Luo wrote:
> I have a windows xp host PC that has two network interfaces, one is for
> internal local network without internet connection, the other can connect
> to internet. These two interfaces have 2 different IPs.
> Somehow, vbox vm (configured as NAT) running on this pc can NOT browse any
> internet websites, but it works for the local network. I checked the
> settings inside vm, the adapter and ip are correct, and there is traffice
> between this vm and the host.
> It seems somehow the vm is hooked to the internal network on host, rather
> than the one that can browse internet. I don't know how slirp works
> internally, but I assume it uses windows socket api to send/receive
> packets. Any chance that traffic is bounded to a specific interface?
Please try again in NAT mode. Then have a look at the VBox.log
file yourself. Search for 'NAT: ...' lines and have a look at
lines which mention name servers. Please check if the correct
name server is passed to the guest.
Dr.-Ing. Frank Mehnert Sun Microsystems http://www.sun.com/
vbox-dev mailing list
vbox-dev at virtualbox.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vbox-dev