This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 79%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJN%3C/text%3E%3C/svg%3E)
I had my organization domain password expired last month. I didn't change my password but right now I am not able to login to my machine as it is showing an error : "We can’t sign you 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."
I had connected to organization VPN recently and i believe the sync happened with on-premise AD environment which caught the password expired thing which eliminated the chances of cache based login.
Is there any possible way to re join the domain or resolve this issue without reimaging or any other initialization process?
Please share your thoughts as this is really critical. Thanks
Hi @Jijith Nair , what steps have you taken to debug or fix this issue? This article is pretty extensive: https://thegeekpage.com/we-cant-sign-you-with-this-credential-because-your-domain-isnt-available/
If you've already exhausted these options the best thing we can do is open a support ticket for you. Please let me know.
Best,
James
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 23%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
We are experiencing the same issue on a Windows 2019 RDS server. There are two of these servers configured with a broker in between and yesterday one of them had this issue. We re-joined it into the domain and today the second server expierences the same problem. We now also well apply the re-join fix on this system. But not sure what the root cause is of this, you guys any idea?