I have recently configured a wireless configuration for a customer. The configuration is as follows;
1) Staff SSID. This uses 802.1x with RADIUS configured via NPS on a sever 2k8 R2 box. This has a cert provided via GoDaddy. 2) Guest SSID. This is VLAN'd out from the staff SSID off to a different subnet with a captive portal and this works fine.
The Staff SSID works perfectly fine on a Windows 7 machine. Upon connecting, you get a warning that it can't validate the cert (apparently fairly common with GoDaddy certs). When connecting on a Windows XP machine, you have to change the profile to use PEAP rather than Smart Card or Cert before this will allow you to connect. I have changed the settings to NOT use Windows credentials as part of a logon (the machines aren't actually domain machines, but domain members will be connecting via them) and have checked that the 'Connecting using computer credentials if possible' option is unticked.
Several Windows XP machines will not connect. Some however, do. The ones that don't, generate an error in the NPS logs where I can see that it's attempting to connect with the machine name, rather than the user credentials you provide.
NPS denied access to a user.
Account Name: host/your-2295e402e3 Account Domain: CorrectDomain Fully Qualified Account Name: CorrectDomain\Host/our-2295e402e3
Reason: The specified user account does not exist.
the 'your-2295e402e3' is the computer name that's failing. It shows the correct domain that I had specified upon my connection attempt.
Does anyone know why these machines are attempting to connect using their machine name?