Re: Windows cannot obtain the domain controller name for your comp
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Wed, 29 Aug 2007 18:37:57 +0100
check if you have access to the gpt.ini for that GPO, using
\\domainname\....
also have a look at this
http://support.microsoft.com/kb/842804/en-us
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
"Pauli" <Pauli@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C5ED7DBE-38A6-4BE5-876E-9FDCCD8DD1DA@xxxxxxxxxxxxxxxx
Thanks Paul, your advice was very helpful as it did show some errors in
the
configuration. However, these were not the cause of the error.
The server is an HP Proliant dual core AMD Opteron and the problem was
resolved by installing the AMD drivers. I found this advice on another
post:
Install the AMD Dual Core drivers.
AMD AthlonT 64 X2 Dual Core Processor Driver for Windows XP and Windows
Server 2003 Version
http://www.amd.com/us-en/assets/content_type/utilities/amdcupsetup.exe
Unfortunately, I now get two other errors:
"Windows cannot query for the list of Group Policy objects"
and
Windows cannot access the file gpt.ini for GPO ..... (Access is denied. )
"Paul Bergson [MVP-DS]" wrote:
Run diagnostics against your Active Directory domain.
If you don't have the support tools installed, install them from your
server
install disk.
d:\support\tools\setup.exe
Run dcdiag, netdiag and repadmin in verbose mode.
-> DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
-> netdiag.exe /v > c:\netdiag.log (On each dc)
-> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
**Note: Using the /E switch in dcdiag will run diagnostics against ALL
dc's
in the forest. If you have significant numbers of DC's this test could
generate significant detail and take a long time. You also want to take
into account slow links to dc's will also add to the testing time.
If you download a gui script I wrote it should be simple to set and run
(DCDiag and NetDiag). It also has the option to run individual tests
without having to learn all the switch options. The details will be
output
in notepad text files that pop up automagically.
The script is located on my website at
http://www.pbbergs.com/windows/downloads.htm
Just select both dcdiag and netdiag make sure verbose is set. (Leave the
default settings for dcdiag as set when selected)
When complete search for fail, error and warning messages.
--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Pauli" <Pauli@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B4AFD15C-3C54-491E-851A-F99107671D42@xxxxxxxxxxxxxxxx
Hi,
I have two windows 2003 servers, one running R2 setup as domain
controllers.
Last week the one owing the 5 roles suffered a processor failure and as
it
was pretty old I decided to replace it.
Fortunately, I managed to get it up and running long enough to transfer
the
role ownership to the other box, demote it from being a DC (DCPROMO)
and
remove it from the domain. I then installed the new server from scratch
using
the same name and IP address as the old one, added it to the domain,
promoted
it to being a DC and transferred role ownership back to it.
However, in the new server's event logs every 10 minutes I get the
error:
1054 "Windows cannot obtain the domain controller name for your
computer
network. (An unexpected network error occurred. ). Group Policy
processing
aborted. " every 5 minutes or so.
NTDSUTIL shows the new server is the owner of all the roles, its name
correctly appears in DNS. If I use NTDSUTIL to transfer the
"Infrastructure
master" role to the new machine (even though it already owns it), fixes
the
error for about 12 hours then it reappears.
I would appreaciate any help in resolving this problem.
Thanks
.
- Follow-Ups:
- References:
- Re: Windows cannot obtain the domain controller name for your computer
- From: Paul Bergson [MVP-DS]
- Re: Windows cannot obtain the domain controller name for your comp
- From: Pauli
- Re: Windows cannot obtain the domain controller name for your computer
- Prev by Date: Re: migrate active directory user accounts between production and test systems
- Next by Date: Re: backup FSMO roles
- Previous by thread: Re: Windows cannot obtain the domain controller name for your comp
- Next by thread: Re: Windows cannot obtain the domain controller name for your comp
- Index(es):
Relevant Pages
|
Loading
