forums › forums › Monyog › Using Monyog › Cannot Connect Via Ssh To Windows Server
- This topic is empty.
-
AuthorPosts
-
-
February 17, 2012 at 6:48 pm #12601paulohm1Member
MONYog is installed on a Windows Server 2003. The SSH Host server is Windows Server 2008 R2. I am able to connect using putty from the Monyog server to the SSH host with no issues. However, when attempting to Test the connection through Monyog, I get the popup saying “Failed to connect to SFTP:” but there is no additional description after this.
I tried using the key in ppk format as well as openssh format, but neither seems to work.
My Monyog log file shows this:
Code:[4.81] [2012-02-17 13:46:39] [Server: XXX] srcysshsession.cpp(154) ErrCode:-1 ErrMsg:Unable to create Key file from buffer
[4.81] [2012-02-17 13:46:39] [Server: XXX] connectionmgr.cpp(2158) ErrCode:-1 ErrMsg:What does this error mean?
-
February 18, 2012 at 8:59 am #33142peterlaursenParticipant
Please tell:
1) What is the SSH sofware/service you have installed on the 2008 machine. Is it Cygwin or something else ('Tunnellier' or whatever) ? You may need to configure SFTP options here.
2) Since the error is SFTP related you you try a common GUI SFTP client, such as Filezilla or WinSCP? I think they will not be able to connect for either?
3) maybe you could also try to allow SSH with simple password authentication (no keys) just to check if it is related to this.
But I would try 2) first. If Filezilla etc. cannot connect either, the problem probably is that SFTP is not configured in in the SSHD configuration.
I cannot detail the error message. I am not well-versed in the internals of the SSH library we use. So the reply to this will ahve to wait till Monday, I'm afraid.
And with MONyog you shall use keys in OpenSSH format, BTW.
-
February 18, 2012 at 1:08 pm #33143paulohm1Member
I have tried WinSCP and am able to connect OK.
The SSH server software on the 2008 machine is copSSH, which is a packaging of cygwin.
I will not be able to try password-only authentication until monday, however.
Please let me know if there is anything else I can try.
-
February 21, 2012 at 4:05 am #33144MaheshMember
We are using CopSSH on Windows 7 and able to connect successfully.
You need to “Activate a user” –> Select a User from dropdown menu (Lists all windows users associated for this machine) and uncheck an option called
“Create keys for public authentication” –> Click on Next (see attached screenshot)
Now SSH user is activated.
Now, In MONyog Register/Edit Server –> Give SSH details username and password should match with Windows authentication and Click on
“Test Connection”, What does this return ?
-
February 21, 2012 at 4:54 pm #33145paulohm1MemberQuote:Give SSH details username and password should match with Windows authentication
I am using Public/Private key pair with CopSSH (not password authentication). When I select “key” in Monyog, I do not have an option for password. I enter my 'username' and 'passphrase' and this is when I get the error “Failed to connect to SFTP:” without any details as described above.
-
February 22, 2012 at 4:56 am #33146MaheshMember
You have to select Key based authentication in MONyog as well.
Please see these screen shot attached here with, Which will help you in using Key based authentication.
First you have to copy-paste content of private key in MONyog –> Private key section.
Give Passphrase and click on “Test Connection”.
-
February 22, 2012 at 7:45 pm #33147paulohm1Member
I was able to get the connection to work from MONYog to the DB server when using Password Authentication. So it seems like it is an issue with the format of my private key that I am pasting into Monyog. Am I able to use a key that I generate with Puttygen and then convert to Openssh format using puttygen (this is what I have tried in the past and has not worked)? I am unable to create the key using CopSSH on the DB server for unrelated reasons. Is there anything else I can use to create the keys if puttygen does not work?
-
February 23, 2012 at 4:01 am #33148MaheshMember
MONyog supports only standard OpenSSH keys and keys generated using Puttygen or any other tool does not work.
-
February 24, 2012 at 12:49 pm #33149paulohm1Member'Mahesh' wrote:
MONyog supports only standard OpenSSH keys and keys generated using Puttygen or any other tool does not work.
Are there any tools that you recommend to generate standard OpenSSH keys that will work with MONYog? I had previously only ever used PuttyGen and then converted the ppk to OpenSSH, but I guess you're saying that doesn't work?
-
February 24, 2012 at 3:29 pm #33150peterlaursenParticipant
Do you have a Cygwin command line?
-
February 24, 2012 at 8:13 pm #33151paulohm1Member
I tried creating the key with cygwin using the following command:
ssh-keygen -b 2048
I copied the .pub key that was created into authorized_keys on the server and copied the private key into monyog, but I am still unable to connect.
However, using the ssh client built into cygwin, I am able to connect using the same user and private key, so I know the public/private key authentication is working.
-
February 27, 2012 at 6:50 am #33152MaheshMember
Please create a ticket by sending an email to “[email protected]”
We will discuss regarding this in ticket system and if required arrange a screen sharing session.
-
February 27, 2012 at 2:47 pm #33153paulohm1Member'Mahesh' wrote:
Please create a ticket by sending an email to “[email protected]”
We will discuss regarding this in ticket system and if required arrange a screen sharing session.
Thanks, I created the ticket
-
February 27, 2012 at 3:40 pm #33154peterlaursenParticipant
.. and we have received it.
-
October 24, 2012 at 4:00 pm #33155dvanhollenParticipant
What was the resolution here? I'm experiencing a similar issue with an SSH connection between two Linux hosts, despite being able to connect @ commandline..
-
October 24, 2012 at 4:13 pm #33156paulohm1Member
I was never able to get this setup working as I wanted. I was told by support that they were unable to replicate the issue and that I should attempt to recreate all certificates, but still was unable to fix it. I circumvented the issue by creating a VPN between the two networks and making the connection that way.
-
-
AuthorPosts
- You must be logged in to reply to this topic.