Re: Upgrading 32-bit AD to 64-bit - FSMO problem

Thank you so much Paul. Here is the IPCONFIG info from all 3 DCs:

EX-DC1

Windows IP Configuration

Host Name . . . . . . . . . . . . : ex-dc1
Primary Dns Suffix . . . . . . . : exchange.datagate.net
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : exchange.datagate.net
datagate.net

Ethernet adapter LOCAL:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 XT Server Adapter
Physical Address. . . . . . . . . : 00-02-B3-E6-EF-3A
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.100.211
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Primary WINS Server . . . . . . . : 192.168.100.211

Ethernet adapter PUBLIC:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet
Adapter (10/100)
Physical Address. . . . . . . . . : 00-D0-B7-B6-BA-DF
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 62.204.35.211
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . : 62.204.35.209
DNS Servers . . . . . . . . . . . : 62.204.35.211
62.204.35.212
NetBIOS over Tcpip. . . . . . . . : Disabled


EX-DC2

Windows IP Configuration

Host Name . . . . . . . . . . . . : ex-dc2
Primary Dns Suffix . . . . . . . : exchange.datagate.net
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : exchange.datagate.net
datagate.net

PPP adapter RAS Server (Dial In) Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.100.1
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :

Ethernet adapter PUBLIC:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82559 Fast Ethernet LAN on
Motherboard
Physical Address. . . . . . . . . : 00-D0-B7-A7-5E-10
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 62.204.35.212
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . : 62.204.35.209
DNS Servers . . . . . . . . . . . : 62.204.35.211
62.204.35.212
NetBIOS over Tcpip. . . . . . . . : Disabled

Ethernet adapter LOCAL:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 XT Server Adapter
Physical Address. . . . . . . . . : 00-02-B3-E6-F0-A9
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.212
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.100.212
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Primary WINS Server . . . . . . . : 192.168.100.211


EX-DC3

Windows IP Configuration

Host Name . . . . . . . . . . . . : ex-dc3
Primary Dns Suffix . . . . . . . : exchange.datagate.net
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : exchange.datagate.net

Ethernet adapter LOCAL:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet
Adapter (10/100) #2
Physical Address. . . . . . . . . : 00-07-E9-E6-DC-11
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.100.217
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Ethernet adapter INTERNET:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet
Adapter (10/100)
Physical Address. . . . . . . . . : 00-07-E9-E6-DC-10
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 62.204.35.217
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . : 62.204.35.209
DNS Servers . . . . . . . . . . . : 62.204.35.211
62.204.35.212


I could not find the link to download your script, so I executed all tests
manually. Basically, I found errors and warnings in dcdiag.log only. Warnings
regarding EX-DC3 replication look interesting...anyway, I will paste only
errors and warnings, please let me know if you need complete log:

EX-DC1

Starting test: Topology

* Performing downstream (of target) analysis.
Downstream topology is disconnected for
CN=Schema,CN=Configuration,DC=exchange,DC=datagate,DC=net.
These servers can't get changes from home server EX-DC1:
Default-First-Site-Name/EX-DC3
* Performing downstream (of target) analysis.
Downstream topology is disconnected for
CN=Configuration,DC=exchange,DC=datagate,DC=net.
These servers can't get changes from home server EX-DC1:
Default-First-Site-Name/EX-DC3
* Performing downstream (of target) analysis.
Downstream topology is disconnected for
DC=exchange,DC=datagate,DC=net.
These servers can't get changes from home server EX-DC1:
Default-First-Site-Name/EX-DC3
......................... EX-DC1 failed test Topology

Starting test: CutoffServers

* Performing downstream (of target) analysis.
Downstream topology is disconnected for
CN=Schema,CN=Configuration,DC=exchange,DC=datagate,DC=net.
These servers can't get changes from home server EX-DC1:
Default-First-Site-Name/EX-DC3
* Performing downstream (of target) analysis.
Downstream topology is disconnected for
CN=Configuration,DC=exchange,DC=datagate,DC=net.
These servers can't get changes from home server EX-DC1:
Default-First-Site-Name/EX-DC3
* Performing downstream (of target) analysis.
Downstream topology is disconnected for
DC=exchange,DC=datagate,DC=net.
These servers can't get changes from home server EX-DC1:
Default-First-Site-Name/EX-DC3
......................... EX-DC1 failed test CutoffServers

Starting test: VerifyEnterpriseReferences
The following problems were found while verifying various important
DN
references. Note, that these problems can be reported because of
latency in replication. So follow up to resolve the following
problems, only if the same problem is reported on all DCs for a given
domain or if the problem persists after replication has had
reasonable time to replicate changes.
[1] Problem: Missing Expected Value
Base Object:
CN=EX-DC3,OU=Domain Controllers,DC=exchange,DC=datagate,DC=net
Base Object Description: "DC Account Object"
Value Object Attribute Name: frsComputerReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862

......................... EX-DC1 failed test
VerifyEnterpriseReferences


