NTDS replication problems


F

fghdf

I am working with an exchange 2000 system installed on a windows 2000 DC.
There is only one DC in the domain and only one daomain in the forest.
Problems started when the ecxhnage system attendent would not start (so no
exchange :-( ) the events loged when starting System attendent look like
this:

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: None
Event ID: 2071
Date: 10/07/2004
Time: 12:37:27
User: N/A
Computer: SERVER2
Description:
Process MAD.EXE" (PID=820). All the remote Domain Controller Servers in use
are not responding.

For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 1005
Date: 10/07/2004
Time: 12:37:27
User: N/A
Computer: SERVER2
Description:
Unexpected error An unknown error has occurred. Facility: Win32 ID no:
c0070952 Microsoft Exchange System Attendant occurred.

For more information, click http://www.microsoft.com/contentredirect.asp.

So I was wondering if there was something wrong with the AD. In the
Directory Service Log I see the following every hour:

Event Type: Error
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1411
Date: 10/07/2004
Time: 12:25:42
User: Everyone
Computer: SERVER2
Description:
The Directory Service failed to construct a mutual authentication Service
Principal Name (SPN) for server SERVER2. The call is denied. The error was:
A Service Principal Name (SPN) could not be constructed because the
provided hostname is not in the necessary format.

The record data is the status code.
Data:
0000: 6a 21 00 00 j!..

Event Type: Warning
Event Source: NTDS General
Event Category: Global Catalog
Event ID: 1655
Date: 10/07/2004
Time: 12:25:42
User: Everyone
Computer: SERVER2
Description:
The attempt to communicate with global catalog \\SERVER2 failed with the
following status:

A Service Principal Name (SPN) could not be constructed because the
provided hostname is not in the necessary format.

The operation in progress might be unable to continue. The directory
service will use the locator to try find an available global catalog server
for the next operation that requires one.

The record data is the status code.
Data:
0000: 6a 21 00 00 j!..

Event Type: Error
Event Source: NTDS General
Event Category: Global Catalog
Event ID: 1126
Date: 10/07/2004
Time: 12:25:42
User: Everyone
Computer: SERVER2
Description:
Unable to establish connection with global catalog.

I do not have a clue why it is telling me that "the provided hostname is not
in the necessary format". But I wonder if it has to do with the following
log which is now logged every time that DNS starts:

Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 414
Date: 10/07/2004
Time: 12:11:51
User: N/A
Computer: SERVER2
Description:
The DNS server machine currently has no DNS domain name. Its DNS name is a
single label hostname with no domain (example: "host" rather than
"host.microsoft.com").

You might have forgotten to configure a primary DNS domain for the server
computer. For more information, see either "DNS server log reference" or "To
configure the primary DNS suffix for a client computer" in the online Help.

While the DNS server has only a single label name, all zones created will
have default records (SOA and NS) created using only this single label name
for the server's hostname. This can lead to incorrect and failed referrals
when clients and other DNS servers use these records to locate this server
by name.

To correct this problem:
1) open ControlPanel
2) open System applet
3) select NetworkIdentification tab
4) click the "Properties" button and enter a domain name or workgroup
name; this name will be used as your DNS domain name
5) reboot to initialize with new domain name

After reboot, the DNS server will attempt to fix up default records,
substituting new DNS name of this server, for old single label name.
However, you should review to make sure zone's SOA and NS records now
properly use correct domain name of this server.

This system has been set up and running for years. However the power supply
failed and needed replacing and at the same time an extra NIC was added.
After this exchange did run, but following a reboot a few hours later it has
not worked since. Is it a DNS problem that is cause NTDS to fail, which is
causing exchange to fail to start? How has it got like this? How can I fix
it?

Cheers all

Phill
 
Ad

Advertisements

H

Herb Martin

