Forum » Support and Bug Reports »

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

anup.ramjeet.singh

Winscp Error

. 2016-11-23 22:25:02.007 Timeout waiting for network events
. 2016-11-23 22:25:02.507 Pooling for data in case they finally arrives
. 2016-11-23 22:25:02.507 Looking for network events
. 2016-11-23 22:25:02.507 Timeout waiting for network events
. 2016-11-23 22:25:03.020 Pooling for data in case they finally arrives
. 2016-11-23 22:25:03.020 Looking for network events
. 2016-11-23 22:25:03.020 Timeout waiting for network events
. 2016-11-23 22:25:03.521 Pooling for data in case they finally arrives
. 2016-11-23 22:25:03.521 Looking for network events
. 2016-11-23 22:25:03.521 Timeout waiting for network events
. 2016-11-23 22:25:04.034 Pooling for data in case they finally arrives
. 2016-11-23 22:25:04.034 Looking for network events
. 2016-11-23 22:25:04.034 Timeout waiting for network events
. 2016-11-23 22:25:04.534 Pooling for data in case they finally arrives
. 2016-11-23 22:25:04.534 Looking for network events
. 2016-11-23 22:25:04.534 Timeout waiting for network events
. 2016-11-23 22:25:05.048 Pooling for data in case they finally arrives
. 2016-11-23 22:25:05.048 Looking for network events
. 2016-11-23 22:25:05.048 Timeout waiting for network events
. 2016-11-23 22:25:05.548 Pooling for data in case they finally arrives
. 2016-11-23 22:25:05.548 Looking for network events
. 2016-11-23 22:25:05.548 Timeout waiting for network events
. 2016-11-23 22:25:06.062 Pooling for data in case they finally arrives
. 2016-11-23 22:25:06.062 Looking for network events
. 2016-11-23 22:25:06.062 Detected network event
. 2016-11-23 22:25:06.062 Enumerating network events for socket 908
. 2016-11-23 22:25:06.062 Enumerated 1 network events making 1 cumulative events for socket 908
. 2016-11-23 22:25:06.062 Data has arrived, closing query to user.
. 2016-11-23 22:25:06.067 Handling network read event on socket 908 with error 0
. 2016-11-23 22:25:06.067 Offered public key
. 2016-11-23 22:25:06.067 Waiting for the server to continue with the initialization
. 2016-11-23 22:25:06.067 Looking for incoming data
. 2016-11-23 22:25:06.067 Looking for network events
. 2016-11-23 22:25:06.335 Detected network event
. 2016-11-23 22:25:06.335 Enumerating network events for socket 908
. 2016-11-23 22:25:06.335 Enumerated 1 network events making 1 cumulative events for socket 908
. 2016-11-23 22:25:06.335 Handling network read event on socket 908 with error 0
! 2016-11-23 22:25:06.335 Server refused our key
. 2016-11-23 22:25:06.368 Server refused our key
. 2016-11-23 22:25:06.368 Selecting events 0 for socket 908
. 2016-11-23 22:25:06.368 Disconnected: No supported authentication methods available (server sent: publickey)
* 2016-11-23 22:25:06.423 (EFatal) Disconnected: No supported authentication methods available (server sent: publickey)
* 2016-11-23 22:25:06.423 Authentication log (see session log for details):
* 2016-11-23 22:25:06.423 Using username "anuprs".
* 2016-11-23 22:25:06.423 Server refused our key.
* 2016-11-23 22:25:06.423
* 2016-11-23 22:25:06.423 Authentication failed.

Generated the private key from the existing private key using a tool putty key generater.

Getting an error
martin

Re: login error when pageant has 2 keys stored

It is possible that the server does not allow you more that one authentication attempt. Try to specify the correct key explicitly on login dialog.
ths

login error when pageant has 2 keys stored

Hallo,


I have a problem with 3.8.2 and 4.0.3. If I load only one key in pageant I can login to an AIX machine.
If pageant has 2 keys in memory, the connection fails.
Strangely enough this only happens for one machine, a similar machine with same AIX (5200-02) and sshd version does not exhibit this behaviour, I can login there even if pageant has 2 keys in memory.
In "View keys" the wrong key which does not match the public key on AIX is listed first, but I cannot tell if this matches the "key #0" from the logfile below (although I guess so): 

Connecting to 10.132.11.132 port 22

Server version: SSH-1.99-OpenSSH_3.4p1

We claim version: SSH-2.0-WinSCP_release_4.0.3

Using SSH protocol version 2

Doing Diffie-Hellman group exchange

Doing Diffie-Hellman key exchange

Host key fingerprint is:

ssh-rsa 1024  xx:xx:...

Initialised AES-256 client->server encryption

Initialised HMAC-SHA1 client->server MAC algorithm

Initialised AES-256 server->client encryption

Initialised HMAC-SHA1 server->client MAC algorithm

Using username "root".

Reading private key file "C:\home\ths\username.ppk"

Pageant is running. Requesting keys.

Pageant has 2 SSH-2 keys

Trying Pageant key #0

Server unexpectedly closed network connection

(ESshFatal) Server unexpectedly closed network connection

Authentication log (see session log for details):

Using username "root".



Authentication failed.

Documentation

Support

Associations

Follow Us