New DC does not have a netlogon share?

[gavm99]

Hi all,

I am installing a new server to replace an old one.

I have made my new server a Domain Controller and transferred all the AD roles to it.

However there is no Netlogon share on the server?

Any ideas why this would occur?

Thanks.

Gavin.

 

[karmic]

Download the windows support tools here and install to c:\support

http://www.microsoft.com/downloads/...78-8BE1-4E81-B3BE-4E7AC4F0912D&displaylang=en

open cmd prompt, navigate to c:\support and run the following commands. the resulting text files should give you an indication of any failures.

dcdiag /v >dcdiag.txt
netdiag /v >netdiag.txt

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[gavm99]

Hi,

Ok below is the failed results from dcdiag (I have edited it down to show only the failed tests)

Domain Controller Diagnosis

Performing initial setup:
* Verifying that the local machine NEWSERVER, is a DC.
* Connecting to directory service on server NEWSERVER.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.

Starting test: NetLogons
* Network Logons Privileges Check
Unable to connect to the NETLOGON share! (\\NEWSERVER\netlogon)
[NEWSERVER] An net use or LsaPolicy operation failed with error 1203, Win32 Error 1203.
......................... NEWSERVER failed test NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for \\OLDSERVER.DOMAIN.LOCAL, when we were trying to reach NEWSERVER.
Server is not responding or is not considered suitable.
The DC NEWSERVER is advertising itself as a DC and having a DS.
The DC NEWSERVER is advertising as an LDAP server
The DC NEWSERVER is advertising as having a writeable directory
The DC NEWSERVER is advertising as a Key Distribution Center
The DC NEWSERVER is advertising as a time server
......................... NEWSERVER failed test Advertising

Starting test: frssysvol
* The File Replication Service SYSVOL ready test
The registry lookup failed to determine the state of the SYSVOL. The

error returned was 0 (Win32 Error 0). Check the FRS event log to see

if the SYSVOL has successfully been shared.
......................... NEWSERVER passed test frssysvol

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: 0x800034FD
Time Generated: 07/19/2007 10:19:05
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x800034C4
Time Generated: 07/19/2007 10:20:58
(Event String could not be retrieved)
......................... NEWSERVER failed test frsevent




Some unexpected network error occurred.
An Error Event occured. EventID: 0x80001774
Time Generated: 07/19/2007 10:15:47
Event String: A driver packet received from the I/O subsystem

was invalid. The data is the packet.
......................... NEWSERVER failed test systemlog



Can anyone help me with why these are failing?

 

[downloadkid]

did you by chance perform a DCPROMO on the old server before promoting the new one. It seems the new server is not considered the DC on your netwrok whioch will cause all manner of problems.

 

[gavm99]

Hi,

Just to let you know I have now resolved this issue. What I had to do was go back to basics. I made my new server a member server again. I rolled AD back to how it was before the new server installation. I then had to remove the links to an old server which no longer existed on the domain. I then used metacleanup. I restarted the server and it was all reporting ok. I then made my new install a domain controller again and this time it all went through fine with the netlogon and sysvol shares appearing straight away.

Thanks.