"Big Chris" wrote:

> I have a DC/GC that does not have the Netlogon and Sysvol Shares. I attempted
> to demote it and repromote the server without success. I ran a DCDIAG and
> received the following:
>          [OSMDC3\\] An net use or LsaPolicy operation failed with error
> 1203, No
>  network provider accepted the given network path..
>          ......................... OSMDC3\\ failed test NetLogons
>       Starting test: Advertising
>          Warning: DsGetDcName returned information for
> \\OSSDC1.IAP.OSIENT.COM,
> when we were trying to reach OSMDC3\\.
>          Server is not responding or is not considered suitable.
>          ......................... OSMDC3\\ failed test Advertising
>       Starting test: KnowsOfRoleHolders
>          [OSIENTDC1] DsBindWithSpnEx() failed with error 1722,
>          The RPC server is unavailable..
>          Warning: OSIENTDC1 is the Schema Owner, but is not responding to DS
> RPC
>  Bind.
>          [OSIENTDC1] LDAP search failed with error 58,
>          The specified server cannot perform the requested operation..
>          Warning: OSIENTDC1 is the Schema Owner, but is not responding to
> LDAP B
> ind.
>          Warning: OSIENTDC1 is the Domain Owner, but is not responding to DS
> RPC
>  Bind.
>          Warning: OSIENTDC1 is the Domain Owner, but is not responding to
> LDAP B
> ind.
>          ......................... OSMDC3\\ failed test KnowsOfRoleHolders
>       Starting test: RidManager
>          Failed with 8481: The search failed to retrieve attributes from the
> dat
> abase.
>          Could not get Rid set Reference :failed with 8481: The search
> failed to
>  retrieve attributes from the database.
>          ......................... OSMDC3\\ failed test RidManager
>       Starting test: MachineAccount
>          ***Error: The server OSMDC3\\ is missing its machine account.  Try
>          running with the /repairmachineaccount option.
>          * The current DC is not in the domain controller's OU
>          Could not open pipe with [OSMDC3\\]:failed with 1203: No network
> provid
> er accepted the given network path.
>          Could not get NetBIOSDomainName
>          Failed can not test for HOST SPN
>          Failed can not test for HOST SPN
>          * Missing SPN :LDAP/OSMDC3\\
>          * Missing SPN :(null)
>          * Missing SPN :HOST/OSMDC3\\
>          * Missing SPN :(null)
>          ......................... OSMDC3\\ failed test MachineAccount
>       Starting test: Services
>          Could not open Remote ipc to [OSMDC3\\]:failed with 1203: No
> network pr
> ovider accepted the given network path.
>          ......................... OSMDC3\\ failed test Services
>       Starting test: ObjectsReplicated
>          ......................... OSMDC3\\ passed test ObjectsReplicated
>       Starting test: frssysvol
>          [OSMDC3\\] An net use or LsaPolicy operation failed with error
> 1203, No
>  network provider accepted the given network path..
>          ......................... OSMDC3\\ failed test frssysvol
>       Starting test: frsevent
>          ......................... OSMDC3\\ failed test frsevent
>       Starting test: kccevent
>          Failed to enumerate event log records, error No network provider
> accept
> ed the given network path.
>          ......................... OSMDC3\\ failed test kccevent
>       Starting test: systemlog
>          Failed to enumerate event log records, error No network provider
> accept
> ed the given network path.
>          ......................... OSMDC3\\ failed test systemlog
>
> I'm also getting the following errors:
>
> Event Type:    Error
> Event Source:    Userenv
> Event Category:    None
> Event ID:    1054
> Date:        2/7/2006
> Time:        12:25:26 AM
> User:        NT AUTHORITY\SYSTEM
> Computer:    OSMDC3
> Description:
> Windows cannot obtain the domain controller name for your computer network.
> (An unexpected network error occurred. ). Group Policy processing aborted.
>
> Event Type:    Warning
> Event Source:    NtFrs
> Event Category:    None
> Event ID:    13508
> Date:        2/6/2006
> Time:        8:16:48 AM
> User:        N/A
> Computer:    OSMDC3
> Description:
> The File Replication Service is having trouble enabling replication from
> OSIIDC1 to OSMDC3 for e:\windows\sysvol\domain using the DNS name
> osiidc1.IAP.OSIENT.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 osiidc1.IAP.OSIENT.COM from
> this computer.
>  [2] FRS is not running on osiidc1.IAP.OSIENT.COM.
>  [3] The topology information in the Active Directory for this replica has
> not yet replicated to all the Domain Controllers.
> 
> What are some steps that I can take to enable replication before this site
> is tombstoned?
>

"Adriana Viola" wrote:

