Answered by:
Netlogon cannot start

Question
-
we have a windows server 2003 standard edition. it's been working really well but just a week ago, the netlogon service stopped and manually starting it also returns an error(0xc0000064). this has made it impossible for some users to access the server. how can we get the service to start?Wednesday, October 28, 2009 2:28 PM
Answers
-
Hi,
I understand that the Net Logon service failed to start with error 0xc0000064 on Windows Server 2003 standard edition.
This problem is usually caused by the incorrect computer name settings or the DC has been renamed. Please check and modify the following computer name registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ComputerName\ComputerName
Key Name: ComputerName
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerName
Key Name: ComputerName
HKey_Local_Machine\System\CurrentControlSet\Services\TCPIP\ Parameters
Key Name: NVHostName
If the issue persists, please collect MPS report for further research:
1) Download proper MPS Report tool from the website below.
Microsoft Product Support Reports
2) Double-click to run it, if requirement is not met, please follow the wizard to download and install them. After that, click Next, when the "Select the diagnostics you want to run" page appears, select "General", "Server Components", click Next.
3)After collecting all log files, choose "Save the results", choose a folder to save <Computername>MPSReports.cab file. Please use Windows Live SkyDrive (http://www.skydrive.live.com/) to upload the file and then give us the download address.
Regards,
Bruce
- Marked as answer by Bruce-Liu Wednesday, November 4, 2009 6:39 AM
Thursday, October 29, 2009 8:39 AM
All replies
-
Please post the DCDIAG /V and IPCONFIG /ALL
Thanks
http://technetfaqs.wordpress.comWednesday, October 28, 2009 3:24 PM -
Hi,
I understand that the Net Logon service failed to start with error 0xc0000064 on Windows Server 2003 standard edition.
This problem is usually caused by the incorrect computer name settings or the DC has been renamed. Please check and modify the following computer name registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ComputerName\ComputerName
Key Name: ComputerName
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerName
Key Name: ComputerName
HKey_Local_Machine\System\CurrentControlSet\Services\TCPIP\ Parameters
Key Name: NVHostName
If the issue persists, please collect MPS report for further research:
1) Download proper MPS Report tool from the website below.
Microsoft Product Support Reports
2) Double-click to run it, if requirement is not met, please follow the wizard to download and install them. After that, click Next, when the "Select the diagnostics you want to run" page appears, select "General", "Server Components", click Next.
3)After collecting all log files, choose "Save the results", choose a folder to save <Computername>MPSReports.cab file. Please use Windows Live SkyDrive (http://www.skydrive.live.com/) to upload the file and then give us the download address.
Regards,
Bruce
- Marked as answer by Bruce-Liu Wednesday, November 4, 2009 6:39 AM
Thursday, October 29, 2009 8:39 AM -
Bruce,
Thank you for this post. I searched the web for 6 hours trying to figure out why my Window Server 2012 r2 was not recognizing that it was the domain controller and not starting netlogon (was also blue screening). I tried many things to repair/recover my ntds but got no where. I tried your solution just a bit ago and it fixed my problem. Your posting was hard to find but I am so thankful to find it. I found it weird that after doing a windows update that my computer's name change back to the default when I first installed it a year ago. I would not have solve this without our posting.
Best wishes,
Daniel Fajardo
Sunday, May 24, 2015 1:20 PM