VPS: Windows 2008 R2 SP1 x64 bit. Intel 3.x Ghz quad-core processor, 4GB ram, unshared.
1) I installed the Netwrix Account Lockout Examiner on my VPS to diagnose lockout problem with one of my accounts. I am getting this error message:
This request operation sent to net. pipe ://localhost/ALService/Settings did not receive a reply within the configured timeout (00:02:00). The time allotted to this operation may have been a portioj^f a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.
then when I press OK, the ALE Console just closes out. So I must open it again and try again. I did this about 5 times. Then finally I still got some progress here
ALE finally connects but nothing useful.png 41.38KB 0 downloads
but still no useful info. no historical info on locked out accounts is available.
2) I'm not sure which name is correct for the "domain name" or "domain controller" . i assumed it is the same domain name I use to connect to my VPS. I am the Administrator of my windows VPS. I do know that each Windows VPS is optimized to run like a desktop in the cloud so to speak. So I don't have Active Directory capability (or I have it but it is disabled by default)
I only use the VPS as a cloud desktop (always on, fast internet connection, etc).
To be honest, ALE has been one of the more difficult pieces of software to install and obtain information with. And there is not even a verbose log that I can see where the error is coming from (e.g. what can Netwrix Account Lockout Examiner see/read vs what it cannot see/read).
Original problem was that one of my regular user accounts suddenly experienced lockout (I could not login remotely). Only by disabling the Group Policy related to This is after using the same vps for several years without any issues. I don't regularly install new software, but it was recently rebooted and I've been having the lockout problem ever since. Since the account was disposable, I ended up moving needed files to a new user account, deleting the problem account, and I've had no lockout issues with the new account.
We rebooted vps and changed the RDP random port without success. According to the VPS provider, it is not coming from an external source trying to connect to the VPS. It is some software or system process on the VPS that is somehow continuously attempting to log into the problem account. If I disabled the account lockout policy via Group Policy completely, then I could login to the locked out accounts without any issue.
Not sure why this process is so difficult to track down,and why us laypersons must go through so much trouble to get some readable info from some related logs. But I did not build windows OS. After some google searches, this netwrix program kept coming up.