Most of My Domain PC's are on WIFI. When user change Password they can no longer logon.

Question

Most of my desktop PC's are on a Wi-Fi networks. Wi-Fi network is functioning properly. They are on the org's domain. I am an Admin on all PC's. I can no longer logon to those PC's. Some of those PC's I have not logged into for several password change cycles. The Wi-Fi isn't connecting to the AD server to verify my account and password. Are there any setting changes I can make, either on the PC or Wi-Fi routers, to force wi-fi to look at the AD for password word authentication? I have a local admin account, but it does not give me domain access. You must first login to windows on the local machine which is on a domain. Once you have successfully login to Windows, does it then pass credentials on to the AD server on a wireless machine. If you have changed your password elsewhere or used a site to change your password, you have to login to the machine using your old password, which is cached on that machine. Then windows passes the old password to the AD server. The ad server will not allow you access anything on the network, only that machine. Your must then click on the wifi icon to connect to the network. Windows will them prompt you for a user name and password, Then you must use your new password login to the network. Windows will then sync your new password to your cached user profile on that machine. Some machines I have not logged into for several password cycles. I don't remember what the password is cached locally. So I can't ever logon to the PC. The only solution I have found so far is to hard wire the PC to the network. In my case this isn't feasible. I have to carry around two 60' cables and a RJ45 couple to get access to the systems.

Answer 1

From what you described there is some sort of authentication requirement to connect to the network. I'd look to turn that off at least for testing.

--please don't forget to close up the thread here by marking answer if the reply is helpful--

Answer 2

The issue was a timing issue. It was taking around 5 minutes to load the drivers for the WiFi on machines with mechanical drives. SSD drives loaded much faster. These machines have no unnecessarily apps installed and the one app is a small foot print. So people were trying to login prior to the complete loading of drivers. Second if machine was logged into by someone else, and they just signed out. You could not login. A person who had changed their password elsewhere has to reboot the machine to be able to login with their new password, provided they waited to until all the drivers loaded. This can be verified by watching the HD activity light and waiting until it has slowed to just the occasional light blip. This had to be done with the Network group who was monitoring the WiFi access point to see when the user actually hit the WiFi access point.