fghdf said:
I am working with an exchange 2000 system installed on a windows 2000 DC.
There is only one DC in the domain and only one daomain in the forest.
Problems started when the ecxhnage system attendent would not start (so no
exchange :-( ) the events loged when starting System attendent look like
this:
AD doesn't have anywhere to "replicate" with ONE DC in one
DOMAIN of a forest.

Given that you errors keep mentioning "Server2" it seems
probably that you USED TO HAVE another DC and have
removed it without properly allowing it to remove itself
from AD.

If so, search the MS Site from Google using something like:

[ ntdsutil.exe "metadata cleanup" 2000 remove site:microsot.com ]

Metadata cleanup (in NTDSUtil) allows one to remove abandom
DCs and abandon Domains.
 
F

fghdf

Fair spot. The AD was originally installed to server1, and over time it (and
exchange) was migrated to server2 by adding server2 as a DC, transferring
the roles across, demoting server1 and then decomissioning server1. That was
done several years ago, and everything has worked nicely since (until
lastnight!) I have used ntdsutil to attempt to clean up the residue from
server1, but the AD has no knowledge of server1, so I can only assume that
server1 was correctly decomissioned, and my troubles are caused by something
else.


Herb Martin said:
fghdf said:
I am working with an exchange 2000 system installed on a windows 2000 DC.
There is only one DC in the domain and only one daomain in the forest.
Problems started when the exchnage system attendent would not start (so no
exchange :-( ) the events loged when starting System attendent look like
this:
AD doesn't have anywhere to "replicate" with ONE DC in one
DOMAIN of a forest.

Given that you errors keep mentioning "Server2" it seems
probably that you USED TO HAVE another DC and have
removed it without properly allowing it to remove itself
from AD.

If so, search the MS Site from Google using something like:

[ ntdsutil.exe "metadata cleanup" 2000 remove site:microsot.com ]

Metadata cleanup (in NTDSUtil) allows one to remove abandom
DCs and abandon Domains.
 
H

Herb Martin

What does DCDiag.exe show?


--
Herb Martin


fghdf said:
Fair spot. The AD was originally installed to server1, and over time it (and
exchange) was migrated to server2 by adding server2 as a DC, transferring
the roles across, demoting server1 and then decomissioning server1. That was
done several years ago, and everything has worked nicely since (until
lastnight!) I have used ntdsutil to attempt to clean up the residue from
server1, but the AD has no knowledge of server1, so I can only assume that
server1 was correctly decomissioned, and my troubles are caused by something
else.


(so
no
exchange :-( ) the events loged when starting System attendent look like
this:
AD doesn't have anywhere to "replicate" with ONE DC in one
DOMAIN of a forest.

Given that you errors keep mentioning "Server2" it seems
probably that you USED TO HAVE another DC and have
removed it without properly allowing it to remove itself
from AD.

If so, search the MS Site from Google using something like:

[ ntdsutil.exe "metadata cleanup" 2000 remove site:microsot.com ]

Metadata cleanup (in NTDSUtil) allows one to remove abandom
DCs and abandon Domains.
 
F

fghdf

Initially there was a failure in the Connectivity test to say that it could
not resolve server2.pwb.null. So I have added a record to the DNS server for
server2 and now I get the following:

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: PWBSite\SERVER2
Starting test: Connectivity
*** Warning: could not confirm the identity of this server in
the directory versus the names returned by DNS servers.
If there are problems accessing this directory server then
you may need to check that this server is correctly
registered
with DNS
......................... SERVER2 passed test Connectivity

Doing primary tests

Testing server: PWBSite\SERVER2
Starting test: Replications
......................... SERVER2 passed test Replications
Starting test: NCSecDesc
......................... SERVER2 passed test NCSecDesc
Starting test: NetLogons
......................... SERVER2 passed test NetLogons
Starting test: Advertising
......................... SERVER2 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... SERVER2 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... SERVER2 passed test RidManager
Starting test: MachineAccount
......................... SERVER2 passed test MachineAccount
Starting test: Services
......................... SERVER2 passed test Services
Starting test: ObjectsReplicated
......................... SERVER2 passed test ObjectsReplicated
Starting test: frssysvol
......................... SERVER2 passed test frssysvol
Starting test: kccevent
......................... SERVER2 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:44:27
Event String: The Microsoft Exchange Information Store service
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:44:28
Event String: The Microsoft Exchange MTA Stacks service depends
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:44:28
Event String: The Microsoft Exchange POP3 service depends on
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:44:39
Event String: The Microsoft Exchange IMAP4 service depends on
An Error Event occured. EventID: 0x80001778
Time Generated: 07/11/2004 16:52:53
Event String: The previous system shutdown at 16:46:36 on
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:55:26
Event String: The Microsoft Exchange Information Store service
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:55:26
Event String: The Microsoft Exchange MTA Stacks service depends
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:55:26
Event String: The Microsoft Exchange POP3 service depends on
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:55:32
Event String: The Microsoft Exchange IMAP4 service depends on
An Error Event occured. EventID: 0x00000411
Time Generated: 07/11/2004 16:56:05
Event String: The DHCP service is not servicing any clients
An Error Event occured. EventID: 0x00004E8A
Time Generated: 07/11/2004 16:56:13
Event String: Unable to add the interface
......................... SERVER2 failed test systemlog

Running enterprise tests on : pwb.null
Starting test: Intersite
......................... pwb.null passed test Intersite
Starting test: FsmoCheck
......................... pwb.null passed test FsmoCheck
Herb Martin said:
What does DCDiag.exe show?


--
Herb Martin


fghdf said:
Fair spot. The AD was originally installed to server1, and over time it (and
exchange) was migrated to server2 by adding server2 as a DC, transferring
the roles across, demoting server1 and then decomissioning server1. That was
done several years ago, and everything has worked nicely since (until
lastnight!) I have used ntdsutil to attempt to clean up the residue from
server1, but the AD has no knowledge of server1, so I can only assume that
server1 was correctly decomissioned, and my troubles are caused by something
else.


Herb Martin said:
I am working with an exchange 2000 system installed on a windows
2000
DC.
There is only one DC in the domain and only one daomain in the forest.
Problems started when the exchnage system attendent would not start
(so
no
exchange :-( ) the events loged when starting System attendent look like
this:

AD doesn't have anywhere to "replicate" with ONE DC in one
DOMAIN of a forest.

Given that you errors keep mentioning "Server2" it seems
probably that you USED TO HAVE another DC and have
removed it without properly allowing it to remove itself
from AD.

If so, search the MS Site from Google using something like:

[ ntdsutil.exe "metadata cleanup" 2000 remove site:microsot.com ]

Metadata cleanup (in NTDSUtil) allows one to remove abandom
DCs and abandon Domains.
 
H

Herb Martin

Do you have a "one tag" Domain/DNS name? PWB instead of
something like PWB.com or PWB.net or PWB.local?

You need at least a two tag name for DNS/AD domains.

--
Herb Martin


fghdf said:
Initially there was a failure in the Connectivity test to say that it could
not resolve server2.pwb.null. So I have added a record to the DNS server for
server2 and now I get the following:

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: PWBSite\SERVER2
Starting test: Connectivity
*** Warning: could not confirm the identity of this server in
the directory versus the names returned by DNS servers.
If there are problems accessing this directory server then
you may need to check that this server is correctly
registered
with DNS
......................... SERVER2 passed test Connectivity

Doing primary tests

Testing server: PWBSite\SERVER2
Starting test: Replications
......................... SERVER2 passed test Replications
Starting test: NCSecDesc
......................... SERVER2 passed test NCSecDesc
Starting test: NetLogons
......................... SERVER2 passed test NetLogons
Starting test: Advertising
......................... SERVER2 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... SERVER2 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... SERVER2 passed test RidManager
Starting test: MachineAccount
......................... SERVER2 passed test MachineAccount
Starting test: Services
......................... SERVER2 passed test Services
Starting test: ObjectsReplicated
......................... SERVER2 passed test ObjectsReplicated
Starting test: frssysvol
......................... SERVER2 passed test frssysvol
Starting test: kccevent
......................... SERVER2 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:44:27
Event String: The Microsoft Exchange Information Store service
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:44:28
Event String: The Microsoft Exchange MTA Stacks service depends
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:44:28
Event String: The Microsoft Exchange POP3 service depends on
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:44:39
Event String: The Microsoft Exchange IMAP4 service depends on
An Error Event occured. EventID: 0x80001778
Time Generated: 07/11/2004 16:52:53
Event String: The previous system shutdown at 16:46:36 on
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:55:26
Event String: The Microsoft Exchange Information Store service
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:55:26
Event String: The Microsoft Exchange MTA Stacks service depends
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:55:26
Event String: The Microsoft Exchange POP3 service depends on
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:55:32
Event String: The Microsoft Exchange IMAP4 service depends on
An Error Event occured. EventID: 0x00000411
Time Generated: 07/11/2004 16:56:05
Event String: The DHCP service is not servicing any clients
An Error Event occured. EventID: 0x00004E8A
Time Generated: 07/11/2004 16:56:13
Event String: Unable to add the interface
......................... SERVER2 failed test systemlog

Running enterprise tests on : pwb.null
Starting test: Intersite
......................... pwb.null passed test Intersite
Starting test: FsmoCheck
......................... pwb.null passed test FsmoCheck
Herb Martin said:
What does DCDiag.exe show?


--
Herb Martin


fghdf said:
Fair spot. The AD was originally installed to server1, and over time
it
(and
exchange) was migrated to server2 by adding server2 as a DC, transferring
the roles across, demoting server1 and then decomissioning server1.
That
was
done several years ago, and everything has worked nicely since (until
lastnight!) I have used ntdsutil to attempt to clean up the residue from
server1, but the AD has no knowledge of server1, so I can only assume that
server1 was correctly decomissioned, and my troubles are caused by something
else.


I am working with an exchange 2000 system installed on a windows 2000
DC.
There is only one DC in the domain and only one daomain in the forest.
Problems started when the exchnage system attendent would not
start
(so
no
exchange :-( ) the events loged when starting System attendent
look
like
this:

AD doesn't have anywhere to "replicate" with ONE DC in one
DOMAIN of a forest.

Given that you errors keep mentioning "Server2" it seems
probably that you USED TO HAVE another DC and have
removed it without properly allowing it to remove itself
from AD.

If so, search the MS Site from Google using something like:

[ ntdsutil.exe "metadata cleanup" 2000 remove site:microsot.com ]

Metadata cleanup (in NTDSUtil) allows one to remove abandom
DCs and abandon Domains.
 
Ad

Advertisements

F

fghdf

Are you asking what the FQDN is - it is server2.pwb.null the name of the
domain is pwb.null

Herb Martin said:
Do you have a "one tag" Domain/DNS name? PWB instead of
something like PWB.com or PWB.net or PWB.local?

You need at least a two tag name for DNS/AD domains.

--
Herb Martin


fghdf said:
Initially there was a failure in the Connectivity test to say that it could
not resolve server2.pwb.null. So I have added a record to the DNS server for
server2 and now I get the following:

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: PWBSite\SERVER2
Starting test: Connectivity
*** Warning: could not confirm the identity of this server in
the directory versus the names returned by DNS servers.
If there are problems accessing this directory server then
you may need to check that this server is correctly
registered
with DNS
......................... SERVER2 passed test Connectivity

Doing primary tests

Testing server: PWBSite\SERVER2
Starting test: Replications
......................... SERVER2 passed test Replications
Starting test: NCSecDesc
......................... SERVER2 passed test NCSecDesc
Starting test: NetLogons
......................... SERVER2 passed test NetLogons
Starting test: Advertising
......................... SERVER2 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... SERVER2 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... SERVER2 passed test RidManager
Starting test: MachineAccount
......................... SERVER2 passed test MachineAccount
Starting test: Services
......................... SERVER2 passed test Services
Starting test: ObjectsReplicated
......................... SERVER2 passed test ObjectsReplicated
Starting test: frssysvol
......................... SERVER2 passed test frssysvol
Starting test: kccevent
......................... SERVER2 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:44:27
Event String: The Microsoft Exchange Information Store service
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:44:28
Event String: The Microsoft Exchange MTA Stacks service depends
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:44:28
Event String: The Microsoft Exchange POP3 service depends on
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:44:39
Event String: The Microsoft Exchange IMAP4 service depends on
An Error Event occured. EventID: 0x80001778
Time Generated: 07/11/2004 16:52:53
Event String: The previous system shutdown at 16:46:36 on
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:55:26
Event String: The Microsoft Exchange Information Store service
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:55:26
Event String: The Microsoft Exchange MTA Stacks service depends
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:55:26
Event String: The Microsoft Exchange POP3 service depends on
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:55:32
Event String: The Microsoft Exchange IMAP4 service depends on
An Error Event occured. EventID: 0x00000411
Time Generated: 07/11/2004 16:56:05
Event String: The DHCP service is not servicing any clients
An Error Event occured. EventID: 0x00004E8A
Time Generated: 07/11/2004 16:56:13
Event String: Unable to add the interface
......................... SERVER2 failed test systemlog

Running enterprise tests on : pwb.null
Starting test: Intersite
......................... pwb.null passed test Intersite
Starting test: FsmoCheck
......................... pwb.null passed test FsmoCheck
Herb Martin said:
What does DCDiag.exe show?


--
Herb Martin


Fair spot. The AD was originally installed to server1, and over time it
(and
exchange) was migrated to server2 by adding server2 as a DC, transferring
the roles across, demoting server1 and then decomissioning server1. That
was
done several years ago, and everything has worked nicely since (until
lastnight!) I have used ntdsutil to attempt to clean up the residue from
server1, but the AD has no knowledge of server1, so I can only
assume
that
server1 was correctly decomissioned, and my troubles are caused by
something
else.


I am working with an exchange 2000 system installed on a windows 2000
DC.
There is only one DC in the domain and only one daomain in the forest.
Problems started when the exchnage system attendent would not start
(so
no
exchange :-( ) the events loged when starting System attendent look
like
this:

AD doesn't have anywhere to "replicate" with ONE DC in one
DOMAIN of a forest.

Given that you errors keep mentioning "Server2" it seems
probably that you USED TO HAVE another DC and have
removed it without properly allowing it to remove itself
from AD.

If so, search the MS Site from Google using something like:

[ ntdsutil.exe "metadata cleanup" 2000 remove site:microsot.com ]

Metadata cleanup (in NTDSUtil) allows one to remove abandom
DCs and abandon Domains.
 
H

Herb Martin

fghdf said:
Are you asking what the FQDN is - it is server2.pwb.null the name of the
domain is pwb.null
Do you mean you actually use the tag "null"?

That is fine, but the word 'null' also means empty or
vacant to having it BE NULL is bad. Having it use the
words or two-tags "pwb.null" is just fine.


--
Herb Martin

Herb Martin said:
Do you have a "one tag" Domain/DNS name? PWB instead of
something like PWB.com or PWB.net or PWB.local?

You need at least a two tag name for DNS/AD domains.

--
Herb Martin


fghdf said:
Initially there was a failure in the Connectivity test to say that it could
not resolve server2.pwb.null. So I have added a record to the DNS
server
for
server2 and now I get the following:

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: PWBSite\SERVER2
Starting test: Connectivity
*** Warning: could not confirm the identity of this server in
the directory versus the names returned by DNS servers.
If there are problems accessing this directory server then
you may need to check that this server is correctly
registered
with DNS
......................... SERVER2 passed test Connectivity

Doing primary tests

Testing server: PWBSite\SERVER2
Starting test: Replications
......................... SERVER2 passed test Replications
Starting test: NCSecDesc
......................... SERVER2 passed test NCSecDesc
Starting test: NetLogons
......................... SERVER2 passed test NetLogons
Starting test: Advertising
......................... SERVER2 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... SERVER2 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... SERVER2 passed test RidManager
Starting test: MachineAccount
......................... SERVER2 passed test MachineAccount
Starting test: Services
......................... SERVER2 passed test Services
Starting test: ObjectsReplicated
......................... SERVER2 passed test ObjectsReplicated
Starting test: frssysvol
......................... SERVER2 passed test frssysvol
Starting test: kccevent
......................... SERVER2 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:44:27
Event String: The Microsoft Exchange Information Store service
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:44:28
Event String: The Microsoft Exchange MTA Stacks service depends
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:44:28
Event String: The Microsoft Exchange POP3 service depends on
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:44:39
Event String: The Microsoft Exchange IMAP4 service depends on
An Error Event occured. EventID: 0x80001778
Time Generated: 07/11/2004 16:52:53
Event String: The previous system shutdown at 16:46:36 on
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:55:26
Event String: The Microsoft Exchange Information Store service
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:55:26
Event String: The Microsoft Exchange MTA Stacks service depends
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:55:26
Event String: The Microsoft Exchange POP3 service depends on
An Error Event occured. EventID: 0xC0001B59
Time Generated: 07/11/2004 16:55:32
Event String: The Microsoft Exchange IMAP4 service depends on
An Error Event occured. EventID: 0x00000411
Time Generated: 07/11/2004 16:56:05
Event String: The DHCP service is not servicing any clients
An Error Event occured. EventID: 0x00004E8A
Time Generated: 07/11/2004 16:56:13
Event String: Unable to add the interface
......................... SERVER2 failed test systemlog

Running enterprise tests on : pwb.null
Starting test: Intersite
......................... pwb.null passed test Intersite
Starting test: FsmoCheck
......................... pwb.null passed test FsmoCheck
What does DCDiag.exe show?


--
Herb Martin


Fair spot. The AD was originally installed to server1, and over
time
it
(and
exchange) was migrated to server2 by adding server2 as a DC,
transferring
the roles across, demoting server1 and then decomissioning
server1.
That
was
done several years ago, and everything has worked nicely since (until
lastnight!) I have used ntdsutil to attempt to clean up the
residue
from
server1, but the AD has no knowledge of server1, so I can only assume
that
server1 was correctly decomissioned, and my troubles are caused by
something
else.


I am working with an exchange 2000 system installed on a windows
2000
DC.
There is only one DC in the domain and only one daomain in the
forest.
Problems started when the exchnage system attendent would not start
(so
no
exchange :-( ) the events loged when starting System attendent look
like
this:

AD doesn't have anywhere to "replicate" with ONE DC in one
DOMAIN of a forest.

Given that you errors keep mentioning "Server2" it seems
probably that you USED TO HAVE another DC and have
removed it without properly allowing it to remove itself
from AD.

If so, search the MS Site from Google using something like:

[ ntdsutil.exe "metadata cleanup" 2000 remove site:microsot.com ]

Metadata cleanup (in NTDSUtil) allows one to remove abandom
DCs and abandon Domains.
 
F

fghdf

Yes, the domain name is "pwb.null" As you say - that should be ok.
All the symptoms I see suggest that the problem is as described here
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q257623
However it is not the case that the hastname and domain name differ. I have
checked the registry entries under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters and
all seems well. But just be be sure I have run the .js script supplied to
fix this problem, and it hasn't :-(
So, still everytime that I start the DNS server it logs in the event log:

Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 414
Date: 13/07/2004
Time: 01:24:35
User: N/A
Computer: SERVER2
Description:
The DNS server machine currently has no DNS domain name. Its DNS name is a
single label hostname with no domain (example: "host" rather than
"host.microsoft.com").

You might have forgotten to configure a primary DNS domain for the server
computer. For more information, see either "DNS server log reference" or "To
configure the primary DNS suffix for a client computer" in the online Help.

While the DNS server has only a single label name, all zones created will
have default records (SOA and NS) created using only this single label name
for the server's hostname. This can lead to incorrect and failed referrals
when clients and other DNS servers use these records to locate this server
by name.

To correct this problem:
1) open ControlPanel
2) open System applet
3) select NetworkIdentification tab
4) click the "Properties" button and enter a domain name or workgroup
name; this name will be used as your DNS domain name
5) reboot to initialize with new domain name

After reboot, the DNS server will attempt to fix up default records,
substituting new DNS name of this server, for old single label name.
However, you should review to make sure zone's SOA and NS records now
properly use correct domain name of this server.

This driving me nuts. I do not want to loose the AD, which seems intact, but
I can't use it because the DNS server is not working properly! I can't add
another DC and mirgate to a new machine because the the new DC candidate
can't find the Global Catalog because the DNS is not working properly. Any
other suggestions anyone?
 
F

fghdf

OK, I am so pleased that I have managed to fix it all, I suppose I had
better post what the solution was:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Hostna
me had value "SERVER2"
Changing it to "server2" caused DNS to stop complaining and so it started to
resolve everything neccassery to get AD going again, and hence exchange can
now be started. Yay! Unfortunately I have butchered the machine as a result
of trying to fix it by trial and error, but I can sort that.

I have several burning question, but accept I might well never get answers
to any of then:
1) WTF??????
2) How did it get broken in the first place? All I did was add a network
card, and even then, it did not break until after 2 reboots.
3) Can I have those 3 days of my life back please?

