Vista - Hyper-v and wireless networking

Hi All

I have an issue in getting wireless networking going with hyper-v. I've
googled various suggestions and my favoured option was to setup a bridge from
a 'virtual internal network' and the wireless nic. However, the guest o/s
always reports a duplicate ip address and disables its NIC.

I am using DHCP and have tried it on two different networks (office and home
which use different sub-nets so I cannot set static IPs - and as I wish to
access customer networks for demos etc - so again cannot use static IPs).

Hardware: Dell XPS M1710 laptop
OS: Windows Server 2008 (configured to run in workstation mode) with SP1 and
patest pathes, including Hyper-V RM (Windows6.0-KB950050-x64)
Wireless NIC: Intel PRO/Wireless 3945ABG

I wish to use the gues o/s for demos / development / testing etc so need
them to have network access and internet access. The guest o/s are all XP Pro
(latest SP and patches).

Last week I totally corrupted hyper-v by damaging its network configs so
have done a fresh O/s install over the last few days. (Note I didn't get
hyper-v and wireless working before then either)

The wireless network works perfectly on the host and i have access to
everything I need - just not from any hyper-v guest.

Any assistance greatly appreciated.
Ian

"Ian Crisp" <IanCrisp@xxxxxx> wrote in message
news:9ECEB007-BC9C-40B6-835D-5511A2B7597D@xxxxxxThat should work, but I have heard of other cases where DHCP from a
server on the LAN doesn't work properly in the vms. It appears to be a
problem with broadcasts not being transferred across the bridge (and DHCP
depends on broadcasts).

The only way to avoid that problem would be to run the vms in their own
network and run a NAT router between that network an the wireless NIC. Your
can then run static IPs on your virtual network.

In the past I tried doing this on the host (ie running RRAS in the
parent partition to link the wireless NIC to an internal virtual network)
but that method has some problems. I now run the virtual machines in a
private virtual network (ie no connection to the host) and route through a
RRAS server (w2k3) running in a vm (one NIC in the virtual network and one
in a network linked to the NIC in the host).

If you want to run Active Directory this is really the best option (which
is why I am running this way). You need to isolate your local network from
the physical one (run local DNS and DHCP and IP subnet) but still have
access to the physical network and the Internet.

Thanks Bill

I wanted to stay away from RRAS.

I've been experimenting with static/dynamic MAC addresses in the guest
settings in hyper-v. Then I came across a strange occurrence which i can
reproduce.

1) Boot host
2) Start a guest (reports a dupe IP)
3) Stop guest
4) Swtich guest to static MAC
5) Start guest (reports dupe IP)
6) Stop guest
7) Switch guest back to dynamic MAC
8) Start guest = Wireless working correctly from the guest! DHCP alloctes a
new IP (both on my wireless router at home, and from the DHCP server at work)


As you can see from above this is painful and has to be done for each guest
that I want to start everytime I need it.

On balance I think wireless and the bridge work, but something is failing
somewhere and switching the MAC settings back and forth seems to trigger
something to make it work.

I will keep digging but am now running out of ideas Any suggestion?

Cheers

"Bill Grant" wrote: