I have been using WeOnlyDo.Client.SFTP to send files with no issues for over a year, however, now I had to migrate component to a new server as well as sending files to a different domain. It is windows service that sends the files at particular time. At appropriate time service logs in to remote site with ssh key but fails to send the file. Every time I restart the service same minute it has to send file, it sends the file just fine. Please take a look at the debug file output. May be you can point me to where my problem may be.


Connect::start
Connect::BeginConnect
Connect:end
ConnectNotification:start
MethodNotification:start
MethodNotification:ExtendedStates.Connecting
ConnectNotification:end
ReceiveNotification:start
ReceiveNotification:ExchangingIdentification
EndReceive before
ReceiveNotification:ExchangingIdentification received 14 bytes
ExchangeIdentification:start
ExchangeIdentification data: SSH-2.0-SSHD

ExchangeIdentification:sent SSH-2.0-WeOnlyDo.Net

ExchangeIdentification:end
ReceiveNotification:start
ReceiveNotification:Default
Received 296 bytes
CipherInbuf len = 296
DoSSH2Packet:start type=20
KexInit:start
Startpacket SSH2_MSG_KEXINIT
SendPacket:start
SendPacket:end
Startpacket SSH2_MSG_KEXDH_INIT
SendPacket:start
SendPacket:end
KexInit:end
DoSSH2Packet:end
SendNotification:start
MethodNotification:start
MethodNotification:ExtendedStates.Default
SendNotification:end
SendNotification:start
MethodNotification:start
MethodNotification:ExtendedStates.Default
SendNotification:end
ReceiveNotification:start
ReceiveNotification:Default
Received 704 bytes
CipherInbuf len = 704
DoSSH2Packet:start type=31
KexReply:start
CheckHostKey2:start
CheckHostKey2:end
Startpacket SSH2_MSG_NEWKEYS
SendPacket:start
SendPacket:end
KexInit:end
DoSSH2Packet:end
SendNotification:start
MethodNotification:start
MethodNotification:ExtendedStates.Default
SendNotification:end
ReceiveNotification:start
ReceiveNotification:Default
Received 16 bytes
CipherInbuf len = 16
DoSSH2Packet:start type=21
NewKeys:start
Startpacket SSH2_MSG_SERVICE_REQUEST
SendPacket:start
SendPacket:end
NewKeys:end
DoSSH2Packet:end
SendNotification:start
MethodNotification:start
MethodNotification:ExtendedStates.Default
SendNotification:end
ReceiveNotification:start
ReceiveNotification:Default
Received 52 bytes
CipherInbuf len = 52
DoSSH2Packet:start type=6
SendAuth:start
SendAuth:trying 'none'
SendPacket:start
SendPacket:end
SendAuth:end
DoSSH2Packet:end
SendNotification:start
MethodNotification:start
MethodNotification:ExtendedStates.Default
SendNotification:end
ReceiveNotification:start
ReceiveNotification:Default
Received 52 bytes
CipherInbuf len = 52
DoSSH2Packet:start type=51
CheckUserAuth:start
SendAuth:start
SendAuth:trying pubkey
SendPacket:start
SendPacket:end
SendAuth:end
DoSSH2Packet:end
SendNotification:start
MethodNotification:start
MethodNotification:ExtendedStates.Default
SendNotification:end
ReceiveNotification:start
ReceiveNotification:Default
Received 196 bytes
CipherInbuf len = 196
DoSSH2Packet:start type=60
SendPacket:start
SendPacket:end
DoSSH2Packet:end
SendNotification:start
MethodNotification:start
MethodNotification:ExtendedStates.Default
SendNotification:end
ReceiveNotification:start
ReceiveNotification:Default
Received 36 bytes
CipherInbuf len = 36
DoSSH2Packet:start type=52
CheckUserAuth:start
SendPacket:start
SendPacket:end
CheckUserAuth:end
DoSSH2Packet:end
SendNotification:start
MethodNotification:start
MethodNotification:ExtendedStates.Default
SendNotification:end
ReceiveNotification:start
ReceiveNotification:Default
Received 52 bytes
CipherInbuf len = 52
DoSSH2Packet:start type=91
SendChanRequest:start
SendChanRequest:end
StartShell:start
Startpacket SSH2_MSG_CHANNEL_REQUEST
SendPacket:start
SendPacket:end
StartShell:end
DoSSH2Packet:end
SendNotification:start
MethodNotification:start
MethodNotification:ExtendedStates.Default
SendNotification:end
ReceiveNotification:s

Hi,

Unfortunately, the log doesn't help us much in SFTP, since whole communication is encrypted.

What version of the component do you use?

Does it work using other clients, or the same issue occurs?

What server are you connecting to?

Is there any chance we could connect and try it out on our side? If that's possible, you can send us the info needed to connect to

Regards,
Damba

I am using 3.3.0.66 version.
I have WSCP installed on the same box and have no issues uploading files.
I do not know what is on the other end.
Sorry, I can not get access to the server.
What are commone casues for this error?
ReceiveNotification:EXCEPTION Failed to read b

Quote:

---

Hi,

Unfortunately, the log doesn't help us much in SFTP, since whole communication is encrypted.

What version of the component do you use?

Does it work using other clients, or the same issue occurs?

What server are you connecting to?

Is there any chance we could connect and try it out on our side? If that's possible, you can send us the info needed to connect to

Regards,
Damba

---

Hi,


Unfortunately we need more information in order to identify why this problem occur.

Can you please go to command prompt and type:

telnet your.hostname 22

and send us first line returned. That should give us information about your server.

Also did you maybe try to upload file using our samples? You can find samples in component Samples folder.

Please make sure that you are using full local and remote path inside PutFile Method.


Regards,
Drazen

this is what server returns
SSH-2.0-SSHD

This is how I use put file method
sftpClient.PutFile(localFile, remotePath);

where localfile = C:Folder1file
remotePath = /Inbound/Encrypted/file

Quote:

---

Hi,


Unfortunately we need more information in order to identify why this problem occur.

Can you please go to command prompt and type:

telnet your.hostname 22

and send us first line returned. That should give us information about your server.

Also did you maybe try to upload file using our samples? You can find samples in component Samples folder.

Please make sure that you are using full local and remote path inside PutFile Method.


Regards,
Drazen

---

Hi,

Did you perhaps try what Drazen suggested about our samples?

Also, when connecting using WinSCP, can you please make sure that "Fallback to SCP" is disabled and try then?

Can you also please try the same using the latest version? Does the same occur?

Regards,
Damba

I did more logging on my end and turns out remote path was too long. I also have compression set to 0.
It is working ok.

Thanks for your support.

Quote:

---

Hi,

Did you perhaps try what Drazen suggested about our samples?

Also, when connecting using WinSCP, can you please make sure that "Fallback to SCP" is disabled and try then?

Can you also please try the same using the latest version? Does the same occur?

Regards,
Damba

---