Re: dcdiag - ... not responding to directory service requests
- From: <churchmouse@xxxxxxxxxxxxxxxxxx>
- Date: Mon, 10 Apr 2006 08:54:50 -0700
"Ace Fekay [MVP]" <PleaseAskMe@xxxxxxxxxxxxxx> wrote in message
news:eOqJgPCXGHA.4484@xxxxxxxxxxxxxxxxxxxxxxx
In news:eT$w%23n$WGHA.3864@xxxxxxxxxxxxxxxxxxxx,
churchmouse@xxxxxxxxxxxxxx <churchmouse@xxxxxxxxxxxxxx> stated, which I
commented on below:
3 servers on this win2k domain...
Because of a HD crash I rebuit the machine using pieces of the raid
set (both drives died simultaniously) and got it working, I then had
a USN rollback problem so I demoted my mail server, did a metadata
cleanup and promoted again. That alowwed me to add users again and it
seems OK but... Now my Role holder event log is throwing KCC
errors (event ID 1265) that refer to DNS entries.
I found that the dsa address guid (cname) was different from the mail
server's dns entries so I deleted and created an identical record.
but still the 1265 error
DCDIAG run on both the Role holder and the mailserver in question
skip the mail server with the message "Not responding to directory
service requests"
I can ping it by name or IP from any machine on the lan but I am at
the end of my experience now.
What would be the next step in resolving this?
I can't see how demoting a mail server will help, unless it was a domain
controller. If that is the case, and you (assuming) reproted the DC into a
brand new domain, then I would also assume it would populate fresh data
into DNS, unless of course this was not the only DC in the domain. (Good
reason not to install Exchnage on a DC).
If you had a complete system state and Exchange backup, you could have
rebuilt the machine, then restored the system state, then restore
Exchange, then ran Exchange setup again with the setup /disasterrecovery
switch.
If this is the only DC in the domain, and you've already lost your user
accounts, and you do not have backups, I would assume the best course of
action is to just rebuild from scratch and install Exchange (preferrably
on another machine), then disjoin and then rejoin the clients to the new
domain.
If you are trying to repair this, I would suggest to delete all the SRV
entries in DNS, and run ipconfig /registerdns, then restart the netlogon
service to repopulate the SRV records. If they are not populating
(registering) , (assuming that DNS is pointed to itself and the zone is
allowed updates, along with the domain is NOT a single label name), then
something else is going on, and if it's that far gone, a fresh rebuild may
be in order.
--
Ace
Hello Ace . mmac here. Good to see you are still around.
The dcpromo was in response to the failure of the HD set. After the
repair, the server functioned and served mail but if I tried to add a user
it wouldn't populate to the mail server the event log error were for USN
rollback. The soution was to demote, and remove metadata that referred to
theat machine and repromote. So I seized the roles and did just that.
So it does seem to be a DNS issue and I'll follow your advice this
evening.
Since there are three DNS servers I assume that I should delete those
records from them all?
And then reregister just the mail server? -correct?
.
- Follow-Ups:
- Re: dcdiag - ... not responding to directory service requests
- From: Ace Fekay [MVP]
- Re: dcdiag - ... not responding to directory service requests
- References:
- dcdiag - ... not responding to directory service requests
- From: churchmouse
- Re: dcdiag - ... not responding to directory service requests
- From: Ace Fekay [MVP]
- dcdiag - ... not responding to directory service requests
- Prev by Date: Re: moving website in house.
- Next by Date: Correct DNS configuration
- Previous by thread: Re: dcdiag - ... not responding to directory service requests
- Next by thread: Re: dcdiag - ... not responding to directory service requests
- Index(es):
Relevant Pages
|
