Domain notebooks login issue on wireless netwok without 802.1x

Question

I have deployed 802.1x on wired ethernet. Wireless adapter keeps without 802.1x until all wired ethernet issues fixed. All the domain joinned notebooks found they can only login with wired connection but not wireless connection with the error prompt "We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential".

***Move from Windows / Windows 11 / Accounts, profiles, and login ***

Answer 1

Hello,

Thank you for posting in the Microsoft Community Forums.

It sounds like you're facing an issue where domain-joined notebooks cannot authenticate over a wireless network that doesn't have 802.1x enabled. This problem arises because domain authentication typically requires network access to validate credentials with the domain controller.

Here are a few steps you could try to mitigate this problem:

1. Cached Credentials: Ensure that users have logged into the domain at least once while connected to the wired network, which allows Windows to cache their credentials. This way, they should be able to log in using cached credentials even when the domain controller is not available.
2. Local Admin Account: Temporarily set up a local administrator account that users can log into when not connected to the wired network. This will at least provide them with the ability to access the machine and connect to the wireless network manually.
3. Group Policy: Consider implementing Group Policy settings that allow for cached logons. You'll want to configure the policy to allow users to log on with cached credentials. Here’s how to do it:
   • Open the Group Policy Management Console (GPMC).
   • Navigate to Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options.
   • Find the policy Interactive logon: Number of previous logons to cache (in case domain controller is not available) .
   • Set this policy to a number higher than 0.
4. Wireless Configuration: If possible, configure the wireless network to allow access to the domain controller without requiring 802.1x temporarily. For instance, a guest or interim network with necessary routing to the domain controller for authentication purposes only.
5. System Network Drives: Ensure no critical scripts or drive mappings rely on being connected to the domain at the time of login, as these can sometimes cause logon processes to fail or hang.

I hope the information above is helpful.

Best regards

Yanhong Liu