> Hi Chris,
>
> 1) First of all I would like to advise you to check if your DNS Server is
> running properly. Usually 50% of the problems regarding replication between
> DCs are imputable to DNS server problems. Seeing your log, it seems that this
> server is not able to connect or get information from it:
>
> -- How many DCs do you have in this network?
> -- Which one is the DNS Server?
> -- Did you configure the DNS Server client properly? It means, the DNS
> Server client in this DC is pointing to the DNS Server? In case for itself,
> please use the ip address 127.0.0.1.
> -- Did you check with the nslookup if you can contact the DNS Server and if
> it is responding properly?
> -- Sometimes, when the DNS Server is not responding/resolving or it is not
> running properly, it’s necessary to reinstall the DNS Server again, instead
> to try to troubleshoot it.
>
> Please find out more information in this article:
> http://support.microsoft.com/kb/814591/en-us
> http://support.microsoft.com/kb/198437/en-us
>
> 2) For your replication, you should be aware that you will be needing two
> mainly things for it: FRS and the folder sysvol. FRS is the service that is
> on charge to transfer the information between the servers (speaking in a easy
> way). Sysvol is a share folder that contains all the information necessary to
> maintain the DCs connected in this network updated.
>
> Please find out in the following article all the steps that you need to
> check if your sysvol is working fine, and just in case, you can use it when
> you need to rebuild it again:
> http://support.microsoft.com/kb/315457/en-us
>
> 3) Force a replication to see if it’s working now:
> http://support.microsoft.com/kb/198437/en-us#XSLTH3124121122120121120120
> Then check with repadmin or other tool to check if the replication is working:
> http://support.microsoft.com/kb/229896/en-us
>
> 4) If it’s still not working you can use this document to help you to
> troubleshoot the replication:
> http://support.microsoft.com/kb/327341/en-us
>
> If you need more help, feel free to ask.
>
> Regards,
>
> Adriana
>
> "Big Chris" wrote:
>
> > I have a DC/GC that does not have the Netlogon and Sysvol Shares. I attempted
> > to demote it and repromote the server without success. I ran a DCDIAG and
> > received the following:
> >          [OSMDC3\\] An net use or LsaPolicy operation failed with error
> > 1203, No
> >  network provider accepted the given network path..
> >          ......................... OSMDC3\\ failed test NetLogons
> >       Starting test: Advertising
> >          Warning: DsGetDcName returned information for
> > \\OSSDC1.IAP.OSIENT.COM,
> > when we were trying to reach OSMDC3\\.
> >          Server is not responding or is not considered suitable.
> >          ......................... OSMDC3\\ failed test Advertising
> >       Starting test: KnowsOfRoleHolders
> >          [OSIENTDC1] DsBindWithSpnEx() failed with error 1722,
> >          The RPC server is unavailable..
> >          Warning: OSIENTDC1 is the Schema Owner, but is not responding to DS
> > RPC
> >  Bind.
> >          [OSIENTDC1] LDAP search failed with error 58,
> >          The specified server cannot perform the requested operation..
> >          Warning: OSIENTDC1 is the Schema Owner, but is not responding to
> > LDAP B
> > ind.
> >          Warning: OSIENTDC1 is the Domain Owner, but is not responding to DS
> > RPC
> >  Bind.
> >          Warning: OSIENTDC1 is the Domain Owner, but is not responding to
> > LDAP B
> > ind.
> >          ......................... OSMDC3\\ failed test KnowsOfRoleHolders
> >       Starting test: RidManager
> >          Failed with 8481: The search failed to retrieve attributes from the
> > dat
> > abase.
> >          Could not get Rid set Reference :failed with 8481: The search
> > failed to
> >  retrieve attributes from the database.
> >          ......................... OSMDC3\\ failed test RidManager
> >       Starting test: MachineAccount
> >          ***Error: The server OSMDC3\\ is missing its machine account.  Try
> >          running with the /repairmachineaccount option.
> >          * The current DC is not in the domain controller's OU
> >          Could not open pipe with [OSMDC3\\]:failed with 1203: No network
> > provid
> > er accepted the given network path.
> >          Could not get NetBIOSDomainName
> >          Failed can not test for HOST SPN
> >          Failed can not test for HOST SPN
> >          * Missing SPN :LDAP/OSMDC3\\
> >          * Missing SPN :(null)
> >          * Missing SPN :HOST/OSMDC3\\
> >          * Missing SPN :(null)
> >          ......................... OSMDC3\\ failed test MachineAccount
> >       Starting test: Services
> >          Could not open Remote ipc to [OSMDC3\\]:failed with 1203: No
> > network pr
> > ovider accepted the given network path.
> >          ......................... OSMDC3\\ failed test Services
> >       Starting test: ObjectsReplicated
> >          ......................... OSMDC3\\ passed test ObjectsReplicated
> >       Starting test: frssysvol
> >          [OSMDC3\\] An net use or LsaPolicy operation failed with error
> > 1203, No
> >  network provider accepted the given network path..
> >          ......................... OSMDC3\\ failed test frssysvol
> >       Starting test: frsevent
> >          ......................... OSMDC3\\ failed test frsevent
> >       Starting test: kccevent
> >          Failed to enumerate event log records, error No network provider
> > accept
> > ed the given network path.
> >          ......................... OSMDC3\\ failed test kccevent
> >       Starting test: systemlog
> >          Failed to enumerate event log records, error No network provider
> > accept
> > ed the given network path.
> >          ......................... OSMDC3\\ failed test systemlog
> >
> > I'm also getting the following errors:
> >
> > Event Type:    Error
> > Event Source:    Userenv
> > Event Category:    None
> > Event ID:    1054
> > Date:        2/7/2006
> > Time:        12:25:26 AM
> > User:        NT AUTHORITY\SYSTEM
> > Computer:    OSMDC3
> > Description:
> > Windows cannot obtain the domain controller name for your computer network.
> > (An unexpected network error occurred. ). Group Policy processing aborted.
> >
> > Event Type:    Warning
> > Event Source:    NtFrs
> > Event Category:    None
> > Event ID:    13508
> > Date:        2/6/2006
> > Time:        8:16:48 AM
> > User:        N/A
> > Computer:    OSMDC3
> > Description:
> > The File Replication Service is having trouble enabling replication from
> > OSIIDC1 to OSMDC3 for e:\windows\sysvol\domain using the DNS name
> > osiidc1.IAP.OSIENT.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 osiidc1.IAP.OSIENT.COM from
> > this computer.
> >  [2] FRS is not running on osiidc1.IAP.OSIENT.COM.
> >  [3] The topology information in the Active Directory for this replica has
> > not yet replicated to all the Domain Controllers.
> > 
> > What are some steps that I can take to enable replication before this site
> > is tombstoned?
> >