In preparing to transfer DC FSMO roles we have found errors using dcdiag. The target DC fails the Advertising and the netlogons tests. dcdiag /test:DNS shows some errors, too (see the 3rd test output below) but I have been unable to determine the problem.Both machines run DNS.While we do have some "The File Replication Service is having trouble enabling replication from SERVER-DELL.BaileyAndClarke.com to JUSTICE for c:\windows\sysvol\domain using the DNS name SERVER-DELL.BaileyAndClarke.com. FRS will keep retrying" errors, we also have the repadmin /showreps indicating recent replications successful.We have been in a single domain controller Windows 2000 Server domain envirnoment for some time. We now have a Windows 2008 Server on-line as a second domain controller. We want to transfer the FSMO roles to the 2008 machine. Eventually, but not immediately, the 2000 machine will problably be decomissioned as a DC and removed from the network. Prior to replicating the DC on the 2008 machine, we ran adprep, domainprep, and gpprep on the 2000 machine. I have reviewed similar issues posted here but have yet to resolve the problem. Perhaps the output of diagnostics will ring a bell with someone.I will separate different test outputs here with: ====================================================From dcdiag test on the Windows 2008 server: initial dcdiag /v on JUSTICE dcdiag /v Directory Server Diagnosis Performing initial setup: Trying to find home server... * Verifying that the local machine Justice, is a Directory Server. Home Server = Justice * Connecting to directory service on server Justice. * Identified AD Forest. Collecting AD specific global data * Collecting site info. Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=BaileyAndClark e,DC=com,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),....... The previous call succeeded Iterating through the sites Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name ,CN=Sites,CN=Configuration,DC=BaileyAndClarke,DC=com Getting ISTG and options for the site * Identifying all servers. Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=BaileyAndClark e,DC=com,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),....... The previous call succeeded.... The previous call succeeded Iterating through the list of servers Getting information for the server CN=NTDS Settings,CN=SERVER-DELL,CN=Servers ,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BaileyAndClarke,DC=com objectGuid obtained InvocationID obtained dnsHostname obtained site info obtained All the info for the server collected Getting information for the server CN=NTDS Settings,CN=JUSTICE,CN=Servers,CN= Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BaileyAndClarke,DC=com objectGuid obtained InvocationID obtained dnsHostname obtained site info obtained All the info for the server collected * Identifying all NC cross-refs. * Found 2 DC(s). Testing 1 of them. Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\JUSTICE Starting test: Connectivity * Active Directory LDAP Services Check Determining IP4 connectivity Determining IP6 connectivity * Active Directory RPC Services Check ......................... JUSTICE passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\JUSTICE Starting test: Advertising Warning: DsGetDcName returned information for \\SERVER-DELL.BaileyAndClarke.com, when we were trying to reach JUSTICE. SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE. ......................... JUSTICE failed test Advertising Test omitted by user request: CheckSecurityError Test omitted by user request: CutoffServers 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 occurred. EventID: 0x800034FD Time Generated: 02/24/2010 16:33:35 Event String: File Replication Service is initializing the system volume with data from another domain controller. Computer JUSTICE cannot become a domain control ler until this process is complete. The system volume will then be shared as SYS VOL. To check for the SYSVOL share, at the command prompt, type: net share When File Replication Service completes the initialization process, the SYSVOL share will appear. The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of ot her domain controllers, and the replication interval between domain controllers. An Warning Event occurred. EventID: 0x800034C4 Time Generated: 02/24/2010 16:35:38 Event String: The File Replication Service is having trouble enabling replication from SERVER-DELL.BaileyAndClarke.com to JUSTICE for c:\windows\sysvol\domain usi ng the DNS name SERVER-DELL.BaileyAndClarke.com. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name SERVER-DELL.BaileyAn dClarke.com from this computer. [2] FRS is not running on SERVER-DELL.BaileyAndClarke.com. [3] The topology information in the Active Directory Domain Service s for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the p roblem is fixed you will see another event log message indicating that the conne ction has been established. An Warning Event occurred. EventID: 0x800034C4 Time Generated: 02/24/2010 16:43:36 Event String: The File Replication Service is having trouble enabling replication from SERVER-DELL to JUSTICE for c:\windows\sysvol\domain using the DNS name SERV ER-DELL.BaileyAndClarke.com. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name SERVER-DELL.BaileyAn dClarke.com from this computer. [2] FRS is not running on SERVER-DELL.BaileyAndClarke.com. [3] The topology information in the Active Directory Domain Service s for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the p roblem is fixed you will see another event log message indicating that the conne ction has been established. ......................... JUSTICE passed test FrsEvent Starting test: DFSREvent The DFS Replication Event Log. ......................... JUSTICE passed test DFSREvent Starting test: SysVolCheck * The File Replication Service SYSVOL ready test The registry lookup failed to determine the state of the SYSVOL. The error returned was 0x0 "The operation completed successfully.". Check the FRS event log to see if the SYSVOL has successfully been shared. ......................... JUSTICE passed test SysVolCheck Starting test: KccEvent * The KCC Event log test Found no KCC errors in "Directory Service" Event log in the last 15 min utes. ......................... JUSTICE passed test KccEvent Starting test: KnowsOfRoleHolders Role Schema Owner = CN=NTDS Settings,CN=SERVER-DELL,CN=Servers,CN=Defau lt-First-Site-Name,CN=Sites,CN=Configuration,DC=BaileyAndClarke,DC=com Role Domain Owner = CN=NTDS Settings,CN=SERVER-DELL,CN=Servers,CN=Defau lt-First-Site-Name,CN=Sites,CN=Configuration,DC=BaileyAndClarke,DC=com Role PDC Owner = CN=NTDS Settings,CN=SERVER-DELL,CN=Servers,CN=Default- First-Site-Name,CN=Sites,CN=Configuration,DC=BaileyAndClarke,DC=com Role Rid Owner = CN=NTDS Settings,CN=SERVER-DELL,CN=Servers,CN=Default- First-Site-Name,CN=Sites,CN=Configuration,DC=BaileyAndClarke,DC=com Role Infrastructure Update Owner = CN=NTDS Settings,CN=SERVER-DELL,CN=S ervers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BaileyAndClarke,D C=com ......................... JUSTICE passed test KnowsOfRoleHolders Starting test: MachineAccount Checking machine account for DC JUSTICE on DC JUSTICE. * SPN found :LDAP/Justice.BaileyAndClarke.com/BaileyAndClarke.com * SPN found :LDAP/Justice.BaileyAndClarke.com * SPN found :LDAP/JUSTICE * SPN found :LDAP/Justice.BaileyAndClarke.com/BAILEYANDCLARKE * SPN found :LDAP/8bd1a3e6-cc25-4d59-8f9e-36e5b398e35a._msdcs.BaileyAnd Clarke.com * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/8bd1a3e6-cc25-4d59-8f 9e-36e5b398e35a/BaileyAndClarke.com * SPN found :HOST/Justice.BaileyAndClarke.com/BaileyAndClarke.com * SPN found :HOST/Justice.BaileyAndClarke.com * SPN found :HOST/JUSTICE * SPN found :HOST/Justice.BaileyAndClarke.com/BAILEYANDCLARKE * SPN found :GC/Justice.BaileyAndClarke.com/BaileyAndClarke.com ......................... JUSTICE passed test MachineAccount Starting test: NCSecDesc * Security Permissions check for all NC's on DC JUSTICE. The forest is not ready for RODC. Will skip checking ERODC ACEs. * Security Permissions Check for CN=Schema,CN=Configuration,DC=BaileyAndClarke,DC=com (Schema,Version 3) * Security Permissions Check for CN=Configuration,DC=BaileyAndClarke,DC=com (Configuration,Version 3) * Security Permissions Check for DC=BaileyAndClarke,DC=com (Domain,Version 3) ......................... JUSTICE passed test NCSecDesc Starting test: NetLogons * Network Logons Privileges Check Unable to connect to the NETLOGON share! (\\JUSTICE\netlogon) [JUSTICE] An net use or LsaPolicy operation failed with error 67, The network name cannot be found.. ......................... JUSTICE failed test NetLogons Starting test: ObjectsReplicated JUSTICE is in domain DC=BaileyAndClarke,DC=com Checking for CN=JUSTICE,OU=Domain Controllers,DC=BaileyAndClarke,DC=com in domain DC=BaileyAndClarke,DC=com on 1 servers Object is up-to-date on all servers. Checking for CN=NTDS Settings,CN=JUSTICE,CN=Servers,CN=Default-First-Si te-Name,CN=Sites,CN=Configuration,DC=BaileyAndClarke,DC=com in domain CN=Configu ration,DC=BaileyAndClarke,DC=com on 1 servers Object is up-to-date on all servers. ......................... JUSTICE passed test ObjectsReplicated Test omitted by user request: OutboundSecureChannels Starting test: Replications * Replications Check * Replication Latency Check * Replication Site Latency Check ......................... JUSTICE passed test Replications Starting test: RidManager * Available RID Pool for the Domain is 2103 to 1073741823 * SERVER-DELL.BaileyAndClarke.com is the RID Master * DsBind with RID Master was successful * rIDAllocationPool is 1603 to 2102 * rIDPreviousAllocationPool is 1603 to 2102 * rIDNextRID: 1606 ......................... JUSTICE passed test RidManager Starting test: Services * Checking Service: EventSystem * Checking Service: RpcSs * Checking Service: NTDS * Checking Service: DnsCache * Checking Service: NtFrs * Checking Service: IsmServ * Checking Service: kdc * Checking Service: SamSs * Checking Service: LanmanServer * Checking Service: LanmanWorkstation * Checking Service: w32time * Checking Service: NETLOGON ......................... JUSTICE passed test Services Starting test: SystemLog * The System Event log test Found no errors in "System" Event log in the last 60 minutes. ......................... JUSTICE passed test SystemLog Test omitted by user request: Topology Test omitted by user request: VerifyEnterpriseReferences Starting test: VerifyReferences The system object reference (serverReference) CN=JUSTICE,OU=Domain Controllers,DC=BaileyAndClarke,DC=com and backlink on CN=JUSTICE,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configurat ion,DC=BaileyAndClarke,DC=com are correct. The system object reference (serverReferenceBL) CN=JUSTICE,CN=Domain System Volume (SYSVOL share),CN=File Replication S ervice,CN=System,DC=BaileyAndClarke,DC=com and backlink on CN=NTDS Settings,CN=JUSTICE,CN=Servers,CN=Default-First-Site-Name,CN=Si tes,CN=Configuration,DC=BaileyAndClarke,DC=com are correct. ......................... JUSTICE passed test VerifyReferences Test omitted by user request: VerifyReplicas Test omitted by user request: DNS Test omitted by user request: DNS Running partition tests on : Schema Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Running partition tests on : Configuration Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Running partition tests on : BaileyAndClarke Starting test: CheckSDRefDom ......................... BaileyAndClarke passed test CheckSDRefDom Starting test: CrossRefValidation ......................... BaileyAndClarke passed test CrossRefValidation Running enterprise tests on : BaileyAndClarke.com Test omitted by user request: DNS Test omitted by user request: DNS Starting test: LocatorCheck GC Name: \\SERVER-DELL.BaileyAndClarke.com Locator Flags: 0xe00001fd PDC Name: \\SERVER-DELL.BaileyAndClarke.com Locator Flags: 0xe00001fd Time Server Name: \\SERVER-DELL.BaileyAndClarke.com Locator Flags: 0xe00001fd Preferred Time Server Name: \\SERVER-DELL.BaileyAndClarke.com Locator Flags: 0xe00001fd KDC Name: \\SERVER-DELL.BaileyAndClarke.com Locator Flags: 0xe00001fd ......................... BaileyAndClarke.com passed test LocatorCheck Starting test: Intersite Skipping site Default-First-Site-Name, this site is outside the scope provided by the command line arguments provided. ......................... BaileyAndClarke.com passed test Intersite ===========================================repadmin /showreps on the 2008 machine returns the following:C:\Users\Administrator.BAILEYANDCLARKE>repadmin /showrepsDefault-First-Site-Name\JUSTICEDSA Options: IS_GCSite Options: (none)DSA object GUID: 8bd1a3e6-cc25-4d59-8f9e-36e5b398e35aDSA invocationID: f90e772f-b8ed-486c-b6c0-0140c2c46a09 ==== INBOUND NEIGHBORS ====================================== DC=BaileyAndClarke,DC=com Default-First-Site-Name\SERVER-DELL via RPC DSA object GUID: 8d24231f-72a3-4a32-a5bd-d994aa6d942b Last attempt @ 2010-02-26 14:18:52 was successful. CN=Configuration,DC=BaileyAndClarke,DC=com Default-First-Site-Name\SERVER-DELL via RPC DSA object GUID: 8d24231f-72a3-4a32-a5bd-d994aa6d942b Last attempt @ 2010-02-26 14:09:02 was successful. CN=Schema,CN=Configuration,DC=BaileyAndClarke,DC=com Default-First-Site-Name\SERVER-DELL via RPC DSA object GUID: 8d24231f-72a3-4a32-a5bd-d994aa6d942b Last attempt @ 2010-02-26 13:48:08 was successful.===============================the dcdiag /test:dns returns the following: Directory Server Diagnosis Performing initial setup: Trying to find home server... Home Server = Justice * Identified AD Forest. Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\JUSTICE Starting test: Connectivity ......................... JUSTICE passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\JUSTICE Starting test: DNS DNS Tests are running and not hung. Please wait a few minutes... ......................... JUSTICE passed test DNS Running partition tests on : Schema Running partition tests on : Configuration Running partition tests on : BaileyAndClarke Running enterprise tests on : BaileyAndClarke.com Starting test: DNS Test results for domain controllers: DC: Justice.BaileyAndClarke.com Domain: BaileyAndClarke.com TEST: Basic (Basc) Warning: The AAAA record for this DC was not found TEST: Records registration (RReg) Network Adapter [00000006] Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client): Warning: Missing AAAA record at DNS server 192.168.1.107: Justice.BaileyAndClarke.com Warning: Missing AAAA record at DNS server 192.168.1.107: gc._msdcs.BaileyAndClarke.com Warning: Missing AAAA record at DNS server 192.168.1.106: Justice.BaileyAndClarke.com Warning: Missing AAAA record at DNS server 192.168.1.106: gc._msdcs.BaileyAndClarke.com Warning: Missing AAAA record at DNS server 192.168.1.107: Justice.BaileyAndClarke.com Warning: Missing AAAA record at DNS server 192.168.1.107: gc._msdcs.BaileyAndClarke.com Warning: Missing AAAA record at DNS server ::1: Justice.BaileyAndClarke.com Warning: Missing AAAA record at DNS server ::1: gc._msdcs.BaileyAndClarke.com Warning: Record Registrations not found in some network adapters Justice PASS WARN PASS PASS PASS WARN n/a ......................... BaileyAndClarke.com passed test DNS =========================== On the Windows 2000 Sever dcdiag /v reports: Domain Controller Diagnosis Performing initial setup: * Verifying that the local machine SERVER-DELL, is a DC. * Connecting to directory service on server SERVER-DELL. * Collecting site info. * Identifying all servers. * Found 2 DC(s). Testing 1 of them. Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\SERVER-DELL Starting test: Connectivity * Active Directory LDAP Services Check * Active Directory RPC Services Check ......................... SERVER-DELL passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\SERVER-DELL Starting test: Replications * Replications Check ......................... SERVER-DELL passed test Replications Test omitted by user request: Topology Test omitted by user request: CutoffServers Starting test: NCSecDesc * Security Permissions Check for CN=Schema,CN=Configuration,DC=BaileyAndClarke,DC=com * Security Permissions Check for CN=Configuration,DC=BaileyAndClarke,DC=com * Security Permissions Check for DC=BaileyAndClarke,DC=com ......................... SERVER-DELL passed test NCSecDesc Starting test: NetLogons * Network Logons Privileges Check ......................... SERVER-DELL passed test NetLogons Starting test: Advertising The DC SERVER-DELL is advertising itself as a DC and having a DS. The DC SERVER-DELL is advertising as an LDAP server The DC SERVER-DELL is advertising as having a writeable directory The DC SERVER-DELL is advertising as a Key Distribution Center The DC SERVER-DELL is advertising as a time server The DS SERVER-DELL is advertising as a GC. ......................... SERVER-DELL passed test Advertising Starting test: KnowsOfRoleHolders Role Schema Owner = CN=NTDS Settings,CN=SERVER-DELL,CN=Servers,CN=Defau lt-First-Site-Name,CN=Sites,CN=Configuration,DC=BaileyAndClarke,DC=com Role Domain Owner = CN=NTDS Settings,CN=SERVER-DELL,CN=Servers,CN=Defau lt-First-Site-Name,CN=Sites,CN=Configuration,DC=BaileyAndClarke,DC=com Role PDC Owner = CN=NTDS Settings,CN=SERVER-DELL,CN=Servers,CN=Default- First-Site-Name,CN=Sites,CN=Configuration,DC=BaileyAndClarke,DC=com Role Rid Owner = CN=NTDS Settings,CN=SERVER-DELL,CN=Servers,CN=Default- First-Site-Name,CN=Sites,CN=Configuration,DC=BaileyAndClarke,DC=com Role Infrastructure Update Owner = CN=NTDS Settings,CN=SERVER-DELL,CN=S ervers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BaileyAndClarke,D C=com ......................... SERVER-DELL passed test KnowsOfRoleHolders Starting test: RidManager * Available RID Pool for the Domain is 2103 to 1073741823 * SERVER-DELL.BaileyAndClarke.com is the RID Master * DsBind with RID Master was successful * rIDAllocationPool is 1103 to 1602 * rIDNextRID: 1186 * rIDPreviousAllocationPool is 1103 to 1602 ......................... SERVER-DELL passed test RidManager Starting test: MachineAccount * SPN found :LDAP/SERVER-DELL.BaileyAndClarke.com/BaileyAndClarke.com * SPN found :LDAP/SERVER-DELL.BaileyAndClarke.com * SPN found :LDAP/SERVER-DELL * SPN found :LDAP/SERVER-DELL.BaileyAndClarke.com/BAILEYANDCLARKE * SPN found :LDAP/8d24231f-72a3-4a32-a5bd-d994aa6d942b._msdcs.BaileyAnd Clarke.com * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/8d24231f-72a3-4a32-a5 bd-d994aa6d942b/BaileyAndClarke.com * SPN found :HOST/SERVER-DELL.BaileyAndClarke.com/BaileyAndClarke.com * SPN found :HOST/SERVER-DELL.BaileyAndClarke.com * SPN found :HOST/SERVER-DELL * SPN found :HOST/SERVER-DELL.BaileyAndClarke.com/BAILEYANDCLARKE * SPN found :GC/SERVER-DELL.BaileyAndClarke.com/BaileyAndClarke.com ......................... SERVER-DELL passed test MachineAccount Starting test: Services * Checking Service: Dnscache * Checking Service: NtFrs * Checking Service: IsmServ * Checking Service: kdc * Checking Service: SamSs * Checking Service: LanmanServer * Checking Service: LanmanWorkstation * Checking Service: RpcSs * Checking Service: RPCLOCATOR * Checking Service: w32time * Checking Service: TrkWks * Checking Service: TrkSvr * Checking Service: NETLOGON * Checking Service: Dnscache * Checking Service: NtFrs SMTPSVC Service is stopped on [SERVER-DELL] ......................... SERVER-DELL failed test Services Test omitted by user request: OutboundSecureChannels Starting test: ObjectsReplicated SERVER-DELL is in domain DC=BaileyAndClarke,DC=com Checking for CN=SERVER-DELL,OU=Domain Controllers,DC=BaileyAndClarke,DC =com in domain DC=BaileyAndClarke,DC=com on 1 servers Object is up-to-date on all servers. Checking for CN=NTDS Settings,CN=SERVER-DELL,CN=Servers,CN=Default-Firs t-Site-Name,CN=Sites,CN=Configuration,DC=BaileyAndClarke,DC=com in domain CN=Con figuration,DC=BaileyAndClarke,DC=com on 1 servers Object is up-to-date on all servers. ......................... SERVER-DELL passed test ObjectsReplicated Starting test: frssysvol * The File Replication Service Event log test Error: No record of File Replication System, SYSVOL started. The Active Directory may be prevented from starting. ......................... SERVER-DELL passed test frssysvol Starting test: kccevent * The KCC Event log test Found no KCC errors in Directory Service Event log in the last 15 minut es. ......................... SERVER-DELL passed test kccevent Starting test: systemlog * The System Event log test Found no errors in System Event log in the last 60 minutes. ......................... SERVER-DELL passed test systemlog Running enterprise tests on : BaileyAndClarke.com Starting test: Intersite Skipping site Default-First-Site-Name, this site is outside the scope provided by the command line arguments provided. ......................... BaileyAndClarke.com passed test Intersite Starting test: FsmoCheck GC Name: \\SERVER-DELL.BaileyAndClarke.com Locator Flags: 0xe00001fd PDC Name: \\SERVER-DELL.BaileyAndClarke.com Locator Flags: 0xe00001fd Time Server Name: \\SERVER-DELL.BaileyAndClarke.com Locator Flags: 0xe00001fd Preferred Time Server Name: \\SERVER-DELL.BaileyAndClarke.com Locator Flags: 0xe00001fd KDC Name: \\SERVER-DELL.BaileyAndClarke.com Locator Flags: 0xe00001fd ......................... BaileyAndClarke.com passed test FsmoCheck ====================================And the netdiag /v /test:dns on the 2000 server reports: Gathering IPX configuration information. Querying status of the Netcard drivers... Passed Testing Domain membership... Passed Gathering NetBT configuration information. Testing DNS The DNS registration for SERVER-DELL.BaileyAndClarke.com is correct on all DNS servers PASS - All the DNS entries for DC are registered on DNS server '192.168.1.106' and other DCs also have some of the names registered. Tests complete. Computer Name: SERVER-DELL DNS Host Name: SERVER-DELL.BaileyAndClarke.com DNS Domain Name: BaileyAndClarke.com System info : Windows 2000 Server (Build 2195) Processor : x86 Family 15 Model 2 Stepping 7, GenuineIntel Hotfixes : Installed? Name Yes KB819696 Yes KB822343 Yes KB823182 Yes KB823559 Yes KB823980 Yes KB824105 Yes KB824141 Yes KB824146 Yes KB824151 Yes KB825119 Yes KB826232 Yes KB828028 Yes KB828035 Yes KB828741 Yes KB828749 Yes KB832353 Yes KB832359 Yes KB834707-IE6SP1-20040929.091901 Yes KB835732 Yes KB837001 Yes KB839643 Yes KB839645 Yes KB840315 Yes KB840987 Yes KB841356 Yes KB841533 Yes KB841872 Yes KB841873 Yes KB842526 Yes KB842773 Yes KB867282-IE6SP1-20050127.163319 Yes KB871250 Yes KB873333 Yes KB873339 Yes KB883939-IE6SP1-20050428.125228 Yes KB885250 Yes KB885834 Yes KB885835 Yes KB885836 Yes KB888113 Yes KB889293-IE6SP1-20041111.235619 Yes KB890046 Yes KB890047 Yes KB890175 Yes KB890859 Yes KB890923-IE6SP1-20050225.103456 Yes KB891711 Yes KB891781 Yes KB893066 Yes KB893086 Yes KB893756 Yes KB893803 Yes KB893803v2 Yes KB894320 Yes KB896358 Yes KB896422 Yes KB896423 Yes KB896424 Yes KB896688-IE6SP1-20051004.130236 Yes KB896727-IE6SP1-20050719.165959 Yes KB897715-OE6SP1-20050503.210336 Yes KB899587 Yes KB899588 Yes KB899589 Yes KB899591 Yes KB900725 Yes KB901017 Yes KB901214 Yes KB902400 Yes KB904368 Yes KB904706 Yes KB905414 Yes KB905495-IE6SP1-20050805.184113 Yes KB905749 Yes KB905915-IE6SP1-20051122.175908 Yes KB908519 Yes KB908523 Yes KB908531 Yes KB911280 Yes KB911564 Yes KB911567-OE6SP1-20060316.165634 Yes KB912812-IE6SP1-20060322.182418 Yes KB912919 Yes KB913580 Yes KB914388 Yes KB914389 Yes KB916281-IE6SP1-20060526.162249 Yes KB917008 Yes KB917159 Yes KB917422 Yes KB917537 Yes KB917736 Yes KB917953 Yes KB918118 Yes KB918899-IE6SP1-20060725.123917 Yes KB920213 Yes KB920670 Yes KB920683 Yes KB920685 Yes KB920958 Yes KB921398 Yes KB921503 Yes KB921883 Yes KB922582 Yes KB922616 Yes KB923191 Yes KB923414 Yes KB923561 Yes KB923694-OE6SP1-20061106.120000 Yes KB923810 Yes KB923980 Yes KB924191 Yes KB924270 Yes KB924667 Yes KB925398_WMP64 Yes KB925454-IE6SP1-20061116.120000 Yes KB925486-IE6SP1-20060918.120000 Yes KB925902 Yes KB926122 Yes KB926436 Yes KB927891 Yes KB928090-IE6SP1-20070125.120000 Yes KB928843 Yes KB929969-IE6SP1-20061220.120000 Yes KB930178 Yes KB931768-IE6SP1-20070219.120000 Yes KB931784 Yes KB932168 Yes KB933566-IE6SP1-20070417.120000 Yes KB933729 Yes KB935839 Yes KB935840 Yes KB935966 Yes KB936021 Yes KB937143-IE6SP1-20070717.120000 Yes KB937894 Yes KB938127-IE6SP1-20070626.120000 Yes KB938464-IE6SP1-20080429.120000 Yes KB938827 Yes KB938829 Yes KB939653-IE6SP1-20070817.120000 Yes KB941202-OE6SP1-20070820.120000 Yes KB941568 Yes KB941644 Yes KB941672 Yes KB941693 Yes KB942615-IE6SP1-20071029.120000 Yes KB942831 Yes KB943055 Yes KB943484 Yes KB943485 Yes KB944338 Yes KB944533-IE6SP1-20071210.120000 Yes KB945553 Yes KB947864-IE6SP1-20080215.120000 Yes KB948590 Yes KB948881-IE6SP1-20080313.120000 Yes KB949014 Yes KB950749 Yes KB950759-IE6SP1-20080418.120000 Yes KB950760 Yes KB950974 Yes KB951066-OE6SP1-20080625.120000 Yes KB951698 Yes KB951746 Yes KB951748 Yes KB951748-V2 Yes KB952004 Yes KB952954 Yes KB953155 Yes KB953838-IE6SP1-20080620.120000 Yes KB953839 Yes KB954211 Yes KB954600_WM41 Yes KB955069 Yes KB955759 Yes KB956390-IE6SP1-20080820.120000 Yes KB956391 Yes KB956802 Yes KB956844 Yes KB957095 Yes KB957097 Yes KB957280 Yes KB958215-IE6SP1-20081016.120000 Yes KB958470 Yes KB958644 Yes KB958687 Yes KB958690 Yes KB958869-IE6SP1-20090818.120000 Yes KB959426 Yes KB960225 Yes KB960714-IE6SP1-20081211.120000 Yes KB960715 Yes KB960803 Yes KB960859 Yes KB961063 Yes KB961371 Yes KB961371-V2 Yes KB961501 Yes KB963027-IE6SP1-20090303.120000 Yes KB967715 Yes KB968537 Yes KB969059 Yes KB969805 Yes KB969897-IE6SP1-20090501.120000 Yes KB969898 Yes KB969947 Yes KB970238 Yes KB970483 Yes KB971468 Yes KB971486 Yes KB971557 Yes KB971633 Yes KB971961 Yes KB972260-IE6SP1-20090722.120000 Yes KB972270 Yes KB973037 Yes KB973346 Yes KB973354-OE6SP1-20090710.120000 Yes KB973507 Yes KB973525 Yes KB973869 Yes KB973904 Yes KB974112_WM41 Yes KB974318 Yes KB974392 Yes KB974455-IE6SP1-20090925.120000 Yes KB974571 Yes KB974783 Yes KB975560 Yes KB976138 Yes KB976325-IE6SP1-20091027.120000 Yes KB977165 Yes KB977290 Yes KB977914 Yes KB978037 Yes KB978207-IE6SP1-20091216.120000 Yes KB978251 Yes KB978262 Yes KB978706 Yes Q147222 Yes Q329115 Yes Q816093 No ServicePackUninstall Yes Update Rollup 1 Netcard queries test . . . . . . . : Passed Information of Netcard drivers: --------------------------------------------------------------------------- Description: Intel(R) 82540EM Based Network Connection Device: \DEVICE\{A9EFB40E-7B17-4C7C-9E9C-E2487CF22AC2} Media State: Connected Device State: Connected Connect Time: 1 days, 20:40:57 Media Speed: 100 Mbps Packets Sent: 820992 Bytes Sent (Optional): 0 Packets Received: 1280641 Directed Pkts Recd (Optional): 1280641 Bytes Received (Optional): 0 Directed Bytes Recd (Optional): 0 --------------------------------------------------------------------------- [PASS] - At least one netcard is in the 'Connected' state. Per interface results: Adapter : Local Area Connection Adapter ID . . . . . . . . : {A9EFB40E-7B17-4C7C-9E9C-E2487CF22AC2} Netcard queries test . . . : Passed Global results: Domain membership test . . . . . . : Passed Machine is a . . . . . . . . . : Primary Domain Controller Emulator Netbios Domain name. . . . . . : BAILEYANDCLARKE Dns domain name. . . . . . . . : BaileyAndClarke.com Dns forest name. . . . . . . . : BaileyAndClarke.com Domain Guid. . . . . . . . . . : {0F20F954-A4B2-483E-B50A-C7EC52D71238} Domain Sid . . . . . . . . . . : S-1-5-21-789336058-1284227242-725345543 Logon User . . . . . . . . . . : Administrator Logon Domain . . . . . . . . . : BAILEYANDCLARKE NetBT transports test. . . . . . . : Passed List of NetBt transports currently configured: NetBT_Tcpip_{A9EFB40E-7B17-4C7C-9E9C-E2487CF22AC2} 1 NetBt transport currently configured. DNS test . . . . . . . . . . . . . : Passed Interface {A9EFB40E-7B17-4C7C-9E9C-E2487CF22AC2} DNS Domain: DNS Servers: 192.168.1.106 IP Address: 192.168.1.106 Expected registration with PDN (primary DNS domain name): Hostname: SERVER-DELL.BaileyAndClarke.com. Authoritative zone: BaileyAndClarke.com. Primary DNS server: SERVER-DELL.BaileyAndClarke.com 192.168.1.106 Authoritative NS:192.168.1.107 192.168.1.106 Verify DNS registration: Name: SERVER-DELL.BaileyAndClarke.com Expected IP: 192.168.1.106 Server 192.168.1.107: NO_ERROR Server 192.168.1.106: NO_ERROR The DNS registration for SERVER-DELL.BaileyAndClarke.com is correct on all DNS servers Check the DNS registration for DCs entries on DNS server '192.168.1.106' The Record is different on DNS server '192.168.1.106'. DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain. Your DC entry is one of them on DNS server '192.168.1.106', no need to re-register. +------------------------------------------------------+ The record on your DC is: DNS NAME = BaileyAndClarke.com. DNS DATA = A 192.168.1.106 The record on DNS server 192.168.1.106 is: DNS NAME = BaileyAndClarke.com DNS DATA = A 192.168.1.106 A 192.168.1.107 +------------------------------------------------------+ The Record is different on DNS server '192.168.1.106'. DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain. Your DC entry is one of them on DNS server '192.168.1.106', no need to re-register. +------------------------------------------------------+ The record on your DC is: DNS NAME = _kerberos._tcp.dc._msdcs.BaileyAndClarke.com. DNS DATA = SRV 0 100 88 SERVER-DELL.BaileyAndClarke.com. The record on DNS server 192.168.1.106 is: DNS NAME = _kerberos._tcp.dc._msdcs.BaileyAndClarke.com DNS DATA = SRV 0 100 88 justice.baileyandclarke.com SRV 0 100 88 server-dell.baileyandclarke.com +------------------------------------------------------+ The Record is different on DNS server '192.168.1.106'. DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain. Your DC entry is one of them on DNS server '192.168.1.106', no need to re-register. +------------------------------------------------------+ The record on your DC is: DNS NAME = _ldap._tcp.BaileyAndClarke.com. DNS DATA = SRV 0 100 389 SERVER-DELL.BaileyAndClarke.com. The record on DNS server 192.168.1.106 is: DNS NAME = _ldap._tcp.BaileyAndClarke.com DNS DATA = SRV 0 100 389 justice.baileyandclarke.com SRV 0 100 389 server-dell.baileyandclarke.com +------------------------------------------------------+ The Record is different on DNS server '192.168.1.106'. DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain. Your DC entry is one of them on DNS server '192.168.1.106', no need to re-register. +------------------------------------------------------+ The record on your DC is: DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.BaileyAndClarke.com. DNS DATA = SRV 0 100 389 SERVER-DELL.BaileyAndClarke.com. The record on DNS server 192.168.1.106 is: DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.BaileyAndClarke.com DNS DATA = SRV 0 100 389 justice.baileyandclarke.com SRV 0 100 389 server-dell.baileyandclarke.com +------------------------------------------------------+ The Record is correct on DNS server '192.168.1.106'. The Record is different on DNS server '192.168.1.106'. DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain. Your DC entry is one of them on DNS server '192.168.1.106', no need to re-register. +------------------------------------------------------+ The record on your DC is: DNS NAME = _ldap._tcp.gc._msdcs.BaileyAndClarke.com. DNS DATA = SRV 0 100 3268 SERVER-DELL.BaileyAndClarke.com. The record on DNS server 192.168.1.106 is: DNS NAME = _ldap._tcp.gc._msdcs.BaileyAndClarke.com DNS DATA = SRV 0 100 3268 justice.baileyandclarke.com SRV 0 100 3268 server-dell.baileyandclarke.com +------------------------------------------------------+ The Record is different on DNS server '192.168.1.106'. DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain. Your DC entry is one of them on DNS server '192.168.1.106', no need to re-register. +------------------------------------------------------+ The record on your DC is: DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.BaileyAndClarke.com. DNS DATA = SRV 0 100 3268 SERVER-DELL.BaileyAndClarke.com. The record on DNS server 192.168.1.106 is: DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.BaileyAndClarke.com DNS DATA = SRV 0 100 3268 justice.baileyandclarke.com SRV 0 100 3268 server-dell.baileyandclarke.com +------------------------------------------------------+ The Record is different on DNS server '192.168.1.106'. DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain. Your DC entry is one of them on DNS server '192.168.1.106', no need to re-register. +------------------------------------------------------+ The record on your DC is: DNS NAME = _ldap._tcp.0f20f954-a4b2-483e-b50a-c7ec52d71238.domains._msdcs.BaileyAndClarke.com. DNS DATA = SRV 0 100 389 SERVER-DELL.BaileyAndClarke.com. The record on DNS server 192.168.1.106 is: DNS NAME = _ldap._tcp.0f20f954-a4b2-483e-b50a-c7ec52d71238.domains._msdcs.BaileyAndClarke.com DNS DATA = SRV 0 100 389 justice.baileyandclarke.com SRV 0 100 389 server-dell.baileyandclarke.com +------------------------------------------------------+ The Record is different on DNS server '192.168.1.106'. DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain. Your DC entry is one of them on DNS server '192.168.1.106', no need to re-register. +------------------------------------------------------+ The record on your DC is: DNS NAME = _gc._tcp.BaileyAndClarke.com. DNS DATA = SRV 0 100 3268 SERVER-DELL.BaileyAndClarke.com. The record on DNS server 192.168.1.106 is: DNS NAME = _gc._tcp.BaileyAndClarke.com DNS DATA = SRV 0 100 3268 justice.baileyandclarke.com SRV 0 100 3268 server-dell.baileyandclarke.com +------------------------------------------------------+ The Record is different on DNS server '192.168.1.106'. DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain. Your DC entry is one of them on DNS server '192.168.1.106', no need to re-register. +------------------------------------------------------+ The record on your DC is: DNS NAME = _gc._tcp.Default-First-Site-Name._sites.BaileyAndClarke.com. DNS DATA = SRV 0 100 3268 SERVER-DELL.BaileyAndClarke.com. The record on DNS server 192.168.1.106 is: DNS NAME = _gc._tcp.Default-First-Site-Name._sites.BaileyAndClarke.com DNS DATA = SRV 0 100 3268 justice.baileyandclarke.com SRV 0 100 3268 server-dell.baileyandclarke.com +------------------------------------------------------+ The Record is different on DNS server '192.168.1.106'. DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain. Your DC entry is one of them on DNS server '192.168.1.106', no need to re-register. +------------------------------------------------------+ The record on your DC is: DNS NAME = _kerberos._udp.BaileyAndClarke.com. DNS DATA = SRV 0 100 88 SERVER-DELL.BaileyAndClarke.com. The record on DNS server 192.168.1.106 is: DNS NAME = _kerberos._udp.BaileyAndClarke.com DNS DATA = SRV 0 100 88 justice.baileyandclarke.com SRV 0 100 88 server-dell.baileyandclarke.com +------------------------------------------------------+ The Record is different on DNS server '192.168.1.106'. DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain. Your DC entry is one of them on DNS server '192.168.1.106', no need to re-register. +------------------------------------------------------+ The record on your DC is: DNS NAME = _kpasswd._tcp.BaileyAndClarke.com. DNS DATA = SRV 0 100 464 SERVER-DELL.BaileyAndClarke.com. The record on DNS server 192.168.1.106 is: DNS NAME = _kpasswd._tcp.BaileyAndClarke.com DNS DATA = SRV 0 100 464 justice.baileyandclarke.com SRV 0 100 464 server-dell.baileyandclarke.com +------------------------------------------------------+ The Record is different on DNS server '192.168.1.106'. DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain. Your DC entry is one of them on DNS server '192.168.1.106', no need to re-register. +------------------------------------------------------+ The record on your DC is: DNS NAME = _kpasswd._udp.BaileyAndClarke.com. DNS DATA = SRV 0 100 464 SERVER-DELL.BaileyAndClarke.com. The record on DNS server 192.168.1.106 is: DNS NAME = _kpasswd._udp.BaileyAndClarke.com DNS DATA = SRV 0 100 464 justice.baileyandclarke.com SRV 0 100 464 server-dell.baileyandclarke.com +------------------------------------------------------+ The Record is different on DNS server '192.168.1.106'. DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain. Your DC entry is one of them on DNS server '192.168.1.106', no need to re-register. +------------------------------------------------------+ The record on your DC is: DNS NAME = gc._msdcs.BaileyAndClarke.com. DNS DATA = A 192.168.1.106 The record on DNS server 192.168.1.106 is: DNS NAME = gc._msdcs.BaileyAndClarke.com DNS DATA = A 192.168.1.106 A 192.168.1.107 +------------------------------------------------------+ The Record is correct on DNS server '192.168.1.106'. The Record is different on DNS server '192.168.1.106'. DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain. Your DC entry is one of them on DNS server '192.168.1.106', no need to re-register. +------------------------------------------------------+ The record on your DC is: DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.BaileyAndClarke.com. DNS DATA = SRV 0 100 88 SERVER-DELL.BaileyAndClarke.com. The record on DNS server 192.168.1.106 is: DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.BaileyAndClarke.com DNS DATA = SRV 0 100 88 justice.baileyandclarke.com SRV 0 100 88 server-dell.baileyandclarke.com +------------------------------------------------------+ The Record is different on DNS server '192.168.1.106'. DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain. Your DC entry is one of them on DNS server '192.168.1.106', no need to re-register. +------------------------------------------------------+ The record on your DC is: DNS NAME = _ldap._tcp.dc._msdcs.BaileyAndClarke.com. DNS DATA = SRV 0 100 389 SERVER-DELL.BaileyAndClarke.com. The record on DNS server 192.168.1.106 is: DNS NAME = _ldap._tcp.dc._msdcs.BaileyAndClarke.com DNS DATA = SRV 0 100 389 justice.baileyandclarke.com SRV 0 100 389 server-dell.baileyandclarke.com +------------------------------------------------------+ The Record is different on DNS server '192.168.1.106'. DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain. Your DC entry is one of them on DNS server '192.168.1.106', no need to re-register. +------------------------------------------------------+ The record on your DC is: DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.BaileyAndClarke.com. DNS DATA = SRV 0 100 389 SERVER-DELL.BaileyAndClarke.com. The record on DNS server 192.168.1.106 is: DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.BaileyAndClarke.com DNS DATA = SRV 0 100 389 justice.baileyandclarke.com SRV 0 100 389 server-dell.baileyandclarke.com +------------------------------------------------------+ The Record is different on DNS server '192.168.1.106'. DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain. Your DC entry is one of them on DNS server '192.168.1.106', no need to re-register. +------------------------------------------------------+ The record on your DC is: DNS NAME = _kerberos._tcp.BaileyAndClarke.com. DNS DATA = SRV 0 100 88 SERVER-DELL.BaileyAndClarke.com. The record on DNS server 192.168.1.106 is: DNS NAME = _kerberos._tcp.BaileyAndClarke.com DNS DATA = SRV 0 100 88 justice.baileyandclarke.com SRV 0 100 88 server-dell.baileyandclarke.com +------------------------------------------------------+ The Record is different on DNS server '192.168.1.106'. DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain. Your DC entry is one of them on DNS server '192.168.1.106', no need to re-register. +------------------------------------------------------+ The record on your DC is: DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.BaileyAndClarke.com. DNS DATA = SRV 0 100 88 SERVER-DELL.BaileyAndClarke.com. The record on DNS server 192.168.1.106 is: DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.BaileyAndClarke.com DNS DATA = SRV 0 100 88 justice.baileyandclarke.com SRV 0 100 88 server-dell.baileyandclarke.com +------------------------------------------------------+ PASS - All the DNS entries for DC are registered on DNS server '192.168.1.106' and other DCs also have some of the names registered. The command completed successfully ============================Although my interpretation must be wrong, seems to me DC replication has worked ok, and the 2000 machine seems to think the DNS is ok. Sorry about all the logs, but I figure if anyone cares to consider this issue they'd want to see these anyway, so might as well provide them up front.Thanks.Ken

