Problems configuring OpenSSH and mxagentconfig for managed system

[Adam Nickells]

Hi,

I'm just setting up SIM for the first time and have some issues witht he set up of the managed systems.

I've installed OpenSSH onto one of our DCs with no problems, and have gone through the HP instructions to add a domain account for SSH. This domain account is a member of the Domain Admins group, so has admin rights on all of our servers.

I run mxagentconfig -g, but this fails to connect to the managed server. I tried the username as domain\username and just username.

If I set this up on a server which is not a DC, and instead of using the domain account, I use the local administrator account (in the initial SSH config and in mxagentconfig), it works fine. This isn't really a solution though as the local admin passwords get changed on a regular basis.

Has anyone else had this working with a domain account? I can't quite see where I'm going wrong.

I can see the following error (listed as informational) in the event log on the CMS server:

PID 3676 : input_userauth_request: illegal user domain\\user
PID 3676 : Failed password for illegal user domain\\user from 128.1.100.168 port 4540 ssh2.

Can anyone help on this? It's a bit of a stopper on the roll out of SIM if we can't get this sorted.

Cheers,

Adam

[Adam Nickells]

Hi,

surely I'm not the only person who wants to use a domain account for OpenSSH and has run into this problem?

Has anyone got this working successfully with a domain account? If so, what steps did you follow to get it to work?

Thanks,

Adam

[David Claypool]

Please add the domain information to the group file

mkgroup -d >> "c:\program files\openssh\etc\group"

[Adam Nickells]

Hi,

I've run the mkgroup command and it seems to have added every group in the domain.

However the mxagentconfig part still doesn't work. It says Failed to establish connection.

I tried entering the username as domain\user and user.domain. I tried entering the machine name as just the machine name, and the fully qualified DNS name.

I've verified that I can connect to the managed node in question from the CMS Server, so there's no problems there.

Surely it shouldn't be this difficult?

I'm unable to get this to work at all at the moemnt. The managed node is a DC so there's no way I can use a local account, and besides which I don't want to as the local accounts change regularly.

Would I be better to raise a call directly with HP about this?

Cheers,

Adam

[Adam Nickells]

Hi,

still having no luck with the OpenSSH stuff. Maybe I'm going to have to wait for the update in April?

Has anyone got OpenSSH working with a domain account? At least if this is the case I know it's possible and I'm not wasting my time here.

Cheers,

Adam

[Wayne Jackson_2 · Accepted solution]

I have used a domain account successfully. The trick was to logon to the server as the account and install the OpenSSH software. Once rebooted, it didn't matter who you logged on as the mxagentconfig should work. This has something to do with the creation of the passwd file on the client machine.
Hope this works for you.

Wayne

[Adam Nickells]

ok...this seems to be working now that I've logged onto the server with the same account. It's a shame the user guide is a bit misleading on this.

Cheers,

Adam