Setting up new wireless, non-domain machines with AD credentials fail login.

  • 0
  • 1
  • Problem
  • Updated 2 years ago
  • Solved
On a newly created wireless (still in testing) non-domain machines cannot connect with AD credentials.  Wireless is a new creature for me as well, where in the controller are logs specific to authentication to help me troubleshoot my issue.
Photo of Christopher Davis

Christopher Davis

  • 366 Points 250 badge 2x thumb

Posted 2 years ago

  • 0
  • 1
Photo of Brandon Clay

Brandon Clay, Escalation Support Engineer

  • 13,304 Points 10k badge 2x thumb
Hi Christopher,

I would make sure that the clients are not set to send the domain with login credentials. I've run into this in the past with non-domain machines, where they will send <computer name>\<user name>.
Photo of Christopher Davis

Christopher Davis

  • 366 Points 250 badge 2x thumb
I attempted to remedy this by setting up the profile manually and disabling this option.  It works for iphones etc but not windows machines currently.
Photo of Doug Hyde

Doug Hyde, Technical Support Manager

  • 20,514 Points 20k badge 2x thumb
(Edited)
Photo of Christopher Davis

Christopher Davis

  • 366 Points 250 badge 2x thumb
Thanks! I see I was sending the log traffic to NetSight and had the detail level set to major.