=====================

EX-DC2


Starting test: Topology
* Performing downstream (of target) analysis.
Downstream topology is disconnected for
CN=Schema,CN=Configuration,DC=exchange,DC=datagate,DC=net.
These servers can't get changes from home server EX-DC2:
Default-First-Site-Name/EX-DC3
* Performing downstream (of target) analysis.
Downstream topology is disconnected for
CN=Configuration,DC=exchange,DC=datagate,DC=net.
These servers can't get changes from home server EX-DC2:
Default-First-Site-Name/EX-DC3
* Performing downstream (of target) analysis.
Downstream topology is disconnected for
DC=exchange,DC=datagate,DC=net.
These servers can't get changes from home server EX-DC2:
Default-First-Site-Name/EX-DC3
......................... EX-DC2 failed test Topology

Starting test: CutoffServers
* Performing downstream (of target) analysis.
Downstream topology is disconnected for
CN=Schema,CN=Configuration,DC=exchange,DC=datagate,DC=net.
These servers can't get changes from home server EX-DC2:
Default-First-Site-Name/EX-DC3
* Performing downstream (of target) analysis.
Downstream topology is disconnected for
CN=Configuration,DC=exchange,DC=datagate,DC=net.
These servers can't get changes from home server EX-DC2:
Default-First-Site-Name/EX-DC3
* Performing downstream (of target) analysis.
Downstream topology is disconnected for
DC=exchange,DC=datagate,DC=net.
These servers can't get changes from home server EX-DC2:
Default-First-Site-Name/EX-DC3
......................... EX-DC2 failed test CutoffServers

Starting test: VerifyEnterpriseReferences
The following problems were found while verifying various important
DN
references. Note, that these problems can be reported because of
latency in replication. So follow up to resolve the following
problems, only if the same problem is reported on all DCs for a given
domain or if the problem persists after replication has had
reasonable time to replicate changes.
[1] Problem: Missing Expected Value
Base Object:
CN=EX-DC3,OU=Domain Controllers,DC=exchange,DC=datagate,DC=net
Base Object Description: "DC Account Object"
Value Object Attribute Name: frsComputerReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862

......................... EX-DC2 failed test
VerifyEnterpriseReferences


=====================

EX-DC3


Testing server: Default-First-Site-Name\EX-DC3
Starting test: Replications
* Replications Check
CN=Schema,CN=Configuration,DC=exchange,DC=datagate,DC=net has 3
cursors.
CN=Configuration,DC=exchange,DC=datagate,DC=net has 3 cursors.
REPLICATION LATENCY WARNING
EX-DC3: This replication path was preempted by higher priority work.
from EX-DC1 to EX-DC3
Reason: The replication operation failed because of a schema
mismatch between the servers involved.
The last success occurred at 2008-09-23 13:06:23.
Replication of new changes along this path will be delayed.
REPLICATION LATENCY WARNING
EX-DC3: This replication path was preempted by higher priority work.
from EX-DC2 to EX-DC3
Reason: The replication operation failed because of a schema
mismatch between the servers involved.
The last success occurred at 2008-09-23 13:10:51.
Replication of new changes along this path will be delayed.
DC=exchange,DC=datagate,DC=net has 3 cursors.
REPLICATION LATENCY WARNING
EX-DC3: This replication path was preempted by higher priority work.
from EX-DC2 to EX-DC3
Reason: The replication operation failed because of a schema
mismatch between the servers involved.
The last success occurred at 2008-09-23 13:10:51.
Replication of new changes along this path will be delayed.
REPLICATION LATENCY WARNING
EX-DC3: This replication path was preempted by higher priority work.
from EX-DC1 to EX-DC3
Reason: The replication operation failed because of a schema
mismatch between the servers involved.
The last success occurred at 2008-09-23 13:06:23.
Replication of new changes along this path will be delayed.
* Replication Latency Check
REPLICATION-RECEIVED LATENCY WARNING
EX-DC3: Current time is 2008-09-24 13:40:34.
CN=Configuration,DC=exchange,DC=datagate,DC=net
Last replication recieved from EX-DC1 at 2008-09-23 13:09:17.
Last replication recieved from EX-DC2 at 2008-09-23 13:10:51.
DC=exchange,DC=datagate,DC=net
Last replication recieved from EX-DC1 at 2008-09-23 13:10:42.
Last replication recieved from EX-DC2 at 2008-09-23 13:10:51.
* Replication Site Latency Check
Site Settings = CN=NTDS Site
Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=exchange,DC=datagate,DC=net
[0x904de,v=55782,t=2008-09-24
13:08:49,g=6c5dcccf-4784-4cd0-8ff3-5fca84c19580,orig=47740,local=47740]
Elapsed time (sec) = 1907
......................... EX-DC3 passed test Replications

