Windows 7 on Virtual Box

[Win7User512]

Anyone running 7 on Sun's Virtual Box? I'm having difficulty connecting the OS in the virtual machine to the internet. Any help would be helpful. LOL.

I've tried several solutions online that worked for others, but they are not working for me.

 

[johngalt]

No issues here at all....when it installed all the drivers did you allow installation?

Also, does your virtual machine have the NIC enabled in its properties?

 

[algypalgy]

Hi all, first posting here. Anyway I have made several unsuccessful attempts at trying to get W7, in Virtual Box, connected to my network. I have spent many hours, and various permutations but all to no avail. I just wonder if W7 has carried over the Vista problems into Virual Box? But I don't really have a clue, and have read VB's Manual, cover-to-cover as well. If anyone does know what the problem is I'd like to know.

I'm also running Ubuntu 8.10 and the 9.04 beta in VB. I have access to the Internet, but, again, can't find away to get my Vista/XP network together in VB, indeed I can't even get the 2 Ubuntus talking to one another, but I love the challenge!!!!!

W7 work fine in VirtualPC, no problems.

Finally also tried to get W7 and Ubuntus running in VMware Player, but couldn't even start a VHD!!!!

 

[johngalt]

Answer my questions above, and also it would be prudent to know which version of VBox you're running....and which version of W7 you're installing....

 

[Win7User512]

Windows 7 x64 Build 7000 is the host.
Windows 7 x64 Build 7077 is the guest.
2.2.0 r45846 is the version of VirtualBox

7077 works fine everywhere except trying to connect.

By default, VB makes the Intel Pro/1000 MT Desktop the network adapter. That installs fine. But I get no connectivity.

I have dynamic IP set.

It is attached to NAT.

I did two or three fresh installs of the guest, but the same result. I tried every network adapter it offers. I tried bridging. But no internet at all, just local.

 

[johngalt]

That is more than strange. Have you had this with every build in VBox, or just 7077?

Anything in Device Manager not working?

Anything in your firewall preventing the NAT in VBox, or else your *router* preventing unauthorized outbound access from unrecognized IPs?

 

[Win7User512]

That is more than strange. Have you had this with every build in VBox, or just 7077?

Anything in Device Manager not working?

Anything in your firewall preventing the NAT in VBox, or else your *router* preventing unauthorized outbound access from unrecognized IPs?

This is the only build of Windows 7 I have installed in VirtualBox.

The only driver not working is audio.

No unique router settings; not blocking any IPs.

 

[bgowers]

I had several vrsions of Win 7 running in VB without any rpoblems, at the moment I'm running Win 7, 6068 x32 and it does all that it should do.
I use it mainly to use my printer which doesn't have any 64 bit drivers provided by it's useless manufacturer. ( Canon )

Bernard

 

[jimbo45]

Hi there
I often mess around with Virtual Machines -- networking CAN (but not necessarily) be a dog.

Do these.
(If you are running Linux as your HOST machine ensure all the Network interfaces are up and running -- Virtual one's as well as real -- I am using vmware but the process is identical with other Virtual Machine software.
The virtual interfaces might be vmnet1, vmnet8 or whatever - ensure they are active via IFUP command or the new GUI network manager found in most distros -- I prefer the old command line IFUP myself).

1) Try "Host Only" networking -- this will test to see if the "Virtual NIC" is working. Share a disk between your "Host" OS running Linux / Windows or whatever. That's the first thing to get working. If the Virtual NIC doesn't work then you are stuck.

2) If host networking works now try "NAT" networking. - This simply shares the IP address between your VM and your Host. Ensure the relevant interface is up and that all the networking adapters are enabled AND CONNECTED in the VM at power on. If this works then you should be able to access the internet.

3) (I prefer but YMMV) switch to "Bridged" networking. This assigns the VM it's OWN IP address. ensure aagin all the interfaces are up and runninf and the Virtal network adapter in the VM is connected and active at power on.

