tl;dr don't use a password that contains double quotes (") followed by another character. Double quotes (") as last character however works just fine.
Hi everyone,
I changed the windows system credential used by PRTG to access windows Systems. Everything seemed to work, according to my Tests, but the moment switched the "live" credentials it all went south.
I noticed that all works fine, no problems with the WMI or powershell sensors, as long as I keep the only print queue senor (ptfsensor) we have on pause. As soon as I un-pause the pftsensor the domain user gets locked due to the number of bad password counts. The event viewer of our print server gave me some clues, first there are a few entries with "Failure Reason: Unknown user name or bad password" followed by some more with "Failure Reason: Account locked out".
It came to my mind that one of the special chars used in the password might be the source of this problem even though I explicitly choose characters from ascii 32 - 127.
After some trial and error, I found out that the problem only occurs if the password contains double quotes (") and if the double quotes (") aren't the last char of the password.
Can someone explain to me why this only happen in this specific situation and why it is only the ptfsensor that got a problem with it?
Regards, More
Add comment