My nic is “Broadcom NetXtreme 57xx Gigabit Controller” and my wireless card is “Intel(R) PRO/Wireless 3945ABG Network Connection.”
While configuring network setting in Virtual box, I choose host interface which does show both of above cards.
While it works just fine with Broadcom but does not seem to work with the wireless card.
Please advice steps to troubleshoot
Wireless Card Intel(R) PRO/Wireless 3945ABG
-
aribendaniels
- Posts: 1
- Joined: 15. Apr 2009, 14:39
- Primary OS: MS Windows XP
- VBox Version: OSE other
- Guest OSses: Linux
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Wireless Card Intel(R) PRO/Wireless 3945ABG
The network adapter that the guest will use is a virtual adapter.
In all actuality the guest will use what ever your host is using.
So selecting the Intel is all you need.
When you change the adapter that the host uses it will still work on the guest as the Intel adapter
In all actuality the guest will use what ever your host is using.
So selecting the Intel is all you need.
When you change the adapter that the host uses it will still work on the guest as the Intel adapter
-
NiteShdw
- Posts: 7
- Joined: 4. Apr 2008, 23:55
- Primary OS: MS Windows 7
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: XP
- Location: San Francisco, CA
- Contact:
Re: Wireless Card Intel(R) PRO/Wireless 3945ABG
I'm having the same issue. Running 2.1 I was able to select my Intel wireless card as a host adapter, which means that the virtual machine would actually get a DHCP address directly from my router.
After upgrading to 2.2, restarting my VM said that the adapter isn't available. When I go to the network settings, it's still set as Host Adapter, but no adapters are listed.
I'm just confused as to why this worked in 2.1 but not in 2.2.
After upgrading to 2.2, restarting my VM said that the adapter isn't available. When I go to the network settings, it's still set as Host Adapter, but no adapters are listed.
I'm just confused as to why this worked in 2.1 but not in 2.2.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Wireless Card Intel(R) PRO/Wireless 3945ABG
Reinstall VBox and tell it to repair.
-
dinkop
- Posts: 2
- Joined: 16. Apr 2009, 04:54
- Primary OS: MS Windows XP
- VBox Version: OSE other
- Guest OSses: Win
Re: Wireless Card Intel(R) PRO/Wireless 3945ABG
It's confusing, isn't it 
In version 2.1x they've used the term "Host-only" to create a bridged network between the virtual adapter inside the Guest (PCnet-FAST III by default) and an existing physical adapter on the Host.
It looks like this is changed now. In version 2.2 "Host-only" is used to create a bridged network between the virtual adapter in the Guest and a VIRTUAL (non-physical) adapter in the host. You can create/delete these VIRTUAL HOST adapters from menu File/Preferences... then Network.
The old 2.1x "Host-only" style of networking is now called "Bridged Network" in version 2.2.0. This is what you have to select in your VMs Network settings.
When you do this, you may have to delete the Guest's Virtual Network adapter from Device Managaer and to force it to be re-detected. Otherwise your network won't work. Or at least this is what happened to me.... twise.
In version 2.1x they've used the term "Host-only" to create a bridged network between the virtual adapter inside the Guest (PCnet-FAST III by default) and an existing physical adapter on the Host.
It looks like this is changed now. In version 2.2 "Host-only" is used to create a bridged network between the virtual adapter in the Guest and a VIRTUAL (non-physical) adapter in the host. You can create/delete these VIRTUAL HOST adapters from menu File/Preferences... then Network.
The old 2.1x "Host-only" style of networking is now called "Bridged Network" in version 2.2.0. This is what you have to select in your VMs Network settings.
When you do this, you may have to delete the Guest's Virtual Network adapter from Device Managaer and to force it to be re-detected. Otherwise your network won't work. Or at least this is what happened to me.... twise.