Cisco WLC 3504 not allowing simultaneous connections from Hyper-V Client via Wireless Network Adapter
To whom it may concern
Setup:
Cisco Wireless LAN Controller with version software version: 8.8.120.0 and Image version: 8.5.103.0
3x Cisco Aironet 1832 Access Points controlled by the Cisco Wireless LAN controller
I have a client with the following problem. Basically there is a team that works from their Virtual Machines via Hyper-V. When connecting via LAN cable, they do not experience problems. However, it is necessary for the team members to roam within the building between the Cisco Access Points and connect to the network or internet, when they do this there are issues with the connection.
Example Client connecting:
Dell Latitude 5580
Windows 10 Pro
Hyper-V Role installed
Core i5-7200U @ 2.5GHz
8GB Ram
500GB HDD
Wireless LAN Adapter updated to latest version via Dell Support Assistant
Basically you configure your Hyper-V Virtual Switch Manager to work with your Wireless Network Adapter. I have attached a screen shot named Hyper-V Virtual Switch settings.docx with the configuration.
You are connected to the SSID that is being broadcast by the Cisco WLC 3504. You start your VM and boot into Windows 10. Your VM will display that you are connected. But once you start testing your connection, you'll see that your VM is getting constant time out to Google DNS 8.8.8.8. In the same time, you will run the same ping request to DNS IP 8.8.8.8 on your laptop (Hyper-V Host) and you will get a constant reply for a let say 20 lines. Then the host will start to time out and the VM will start to reply to 8.8.8.8
It is almost like the Cisco WLC does not like the Hyper-V host and the Virtual Machine connecting to the same SSID at the same time and only prioritizes either to Hyper-V host or the VM.
When connecting to my home Access Point, there is not problem and both host and VM can ping google DNS without time outs.
Please advise on how to get the VM to ping 8.8.8.8 constantly without time outs or get the Cisco WLC to service both requests from VM or Hyper-V host.
Please let me know if you require further information.
Kind Regards
Lourensvd
Cisco WLC 3504 not allowing simultaneous connections from Hyper-V Client via Wireless Network Adapter
Hyper-V-Virtual-Switch-Settings.docx
Setup:
Cisco Wireless LAN Controller with version software version: 8.8.120.0 and Image version: 8.5.103.0
3x Cisco Aironet 1832 Access Points controlled by the Cisco Wireless LAN controller
I have a client with the following problem. Basically there is a team that works from their Virtual Machines via Hyper-V. When connecting via LAN cable, they do not experience problems. However, it is necessary for the team members to roam within the building between the Cisco Access Points and connect to the network or internet, when they do this there are issues with the connection.
Example Client connecting:
Dell Latitude 5580
Windows 10 Pro
Hyper-V Role installed
Core i5-7200U @ 2.5GHz
8GB Ram
500GB HDD
Wireless LAN Adapter updated to latest version via Dell Support Assistant
Basically you configure your Hyper-V Virtual Switch Manager to work with your Wireless Network Adapter. I have attached a screen shot named Hyper-V Virtual Switch settings.docx with the configuration.
You are connected to the SSID that is being broadcast by the Cisco WLC 3504. You start your VM and boot into Windows 10. Your VM will display that you are connected. But once you start testing your connection, you'll see that your VM is getting constant time out to Google DNS 8.8.8.8. In the same time, you will run the same ping request to DNS IP 8.8.8.8 on your laptop (Hyper-V Host) and you will get a constant reply for a let say 20 lines. Then the host will start to time out and the VM will start to reply to 8.8.8.8
It is almost like the Cisco WLC does not like the Hyper-V host and the Virtual Machine connecting to the same SSID at the same time and only prioritizes either to Hyper-V host or the VM.
When connecting to my home Access Point, there is not problem and both host and VM can ping google DNS without time outs.
Please advise on how to get the VM to ping 8.8.8.8 constantly without time outs or get the Cisco WLC to service both requests from VM or Hyper-V host.
Please let me know if you require further information.
Kind Regards
Lourensvd
Cisco WLC 3504 not allowing simultaneous connections from Hyper-V Client via Wireless Network Adapter
Hyper-V-Virtual-Switch-Settings.docx
Im not a Hyper-V expert but if this was Vmware I'd say - is your virtual switch blocking promiscuous mode or forged transmits? check your vSwitch settings.
P
P
ASKER
Hi Hemil
Apologies for the late reply. Herewith a screen for the continuous ping to the Gateway via the Cisco WLC. Shown in Cisco - Ping the default gateway-10.0.0.10.jpg
Cisco---Ping-the-gateway-10.0.0.10.jpg
Apologies for the late reply. Herewith a screen for the continuous ping to the Gateway via the Cisco WLC. Shown in Cisco - Ping the default gateway-10.0.0.10.jpg
Cisco---Ping-the-gateway-10.0.0.10.jpg
In a post on a separate Hyper-V/WiFi issue, one expert recommended the following. It may help here:
https://blogs.msdn.microsoft.com/virtual_pc_guy/2016/05/02/windows-10-hyper-v-and-wireless-a-new-way-to-make-this-all-work/
https://blogs.msdn.microsoft.com/virtual_pc_guy/2016/05/02/windows-10-hyper-v-and-wireless-a-new-way-to-make-this-all-work/
He also suggested:
https://blogs.msdn.microsoft.com/virtual_pc_guy/2015/02/02/hyper-v-and-wireless-networking/
I've not read those, don't know if they really apply here, but they sounded as if they may be useful.
I've never tried to do WiFi with Hyper-V... fortunately!
https://blogs.msdn.microsoft.com/virtual_pc_guy/2015/02/02/hyper-v-and-wireless-networking/
I've not read those, don't know if they really apply here, but they sounded as if they may be useful.
I've never tried to do WiFi with Hyper-V... fortunately!
Try without sharing the Wi-Fi NIC with the management OS.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Do the following,
1- Try pinging the default gateway of the router and tell me if you get the same thing.
2- Make sure QOS has been disabled.
3- Make sure you don't have data plane enable on your firewall, this means you have a policy after certain ping for the packet to get reset.
4- set static IP address to each host and server, do not use dynamic.
5- Remember if you are using 802.11 WiFi, they are half-duplex devices, so if a client is sending data to the AP, the AP can not also send data to the same or any other client at the same time.
6- For virtualization Wireless card are not recommended. It could bring bogus issues. I highly recommend you to use hard wire.
Remember Wifi are very slow when transmistting packet back and forth, I do not recommend you to use it for environment as virtualization, you are dealing with multiple IP/DATA in one card simultaneously.