Ever since migrating to 8.x code from 6.x we received a handful of reports with issues with our AD Managed wireless laptops.
One of the issues we are seeing is when a user with cached credentials logs into a wireless machine, they see the message "Unable to Connect to Network, logging on". Our AD machines are configured to machine auth using the AD Computer object. I confirmed that when the machine is that the control-alt-delete screen, they have a valid role and IP address. I started a ping to the machines IP from my desktop and proceeded to login with my AD credentials. After doing so, the machine drops a few pings, displays the "unable to connect message" and continues to login with cached credentials, then the machine starts pinging again.
Also once a user is logged into the machine, they get the message they were logged on using previously stored credentials and their mapped drives have red Xs. However, you can just click on them and they connect.
If a user without cached credentials trys to login they get the "no logon sevrers" message, even though the machine is machine authed with valid IP and role.
I have compared all of the settings for this VAP and AAA profile between the old and new controller environment and they are identical. I also opened a TAC case but they were unable to find any issues with the config. If I bring up an AP on our old controllers the issue goes away when connected to that AP.
We use NPS for our AD joined machines and are running 8.4.0.1 with 7240XMs for the MDs.
Anyone else seen this issue?
-