NAT is not working on WinXP64 guest

Discussions about using Windows guests in VirtualBox.
Post Reply
kleva
Posts: 4
Joined: 11. Nov 2010, 07:48
Primary OS: MS Windows XP
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: XP64bit

NAT is not working on WinXP64 guest

Post by kleva »

Hi all.

I have Win32 host, and Win64 guest. Virtual Box is 3.2.10.
I've set up NAT network adapter for my guest system.
The IP given by DHCP is 10.0.2.15, Gateway is 10.0.2.2, DNS is 192.168.0.1 (which is the same as on my host system).
The internet on guest system is not working. Ping is not working. But if I ping for example virtualbox.org, then the IP is determined in ping (88.198.19.108).

Why this can be?


Another question: on my host system I have new network adapter now: "Virtual Box Host Network Only". Host system has IP 192.168.56.1, Virtual Box is configured to run DHCP with range 192.168.56.101-192.168.56.254. I assume, that guest system should obtain IP from this range. How can I check it?
BillG
Volunteer
Posts: 5106
Joined: 19. Sep 2009, 04:44
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows 10,7 and earlier
Location: Sydney, Australia

Re: NAT is not working on WinXP64 guest

Post by BillG »

If you want to use the host only network, link a NIC in the guest to the host only network. It will get an IP in the 192.168.56 subnet and will be able to reach the host through its 192.168.56.1 interface. If you do not want or need to use the host only interface on the host you can disable it (from the host OS) just as you can disable any other interface.

What does not work with Internet from the guest? If virtualbox.org is resolving to an IP address, the guest must be able to find the DNS server (which it can only do through NAT).

From a command prompt, does nslookup virtualbox.org also give you the IP address? Does http://88.198.19.108 bring up the web page?
Bill
kleva
Posts: 4
Joined: 11. Nov 2010, 07:48
Primary OS: MS Windows XP
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: XP64bit

Re: NAT is not working on WinXP64 guest

Post by kleva »

Thanks, will try with 192.168*

Regarding NAT: nslookup works. Http://88.198.19.108 does not work on guest mashine. On Host it is ok:-)
BillG
Volunteer
Posts: 5106
Joined: 19. Sep 2009, 04:44
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows 10,7 and earlier
Location: Sydney, Australia

Re: NAT is not working on WinXP64 guest

Post by BillG »

That is very odd, and does not sound like NAT is the problem. If the DNS lookup works, your DNS request is getting through NAT to the DNS server on the 192.168.0 network. But your http request is not being processed. That sounds more like a firewall somewhere rather than NAT. NAT is a pretty simple process. What device is at 192.168.0.1? Does it do packet filtering?
Bill
kleva
Posts: 4
Joined: 11. Nov 2010, 07:48
Primary OS: MS Windows XP
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: XP64bit

Re: NAT is not working on WinXP64 guest

Post by kleva »

192.168.0.1 is a wifi router. It does not filter packets. The packets from host mashine are passing through.
Firewall on guest mashine is turned off.

Are there any ways to try to find out the place where the packets are beeing blocked?
kleva
Posts: 4
Joined: 11. Nov 2010, 07:48
Primary OS: MS Windows XP
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: XP64bit

Re: NAT is not working on WinXP64 guest

Post by kleva »

Another question regarding VRDP support: I've tryied to start up guest with headless mode on port 5000.

How can I connect through RemoteDesktop (mstsc.exe) to it? I mean using which IP address? I've tried to use 192.168.56.101, but it doesn't help.

I've also tried to connect using global IP of the host mashine - 217.117.118.xxx:5000 but still doesn't work.
Post Reply