Thanks for all the help I received on this problem.

Phill



fghdf said:
Yes, the domain name is "pwb.null" As you say - that should be ok.
All the symptoms I see suggest that the problem is as described here
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q257623
However it is not the case that the hastname and domain name differ. I have
checked the registry entries under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters and
all seems well. But just be be sure I have run the .js script supplied to
fix this problem, and it hasn't :-(
So, still everytime that I start the DNS server it logs in the event log:

Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 414
Date: 13/07/2004
Time: 01:24:35
User: N/A
Computer: SERVER2
Description:
The DNS server machine currently has no DNS domain name. Its DNS name is a
single label hostname with no domain (example: "host" rather than
"host.microsoft.com").

You might have forgotten to configure a primary DNS domain for the server
computer. For more information, see either "DNS server log reference" or "To
configure the primary DNS suffix for a client computer" in the online Help.

While the DNS server has only a single label name, all zones created will
have default records (SOA and NS) created using only this single label name
for the server's hostname. This can lead to incorrect and failed referrals
when clients and other DNS servers use these records to locate this server
by name.

To correct this problem:
1) open ControlPanel
2) open System applet
3) select NetworkIdentification tab
4) click the "Properties" button and enter a domain name or workgroup
name; this name will be used as your DNS domain name
5) reboot to initialize with new domain name

