<div>
P.S....I ran a dcdiag, my only favor is such.<br />
<br />
Starting test: NetLogons<br />
Unable to connect to the NETLOGON share! (\\&lt;servername&gt;\netlogon)<br />
[&lt;servername&gt;] An net use or LsaPolicy operation failed with error 53, The network path was not found..
</div>


P.S....I ran a dcdiag, my only favor is such.

Starting test: NetLogons
Unable to connect to the NETLOGON share! (\\<servername>\netlogon)
[<servername>] An net use or LsaPolicy operation failed with error 53, The network path was not found..

<div>
err...meant to say &quot;my only ERROR is such&quot;....had too much caffiene today. Perhaps thats the problem. 
</div>


err...meant to say "my only ERROR is such"....had too much caffiene today. Perhaps thats the problem.

<div>
<div class="content wysiwyg-content">
I recently had to wipe my primary server due to server errors (refer my only other question), however before I wiped the server (my only DC) I was able to add another DC online. Unfortunately, it would not allow me to transfer the FSMO roles, so I had to shut the original server (henceforth known as Svr1) and seize the all of the roles, that process was successful. Since, I have been able to do much more, since I was having replication errors, but the only error I have left is my SYSVOL is practically empty (read: 1 folder named to my domain name) and my netlogon doesn't exist. <br />
<br />
I've read through these articles, followed them to the letter, to no avail. Let me know if you have any ideas or need any more info. <br />
<br />
<a href="http://support.microsoft.com/kb/315457/" rel="ugc">http://support.microsoft.com/kb/315457/</a><br />
<a href="http://support.microsoft.com/kb/316790/" rel="ugc nofollow">http://support.microsoft.com/kb/316790/</a>
</div>
</div>


I recently had to wipe my primary server due to server errors (refer my only other question), however before I wiped the server (my only DC) I was able to add another DC online. Unfortunately, it would not allow me to transfer the FSMO roles, so I had to shut the original server (henceforth known as Svr1) and seize the all of the roles, that process was successful. Since, I have been able to do much more, since I was having replication errors, but the only error I have left is my SYSVOL is practically empty (read: 1 folder named to my domain name) and my netlogon doesn't exist. 

I've read through these articles, followed them to the letter, to no avail. Let me know if you have any ideas or need any more info. 

http://support.microsoft.com/kb/315457/
http://support.microsoft.com/kb/316790/

Recovery of SYSVOL policies and NETLOGON shares

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.