Windows 10 x T29g

[fabianochoueiri]

Hi, I have a T29G phone. We are having problems when using Windows 10 connected to the phone.
802.1x is disabled on the phone and enabled on the PC.
The switch port authenticates the phone, using its mac-address, and the PC, using 8021.x.
It works fine for all PCs with Windows 7 or Linux, but not works with Windows 10.

It seems that when the phone (with 802.1x disabled) is connect to the Windows 10, it is trying
to pass 802.1x authentication and it fails, even passing the mac-authentication it can not
get connected. The PC authenticates using 802.1x correctly and get connected.

So, why the phone is trying to authenticate using 802.1x even if 802.1x is disabled on the phone ?
And why this happens only when the phone is connected on a PC using Windows 10 ?

[Karl_Yealink]

The phone can work normally with PC(window 7 or Linux), and the PC use the 802.1x. Is right?

Would you please help us to get the syslog and config.bin and pcap files, we can check something from them.
You can get more info from the FAQ: http://support.yealink.com/faq/faqInfo?id=311

[fabianochoueiri]

(01-29-2016 05:43 PM)Yealink_Karl Wrote:  The phone can work normally with PC(window 7 or Linux), and the PC use the 802.1x. Is right?

Would you please help us to get the syslog and config.bin and pcap files, we can check something from them.
You can get more info from the FAQ: http://support.yealink.com/faq/faqInfo?id=311

Yes, the PCs are using 802.1x. The switch port admits 802.1x and mac-address authentication. Then, the PC get authenticated using 802.1x and the phones get authenticated using their mac-address. It works fine. The only problem is with windows 10. The PC with windows 10 is authenticated using 802.1x ok. Then the phone is authenticated using its mac-address and after that it looks like the phone,
even authenticated with mac-address, try also to authenticate with 802.1x. But I have disabled the 802.1x in the phone. As it fails 802.1x authentication it get no access to the network.

[fabianochoueiri]

Thanks Yealink_Karl for your help.
I just found out the problem. The Windows 10 PC had the "Microsoft LLDP protocol driver" enabled. When we disabled it the phone starts working fine.
I dont know why this happens but if you enable "Microsoft LLDP protocol driver" the phone stop working.

It has nothing to do with authentication methods.

And I dont have an explanation to that.