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

  • 15 April 2016
  • 4 replies
  • 207 views

Userlevel 1
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.

4 replies

Userlevel 7
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 \[u].
Userlevel 1
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 \[u].
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.
Userlevel 7
Take a look at the following article:

https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-enable-wireless-client-reporting-on...
Userlevel 1
Thanks! I see I was sending the log traffic to NetSight and had the detail level set to major.

Reply