![]() So this points at the synology not being able to agree with the client and just terminating the connection.ĭigging in furhter & comparing the algorithm lists sent by each, it seems they could not agree on a common cipher. The first FIN comes from the synology box, followed by an ACK & FIN from the CUCM. The capture shows 13 packets, where there is the initial handshake, then the SSH protocol identifiers, Key Exchange Inits, and then is closed. I did a packet capture on this, which ironically involved me using SFTP to upload the capture file to a Linux box. I also know it's not "too slow" because that message is returned almost instantly - no waiting on timeouts. I have tried all sorts of values for the path as that is known to be very picky. The sollution is simple, to reconnect: Drive Client settings - edit connection, enter password and everyting is back to normal. He also has a 1Gbps fiber internet connection at his place. From time to time, several months, Drive Client (Windows 10) displays 'Status abnormal - SSL certificate has been changed'. I installed Synology Drive client on my home computer and my coworker's computer at his place also. I have a 1Gbps internet fiber connection at home. Update failed : Unable to access SFTP server or SFTP server too slow to respond. 1 Hey all, This problem drives me crazy Just bought a DS1621+ on Raid 5. But it seems that like you, Im using the ondemand sync for the my drive folder, and a full synchro for all other. Like you, I have always had the issue with 'My Drive' the other team folders are synching without any issues. ![]() Unable to save Backup Device successfully. Im currently using client 2.0.2 but this basically has never worked for me. I am trying to set up the same thing here.Įverything looks good via WinSCP, can log in upload & download files, create directories, etc. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |