asked on

Sysvol/Netlogon share missing

Hey guys,

I have an 2003 domain, and i added a new Server 2008 DC (i ran ADprep) and it joined successfully and is replicating. However i noticed on the new DC it's missing the netlogon and sysvol shares and had another error. It threw this error in dcdiag:

Starting test: NetLogons
Unable to connect to the NETLOGON share! (\\server\netlogon)
[server] An net use or LsaPolicy operation failed with error 67,
The network name cannot be found..
......................... server failed test NetLogons

Starting test: Advertising
Warning: DsGetDcName returned information for
\\ad.server.local, when we were trying to reach server.
SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.

Will Szymkowski

The quickest way to correct this issue is demote this DC and re-promote it. It probably failed on some steps during the promoting of this server to a DC.

Will.

ASKER CERTIFIED SOLUTION

Cliff Galiher

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Bill H

ASKER

Cliff, there was an OLD dc that was on the domain prior, i did a metadata cleanup and removed it successfully.

I did notice a journal wrap condition on the existing 2003 dc that's there...could that be it?

Cliff Galiher

That's it.

Cliff Galiher

Or I should say, that is part of it. There may also be other causes. But yes, a server in journal wrap will prevent a new DC from coming online.

Bill H

ASKER

How do i identify other causes? I didnt see anything else in the logs.

Cliff Galiher

As I Dao, there *may* be other causes. I was just setting expectations. Journal wrap may be the only issue. It may not be. We can't tell from here.

Bill H

ASKER

Does anyone have steps for the journal wrap restore for server 2003? I need to complete this is it seems.

Bill H

ASKER

I ran the journal wrap fix and everything is now successfully replicated.