You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I upgraded to the 4166 build and immediately had problems connected to FTP sites. Our corporate site contains the directory structure '/files/Tools' but after connecting to the site using the new build I can navigate into '/files' but when I try to navigate into the tools subfolder it fails telling me the directory does not exist. Log snip below. Looks like it is putting the "files" name in the string twice - is it using it instead of the server name? Very strange.
Note I tried same transfer using a different tool (net2ftp) and it works file. Also, the build previous to 4166 I was using worked fine.
Any help appreciated.
200 NOOP command successful.
STAT //files/files/Tools
211-status of //files/files/Tools:
550 //files/files/Tools: No such file or directory.
211 End of Status
CWD //files/files/Tools
550 //files/files/Tools: No such file or directory.
The text was updated successfully, but these errors were encountered:
Further info - I can connect to any directory (in my example, /files/Tools) if I set it as the "initial directory" during the connection. But once in a directory I can not use Cyberduck to navigate / drill-down into sub folders.
I upgraded to the 4166 build and immediately had problems connected to FTP sites. Our corporate site contains the directory structure '/files/Tools' but after connecting to the site using the new build I can navigate into '/files' but when I try to navigate into the tools subfolder it fails telling me the directory does not exist. Log snip below. Looks like it is putting the "files" name in the string twice - is it using it instead of the server name? Very strange.
Note I tried same transfer using a different tool (net2ftp) and it works file. Also, the build previous to 4166 I was using worked fine.
Any help appreciated.
The text was updated successfully, but these errors were encountered: