TLD is missing to authenticate in an 802.1x network

Intel vPro® Platform

Intel Manageability Forum for Intel® EMA, AMT, SCS & Manageability Commander

TLD is missing to authenticate in an 802.1x network

1,370 Views

Hello everyone,

we are currently impementing AMT Clients (Versions 5.x - 7.x) with SCCM and Microsoft NPS in our 802.1x protected network. Everthing worked as expected (Provisioning OK, TLS OK, Kerberos OK, KVM OK Power Control OK) until now. The 802.1x authentication is failing because of an incorrect domain Name.

For example: Lets say our domain name (DNS) is vpro.com. NETBIOS Name is corpvro. Usually the clients are authentication with PEAP-MS-CHAPv2 using this notation: corpvro\COMPUTERNAME$. If AMT tries to authenticate the notation is: vrpo\COMPUTERNAME$iME. So it is using the DNS Name without the top level domain behind the dot. Now the NPS is saying "domain not exist" Errorcode 7 and drops the authentication attempt. Where could i have made a mistake, everything else is working as is should.

Thank you for your help....

Link Copied

0 Replies

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.