- Remove From My Forums
-
Question
-
I have a server, lets call it FRED, running windows server 2003 R2 Enterprise.
When FRED gets to the logon screen, I hit control+alt+delete and try to logon to the local PC with the administrator account. I get a dialog stating «The system could not log you on now because the domain FRED is unavailable»
If I try to log on using a domain account, I get the message «Unable to log you on because the netlogon service is not running on this machine.»
FRED is not a DNS server or a domain controller.
I can’t RDP to FRED and I can’t connect to FRED from another server’s MMC. How can I start the netlogon service?
Answers
-
Hi JMorrisws,
As you stated, that the Netlogon service is started when you logged in to safe mode with networking.
You may perform a clean boot of your server to see if it’s started.
To manually perform a clean boot of your computer in Windows 2000, Windows XP, or Windows Server 2003, follow these steps:
1. Click Start, click Run, type msconfig, and then click OK.
2. On the General tab, click Selective Startup, and then click to clear the following check boxes:
o Process SYSTEM.INI File
o Process WIN.INI File
o Load Startup Items
3. On the Services tab, click to select the Hide All Microsoft Services check box, and then click Disable All.
4. Click OK, and then click Restart to restart your computer.
Regards,
Wilson Jia
This posting is provided «AS IS» with no warranties, and confers no rights.
-
Marked as answer by
Tuesday, March 23, 2010 2:52 AM
-
Marked as answer by
Sorry should of said — while it is at the login screen, i can ping it. But thats it, also no users can access the server.
Was this post helpful?
thumb_up
thumb_down
akp982 is an IT service provider.
pure capsaicin
can you connect to \servernetlogon
Was this post helpful?
thumb_up
thumb_down
Hey akp — nope! no joy
Was this post helpful?
thumb_up
thumb_down
The Domain Controller is up and running as the other servers have connected with no problems either, just looks like this server disabled netlogon.
PS — On hunt for the CD … am still hunting!
Was this post helpful?
thumb_up
thumb_down
akp982 is an IT service provider.
pure capsaicin
Reboot all off the DC’s and try again
Was this post helpful?
thumb_up
thumb_down
Was chatting with our server guy there, he says boot into safe mood and it should re-establish netlogon. I will try that first as there is about 80 users currently connected to DC.
Am sure you know the hassle of getting users to log out / disconnect!!!
Nothing «good» about this Friday!!!
Was this post helpful?
thumb_up
thumb_down
akp982 is an IT service provider.
pure capsaicin
John8095 wrote:
Was chatting with our server guy there, he says boot into safe mood and it should re-establish netlogon. I will try that first as there is about 80 users currently connected to DC.
Am sure you know the hassle of getting users to log out / disconnect!!!
Nothing «good» about this Friday!!!
why are you working on good friday… fools
Was this post helpful?
thumb_up
thumb_down
Open a Command Prompt on the Server and first display all the Services running by typing NET START or go to Start > Run > Services.msc.. Under the NETLOGON Service check your Recovery & Dependencies and make sure they are running and set to Restart Service (these must be set as Automatic and Started in their Properties). If they are not running, start the Dependency Service either in the MMC or thru the Command Prompt…NET START [Service].
If all is a go at this point, go back to your Command Prompt and try to start the NETLOGON Service by typing the following command:
net start netlogon
An Explanation of the action from the Command Prompt is available after the action by searching the Event Code (if failed) or typing NET HELPMSG 2182
Good Luck.
Was this post helpful?
thumb_up
thumb_down
Problem being unable to log in! Under admin, locally no good either. If i could get into the machine I would manually set netlogon on.
SafeMode — No Joy…
Going with restart of DC’s now
Was this post helpful?
thumb_up
thumb_down
@akp —why are you working on good friday… fools
Beginning to wonder that myself!
Was this post helpful?
thumb_up
thumb_down
akp982 is an IT service provider.
pure capsaicin
John8095 wrote:
@akp —why are you working on good friday… fools
Beginning to wonder that myself!
Its only me working here, trying to setup and test out new DR systems.
Was this post helpful?
thumb_up
thumb_down
Someone has to pay the bills:-)
Actually, open up the Services.msc MMC on your local workstation, right-click Services (local) and select Connect to another Computer. Type in the name of the Server then navigate to the NETLOGON Service and its Dependencies. Start any from here and then set the Recovery to Restart Service all the way down the line. If you have the opportunity to Reboot, do so after.
Good Luck.
Was this post helpful?
thumb_up
thumb_down
If you’re having trouble rebooting the servers you can issue the command from your local machine to restart it remotely:
shutdown -f -r -m \computername -t 00
Was this post helpful?
thumb_up
thumb_down
Twisted Twin wrote:
Someone has to pay the bills:-)
Actually, open up the Services.msc MMC on your local workstation, right-click Services (local) and select Connect to another Computer. Type in the name of the Server then navigate to the NETLOGON Service and its Dependencies. Start any from here and then set the Recovery to Restart Service all the way down the line. If you have the opportunity to Reboot, do so after.
Good Luck.
Cheers twisted twin — going to give that a go now.
Was this post helpful?
thumb_up
thumb_down
I get the «server is unavailable» error.
Its pinging ok. Anyone recommend a good hammer?
Was this post helpful?
thumb_up
thumb_down
i would go for a reboot first. do it the way Orl described. good change that all is solved.
Was this post helpful?
thumb_up
thumb_down
I know everyone is thinking it — so I am going to say it.
Once you get this issue resolved — UPGRADE or retire the box. Server 2000 should not be running in any prod environment anymore.
Was this post helpful?
thumb_up
thumb_down
Tell that to the Gov…
Was this post helpful?
thumb_up
thumb_down
No prob, it is easy to tell the gov. End of Life for support is coming in July 13, plus 2000 is not as reliable, and probably the hardware is old. The cost of not updating most likely will be higher than updating. Also gov agencies, have regulations where you need to have the OS with support.
I don’t want to scare you, but usually there is 3 (4) reasons why the DC services will stop responding., going from the most unlikely to the most likely.
4) The network has problems that do not allow you to contact the DC. You can test this in the simplest form by pinging, and with more detail using dcdiag
3) The firewall on the server is blocking the request.
2) there is problems on the server (usually hardware, and most likely RAM or HDD) corrupting the data. A restart usually recovers the services.
1) you have been hijacked, or you got a virus. Do your DC have antivirus? Have you run a full scan lately?
Go thru all these points to see what might be the problem.
It is also possible that you have current connections, but cannot make new ones. This is usually an indication of part of the TCP/IP not working or the connection being blocked.
I worked for a government agency for 5 years, and I also did contracting work for department of transportation, so I know that they expect high levels of SLA, but it is very difficult to make changes. However, with time I was able to prove that the more that they resist to change, the more downtime they have. It took me almost 2 years to bring the network to a more updated state where I used to work. I got hired on 2002, in 2004 was when I got rid of the last NT server. However, the SLA had a turn around from 85% uptime to 99.98% proven uptime.
Was this post helpful?
thumb_up
thumb_down
Hehehehe…
Well, as much as I agree, that «Server 200» shouldn’t be running in any production environments anymore… I have to say, GUILTY!!!
I have 3 boxes still running Advanced Server 2000…
The majority of the difference are running 2003 SP2 Std.
And I am just beginning to receive some blades on which I can install and run 2008 x64.
Did the reboot or going through the services menu help at all?
And how come you can’t log into the machine locally? No physical access??
You could, from a «run» box… (requiring a server)
mstsc /console which is the same as opening up the box locally…
OR
Using xVNC establish a connection, without the client being installed as long as you are on the same subnet…
Was this post helpful?
thumb_up
thumb_down
mstsc.exe /v:x.x.x.x /console /f — no good.
I have a server guy coming in today — will update (hopefully) a fix in an hour or 2.
Was this post helpful?
thumb_up
thumb_down
Server guy called and was unable to bypass the login screen either. He ended up running some diagnostic tools onsite (from – herins, http://hotfile.com/dl/36418245/7dd0c95/Hirens.BootCD.10.3.zip.html Opens a new window) but no joy – but great tools there I will use them at some stage later – test hardware and so on.
So, he took the server offsite. OS was completely corrupt.
At least we got the data back by mounting that win 2000 on another CPU as secondly drive.
Was this post helpful?
thumb_up
thumb_down
Glad to hear you got your data back and mounted.
the actual command though is:
MSTSC.EXE /console (opens up the «local machine emulation)
MSTSC.EXE /v:[machine name] (opens a terminal session)
Was this post helpful?
thumb_up
thumb_down
Not for anything, but Hiren’s is quite know 
I like miniPE better though.
As for recovering the data, that was last resource. In most of my servers the data is not the problem, but the software running on it. I have 3 Windows 2000 servers, and I moved them to VM since the hardware was failing. 2 have Citrix metaframe which cannot be easily moved to 2003 (I will have to buy at least new TS cal), so instead I am planning on replacing the whole solution, but it will take time. The 3rd server is a DC, which also is the RS licensing server. That server is holding me from raising the function level of the domain
Was this post helpful?
thumb_up
thumb_down
Generally Error 1792 An attempt was made to logon but the network logon service was not started windows occurs when netlogon service is either disabled or not responding. This error can occur in specific scenarios, like when a user login through RDP to the local administrator account on the domain controller. Also, when a user tries to map two different drives, then this error occurs. Now there are few reasons why this error occurs. Firstly the netlogon service is disabled. Secondly, the error also arises due to metadata in the active directory. Furthermore, replications can also be the possible cause of this An Attempt was Made to Logon error. This troubleshooting guide will demonstrate methods by which you can fix the issue.
Causes of An Attempt Was Made To Logon But The Network Logon Service Was Not Started:
As in the introductory part, we have already mentioned that the major causes of this An Attempt was Made to Logon error are Disabled netlogon service. Misconfigured IP settings, recent changes in the network adapter, or windows update are some possible causes of Error 1792 An Attempt was Made to Logon But the Network Logon Service was not Started windows error. Further, the problem can also occur due to outdated drivers.
- Disabled Netlogon Service
- Misconfigured IP settings
- Windows Update
- Recent Network Setting Changes
- Outdated Drivers
- Meta Data and Network Cache in Active Directory
Similar Types of An Attempt Was Made To Logon But The Network Logon Service Was Not Started:
- Windows server
- Logon service not started – windows 10
- Netlogon service not starting windows 7
- Windows could not start the netlogon service on local computer
- Error 1792
- Windows 2008 r2
- Error 1792 An attempt was made to logon service was not started – windows 10
- Network logon service was not started win 10
To fix the An Attempt was Made to Logon error, we have some methods that will be helpful for you. The following are the methods. The first will be all about manually start the netlogon by going into windows services. In the second method, we will try to eliminate the error using command prompt and some useful commands. Finally, if any method does not work, the only way to remove Error 1792 An Attempt was Made to Logon But the Network Logon Service was not Started windows error is by using system restore. Let us proceed to each method in more detail.
1. Starting the Netlogon Service –
In this method, we will eliminate An Attempt was Made to Logon But the Network Logon Service was not Started error by starting the netlogon service. In most cases, this method fixes the problem. Let get onto the steps.
- STEP 1. Open the Run window by pressing Window+R key at the same time
- STEP 2. In the search field type services.msc and then hit enter
- STEP 3. In the services window, locate Netlogon service
- STEP 4. Now to start the right service click then go to Properties
- STEP 5. In the properties put the startup type to Automatic
- STEP 6. Finally, click the Start button to start the service
- STEP 7. Click on Apply then OK to save the changes, now restart the system
- STEP 8. Check if the An Attempt was Made to Logon error still persists
2. Using the Command Prompt –
If the above methods fail to work, follow this method. In this method, we will perform some commands that will help remove An Attempt was Made to Logon But the Network Logon Service was not Started error. Follow the steps.
- STEP 1. Click the Start button then type cmd
- STEP 2. Now right-click on the command prompt and Run as administrator
- STEP 3. In the command window type the ipconfig/flushdns hit Enter
- STEP 4. After performing the above command type nbtstat –r and hit Enter
- STEP 5. Now enter netsh winsock reset command and hit Enter
- STEP 6. Finally, type netsh int ip reset and hit Enter
- STEP 7. Restart Your System Now and check if the An Attempt was Made to Logon error occurs
3. Using System Restore –
If all of the above failed to solve An Attempt was Made to Logon But the Network Logon Service was not Started issue. The only way to recover using the system restore. Using the system to restore your system will go back to the point where this error does not exist. Follow the steps to see how it is done.
- STEP 1. Open up the Start menu and Type System Restore
- STEP 2. Navigate to the System Protection Tab
- STEP 3. Hit System Restore Button then Click Next
- STEP 4. You will see a list of restore points, select your preferred restore point
- STEP 5. Then to start the process, Click Next Button
- STEP 6. Now your system restore process will start
- STEP 7. Follow the guidelines on the screen if it occurs
- STEP 8. After restoring, you will find that your system is free from the An Attempt was Made to Logon error
Conclusion:
This article demonstrates three troubleshooting methods to fix Error 1792 An Attempt was Made to Logon But the Network Logon Service was not Started windows error. Furthermore, this article also tells us the different causes of this An Attempt was Made to Logon error. If you find any issue with the steps or methods, tell us in the comments.
For more error solving guides like this, An Attempt was Made to Logon, then follow us. Thank You!
This post is a list of common agent push deployment errors… and some possible remediation options.
Most common errors while pushing an agent:
| Error | Error Code(s) | Remediation Steps |
|
The MOM Server could not execute WMI Query “Select * from Win32_Environment where Operation: Agent Install |
80004005 |
1. Check the PATH environment variable. If the PATH statement is very long, due to lots of installed third party software – this can fail. Reduce the path by converting any long filename destinations to 8.3, and remove any path statements that are not necessary. Or apply hotfix: http://support.microsoft.com/?id=969572 2. The cause could be corrupted Performance Counters on the target Agent. To rebuild all Performance counters including extensible and third party counters in Windows Server 2003, type the following commands at a command prompt. Press ENTER after each command. How to manually rebuild Performance Counter Library values 3. Manual agent install. |
|
The MOM Server could not execute WMI Query “Select * from Win32_OperatingSystem” on The MOM Server could not execute WMI Query “(null)” on |
8004100A 800706BA |
1. Ensure agent push account has local admin rights
2. Firewall is blocking NetBIOS access. If Windows 2008 firewall is enabled, ensure “Remote Administration (RPC)” rule is enabled/allowed. We need port 135 (RPC) and the DCOM port range opened for console push through a firewall. 3. Inspect WMI service, health, and rebuild repository if necessary 4. Firewall is blocking ICMP (Live OneCare) 5. DNS incorrect |
|
The MOM Server failed to open service control manager on computer “servername.domain.com”. Access is Denied |
80070005
80041002 |
1. Verify SCOM agent push account is in Local Administrators group on target computer. 2. On Domain controllers will have to work with AD team to install agent manually if agent push account is not a domain admin. 3. Disable McAfee antivirus during push |
|
The MOM Server failed to open service control manager on computer “servername.domain.com”. |
800706BA | 1. Firewall blocking NetBIOS ports
2. DNS resolution issue. Make sure the agent can ping the MS by NetBIOS and FQDN. Make sure the MS can ping the agent by NetBIOS and FQDN 3. Firewall blocking ICMP 4. RPC services stopped. |
|
The MOM Server failed to acquire lock to remote computer servername.domain.com. This means there is already an agent management operation proceeding on this computer, please retry the Push Agent operation after some time. |
80072971 |
This problem occurs if the LockFileTime.txt file is located in the following folder on the remote computer: http://support.microsoft.com/kb/934760/en-us |
|
The MOM Server detected that the following services on computer “(null);NetLogon” are not running. These services are required for push agent installation. To complete this operation, either start the required services on the computer or install the MOM agent manually by using MOMAgent.msi located on the product CD. |
C000296E |
1. Netlogon service is not running. It must be set to auto/started |
|
The MOM Server detected that the following services on computer |
C000296E | 1. WMI services not running or WMI corrupt |
|
The MOM Server detected that the Windows Installer service (MSIServer) is disabled on computer “servername.domain.com”. This service is required for push agent installation. To complete this operation on the computer, either set the MSIServer startup type to “Manual” or “Automatic”, or install the MOM agent manually by using MOMAgent.msi located on the product CD. |
C0002976 |
1. Windows Installer service is not running or set to disabled – set this to manual or auto and start it. |
|
The Agent Management Operation Agent Install failed for remote computer servername.domain.com. |
80070643 |
1. Enable the automatic Updates service…. Install the agent – then disable the auto-updates service if desired. |
| Call was canceled by the message filter | 80010002 | Install latest SP and retry. One server that failed did not have Service pack installed |
| The MOM Server could not find directory \I.P.C$WINDOWS. Agent will not be installed on computer “name”. Please verify the required share exists. | 80070006 |
1. Manual agent install Possible locking on registry? http://www.sysadmintales.com/category/operations-manager/ Try manual install. Verified share does not exist. |
| The network path was not found. | 80070035 | 1. Manual agent install |
| The Agent Management Operation Agent Install failed for remote computer “name”. There is not enough space on the disk. | 80070070 | 1. Free space on install disk |
| The MOM Server failed to perform specified operation on computer “name”. The semaphore timeout period has expired. | 80070079 |
NSlookup failed on server. Possible DNS resolution issue. Try adding dnsname to dnssuffix search list. |
| The MOM Server could not start the MOMAgentInstaller service on computer “name” in the time. | 8007041D
80070102 |
NSlookup failed on server. Possible DNS resolution issue. Verify domain is in suffix search list on management servers. Sometimes – the Windows Firewall service – even if disabled – will have a stuck rule. Run: (netsh advfirewall firewall delete rule name=”MOM Agent Installer Service”) |
| The Agent Management Operation Agent Install failed for remote computer “name” | 80070643 | 1. Ensure automatic updates service is started 2. Rebuild WMI repository 3. DNS resolution issue |
| The Agent Management Operation Agent Install failed for remote computer “name”. Another installation is already in progress. | 80070652 |
Verify not in pending management. If yes, remove and then attempt installation again. |
| The MOM Server detected that computer “name” has an unsupported operating system or service pack version | 80072977 | Install latest SP and verify you are installing to Windows system. |
| Not discovered | Agent machine is not a member of domain | |
| Ping fails | 1. Server is down 2. Server is blocked by firewall 3. DNS resolving to wrong IP. |
|
| Fail to resolve machine | 1. DNS issue | |
| The MOM Server failed to perform specified operation on computer “name”. Not enough server storage… | 8007046A | 1. This is typically a memory error caused by the remote OS that the agent is being installed on. |
| There are currently no logon servers available to service the logon request. | 8007051F | 1. Possible DNS issue |
| This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service. | 8007064D | 1. Install Windows Installer 3.1 |
| The network address is invalid | 800706AB |
Possible DNS name resolution issue. Tried nslookup on server name and did not get response. Verify domain is in suffix search list on management servers. |
| The MOM Server failed to perform specified operation on computer servername.domain.com | 80070040 | 1. Ensure agent push account has local admin rights |
| The MOM Server detected that the actual NetBIOS name SERVERNAME is not same as the given NetBIOS name provide for remote computer SERVERNAME.domain.com. | 80072979 | 1. Correct DNS/WINS issue. 2. Try pushing to NetBIOS name |
| The Operations Manager Server cannot process the install/uninstall request for computer xxxxxxx due to failure of operating system version verification | 80070035 | When Error Code: 80070035 appears with a Console based installation of the OpsMgr Agent and the targeted systems are Windows Server 2008 based systems which have their security hardened by using the Security Configuration Wizard, check to see whether the Server service is running |