After reboot, the DNS server will attempt to fix up default records,
substituting new DNS name of this server, for old single label name.
However, you should review to make sure zone's SOA and NS records now
properly use correct domain name of this server.

This driving me nuts. I do not want to loose the AD, which seems intact, but
I can't use it because the DNS server is not working properly! I can't add
another DC and mirgate to a new machine because the the new DC candidate
can't find the Global Catalog because the DNS is not working properly. Any
other suggestions anyone?
 
Ad

Advertisements

P

ptwilliams

3) Can I have those 3 days of my life back please?

No.

;-)


--

Paul Williams
_________________________________________
http://www.msresource.net


Join us in our new forums!
http://forums.msresource.net
_________________________________________


OK, I am so pleased that I have managed to fix it all, I suppose I had
better post what the solution was:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Hostna
me had value "SERVER2"
Changing it to "server2" caused DNS to stop complaining and so it started to
resolve everything neccassery to get AD going again, and hence exchange can
now be started. Yay! Unfortunately I have butchered the machine as a result
of trying to fix it by trial and error, but I can sort that.

I have several burning question, but accept I might well never get answers
to any of then:
1) WTF??????
2) How did it get broken in the first place? All I did was add a network
card, and even then, it did not break until after 2 reboots.
3) Can I have those 3 days of my life back please?

