Highlighted
Absent Member.. NGT Absent Member..
Absent Member..
2107 views

Issue with connecting using SSH and Secure copy to a sftp server

Hi All

 

We were using telnet and ftp earlier in the previous ppm version and now have upgraded to 9.1 and are asked to use SSH and secure copy.

 

So the open SSh has been installed and we are able to use the command line to initiate a connection to another server however when we try to connect to a sftp site we are getting the following error when doing a check for SSH2 or Secure copy2

 

SSH version sent to remote host: SSH-2.0-1.0 Kintana SSH client
Initiating key exchange.
Succeeded in key exchange.
Authenticating user.
ERROR: java.io.IOException: All SSH authentication methods failed.  Check the Key Identity file or password.   (KNTA-10903)

 

Has anyone ever encountered this issue - if yes can you please give some guidance as to how to get over this issue?

 

Regards

Nishant GT

Tags (2)
0 Likes
4 Replies
Jason Nichols K Absent Member.
Absent Member.

Re: Issue with connecting using SSH and Secure copy to a sftp server

What version of PPM did you upgrade from? I've seen this message a couple of different times with different solutions for each scenario. If memory serves, I have seen this after an upgrade from a pre-8.x version to 8.x or higher. There's a new field added to the Environment Definition for encoding type. While it may look like there is a value in Workbench, there isn't one store in the database. You would need to set that to some value and save it. If it is showing the encoding to you intend to use, change it to some other value, save it, then change it to the correct value and save one more time.
Established Member.. Utkarsh_Mishra
Established Member..

Re: Issue with connecting using SSH and Secure copy to a sftp server

This issue is observed when user/group entiry is missing from the SSH passsword file.

 

 

In you SSH installation directory Identify the file with Name = "passwd"

 

Thenfollow below step

 

cd c:/cygwin/etc (or change the directory to where the passwd file is stored)

 

Finally run

 

mkpasswd -d <Windows_Domain_name> -u <Windows_Login_ID> >> passwd

 

example

mkpasswd -d xyx -u umishra >> passwd

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
Absent Member.. NGT Absent Member..
Absent Member..

Re: Issue with connecting using SSH and Secure copy to a sftp server

Hi All

 

thanks for your response. Currently we are in 9.1 version and moved from 7.5.

 

We have managed to solve the issue that was raised yesterday and now are able to get the message as user authenticated when we do a check from the workbench, however we are getting the following new issue.

 

SSH version sent to remote host: SSH-2.0-1.0 Kintana SSH client
Initiating key exchange.
Succeeded in key exchange.
Authenticating user.
Succeeded in authenticating user.
Opening channel.
Attempting to negotiate the terminal type.
Sent a PTY request with terminal type dumb.
The PTY request for a dumb terminal type was not successful.
ERROR: java.io.IOException: pty-req failed

 

Have been trying to resolve this pty error and if anyone has any input regarding this, it'll be really appreciated.

 

regards

Nishant GT

0 Likes
Established Member.. Utkarsh_Mishra
Established Member..

Re: Issue with connecting using SSH and Secure copy to a sftp server

This issue is obsereved when maximum invalid tries are exceeded in SSH.

 

The solution to this problem is the restrat the machine/serve (i.e. machine on which PPM is hosted)

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.