RE: DC does not have Netlogon and Sysvol shares

Can you ping the other dc? Did you just promote the domain controller?

"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?
.

Relevant Pages

  • Re: How to connect the NT4 PCD from windows 2003 server
    ... internal is on top of external on the network connection ... for lmhosts files on NT4 server, ... >> type glcdom, which is my NT4 domain controller name, it ...
    (microsoft.public.win2000.security)
  • RE: Strange Irregular DNS/Networking Problems
    ... My network is not a complicated set up and only has one domain controller. ... problems with DNS resolving after changing DNS servers. ... I was already using the server for DHCP. ...
    (microsoft.public.windows.server.dns)
  • Re: IPSec / domain isolation: confusing MS documents
    ... workstation, he is able to attach to server ressources again, but for our ... The user right for access this computer from the network ... will not work for computer accounts unless ipsec is being used. ... securing a domain controller. ...
    (microsoft.public.windows.server.security)
  • DC does not have Netlogon and Sysvol shares
    ... network provider accepted the given network path.. ... Server is not responding or is not considered suitable. ... OSIENTDC1 is the Schema Owner, but is not responding to DS ... Missing SPN: ...
    (microsoft.public.windows.server.active_directory)
  • RE: DC does not have Netlogon and Sysvol shares
    ... network provider accepted the given network path.. ... Server is not responding or is not considered suitable. ... OSIENTDC1 is the Schema Owner, but is not responding to DS ... Missing SPN: ...
    (microsoft.public.windows.server.active_directory)