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
Event ID: 5721
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%.
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.
Event ID: 130
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)
Event ID: 1129
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.