Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: Authentification failure at log in

You should ask the server administrator to check the log of the SSH server for reason of the failure. I cannot tell why the server denies you to log in.
lanxle

Authentification failure at log in

I'm not very well-versed on computers and I've only recently begun using WinSCP, so please bear with me.

I've recently graduated college. When I got home, my computer broke, so I downloaded WinSCP to my brother's computer to access the school server where I keep some of my stuff. When I go to log in on the latest version, 3.6.1, there seems to be an authentification failure and it prompts me for my session password. This is the same as my normal password as I have gathered from other posts. The server refuses to let me on and gives me this message.

_________________________________________________

Authentication log (see session log for details):
Using username "lanxle".
Access denied
Access denied

Server sent disconnect message
type 2 (SSH_DISCONNECT_PROTOCOL_ERROR):
"Too many authentication failures for lanxle"

_________________________________________________

So I enabled the logs so that I could see what was going on.

_________________________________________________

. ----------------------------------------------------
. WinSCP Version 3.6.1 (Build 221) (OS 5.1.2600 Service Pack 1)
. Login time: Wednesday, June 09, 2004 9:21:54 PM
. ----------------------------------------------------
. Session name: lanxle@www.sccs.swarthmore.edu
. Host name: www.sccs.swarthmore.edu (Port: 22)
. User name: lanxle (Password: Yes, Key file: No)
. Transfer Protocol: SFTP (SCP)
. SSH protocol version: 2; Compression: No
. Agent forwarding: No; TIS/CryptoCard: No; KI: Yes; GSSAPI: No
. Ciphers: aes,blowfish,3des,WARN,des; Ssh2DES: No
. Ping type: -, Ping interval: 30 sec; Timeout: 15 sec
. SSH Bugs:
. Proxy: none
. Return code variable: Autodetect; Lookup user groups: Yes
. Shell: default, EOL: 0
. Local directory: default, Remote directory: home, Update: No, Cache: Yes
. Cache directory changes: Yes, Permanent: Yes
. Clear aliases: Yes, Unset nat.vars: Yes, Resolve symlinks: Yes
. Alias LS: No, Ign LS warn: Yes, Scp1 Comp: No
. ----------------------------------------------------
. Looking up host "www.sccs.swarthmore.edu"
. Connecting to 130.58.218.5 port 22
. Server version: SSH-2.0-OpenSSH_3.4p1 Debian 1:3.4p1-1.woody.3
. We claim version: SSH-2.0-WinSCP-release-3.6.1
. Using SSH protocol version 2
. Doing Diffie-Hellman group exchange
. Doing Diffie-Hellman key exchange
. Host key fingerprint is:
. ssh-rsa 1024 32:5d:5e:f9:fd:ec:f3:48:f3:7f:ef:f0:7d:31:dc:b6
. Initialised AES-256 client->server encryption
. Initialised AES-256 server->client encryption
! Using username "lanxle".
. Keyboard-interactive authentication refused
. Session password prompt (lanxle@www.sccs.swarthmore.edu's password: )
. Using stored password.
. Sent password
! Access denied
. Access denied
. Keyboard-interactive authentication refused
. Session password prompt (lanxle@www.sccs.swarthmore.edu's password: )
. Asking user for password.
. Sent password
! Access denied
. Access denied
. Received disconnect message (SSH_DISCONNECT_PROTOCOL_ERROR)
. Disconnection message text: Too many authentication failures for lanxle
. Server sent disconnect message
. type 2 (SSH_DISCONNECT_PROTOCOL_ERROR):
. "Too many authentication failures for lanxle"
* (ESshFatal) Authentication failed.
* Authentication log (see session log for details):
* Using username "lanxle".
* Access denied
* Access denied
*
* Server sent disconnect message
* type 2 (SSH_DISCONNECT_PROTOCOL_ERROR):
* "Too many authentication failures for lanxle"
__________________________________________________

I am unclear as to whether this is a problem with the program or the server at my alma mater. In any case, I have also downloaded PuTTY and attempted to log on there. It did not work.

However, when logging on via the Java applet on the college website, I was allowed in. So I know that the password is correct and I still have an active account. Thank you very much for your time.