Direkt zum Inhalt

Need help debugging an ATI / FTP problem

Thread needs solution

Actually, I need recommendations on how to successfully interact with Acronis support concerning an FTP problem.

Sorry - long background paragraph follow.

A year ago I discovered that ATI (ATI 2017 back then) could not talk to a WD MyCloud Gen 2 FTP server.  People on the ATI 2017 forum confirmed that ATI would successfully talk with WD MC Gen 1 server, and I had no problem getting 3 other FTP clients to talk with the MyCloud server.  I spent a couple frustrating weeks trying to work with Acronis support but eventually gave up.  ATI successfully talks FTP with the WD MyBookLive devices I have so I stopped using the MyCloud.  Unfortunately,  Western Digital no longer sells MyBookLive (and transfers with MyCloud are much faster) so I want to try talking to Acronis support about this. 

When trying to establish an TP connection with the MyCloud server ATI displays the "Connection failed" message.  It looks just like a credentials problem, but a packet trace shows that the connection was actually established and the the client and server start talking.  But the ATI client issues the command "MLST /" and doesn't like the server's response: "550 Can't check for file existence".  (This may be a bug in the server.  I don't know..)  Clients that successfully communicate with the server issue  "MLSD" rather than "MLST /".  ATI also uses the "MLSD" command when talking with the MyBookLive server.

I have both WireShark and Windows Netsh traces that show the interaction but could not get Acronis support to look at them.  Is there another trace I can take that is more acceptable to Acronis support?  I don't particularly want a repeat of last year's runaround.

0 Users found this helpful

Patrick, one of the core issues that I am aware of with ATI and FTP is simply that it only supports the most basic implementation of FTP with no provision for using SFTP to secure the connection.

I did try to establish an FTP connection to my Synology NAS but gave up when no security or encryption type connections were possible and I did not want to have an open FTP server access open on the NAS.

I would suggest starting a private conversation with Slava on this issue who should be better placed to direct you to the right person in the Acronis development team.

Thanks for your comments, Steve.  A secure FTP option would be nice, but I'm willing to use old vanilla FTP on my local network for now.

I'll contact Slava.  Thanks.

I sent a note to Slava and have not heard back yet, but I also notice that the indecent report I thought I opened a year ago does not exist.  (Perhaps I'm remembering the unproductive incident report I opened with Western Digital.)  I've opened one with Acronis support now.  I'll see if this one goes anywhere.