virtualbox.org

Thank you for your response, socratis.

socratis wrote:

MickeyBlue wrote:using NAT instead of Bridged Adapter

From the screenshot you provided you didn't use "NAT", you used "NAT Network". They're close, but not the same. Try with "NAT" at the beginning; it's the easiest and most reliable.

I tried all the options listed in the Attached To: drop down, but I didn't take a screen shot of all of them, because I thought it would be overkill, so I only did a couple of them. I have attached the screen shot of me trying NAT.

If you want to go down the "NAT Network" path, you have to go to VirtualBox preferences -> Network -> NAT Networks and add a NAT network. Read the manual for more information.

I'm not partial to NAT Network, as I'm willing to go down whatever path I need to. I'll look into this more when I get home, but I'm about to get in the car and drive, which makes troubleshooting a computer a little difficult. haha

I'm assuming VirtualBox preferences are to be found in a different location than where you find Preferences for most Mac apps as I cannot find VirtualBox preferences anywhere in the menu bar.

If VirtualBox has the focus (your main application, not the VM), you'll definitely see the preferences option in the usual place.

From the screenshot you provided; did you notice that the checkbox that is titled "Cable connected" is not checked? I'll have to admit that I didn't notice it in the first screenshots that you provided. If you want connectivity, you must be connected. By definition .

socratis wrote:If VirtualBox has the focus (your main application, not the VM), you'll definitely see the preferences option in the usual place.

That statement is correct. I had the VM front and center.

From the screenshot you provided; did you notice that the checkbox that is titled "Cable connected" is not checked? I'll have to admit that I didn't notice it in the first screenshots that you provided. If you want connectivity, you must be connected. By definition .

Originally, the "Cable connected" box was checked. But after trying many things and still no success generating internet connectivity, I unchecked the box as I had hit the "I'll try anything even though it shouldn't work in theory" stage of troubleshooting. So, I've tried with that box checked and without it checked. Not even after setting up a NAT Network once I found Preferences.

I have noticed that I can no longer choose Adapter 2, 3, or 4 anymore. Not sure when that option went away, but I used to be able to pick an adapter and not be stuck with Adapter 1.

I've also removed the VM and set up a new one. Everything remains the same.

Hi - I have been having the exact same problem with my XP install on my Mavericks Macbook Pro.

At first when i tried to open IE, it would not open at all and a message would pop up saying 'the computer had no connection to the internet'. I tried every setting possible (bridge, NAT etc) in the network settings, to no avail. I too had all the other adapters greyed out and no 'Name' available with NAT selected.

I then went and enabled 'internet sharing' on OSX in the pref pane (it was disabled before). I can now open IE on the VM but it still cannot connect to any internet sites. So, something has changed but it is not yet fixed. Any thoughts?

Ok - so I managed to fix this problem. When you I first set up the machine, the network settings defaulted to NAT but the 'Adapter Type:' was Intel PRO/1000 MT Desktop (82540EM)' . After checking on my XP VM on my iMac i noticed that the adapter type on this was set to 'PCnet-FAST III (Am79C973)' .

I changed the one on my macbook to match this and hey presto it worked! Note that you can only change this setting when the VM is powered off, otherwise it is greyed out. When it is powered off you will get the Adapter options available to you again also.

Screenshot of the working settings below:

That did the trick for me, too, Sandy. Of all the things I tried, I didn't think to play around in Settings in VirtualBox because it looked exactly the same as the Settings within the VM, so I didn't think it mattered. That also explains why I couldn't choose Adapter 2, 3, or 4, either. Thank you for ending four days of frustration!