Tim, I need your help, pleeeeease! I am pulling my hair out (what
little there is left) over these issues with Windows XP boxes on a
2000 AD domain. I have read the post you responded to that is listed
in the subject, and judging by your responses, you are very
knowledgeable in these areas. I have much the same problem, although
my domain controllers are both onsite, rather than across the WAN. I
have scoured the newsgroups and the Microsoft Knowledge base for days
now and tried countless attempts to correct the issues. Could you
please help me resolve this issue, as I am in the hot seat now with my
company!
Here is the situation. I get the following errors:
System:
NETLOGON (bigger problem)
Event ID 5719
No Domain Controller is available for domain MTS due to the following:
There are currently no logon servers available to service the logon
request. Make sure that the computer is connected to the network and
try again. If the problem persists, please contact your domain
administrator.
W32Time (I think due to the other problem…)
Event ID 29
The time provider NtpClient is configured to acquire time from one or
more time sources, however none of the sources are currently
accessible. No attempt to contact a source will be made for 15
minutes. NtpClient has no source of accurate time.
I also get warnings about DHCP Event ID 1003 – You r computer was not
able to renew its address from the network (from the DHCP Server) for
the Network Card with network address….. The semaphore timeout period
has expired. Your computer will continue to try and obtain an address
on its own from the network DHCP server.
Application:
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 aborted.
In addition to these errors, the group policy obviously does not get
applied properly. The GP Core has a failure each time with the big
red X through it. Occasionally, the user portion will work, but many
times it does not. When I run the gpupdate command after I am logged
on, most of the group policy gets applied. I have tried
troubleshooting all of the DNS issues listed in Q314861, Q260371,
Q237675, Q300202, Q291382 and Q298656 among others.
In Q314861, they discuss that you should be able to do an nslookup
guid._msdcs.root_domain.com When I do this, the command does not
succeed, but I have tried the steps the article advises and that entry
still does not exist. Then, I manually tried to enter it, but am not
certain if that was necessary or not. Can you please advise?
Can you help me get these issues resolved? I feel like I am chasing
my tail! And then it will look like it works for 1 boot cycle and it
reappears at the next logon. (By the way, I have also set the local
computer policy to "Always wait for the network at computer startup
and logon") That doesn't seem to resolve it either. It seems to me
like the computer is still booting before the network is started,
which would explain the DHCP error, and probably the others too! What
can I do to resolve these issues? They are happening on all of the XP
Pro boxes we've introduced into our environment.
One last question about Group Policy: I tried to push the automatic
updates client per the instructions in the deployment guide (using the
Active Directory GP approach). The software install failed on all of
my machines, so I removed that from the software installation
directory. It seems that it is still stuck because when I use RSoP to
monitor the policy, it still fails to do the "software install" even
though I've removed it from the policy. How can I trick it or remove
so that it gets the new policy and forgets about the install of that
app?
Thank you very much for any help you can offer. Like I said, it's
been a very rough 3-4 weeks.
