virtualbox.org

Running Windows XP (SP2) as guest on Windows Vista x64, independant of the Virtualbox version (tried 2.2.4, running 3.0.6) the following occurs:
- if the network adapter is in NAT the XP guest gets an IP (10.2.x.x) and connect to the internet without problems, but no connection to the host ip is possible, which is OK
- if the network adapter is in Bridged the XP guest gets an IP from the DHCP/Router (192.168.1.x) and connect to the host, which is OK. But no connection to the internet (through http-browsers) is possible. A ping will resolve to the internet (like. virtualbox.org), just browsing with Internet Explorer of FireFox will not work. Errors like "reinitialized connection" and "webpage cannot be loaded" come on the screens.
I would like to use this guest to be able to connect as well to the internet and the host computer, as it were a seperate physical computer on the router's network.
Thanks for suggestions and/or responses.

This sure is a strange situation. NAT works, but you can't access the Host (you can access it through it's normal IP address and 10.0.2.2 though, just not it's name). Bridged gives you access to your network, just not the internet over port 80 (ICMP ping apparently works). DNS works, because it resolves.

With NAT, you can open a website without issues, right? If you use bridged, can you access the webinterface of your router? If so, try to open a website using it's IP address. Try setting a static IP address to the Guest, making sure it won't conflict with other systems on the network. Gateway and DNS both to the router.

Hi Sasquatch, in reply to your suggestions:
- with NAT still can open a website without issues = YES
- with Bridged, can you access the webintf of the router = NO
- with NAT, can you access the webintf of the router = YES
- try static IP's on the guest incl. Gateway & DNS = no solution, still the same
Thanks

With bridged, can you access resources on the Host or other system on the network like shares? If not, can you do it if you don't set a gateway?

In Bridged mode I can access both shares (\\VBOXSVR\whatever and \\Server-name\share-name)
In NAT only the VirtualBox Shared Folders wil work (\\VBOXSVR\whatever), but can access server-shares only through the IP-adress (like \\IP.of.Server.name\share-name)
P.S. For now I have to accept the NAT solution to access Internet normally and the internal network environment through the IP's (maybe make them static).
Thanks, Arie

Sounds like the servernamed share is resolved via other then tcpip like netbios, such resolution is not passed via nat.

You think? My concern is more that of bridged not working outside his LAN. There is a very small possibility that the router has MAC filtering and thus blocks his Guest, but that contradicts the working DNS resolving and ping replies.

I can see my LAN's machine names (netbios) in Bridge but not in NAT, which is normal nat behaviour.

Did you really think I didn't know that? I've been telling people from the start that they have to use IP addresses when using NAT to get onto the network.
What I'm trying here, is a way to know what's wrong with bridged in his network.