Logon Failure... « dougzuck.com

dougzuck.com - Forum » Remote Reboot X - The Ultimate WSUS Companion Tool

Logon Failure...

(5 posts) (2 voices)

Started 6 months ago by cberneburg
Latest reply from doug

Tags:

No tags yet.

cberneburg
Member

Hey Doug

Remote-Reboot-X is *exactly* the kind of tool I was looking for and gave up on writing myself long ago. :-) I am having a bit of trouble learning how to use the WSUS actions, so I was hoping you could provide some help.

The error that keeps occurring is "Logon failure: unknown user name or bad password". Now, I *know* that my user name and password are good, because I can log directly into the (remote computer) console using them. I am also able to log into the remote computer and execute a command prompt using PsExec. Within RRX, the Ping, Get Last Boot Time, and Reboot (normal) actions all work too. But "WSUS - install ..." and "WSUS - search..." action suite keep returning "Logon Failure". Turning off Windows Firewall does not seem to help either.

FYI, the remote computer is not part of a domain, so I have set RRX credentials to use the local domain by specifying dot (.) in the Domain field. I can provide other info and try other settings at your request. Thanks for your time and assistance!

-Cris

Posted 6 months ago #
cberneburg
Member

Hmm... works with Integrated Security. Just can't figure out what I'm doing wrong with non-integrated credentials.

Posted 6 months ago #
doug
Key Master

Cris - first, I have to tell you that I designed Remote Reboot X for use in a domain, so I'm admittedly not too concerned with non-domain usage since it's not what most sys admins are dealing with. That said, from what you're describing I believe the issue is the dot notation. When you execute the WSUS options, PsExec is being used. I don't think PsExec likes the dot. So, what happens if instead of using a dot you use the actual remote machine name. I'm pretty sure that this worked when I tested it originally. Unfortunately I'm in the midst of moving to a new home and don't have a means to test or look at the code right now to confirm. I realize that since you specify the global credentials in one location, it's not ideal to have a bunch of machines that are not on the domain because they would need to each have their own credentials when the dot notation doesn't work. This has been implemented for the next release of the app, but I'm still adding more functionality and testing a lot more, so it's not ready for public consumption just yet.

Let me know how it goes.

-Doug

Posted 6 months ago #
cberneburg
Member

Hey Doug

My congratulations and condolences on your move. :-)

I tried the remote machine name for the domain, and that did not work either. Nevermind then, I got a workaround. As long as there are identically credentialed local accounts for each machine, the Integrated Security credentials work fine.

FYI, I host some Windows XP virtual desktops which are not part of the corporate domain. I'd like to move in the direction of centrally managing them, and RRX seemed like a good start. Maybe in the future I could set up a subnet, active directory, and WSUS server, but that kind of admin stuff is a bit too hefty for my needs ATM.

-Cris

Posted 6 months ago #
doug
Key Master

Interesting about the credentials. Thanks for following up. I'll have to mess around with testing once I'm settled into my new place.

-Doug

Posted 6 months ago #

RSS feed for this topic

Reply

You must log in to post.