Incidentally for some Linux distros there's a problem in using "Bridged" networking when the Host machine has a wireless card. In this case switch to "NAT" networking. This doesn't seem to be a problem when your host is a Windows machine.

I assume you've allowed networking via firewalls/router etc etc. For these purposes your VM will be seen to the network just like another physical (REAL) computer and you have to set the configuration accordingly. Probably best while testing to switch all firewalls and AV software off -- just another area where things can go wrong. Turn them on again once you've got it all working.

Cheers
jimbo

 

[Win7User512]

Hi there
I often mess around with Virtual Machines -- networking CAN (but not necessarily) be a dog.

Do these.
(If you are running Linux as your HOST machine ensure all the Network interfaces are up and running -- Virtual one's as well as real -- I am using vmware but the process is identical with other Virtual Machine software.
The virtual interfaces might be vmnet1, vmnet8 or whatever - ensure they are active via IFUP command or the new GUI network manager found in most distros -- I prefer the old command line IFUP myself).

1) Try "Host Only" networking -- this will test to see if the "Virtual NIC" is working. Share a disk between your "Host" OS running Linux / Windows or whatever. That's the first thing to get working. If the Virtual NIC doesn't work then you are stuck.

2) If host networking works now try "NAT" networking. - This simply shares the IP address between your VM and your Host. Ensure the relevant interface is up and that all the networking adapters are enabled AND CONNECTED in the VM at power on. If this works then you should be able to access the internet.

3) (I prefer but YMMV) switch to "Bridged" networking. This assigns the VM it's OWN IP address. ensure aagin all the interfaces are up and runninf and the Virtal network adapter in the VM is connected and active at power on.

Incidentally for some Linux distros there's a problem in using "Bridged" networking when the Host machine has a wireless card. In this case switch to "NAT" networking. This doesn't seem to be a problem when your host is a Windows machine.

I assume you've allowed networking via firewalls/router etc etc. For these purposes your VM will be seen to the network just like another physical (REAL) computer and you have to set the configuration accordingly. Probably best while testing to switch all firewalls and AV software off -- just another area where things can go wrong. Turn them on again once you've got it all working.

Cheers
jimbo

Thanks Jimbo, I'll try some of those suggestions. I don't know if it is relevant, but my real networking adapter is an Intel wireless one.

 

[Win7User512]

Update:

Nothing his working. :-(

I don't get why a fresh install of VB and Windows 7 isn't working.

 

[sishuinian]

manual set ip:10.0.2.n (n>3)
subnet mask:255.255.255.0
gateway:10.0.2.2
DNS:10.0.2.3
have a try,maybe success!
good luck!

 

[Win7User512]

manual set ip:10.0.2.n (n>3)
subnet mask:255.255.255.0
gateway:10.0.2.2
DNS:10.0.2.3
have a try,maybe success!
good luck!

In the virtual machine, or the networking settings on the host?

 

[sishuinian]

of course！In the virtual machine！！

 

[Win7User512]

of course！In the virtual machine！！

Well you could have meant the VB adapter in the host.

Anyway, I "solved" it by creating a new vhd, setting the networking options BEFORE re-installing 7077. I was trying to set them after installation...seems like a bug in VB perhaps?

 

[sishuinian]

i think it's a bug,too.cost my much time on it! my english is poor! hoho

 

[johngalt]

When you did a fresh install of VBox did you make sure to remove all the old traces of it, including old machines and old settings?

 

[Win7User512]

When you did a fresh install of VBox did you make sure to remove all the old traces of it, including old machines and old settings?

Yes, I deleted the old vhd and such. Didn't re-install the app. Just got rid of all traces of the guest.

 

[johngalt]

Sorry, was actually asking the previous poster...

Glad you got yours working....

I need to figure out how to migrate Machines from one install to another so I can perform clean installs of the OS and still have access to all my VMs...without having to convert to OVMF format every time....