Hi,

we use 802.1x Computer Authentication in our enviroment.

Our NPS is a Windows Server 2008 R2 SP1 and in our Network Cisco ESW-540-24 Switches. We request PEAP-TLS with computer certificates from our internal Enterprise CA.

Windows 7 and Windows 8 Clients do an authentication over 802.1x and get Access to the corpnet.

But when i configure 1 Hyper-V Switch on my Windows 8 Client, my machine dont do an authentication over 802.1x.
In Netmon/Wireshark we dont see any EAPOL request from my Client to the cisco Switch.

Is 802.1X is supported on Windows 8 with Hyper-V? If its true how can i configured my Windows 8 hyper-v Client to get Access over 802.1x?

Thanks in advance!

Hello,

do you have any updates on this problem?

thx

Are you using wireless network with Hyper-V virtual switch? Does authentication starts working when you disable hyper-v wireless switch?

I am experiencing this same issue as well through a wired connection.

After starting up, I have to go into the Hyper-V Virtual Switch properties, change it from External to Internal, let my actual NIC authenticate and connect to our network. Then I switch back from Internal to External and let the Virtual Switch take over the physical NIC again.

I have tried playing with the Authentication tab for the vEthernet connection, but matching the physical NIC settings does not work AND I've noticed that these settings "reset" every time I reboot the system.

We're seeing the same issue on a Windows 8 client machine running Hyper-V on our network as well.  Does anyone have any ideas we could try?

Hi,

are there any news regarding this issue? I experience a similar behavior. IEEE 802.1X and certificate auto-enrollment is configured via GPO and works find without Hyper-V Switch. If the Hyper-V Switch is configured for the external network adapter 802.1X stops working. 

I see that both network adapters (physical and virtual) have the same 802.1X Config.

Is it possible that the new adapter does not have the .1X config on the hypervisor and instead on the virtual host? This would make ist possible that the VM has it's own certificate.

Best Regards,
Michael

I am also experiencing the same issue. Did anyone end up with a solution to this? 

Any update? Has anyone called Microsoft Support to report this defect?

Have you found some kind of work around ?
We are implementing 802.1x in our enviorment and all of the machines that have a Vitual switch in hyper-V with external access and host access stop working with the 802.1x

This must be a known issue and MS must have a work around.

Best regards,
Valdi Hafdal

Not so far. Did anyone Check with Windows 8.1? BR Michael

Same issue on Windows 8.1 - as soon as the physical NIC is used for the Hyper-V switch authentication fails on the host and guests, no EAP packets can be seen on the physical switch from either.

If the physical port is force authenticated then the same configuration works absolutely fine.

Has anybody confirmation from Microsoft if this is intended to work or if this is actually a bug?

We're still seeing the same behavior in Windows 8.1.  One of our network techs and I just worked through every possible permutation of .1x authentication - computer account, computer certificate, user account, user certificate.  Each of them would pass .1x authentication with Hyper-V not enabled, or with an internal virtual switch, but as soon as we turned the onboard NIC into a Hyper-V external switch, .1x authentication stopped.  We verified on the Cisco switch that the EAPOL packets were not even reaching the switch.

We'd love to use Hyper-V in our production environment, but we must have .1x authentication enabled due to the requirements of our industry.  Looks like this is something that Microsoft has to step up to fix.

Any Update of how to resolve this issue? i encounter the same problem here. mine was a win8 box,i have updated all the patches from microsoft .

We're still seeing the same behavior in Windows 8.1.  One of our network techs and I just worked through every possible permutation of .1x authentication - computer account, computer certificate, user account, user certificate.  Each of them would pass .1x authentication with Hyper-V not enabled, or with an internal virtual switch, but as soon as we turned the onboard NIC into a Hyper-V external switch, .1x authentication stopped.  We verified on the Cisco switch that the EAPOL packets were not even reaching the switch.

We'd love to use Hyper-V in our production environment, but we must have .1x authentication enabled due to the requirements of our industry.  Looks like this is something that Microsoft has to step up to fix.

Same here as well. I saw the problem on Windows 8 originally and upgrading to 8.1 had zero effect. Has anyone tried with the new Windows 8.1 Update 1 installed?

• Edited by Impulse12 Monday, April 21, 2014 12:19 PM spelling mistakes

I have tried with windows 8.1 update 1 installed ,but the problem still exist

Any update on the issue from Microsoft? Or do we have to wait for Windows 10?

Just throwing in my hat here as I too am running Windows 8.1 update 1 and still have the problem whereby .1x authentication  is not possible when Hyper V is enabled.

Hello,

I got official statement from Microsoft that 802.1x with Hyper-V on Windows 8.1 is not working by design.

• Proposed as answer by c_altair Thursday, June 11, 2015 6:54 PM
• Unproposed as answer by c_altair Thursday, June 11, 2015 6:54 PM

Any solution for Hyper-V?
I'm having to use Virtualbox !!