cannot obtain domain controller name

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a brand new system, just out of the box running Win XP Pro SP2. It
joined the domain with no problem and gets it's IP via DHCP. However, our
group policy should be pushing out Microsoft Office but it's not getting it.
In the event viewer this error shows up under applications.

Source: Userenv
Event ID: 1054
Windows cannot obtain the domain controller name for your computer network
(The specified domain either does not exist or could not be contacted). Group
policy processing abored.

Now.... from this machine I can ping all of the servers and other
workstations on the network. Everything works perfectly except for this one
problem. I have entered the DNS server into tcp/ip manually, I've editet the
hosts file so all of the servers are in there, I've removed the computer from
the domain and rejoined with a different name... I don't know where else to
go with this.

I'm open to any ideas.

Thank you in advance.

Mark I
 
Mark I said:
I have a brand new system, just out of the box running Win XP Pro
SP2. It joined the domain with no problem and gets it's IP via DHCP.
However, our group policy should be pushing out Microsoft Office but
it's not getting it. In the event viewer this error shows up under
applications.

Source: Userenv
Event ID: 1054
Windows cannot obtain the domain controller name for your computer
network (The specified domain either does not exist or could not be
contacted). Group policy processing abored.

Now.... from this machine I can ping all of the servers and other
workstations on the network. Everything works perfectly except for
this one problem. I have entered the DNS server into tcp/ip manually,

Just your internal (AD-integrated) DNS server, right? No others?
I've editet the hosts file so all of the servers are in there,

Ooooh, take those out. The only thing you should have in there is localhost.
I've
removed the computer from the domain and rejoined with a different
name... I don't know where else to go with this.

I'm open to any ideas.

Thank you in advance.

Mark I

Fix the hosts/DNS thingy, then run

start | run | gpupdate /force

and then

start | run | rsop.msc

Look for errors therein.
 
This seems to have done the trick, except I have to reboot once or twice to
get it to work:

DNS is working fine and in all the client machines both
Primary and Alternate DNS Server are defined.No other thrid party are running.
According to the following microsoft support
http://support.microsoft.com/kb/840996 , I have added an entry named
"GpNetworkStartTimeoutPolicyValue" with DWord Value 60 under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\Current Version\Winlogon.
 
Mark I said:
This seems to have done the trick, except I have to reboot once or
twice to get it to work:

DNS is working fine and in all the client machines both
Primary and Alternate DNS Server are defined.

So do you have *two* AD-integrated DNS servers? If not, you shouldn't have
anything but primary.....

No other thrid party are
running. According to the following microsoft
support http://support.microsoft.com/kb/840996 , I have added an
entry named "GpNetworkStartTimeoutPolicyValue" with DWord Value 60
under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\Current
Version\Winlogon.

I'm not familiar with that (never needed it). But I'm glad things are
working now.
 
Back
Top