When trying to connect remotely to one PC with Windows XP, my colleague reported to me the following error (I’m not sure if it is the exact error message):
Cannot connect. The NetLogon service is not running on the machine.
I went to the machine he’s trying to access and checked the Services on the Administrative Tools folder. From there, I could see that NetLogon is indeed not running. So, what did I do? I click the start button to run it. However, I got the following error message:
Error 10044: Could not start Net Logon Service on local computer. The support for the specific socket type does not exist in the address family.
Now, this looks Greek to me. Now, the machine is talking about sockets and address family. I know a little bit of everything, but not everything. So, I googled for this error message but I can’t find a decent forum thread giving a solution to that error. All I could see are people having the problems and reinstalling Windows as a solution.
I don’t want to reinstall yet. So, I restarted the machine and checked the logs again. Same error messages. Net Logon cannot be started.
I don’t know what got into me when I just pressed the reset button. Maybe, out of hopelessness, I tried restarting without shutting it down properly. Hehehe. Anyway, I’m going to reinstall Windows as the last resort to this problem.
However, after restarting, lo and behold! The error message was gone! And Net Logon service is running on the Services list. So, I asked my colleague to connect remotely, and he was able to connect! WTF?!
When he asked me how I fixed the problem, I told him I just restarted the machine. Hehe. Well, really, I don’t know what happened. How come it gets fixed after being shut down improperly? Do I have some magic in my fingers? LOL!
Now, why am I blogging about this? Here’s why.
Now, any experts wanna share experience with this error? I’m sure, pressing reset will not always work. 🙂