Skip to main content

What is the error message when a disable computer tries to log in?

By

In our test environment, we determined that the user was able to log on and access network recourses. We discovered that the computer was not able to authenticate itself and therefore was not able to take advantage of active directory. For example, we were not able to to update the computer portion of group policy

Another problem is that if the user did not have a cached profile on the client, the user will recieve the following error at login:

The trust relationship between this workstation and the primary domain failed.

Once logged in with a user account that had cached credentials (or a local account) an examination of the System log revealed

Level: Error

Source: NETLOGON

Event ID: 5721

Description:

The Session setup in Windows NT or Windows 2000 Domain Controller %\\Server\domain% for the domain %domain% failed because the Domain Controller did not have an account %Client% needed to set up the session by this computer %Client%.

ADDITIONAL DATA

If this computer is a member of or a Domain Controller in the specified domain, the aforementioned account is a copmuter account for this computer in the specified domain. Otherwise, the account is an interdomain trust account with the specified domain.

Level: Warning

Source: Time-Service

Event ID: 130

Description:

NtpClient was unable to set a domain peer to use as a time source because of failure in establishing a trust relationship between this copmuter and the '%domain%' domain in order to securely sycronize time. NtpClient will try again in 15 minutes and double the reattempted interval therafter. The error was: then trust relationship between this workstation and the primary domain failed. (0x800706FD)

Level: Error

Source: GroupPolicy

Event ID: 1129

Description:

The processing fo Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connect to the domain controller and Group Policy has succesfully processed. if you do not see a secure message for several hours, then contact your administrator.

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Sticky Key problem between Windows Server 2012 and LogMeIn

By
This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .
6 comments
Read more