This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Problems logging into Serv-U MFT

First of all, thanks in advance for any help I may receive.

I am new to Serv-U MFT and got a problem that is baffling me.

I installed Serv-U on Windows Server 2016 with IIS and FTP installed.

Active Directory is enabled and configured on Serv-U with groups from the root of the domain down to where the users accounts reside.

I added the listener, SFTP using SSH, added the IP Access, and created an SSH Public/Private key.

On my PC, Windows 7, connected to the domain, I can launch FTP Voyager and configure a profile.

It connects perfectly using the Private key.  It sees the home folder and lists out the Virtual Paths, which work fine.

I have another PC, Windows 10.  The PC is fully patched, TLS1.0, TLS1.1 and SSL3 is disabled.  Logged into the PC with my Domain account.

I created the Same Profile, used the same Private Key and my Domain account.

It will not connect, keeps retrying.

It appears to accept the fingerprint and key, but it displays, Password not accepted.

I have tried several Domain Accounts, all within the same domain OU, and listed as a group in Serv-U.

Below is the log from the client;

STATUS>            
Retrying Connection (attempt 3)...

STATUS>            
Connecting to "10.70.25.14" on port 22.

STATUS>            
Connected to 10.70.25.14:22 from 10.70.29.97:63317.

STATUS>            
Negotiating SSH2 session with server...

STATUS>            
Client Identification: SSH-2.0-FTP Voyager_16.2.0.328

STATUS>            
Server Identification: SSH-2.0-Serv-U_15.1.6.25

STATUS>            
Initializing key exchange process...

STATUS>            
Selected key exchange algorithm: diffie-hellman-group1-sha1

STATUS>            
Host Key Fingerprint: D1:D2:61:D8:B1:A7:68:D3:2A:CB:88:A0:3A:85:1C:F4

STATUS>            
Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>            
Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>            
Selected public key protocol: ssh-dss

STATUS>            
Key exchange process successfully completed.

COMMAND>     
SSH_MSG_SERVICE_REQUEST: service: ssh-userauth

             
SSH_MSG_SERVICE_ACCEPT: service accepted

STATUS>            
Querying server for supported authentication methods

COMMAND>     
SSH_MSG_USERAUTH_REQUEST: user: dkohnken; service: ssh-connection; type: none

             
SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password

STATUS>            
Supported authentication methods: password

COMMAND>     
SSH_MSG_USERAUTH_REQUEST: user: dkohnken; service: ssh-connection; type:
password

ERROR>             
Password not accepted.

ERROR>             
Unable to login.

ERROR>             
Connection attempt failed.  Retrying in 3 seconds...

COMMAND>       SSH_MSG_DISCONNECT:
reason code 11; description: Password not accepted.

ERROR>             
The server has unexpectedly closed the connection.

Thank you

Doughk

  • You might want to create a support ticket for that as it might be a problem with software.  Although, you said it is only happening to one machine and that might indicate an environmental issue.


    Also, you might want to disable the IIS on the Serv-U Application Server as the Serv-U acts as it's own web server and IIS would only mess it up.

  • I found my problem.  It was a mistake I made regarding IP Access.

    When I setup IP Access, I defined several subnets access, but on the one I was testing with I defined it as 10.x.x.x/24.  In fact, it should have been 10.x.x.x/22.

    Because my test client was in the /22, it was being denied access to the SFTP Server.

    The failure message I got was "Password not accepted".  If it said, "IP Access Violation", it would have given my an idea where to look.

    This is now resolved.

  • That's a fair feedback.  Hoping someone would read this