Re: GPO not applied to clients



I would also run dcdiag and gpotool on the domain controller and netdiag on
a domain computer that is having the problem receiving the Group Policy.
Verify that the domain computers are using only the domain controller as
their preferred dns server in tcp/ip properties and as shown with ipconfig
/all. You should also be able to ping the domain controller from any domain
workstation by tcp/ip address and fully qualified domain name and vice
versa. I would also use nslookup to verify that the domain workstation shows
only the domain controller as its dns server and that it can resolve names
for the domain including that if you enter the domain controller's name it
shows the correct IP address for the domain controller. If your domain
controller for some reason has more than one network adapter or is also a
rras server you can easily have problems as described. --- Steve


"Guillermo Lovato" <glovato@xxxxxxxxxxx> wrote in message
news:%23NVjfiFaFHA.2984@xxxxxxxxxxxxxxxxxxxxxxx
> win2k3 domain, single server environment.
>
> in all clients i have userenv events with the following:
> Event Type: Error
> Event Source: Userenv
> Event Category: None
> Event ID: 1054
> Date: 03/06/2005
> Time: 10:52:08
> User: NT AUTHORITY\SYSTEM
> Computer: TARJETA02
> Description:
> Windows cannot obtain the domain controller name for your computer
> network. (An unexpected network error occurred. ). Group Policy processing
> aborted.
>
> I did a netdiag on the server itself and i found this odd thing:
> [WARNING] You don't have a single interface with the <00> 'WorkStation
> Service', <03> 'Messenger Service', <20> 'WINS' names defined.
>
> Doing a gpresult on the client machine shows that only the "default domain
> policy" is applied.
>
> sysvol is accesible from the workstations
>
> right now i'm baffled, i have no idea what to do to fix this.
>
> thanks in advance
>


.



Relevant Pages

  • RE: Exchange 2003 server problems after login.
    ... I would configure the exchange server to use Kerberos over TCP. ... Group Policy Infrastructure failed due to the error listed below. ... The specified domain either does not exist or could not be contacted. ... If this computer is a domain controller for the specified domain, ...
    (microsoft.public.windows.server.active_directory)
  • RE: Exchange 2003 server problems after login.
    ... I would configure the exchange server to use Kerberos over TCP. ... Group Policy Infrastructure failed due to the error listed below. ... The specified domain either does not exist or could not be contacted. ... If this computer is a domain controller for the specified domain, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Group Policy Problems on new server
    ... 256986 Description of the Microsoft Windows Registry ... | Subject: Re: Group Policy Problems on new server ... |> 257435 Error Message When Opening or Editing a Domain Group Policy ... |> | The Domain controller for Group Policy operations is not available. ...
    (microsoft.public.windows.server.migration)
  • Re: Cannot access Active Directory
    ... If I try to go to Group Policy Management I get a message to ... > that the server is not operational. ... > Win32 Error 58. ... Check to make sure that this machine is a Domain Controller. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Can we limit the total number of search results returned?
    ... which is the number of records the domain controller will return before ... similar limit exists on the server. ... Group Policy - User Configuration, Administrative Templates, Desktop, Active ... >>> Currently we can track abuses by logging expensive queries and long ...
    (microsoft.public.windows.server.active_directory)

Loading