Thansk Doug, I did that on the W2k Server. Rebooted it and rebooted the 2003
server. After rebooting the 2003 server I lost all network connectivity on
it. I got a message in the event viewer that IPSec had gone into blocking
mode. Si I can't ping my w2k server or my gateway any more.
So I changed the w2003 server from belonging to my domain to belonging to
workgroup. Removed the w2003 server from the computers in the domain in the
w2k server domain. And disabled the IPSec service on the w2003 computer, to
see if I can get network connectivity back.
After rebooting the w2003 server I could again ping my w2k server and my
gateway. I could also rejoin the domain. But when I tried to make the 2003
server a second domain controller I got exactly the same behaviour as what
was described in my original message.
Would you have any other ideas on how to solve this?
Thanks for your help.
Bob
"Doug Sherman [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Try:
>
> 1. Run a system state backup on your Win2k domain controller.
>
> 2. Run adprep - see:
>
> http://support.microsoft.com/default...b;en-us;278875
>
> http://support.microsoft.com/default...b;en-us;309628
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
> "Bob" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> I already have a w2000 server on a small network that is a domain
>> controller. I just added a w2003 Standard server and made i part of the
>> domain. Now I want to configure it as a second domain controller
> (essentialy
>> as a backup domain controller for the w2k one on the same domain).
>>
>> After I select to create a second sever for an existing domain, and enter
>> the existing domain's user name and password I get a message saying an
>> Active directory domain controller for the domain.XXXX could not be
>> contacted. Ensure that the DNS domain is type correctly ( it is)
>>
>> clicking help I get
>>
>> The following error occurred when DNS was queried for the service
>> location
>> (SRV) resource record used to locate a domain controller for domain
>> domain.xxxx
>> The error was: "DNS name does not exist."
>> (error code 0x0000232B RCODE_NAME_ERROR)
>>
>> The query was for the SRV record for _ldap._tcp.dc._msdcs.domain.xxxx
>> Common causes of this error include the following:
>>
>> - The DNS SRV records required to locate a domain controller for the
> domain
>> are not registered in DNS. These records are registered with a DNS server
>> automatically when a domain controller is added to a domain. They are
>> updated by the domain controller at set intervals. This computer is
>> configured to use DNS servers with following IP addresses:
>>
>> 204.101.251.2
>> 204.101.251.1
>> 192.168.1.10
>>
>> - One or more of the following zones do not include delegation to its
> child
>> zone:
>>
>> domain.xxxx
>> xxxx
>> . (the root zone)
>>
>> For information about correcting this problem, click Help.
>>
>> Any help in resolving this problem would be greatly appreciated.
>>
>> Bob
>>
>>
>
>
Similar Threads
Linear Mode