Thanks for all the help I received on this problem.

Phill



fghdf said:
Yes, the domain name is "pwb.null" As you say - that should be ok.
All the symptoms I see suggest that the problem is as described here
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q257623
However it is not the case that the hastname and domain name differ. I have
checked the registry entries under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters and
all seems well. But just be be sure I have run the .js script supplied to
fix this problem, and it hasn't :-(
So, still everytime that I start the DNS server it logs in the event log:

Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 414
Date: 13/07/2004
Time: 01:24:35
User: N/A
Computer: SERVER2
Description:
The DNS server machine currently has no DNS domain name. Its DNS name is a
single label hostname with no domain (example: "host" rather than
"host.microsoft.com").

You might have forgotten to configure a primary DNS domain for the server
computer. For more information, see either "DNS server log reference" or "To
configure the primary DNS suffix for a client computer" in the online Help.

While the DNS server has only a single label name, all zones created will
have default records (SOA and NS) created using only this single label name
for the server's hostname. This can lead to incorrect and failed referrals
when clients and other DNS servers use these records to locate this server
by name.

To correct this problem:
1) open ControlPanel
2) open System applet
3) select NetworkIdentification tab
4) click the "Properties" button and enter a domain name or workgroup
name; this name will be used as your DNS domain name
5) reboot to initialize with new domain name

After reboot, the DNS server will attempt to fix up default records,
substituting new DNS name of this server, for old single label name.
However, you should review to make sure zone's SOA and NS records now
properly use correct domain name of this server.

This driving me nuts. I do not want to loose the AD, which seems intact, but
I can't use it because the DNS server is not working properly! I can't add
another DC and mirgate to a new machine because the the new DC candidate
can't find the Global Catalog because the DNS is not working properly. Any
other suggestions anyone?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

NTDS Replication problem 0
NTDS and replication! 1
NTDS Replication Problems 2
NTDS Replication 4
NTDS Replication.. 2
NTDS Replication 0
NTDS Connections for replication 1
NTDS Replication Warning 6

Top