The domain specified is not available

"the mechanism might not log you on, the domajor specified is not obtainable. Please attempt again later on."

I got this error over when I try to login to my work computer system from residence through my PIV smart card. I always take my occupational computer residence and also login through my PIV smart card, yet over the last month me and some various other users are acquiring this error. Only when I bring the computer system earlier in the office I"m able to login via no difficulty.

You watching: The domain specified is not available

Have anyone endure this worry and also just how did you deal with it?

Thanks in progressed.

Which of the adhering to retains the indevelopment it's storing once the device power is turned off?




Don007 wrote:

Check the time on your AD servers.

My blind guess is that it is off by over 2 minutes.

If they sync to themselves or the VM-host (and also the VM-organize in turn syncs with the DC) this deserve to happen.Have likewise had actually problems through (the default) formerly, could have been sorted, yet I use various other NTP servers.

See more: Request Was Denied For Security Fix, Request Was Denied For Security Error

Is this over some VPN or MS direct access?

It sounds prefer the computer system is joined to the domain, which is available as soon as you"re at job-related, but not at residence. I don"t understand also why it isn"t caching your user account though. Are you making use of a VPN to obtain right into the office network? You may ask I.T. if they"ve made any kind of alters that would not enable a user to log in as soon as the domajor is not available.

We are having actually the same concern as well. A few of the users who are utilizing VPN are getting "The mechanism can not log you on, the domajor specified is not accessible. Please try again"later." and "The device can not log you on. The smart card certificate provided for authentication has been revoked." It is working fine prior to. Do we have any kind of solve for this yet? Th concern appears to be intermittent at some allude.

Getting error below on event viewer..

See more: Windows Could Not Finish Configuring The System Sysprep, Windows Could Not Finish Configuring The System

An account fairesulted in log on.Subject: Security ID: SYSTEM Account Name: ComputerName$ Account Domain: Domain Logon ID: 0x3e7Logon Type: 7Account For Which Logon Failed: Security ID: NULL SID Account Name: user Account Domain: Faientice Information: Faitempt Reason: An Error occured throughout Logon. Status: 0xc000006d Below Status: 0xc0000321Process Information: Caller Process ID: 0x394 Caller Process Name: C:WindowsSystem32winlogon.exeNetwork Information: Workstation Name: ComputerName Source Network-related Address: Source Port: 0Detailed Authentication Information: Logon Process: User32 Authentication Package: Negotiate Transited Services: - Package Name (NTLM only): - Key Length: 0This occasion is generated when a logon research fails. It is generated on the computer wright here access was attempted.The Subject fields show the account on the local device which asked for the logon. This is many typically a company such as the Server business, or a local procedure such as Winlogon.exe or Services.exe.The Logon Type area indicates the kind of logon that was asked for. The the majority of common types are 2 (interactive) and also 3 (network).The Process Information fields indicate which account and process on the mechanism asked for the logon.The Network-related Indevelopment areas indicate wright here a remote logon research originated. Workterminal name is not always available and also may be left empty in some instances.The authentication information areas administer detailed indevelopment around this particular logon research. - Transited services indicate which intermediate services have participated in this logon repursuit. - Package name suggests which sub-protocol was offered among the NTLM protocols. - Key length indicates the length of the generated session crucial. This will certainly be 0 if no session crucial was requested.