Home / server / Questions / 388268
Accepted
David
Asked: 2012-05-12 06:37:03 +0800 CST

An attempt was made to logon, but the network logon service was not started Server 2008 R2

  • 772

On my main 2008 R2 domain controller:

When I boot, the screen goes black (monitor light goes amber)

RDP logon to the server says "An attempt was made to logon, but the network logon service was not started"

Trying to logon to the local admin account on the domain controller via RDP gives the same problem.

It's a really big mess..

EDIT: After playing around with some remote management tools, it seems neither netlogon nor RPC server are running.. tried starting them but they won't start..

netlogon windows-server-2008-r2

6 Answers

  1. On my main 2008 R2 domain controller:

    Luckily for you, there's no such thing as a main domain controller. They're all peers, and some just hold more roles than others.

    It sounds like your server has some serious issues and you haven't provided any meaningful details for us to help resolve them, so I'll recommend this: Remove all FSMO roles from this DC. Demote it (or do a metadata cleanup if you can't demote it) so that it's no longer a Domain Controller. Reinstall it and dcpromo it again.

    It's better to just rebuild a wonky DC than to mess with it, considering how modular they are.

    • 1

  2. you have to start "Netlogon" service so follow the path : "Control Panel\Administrative Tools\services" then find the service named "Netlogon" and double click on this service int the "startup type" choose "manual" on "service status" click start

    • 1

  3. Try to change the Netlogon service to automatic and restart the server.

    1. Click on Administrative tool ->> services ->> double click on Netlogon.
    2. Change the startup type to automatic.
    3. Restart the server.
    • 1
  4. Best Answer

    Ended up just nuking the server

    • 0

  5. Try Entering the Following Command in CMD with Admin Rights

    netsh winsock reset catalog
    • 0

  6. I understand, how it feels when domain controller doesn't work up to the mark.

    As you have tried all remote access tools, assuming RSAT also, but to no purpose.

    Therefore, I would suggest if you have any RODC in your domain, just seize (FSMO) 5 roles. You have to run ntdsutil command on RODC.

    Convert your RODC to DC.

    http://kpytko.pl/active-directory-domain-services/seizing-fsmo-roles/

    Regards. Sairam

    • 0