Start a Conversation

Unsolved

88 Posts

180

August 30th, 2023 09:20

ssh connection to Windows failes because of wrong user name path

Since a few weeks (I saw August 23 on some servers) the ssh connection for OME on Windows Servers fails. I found this in the eventlog:

sshd: fatal: ga_init, unable to resolve user win\\username

See the double back slash. It's clear to see that Windows can't resolve this.

I don't know exactly when this happened the first time, maybe since the update to Version 3.10.2 (Build 13).

Greetings Barbara

August 30th, 2023 09:37

More information: This error appeared after the update to Version 3.10.1 (Build 51). Unfortunately, I have no older snapshot from the VM. Because it seemed to me that the update worked fine, I deleted the snapshot I took before.

Moderator

 • 

8.4K Posts

30-08-2023 03:08 PM

MdmBarbarella,

 

I am not certain there is solution based on the information provided, but would you confirm the following so that I may research if there is. 

 

1) Does a re-discover help

2) Are You using a non-standard port for OpenSSH

3) What version of OpenSSH are you using?

 

Let me know and I can see if there are any solutions.

 

 

 

 

DELL-Chris H

Social Media and Communities Professional

Dell Technologies | Enterprise Support Services

#IWork4Dell

Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!

October 18th, 2023 15:03

Sorry that I lost this thread.

The problem persists.

- Re-discover doesn't help

- no, we use the standard port 22

- on Server 2019 and higher we use the OpenSSH-version integrated in the OS. On older servers or servers without internet connection wie use the known package from github (version 8.x)

Greetings Barbara

Moderator

 • 

8.4K Posts

18-10-2023 03:38 PM

MdmBarbarella,
 
 
My opinion is it's either configuration or something about the user/environment it doesn't like, as I haven't heard of this occurring before. 
What you may want to try is if you use UPN like user@domain.com if it makes a difference instead of Domain\User.
If that doesn't work you may want to call in to the sysmgmt/openmanage group so they can directly analyze the issue.
 
Let me know what you see.
 
 
 

DELL-Chris H

Social Media and Communities Professional

Dell Technologies | Enterprise Support Services

#IWork4Dell

Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!

October 19th, 2023 08:15

Our domain refuses all LM- and NTLM-traffic but NTLMv2. Maybe that's the problem. The OME appliance is a Linux machine outside the domain, so, the authentication against the domain runs with NTLM per design. OME must use NTLMv2, otherwise the authentication will fail.

A manual login from an Ubuntu 2204 LTS via ssh outside the domain in our environment runs without problems.

On a windows server I see still this error:

sshd: fatal: ga_init, unable to resolve user win\\username

where username ist the name of the service account used by OME. The double backslash is strange. I think, this causes the problem.

Greetings Barbara

Moderator

 • 

3.2K Posts

19-10-2023 01:55 PM

Hi,

thank you for your reply I would appreciate if you tell us the results from the call with our sysmgmt/openmanage group.

 

with kind regards Martin

DELL-Martin S

Social Media and Communities Professional

Dell Technologies | Enterprise Support Services

#IWork4Dell

Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!

No Events found!

Top