Starting test: ObjectsReplicated
EX-DC3 is in domain DC=exchange,DC=datagate,DC=net
Checking for CN=EX-DC3,OU=Domain
Controllers,DC=exchange,DC=datagate,DC=net in domain
DC=exchange,DC=datagate,DC=net on 3 servers
Authoritative attribute nTSecurityDescriptor on EX-DC3 (writeable)
usnLocalChange = 20482
LastOriginatingDsa = EX-DC3
usnOriginatingChange = 20482
timeLastOriginatingChange = 2008-09-23 13:05:45
VersionLastOriginatingChange = 2
Out-of-date attribute nTSecurityDescriptor on EX-DC1 (writeable)
usnLocalChange = 11152317
LastOriginatingDsa = EX-DC1
usnOriginatingChange = 11152317
timeLastOriginatingChange = 2006-05-15 15:53:40
VersionLastOriginatingChange = 1
Out-of-date attribute nTSecurityDescriptor on EX-DC2 (writeable)
usnLocalChange = 10920641
LastOriginatingDsa = EX-DC1
usnOriginatingChange = 11152317
timeLastOriginatingChange = 2006-05-15 15:53:40
VersionLastOriginatingChange = 1
Authoritative attribute servicePrincipalName on EX-DC3 (writeable)
usnLocalChange = 20519
LastOriginatingDsa = EX-DC3
usnOriginatingChange = 20519
timeLastOriginatingChange = 2008-09-23 13:06:36
VersionLastOriginatingChange = 20
Out-of-date attribute servicePrincipalName on EX-DC2 (writeable)
usnLocalChange = 31531976
LastOriginatingDsa = EX-DC1
usnOriginatingChange = 33428219
timeLastOriginatingChange = 2008-09-23 13:01:38
VersionLastOriginatingChange = 19
Out-of-date attribute servicePrincipalName on EX-DC1 (writeable)
usnLocalChange = 33428219
LastOriginatingDsa = EX-DC1
usnOriginatingChange = 33428219
timeLastOriginatingChange = 2008-09-23 13:01:38
VersionLastOriginatingChange = 19
Checking for CN=NTDS
Settings,CN=EX-DC3,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=exchange,DC=datagate,DC=net
in domain CN=Configuration,DC=exchange,DC=datagate,DC=net on 3 servers
Authoritative attribute msDS-hasMasterNCs on EX-DC3 (writeable)
usnLocalChange = 20141
LastOriginatingDsa = EX-DC3
usnOriginatingChange = 20141
timeLastOriginatingChange = 2008-09-23 13:03:39
VersionLastOriginatingChange = 5
Out-of-date attribute msDS-hasMasterNCs on EX-DC1 (writeable)
usnLocalChange = 33428218
LastOriginatingDsa = EX-DC1
usnOriginatingChange = 33428218
timeLastOriginatingChange = 2008-09-23 13:01:38
VersionLastOriginatingChange = 1
Out-of-date attribute msDS-hasMasterNCs on EX-DC2 (writeable)
usnLocalChange = 31531981
LastOriginatingDsa = EX-DC1
usnOriginatingChange = 33428218
timeLastOriginatingChange = 2008-09-23 13:01:38
VersionLastOriginatingChange = 1
......................... EX-DC3 failed test ObjectsReplicated

Starting test: frsevent
* The File Replication Service Event log test
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may
cause
Group Policy problems.
An Warning Event occured. EventID: 0x800034C4
Time Generated: 09/23/2008 16:50:55
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x800034C4
Time Generated: 09/23/2008 16:50:55
(Event String could not be retrieved)
......................... EX-DC3 failed test frsevent


Once again - thanks a lot.


"Paul Bergson [MVP-DS]" wrote:

.

Relevant Pages

  • Re: Upgrading 32-bit AD to 64-bit - FSMO problem
    ... regarding EX-DC3 replication look interesting...anyway, ... Performing downstream analysis. ... These servers can't get changes from home server EX-DC1: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Upgrading 32-bit AD to 64-bit - FSMO problem
    ... Warnings regarding EX-DC3 replication look interesting...anyway, ... Performing downstream analysis. ... Downstream topology is disconnected for ... These servers can't get changes from home server EX-DC1: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Upgrading 32-bit AD to 64-bit - FSMO problem
    ... DC's should NOT be multihomed, this creates lot's of problems, especially with replication. ... Performing downstream analysis. ... These servers can't get changes from home server EX-DC1: ...
    (microsoft.public.windows.server.active_directory)
  • RE: Global Katalog defekt
    ... also im Active Directory ist der Haken bei GC gesetzt. ... Identifying all servers. ... Active Directory LDAP Services Check ... The replication generated an error: ...
    (microsoft.public.de.german.win2000.active_directory)
  • Re: How to stop two servers in different sites trying to replicate with each other
    ... communicate directly with Site C and vice versa. ... ADSS the DC in Site B keeps setting up one of its replication partners to ... ISTG for intersites connections using BH) ... the ISTG won't use the BH servers between Site C and SiteB to ...
    (microsoft.public.win2000.active_directory)