If its just one system, then you might try
just re-joining the machine to the domain. Perhaps its machine account got
fudged up. You might check its system event log for Netlogon errors that give
some clue to this.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Salandra, Justin A. Sent: Thursday, December 30, 2004 9:00 AM To: ActiveDir@mail.activedir.org Subject: RE: [FNB Spam Filter][ActiveDir] GPO Processing My DNS is working since ALL other workstations have no problems, just this one.
-----Original
Message-----
James- I think you mean LMHosts right? I'm not aware that etc/hosts allows NetBIOS records like that. In any case, I don't think that will help because GP processing is strictly LDAP based--there is no use of NetBIOS protocols to find or process GPOs. That is why, in an environment where WINS is still running and DNS resolution is broken, the normal signs that DNS isn't working, such as inability to logon to an AD domain, don't appear, but GP processing will still fail.
Darren
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Rogers,
James As a trouble-shooting method, try creating a #DOM record in your HOST file that points at the domain controller. If this works, you most likely have a DNS problem.
-James R. Rogers
|
Title: Message
- RE: [FNB Spam Filter][ActiveDir] GPO Processing Darren Mar-Elia
- RE: [FNB Spam Filter][ActiveDir] GPO Processing Steve Shaff