Hello,please post an unedited ipconfig /all from both DCs. Also check with net share on the Windows server 2008 that sysvol and netlogon share exists and that you can access them both and see the content.Also if you don't use IPv6 on the Windows server 2008 DC you should think about disbling it complete according to:http://blogs.dirteam.com/blogs/paulbergson/archive/2009/03/19/disabling-ipv6-on-windows-2008.aspxBest regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.

Thank you for your response.I had checked the netlogon service but apparently I had not checked the share itself, and I find it missing on the 2008 server. So I am proceeding with the recommendations in KBKB947022. Due to my limited time today and the production environment, a reboot won't occur until sometime Tuesday. Since that share is missing, creating it may resolve lots/all the problems in this regard. I'll go ahead and post the ipconfig info below but wait to see what the status is after creating the netlogon share before addressing the IPv6 suggestons.Thanks again.==========ipconfig from the Windows 2008 Server: Windows IP Configuration Host Name . . . . . . . . . . . . : Justice Primary Dns Suffix . . . . . . . : BaileyAndClarke.com Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : BaileyAndClarke.com Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) Physical Address. . . . . . . . . : 00-26-B9-47-D7-56 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::60bc:21e1:e898:9468%11(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.1.107(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DHCPv6 IAID . . . . . . . . . . . : 234890937 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-D9-EA-D9-00-26-B9-47-D7-56 DNS Servers . . . . . . . . . . . : ::1 192.168.1.107 192.168.1.106 127.0.0.1 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter Local Area Connection* 8: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{98C4E6BD-0C92-4A73-A03B-795305C64B18} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 9: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 02-00-54-55-4E-01 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e74:10b4:5e87:b46e:9686(Preferred) Link-local IPv6 Address . . . . . : fe80::10b4:5e87:b46e:9686%10(Preferred) Default Gateway . . . . . . . . . : :: NetBIOS over Tcpip. . . . . . . . : Disabled ==============ipconfig from the Windows 2000 Server:Windows 2000 IP Configuration Host Name . . . . . . . . . . . . : SERVER-DELL Primary DNS Suffix . . . . . . . : BaileyAndClarke.com Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : baileyandbenfield.com baileyandclarke.com Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) 82540EM Based Network Connection Physical Address. . . . . . . . . : 00-C0-9F-20-92-B4 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.1.106 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.106

Having found the netlogon share not on the Windows 2008 server, I followed the procedure in KB947022 to modify a registry value and then modify it back. However, that did not create the share. The 2008 machine system event log shows: ------The Netlogon service could not create server share C:\Windows\SYSVOL\sysvol\BaileyAndClarke.com\SCRIPTS. The following error occurred: The system cannot find the file specified.------Anything catch anyone's attention on the ipconfig information or anything else at this point?I started working on dsiabling IPv6 per paul bergson's blog, but stopped when I ran across the registry addition ofHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6Parameters\DisabledComponents DWORD => FFFFFFFFbecause I had a hard time believing that shouldn't be HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents DWORD => FFFFFFFF(Parameters being a new subkey to the existing tcpip6 key rather than a new tepip6paramaters key.) Do you happen to know if my caution and assumtion is unwarranted?Thanks.