0 votes
by (120 points)

No matter what password I set and attempt to use it fails, I've tried winscp, filezilla, and connecting from Linux

I've tried it with -vvv and PubkeyAuthentication=no

I'm connecting from a public IP natted to a private one, so the IP in the Tiny SFTP window does not match the user@ip when I'm trying to log on

I'm using sftp -o Port=2222 user@publicip no private keys nothing

It askes for a password 3 times with no error then asks for a password for user@publicip and replies with Permission Denied

With verbose logging turned on in TinyFTP I get response not accepted the first 3 times followed by Invalid password the next 3 times

Applies to: Rebex SFTP

1 Answer

0 votes
by (1.1k points)

Hi,

Have you made any changes to the configuration file (except for the password)? Can you connect to the server from the same machine without any issues?

by (120 points)
I tried from the same machine and it fails. I deleted the existing files and reextracted them and attempted a connection using all defaults tester/password over port 2222 and the login fails. This is a Windows XP workstation.
by (15.2k points)
Hi,
do you get any error in Rebex Tiny SFTP Server application itself?  Can you please share the log from the application window with us?
by (120 points)
edited by
Sure, here you go, connect from a local client, with stored password, including a manual password attempt.

Log level changed to Verbose.
08:53:26.728 Info SSH: Session 1: Connection closed by the remote host.
08:53:26.728 Info Server: Session 1: Closed connection from 127.0.0.1:2831.
08:53:28.400 Debug Server: Accepted connection from 127.0.0.1:2853.
08:53:28.400 Info Server: Session 2: Started on connection from 127.0.0.1:2853.
08:53:28.400 Debug SSH: Session 2: Local SSH version: SSH-2.0-RebexSSH_5.0.8020.0
08:53:28.416 Debug SSH: Session 2: Remote SSH version: SSH-2.0-WinSCP_release_5.19.6
08:53:28.416 Debug SSH: Session 2: Performing algorithm negotiation and key exchange.
08:53:28.416 Verbose SSH: Session 2: Sent packet SSH_MSG_KEXINIT (1031 bytes).
08:53:28.416 Verbose SSH: Session 2: Received packet SSH_MSG_KEXINIT (1177 bytes).
08:53:28.416 Debug SSH: Session 2: Performing key exchange using diffie-hellman-group-exchange-sha256 with ssh-rsa.
08:53:28.416 Verbose SSH: Session 2: Received packet SSH_MSG_PACKET34 (13 bytes).
08:53:28.416 Verbose SSH: Session 2: Sent packet SSH_MSG_KEXDH_REPLY (1034 bytes).
08:53:28.853 Verbose SSH: Session 2: Received packet SSH_MSG_PACKET32 (517 bytes).
08:53:31.603 Verbose SSH: Session 2: Sent packet SSH_MSG_PACKET33 (1075 bytes).
08:53:31.603 Verbose SSH: Session 2: Sent packet SSH_MSG_NEWKEYS (1 bytes).
08:53:31.603 Debug SSH: Session 2: Cipher info: SSH 2.0, diffie-hellman-group-exchange-sha256, ssh-rsa, aes256-ctr/aes256-ctr, hmac-sha2-256/hmac-sha2-256
08:53:32.119 Verbose SSH: Session 2: Received packet SSH_MSG_NEWKEYS (1 bytes).
08:53:32.119 Debug SSH: Session 2: Key exchange finished.
08:53:32.119 Verbose SSH: Session 2: Received packet SSH_MSG_SERVICE_REQUEST (17 bytes).
08:53:32.119 Debug SSH: Session 2: Performing authentication.
08:53:32.119 Verbose SSH: Session 2: Sent packet SSH_MSG_SERVICE_ACCEPT (17 bytes).
08:53:32.134 Verbose SSH: Session 2: Received packet SSH_MSG_USERAUTH_REQUEST (37 bytes).
08:53:32.134 Debug SSH: Session 2: Starting authentication as 'tester' for 'ssh-connection'.
08:53:32.134 Verbose SSH: Session 2: Sent packet SSH_MSG_USERAUTH_FAILURE (35 bytes).
08:53:32.134 Verbose SSH: Session 2: Received packet SSH_MSG_USERAUTH_REQUEST (61 bytes).
08:53:32.134 Verbose SSH: Session 2: Sent packet SSH_MSG_PACKET60 (32 bytes).
08:53:32.150 Verbose SSH: Session 2: Received packet SSH_MSG_IGNORE (152 bytes).
08:53:32.150 Verbose SSH: Session 2: Received packet SSH_MSG_USERAUTH_INFO_RESPONSE (17 bytes).
08:53:32.150 Info Server: Session 2: Authentication for 'tester' failed.
08:53:32.150 Debug SSH: Session 2: Response from 'tester' not accepted.
08:53:32.150 Verbose SSH: Session 2: Sent packet SSH_MSG_USERAUTH_FAILURE (35 bytes).
08:53:32.166 Verbose SSH: Session 2: Received packet SSH_MSG_USERAUTH_REQUEST (61 bytes).
08:53:32.166 Verbose SSH: Session 2: Sent packet SSH_MSG_PACKET60 (32 bytes).
08:53:37.103 Verbose SSH: Session 2: Received packet SSH_MSG_IGNORE (152 bytes).
08:53:37.103 Verbose SSH: Session 2: Received packet SSH_MSG_USERAUTH_INFO_RESPONSE (17 bytes).
08:53:37.103 Info Server: Session 2: Authentication for 'tester' failed.
08:53:37.103 Debug SSH: Session 2: Response from 'tester' not accepted.
08:53:37.103 Verbose SSH: Session 2: Sent packet SSH_MSG_USERAUTH_FAILURE (35 bytes).
08:53:37.119 Verbose SSH: Session 2: Received packet SSH_MSG_USERAUTH_REQUEST (61 bytes).
08:53:37.119 Verbose SSH: Session 2: Sent packet SSH_MSG_PACKET60 (32 bytes).
by (120 points)
I tested from a windows 10 machine and had no issues. This is almost certainly an XP related issue.
by (15.2k points)
Hi, thank you for the log. Unfortunately, it does not show any unexpected error.
Please correct my understanding of your setup to simulate it on our side. Tiny SFTP Server runs on Windows XP machine. You are able to log in from Windows 10 machine, logging in fail from a Linux machine? Both machines communicates with Tiny SFTP Server on Windows XP?
As I understand your setup that way I set up a Windows XP machine, run Tiny SFTP Server in it to try to get that issue. I could connect form Windows 10 as you did and also from a Linux OS. The only time I got "Authentication failed" error was when I set wrong password. You wrote that you tried authenticate with some stored password. Is the stored password in sync with the password displayed in Tiny SFTP Server application window (which displays it from RebexTinySftpServer.exe.config file) ? What about setting the password in RebexTinySftpServer.exe.config file to 'a' (yes, one letter 'a')? Is it still not possible for you to authenticate?
by (120 points)
Please ignore my Windows 10 comment, that was a separate install of the server so I had a control environment to compare to.

Currently from the Windows XP workstation I am unable to make a local connection. I've gone so far as to reextract the server files to test with a fresh install. I've tested with a password of "1" as well. All connection attempts fail.

I've since installed another product CoreFTP Server and I'm using that as my solution. I've been able to make an SFTP connection, authenticate, and get files on the same Windows XP workstation.

I'm willing to continue tested Tiny SFTP though if that's useful.
by (15.2k points)
Hi, thank you for your offer. Since I was not able to reproduce the issue, I was able to make local connection on WindowsXP and also from remote Linux or Windows 10 system, you confirmed that you tried with fresh "install" and also with a simple password with no luck, I am out of possibilities what to try next.

Thank you for letting us know, we are happy you found a solution which works for you. If you ever find out what the problem was, please let us know since it is clearly an environment issue we are unable to reproduce.
...