Sie müssen die Benutzerberechtigungen zu analysieren Sie verwenden die wahrscheinlichste ist, dass es ist, oder gibt es eine Regel, eine Firewall im Netzwerk, der Zugriff verweigert.
Ich denke, die eher etwas Zugang oder Tür ist nicht in einer Netzwerk-Firewall freigegeben.
@ cjfranca: I have added exceptions both to Windows Firewall and AntiVir for FTP Voyager Scheduler.exe and ~Tray.exe - with no effect :-(
If I use the "download" action with "/*" - the Scheduler works fine and downloads all files in the / directory. Meaning, there's obviously no general access issue.
But if I use the "synchronize local folder" action with "/", I get the error message after Scheduler has sent the MLST command. ("/*" doesn't work either)
If I use the "synchronize local folder" action for another server with a subfolder to be synchronized, I just specify the subfolder name (no / or \ behind the folder name!) - and it works fine.
Now my conclusion is: Maybe the Scheduler cannot synchronize the root directory, because it does not accept an empty "File or Path on server" field?
Unfortunately I have no chance to get the content moved to a subfolder on the server...
Any idea if my guess can be right? any help?
Your guess is possible. Its worth checking out.
If you can't add a folder to the remote server, you can do a trial of serv-u, and try a different directory there.
Meanwhile I'm quite sure my guess is correct: for several other ftp servers I was able to synchronize subdirectories, but never the root directory. "." does not work, "/" does not work, "/*" does not work, blank does not work, and an empty parameter (which logically should be the correct setting!) is not accepted.
And I have even found a workaround: if any subdirectory is in the root folder, you can specify the root directory as "/subdirectory/.." - this works ok. Unfortunately the server directory I want to sync has no subdirectory :-(
Is there any chance that this issue with FTP voyager is fixed?