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: Can connect to sftp server from computer A but not computer B

You need to contact the server administrator.
alidayvn

Can connect to sftp server from computer A but not computer B

This is more of an advanced networking question but I'm running out of ideas.
We have to dump some data to a server we don't control, running sftp. From home, cable internet, winscp does fine. From work, the connection negotiates the encryption, then sends 1 sent encrypted packet, 1 received, then errors out.

The error I get is:
. 2019-04-22 14:46:11.907 Password authentication failed
! 2019-04-22 14:46:11.907 Access denied
. 2019-04-22 14:46:11.938 Server offered these authentication methods:
. 2019-04-22 14:46:11.938 Selecting events 0 for socket 1504
. 2019-04-22 14:46:11.938 Disconnected: No supported authentication methods available (server sent: )
* 2019-04-22 14:46:11.954 (EFatal) Disconnected: No supported authentication methods available (server sent: )
* 2019-04-22 14:46:11.954 Authentication log (see session log for details):
* 2019-04-22 14:46:11.954 Using username "redacted".
* 2019-04-22 14:46:11.954 Access denied.
* 2019-04-22 14:46:11.954
* 2019-04-22 14:46:11.954 Authentication failed.

It seems like the server is not sending any authentication methods.


From home the log looks different, and has authentication methods and then uses them and logs in fine.


Server offered these authentication methods: publickey,password
.


so, why would one network/computer/winscp get nothing, and one get publickey,password?

another question, I used wireshark to grab the packets, is there a way to use the key data from winscp to decode those packets and see what's going wrong?
Thanks,
Aaronski