virtualbox.org

Hi, I'm only about 4 hours into using VirtualBox, and I already have a problem. Actually, I'm pretty shocked how well everything has gone so far. I have the VM running ( 3.1.4 r57460 ), XP guest installed and running, shared folder setup, and Additions installed.

What I don't have is a network connection on the Guest. I've searched this forum, and checked the FAQ, to no avail so far. The FAQ mentions using "Internet Connection Sharing to the virtual Interface without the use of a bridge" but when I go into 'Advanced Properties' of the LAN connection, I only see an error about "Windows cannot display the properties..." ( using http://support.microsoft.com/kb/306126 as a reference, fwiw ).

The host connection is fine, and the Guest thinks it has a connection, but no HTTP traffic will pass ( Local Area Connection status claims to be 'Connected' for some 45 minutes now, at 100M, but sent and received packets are both zero ). The host is a MacBook Pro connected to an 802.11g wireless router. I'm still using the default NAT, but without success.

I tried pinging a few hosts, until I read that ping won't work anyway. Now I'm testing solely with simple HTTP, and it doesn't work. It is not a DNS issue ( also found in the FAQ ) as I cannot reach servers by direct IP either.

If you have any further suggestions, or a reference to more information about ICS on VB, please let me know. Thanks.

Sounds like a firewall issue to me.

My understanding of NAT is that devices upstream from the host would not have any knowledge of virtualization. In other words, from the perspective of the wireless router ( or any other point on AT&T's network, or the internet ) traffic from the host OS and the guest OS are indistinguishable ( for most protocols, anyway ). If that's the case, I don't see how a firewall could selectively allow one to pass but not the other.

Seems like the problem has to be internal to my VirtualBox, or am I misunderstanding something?

Thanks.

I too am a recent starting user of VirtualBox 3.1.4.

I think it's something within the Guest machine. I too run on a Mac, a 2009 iMac Core 2 Duo, and my access to the world is a DSL modem via phone line connected to an older Airport Extreme snow dome (for wireless access) that BOTH my host and Linux Guest(s) see (to my surprise - and delight) and work with no problems. I'm using the default NAT access.

I've tried Linux Mint 8, PC-BSD 8 and now have PCLinuxOS-2010-beta2. All have seen and are able to use the wireless.

I think you mentioned you run Windows XP as your Guest. Could it be something within Windows XP?

humdinger70 wrote: I think you mentioned you run Windows XP as your Guest. Could it be something within Windows XP?

I guess it could be, but XP is listed as a supported guest OS in the VB UserManual, with the comment...

"Windows 2000 / XP / Server 2003 / Vista / Server 2008 / Windows 7 beta

All versions/editions and service packs are fully supported (including 64-bit versions, under the preconditions listed below). Guest Additions are available."

I would think that if there was a terminal problem with networking under XP, that would at least warrant a note there.

After a little more digging, it appears that XP is not getting an IP address. That MAC address is not the same as the host's, so I don't know where it came from, although the DNS server address is correct.

There must be a step I'm missing here, but I can't seem to find it. I also tried switching to bridged networking, but I get the same result as with NAT.

The guest will never have the same MAC address as the host with NAT or bridged networking. You can't have 2 network adapters with the same MAC address. VirtualBox assigned the MAC address to the guest's virtual network adapter.

That what I was hoping, but I wasn't sure if there was any need for VB to actually fake a MAC address.

So the question is then, what does VB need to have (happen) to assign an IP address to the guest's adapter?

In the guests network settings ipv4 properties, is it set to automatically receive its ip address and dns?
Also from the host terminal/command windows VBoxManage showvminfo <VM Name> --details --machinereadable and post here. Replace <VM Name> with the actual name of the VM. Use "" if the name has a space in it.

Well, if you are using NAT networking in VB, VB should have assigned an IP address to the guest. This by default would be 10.0.2.15.

If you are using bridged networking, you would either need to have a router that assigns the IP address to the guest or you would assign the IP address statically.

Perryg wrote:In the guests network settings ipv4 properties, is it set to automatically receive its ip address and dns?

Yes, both.

Perryg wrote: Also from the host terminal/command windows VBoxManage showvminfo <VM Name> --details --machinereadable and post here. Replace <VM Name> with the actual name of the VM. Use "" if the name has a space in it.

Code: Select all

Sun VirtualBox Command Line Management Interface Version 3.1.4
(C) 2005-2010 Sun Microsystems, Inc.
All rights reserved.

name="XP Pro"
ostype="WindowsXP"
UUID="b2597bf1-868f-40cb-8b58-af04764ca273"
CfgFile="/Users/hillman/Library/VirtualBox/Machines/XP Pro/XP Pro.xml"
hardwareuuid="b2597bf1-868f-40cb-8b58-af04764ca273"
memory=512
vram=16
cpus=1
synthcpu="off"
bootmenu="messageandmenu"
boot1="floppy"
boot2="dvd"
boot3="disk"
boot4="none"
acpi="on"
ioapic="off"
pae="on"
biossystemtimeoffset=0
hwvirtex="on"
hwvirtexexcl="off"
nestedpaging="on"
vtxvpid="on"
VMState="running"
VMStateChangeTime="2010-03-27T13:55:36.499000000"
monitorcount=1
accelerate3d="off"
accelerate2dvideo="off"
teleporterenabled="off"
teleporterport=0
teleporteraddress=""
teleporterpassword=""
storagecontrollername0="IDE Controller"
storagecontrollertype0="PIIX4"
storagecontrollerinstance0="0"
storagecontrollermaxportcount0="2"
storagecontrollerportcount0="2"
storagecontrollername1="Floppy Controller"
storagecontrollertype1="I82078"
storagecontrollerinstance1="0"
storagecontrollermaxportcount1="1"
storagecontrollerportcount1="1"
"IDE Controller-0-0"="/virtual/pro.vdi"
"IDE Controller-ImageUUID-0-0"="1b615a13-f58e-46f7-a1c8-7bdcba432a04"
"IDE Controller-0-1"="none"
"IDE Controller-1-0"="/Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso"
"IDE Controller-ImageUUID-1-0"="77e2a3d4-051d-45dc-9bfa-2473c56ab6d7"
"IDE Controller-1-1"="none"
"Floppy Controller-0-0"="emptydrive"
"Floppy Controller-0-1"="none"
natnet1=""
macaddress1="0800274B074D"
cableconnected1="on"
nic1="nat"
nic2="none"
nic3="none"
nic4="none"
nic5="none"
nic6="none"
nic7="none"
nic8="none"
uart1="off"
uart2="off"
audio="coreaudio"
clipboard="bidirectional"
VideoMode="1040,780,32"
vrdp="off"
usb="on"
SharedFolderNameMachineMapping1="VirtualShare"
SharedFolderPathMachineMapping1="/virtual/shared"
VRDPActiveConnection="off"
VRDPClients=0
GuestStatisticsUpdateInterval=0
StatGuestSample=0

dmcgraw wrote:Well, if you are using NAT networking in VB, VB should have assigned an IP address to the guest. This by default would be 10.0.2.15.

This made me think 'Maybe I can just configure it manually?'

I turned off automatic assignment of IP address, and set it to 10.0.2.15. I also set the DNS server address, and the default gateway to the Host's IP address ( as I read elsewhere is required ). I copied the subnet mask from the host, as well.

Still no joy, although the failure mode has changed. Previously, I got an instantaneous error as you'd expect with basically no network configuration in-place. Now, I appear to be getting a timeout, so it is at least trying.

When you installed VirtualBox if you did not select to not install the network drivers then they should have installed by default.
You more then likely can not assign a static NAT address due to the way VBox handles NAT.
The fact that Windows sees the adapter and has loaded the drivers means it does see it and is happy with it.
Ready to check out the firewall yet?

Perryg wrote:When you installed VirtualBox if you did not select to not install the network drivers then they should have installed by default.
You more then likely can not assign a static NAT address due to the way VBox handles NAT.
The fact that Windows sees the adapter and has loaded the drivers means it does see it and is happy with it.
Ready to check out the firewall yet?

Sure, I'll check the firewall. The Mac OS X firewall is off. Checked the log anyway, nothing in it.

The wireless router has one too, but I don't see how it can either prevent the guest OS from getting assigned an IP address, or differentiate between host and guest traffic. The only entries in the firewall log for today are 'unknown inbound connection denied'. It is setup to allow all outbound traffic. The router currently sees two machines, my host and my wireless printer, as you'd expect. It has no knowledge of the guest.

Normally using NAT just works.
The guest gets its NAT address from VBox and it actually works as a switch. It uses the host adapter as its means of connection since VBox uses a virtual adapter.
Something has to be blocking this from working.
Since the guest actually sees the adapter it has to be something after that. How about the Windows Firewall?
Since you have a router try to use Bridged and see if it has to do the VBox drivers. Did you select to not install them (or some) on the original installation?
Maybe there was something corrupt in the install. There is a new version that came out this week version 3.1.6 and it did have some fixes for MAC and for NAT as well. See if that is the problem.

In case it happens to anyone else...

I never did figure out why VB 3.1.4 wouldn't provide an IP address to my guest OS. I didn't use my virtual box much as a result, but yesterday, I had cause to do so again. I saw that 3.2.8 was available, so I upgraded, and re-installed the (exact same) guest OS.

It works now. If you have problems with NAT, and are using 3.1 or thereabouts... try upgrading.

Thanks.

virtualbox.org

No Traffic Over NAT LAN, XP on OSX

No Traffic Over NAT LAN, XP on OSX

Re: No Traffic Over NAT LAN, XP on OSX

Re: No Traffic Over NAT LAN, XP on OSX

Re: No Traffic Over NAT LAN, XP on OSX

Re: No Traffic Over NAT LAN, XP on OSX

Re: No Traffic Over NAT LAN, XP on OSX

Re: No Traffic Over NAT LAN, XP on OSX

Re: No Traffic Over NAT LAN, XP on OSX

Re: No Traffic Over NAT LAN, XP on OSX

Re: No Traffic Over NAT LAN, XP on OSX

Re: No Traffic Over NAT LAN, XP on OSX

Re: No Traffic Over NAT LAN, XP on OSX

Re: No Traffic Over NAT LAN, XP on OSX

Re: No Traffic Over NAT LAN, XP on OSX

Re: No Traffic Over NAT LAN, XP on OSX