Command not allowed

[Alexander Regueiro]

Every time I try to run sudo.exe from the command-line or Windows Explorer (via the context menu), I get the "command not allowed" error message, having entered my password. I have no idea why I'm getting this, nor even what it means. Could someone please clarify what is happening here and how I can resolve it?

I'm running Windows 7 64-bit; will glady provide more information if necessary.

Thanks.

[Greg R]

Had the same issue and the only way I could get around it was to sudo cmd.exe first and then run the installer

[Anonymous]

I am getting this error as well.
Which password shoul i be using, my computer's password or what, in case thats the problem.

thanks.

[Alexander Regueiro]

Hello. I'm still curious if any help is available on this? Is this a known bug in the app perhaps? Cheers.

[Kiliman]

Can you send me your sudoers.xml file as well as the user and command you were trying to run?

You can email me: kiliman@systemex.net

[Jason]

Hi, I've been using this version of SudoWin for a couple of years for various applications and it's been working well.  I've recently attempted to implement a couple of other applications using SudoWin and keep getting the 'Command Not Allowed' message.  (I even get this message when entering a passphrase that I know is incorrect).  All the groups, sudoers.xml files, etc I'm using are set up the same as I've always done, so I'm rather confused as to what's happening.  I'd be happy to e-mail any further information you need if you are able to assist.

Thanks.

[Kiliman]

@jasongov,

Can you send me your sudoers.xml file as well as the user and command you were trying to run?

You can email me: kiliman@systemex.net

[Jason]

Hi,

I have an update:

We used the same groups and sudoers.xml file and configured SudoWin on servers in our production data center and they work there.  I can still send you the sudoers.xml file if you want but this issue seems to point to some difference between the servers in the two data centers.  I'm looking to see if there are any patch differences or variations in group policy.  We had always been able to use SudoWin in both data centers, so I'm not sure what's changed.  If you have any thoughts on what to check, please let me know.

Thanks.

[Anonymous]

I'm getting this same issue on a brand-new Windows 8 PC. Here's my sudoers.xml file (taken from C:\Program Files (x86)\Sudowin\Server): http://ge.tt/5HnbvZV/v/0?c

The command I was attempting to run was `sudo gem install bundler`.

[Kiliman]

First of all, I want to apologize to everyone for not responding to your issues sooner. Real life has kept me pretty busy.

Anyway, let's see if we can figure out the issue.

I don't remember if the group name is case sensitive, so make sure you have a "sudoers" user group and add the user accounts to it. If the group name is "Sudoers", then change it in the sudoers.xml file to match.

Next, I never liked the "default" sudoers.xml file. It's confusing.

This is all you need in it to allow any user in the Sudoers group to run any command as Admin. I think this is much simpler. Once you get this to work, then you can deal with more advanced stuff.

Let me know how this works for you.

<sudoers    xmlns="http://sudowin.sourceforge.net/schemas/XmlAuthorizationPlugin/"
            privilegesGroup="Administrators" 
            invalidLogons="3"
            timesExceededInvalidLogons="3"
            invalidLogonTimeout="180"
            lockoutTimeout="180" 
            logonTimeout="180" 
            startTime="00:00:00.00000" 
            endTime="23:59:59.99999" 
            loggingLevel="Both" 
            allowAllCommands="false">
    <users>
        <userGroup name="sudoers" allowAllCommands="true">
        </userGroup>
    </users>
</sudoers>