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 have cyberduck connecting to a shared file resurce, while it does work for some machines not all.
I have a log of a user and it logs on ok, but then the prgram quits and issues error message "connection refused"
here is the comment from servu :
Based on this log, Serv-U is acting correctly - the last two numbers in the PASV response are for the PASV port, which is different per-session. However, in the case of the user who can't log in, the user quits right after logging in. You'll have to work with Cyberduck support to find out why it is using QUIT right after connecting.
Here is rhe log :
At the bottom is where the quit commend started.
The transcript looks fine but it doesn't seem to originate from the log drawer. A Connection refused message would indicate that the client wants to connect to a server and port which can be reached but does not accept the connection.
I have cyberduck connecting to a shared file resurce, while it does work for some machines not all.
I have a log of a user and it logs on ok, but then the prgram quits and issues error message "connection refused"
here is the comment from servu :
Here is rhe log :
At the bottom is where the quit commend started.
The text was updated successfully, but these errors were encountered: