Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Connection Problem #4189

Closed
cyberduck opened this issue Feb 3, 2010 · 8 comments
Closed

Connection Problem #4189

cyberduck opened this issue Feb 3, 2010 · 8 comments
Assignees
@dkocher
Labels
bug ftp FTP Protocol Implementation thirdparty Issue caused by third party

Comments

@cyberduck
Copy link
Collaborator

942be72 created the issue

I am the client and the host. So I have log files for both ends.

See attached.

I can connect with html editor BBedit, but not with FTP client Cyberduck.

Totally at a loss.

We have 5 servers, and 4 we can connect to fine, one is giving us fits.

It worked up until it was "upgraded" a week ago. So some setting changed somewhere and literally have tried everything we can think of.

Figured a fresh look and different perspective is needed.

Below is the error message from CyberDuck,

Attached is a screen shot from the server log.

We can connect using BBedit, but no with CyberDuck or other FTP clients, only the HTML editor.

I have changed USER/PASS, added, deleted doesn't change things.

It has to be some setting that during some upgrade it toggled something.

Any ideas as where to look? or things to try?

Here is a test access I set up for you:

FTP HOST: srvr18.ud.net
USERNAME: cyberduck
PASSWORK: please

Thanks in advance.

Using the above login... was able to connect via BBedit, but no FTP client (CyberDuck)

Any help is appreciated.

Regards,

Alan

--

Alan Bird alan@ud.net
Phone: 502-212-7500
Universal Design, Inc.
http://www.ud.net

--

FTP CLIENT

ERROR FROM CYBERDUCK

NOOP
220 FTP server ready.
USER nnep
331 User name OK, need password.
PASS ********
230 User logged in.
FEAT
500 Command "FEAT" unrecognized.
CWD /
250 CWD OK, "/".
STAT /
502 Command "STAT /" not implemented.
PASV
NOOP
220 FTP server ready.
USER nnep
331 User name OK, need password.
PASS ********
230 User logged in.
FEAT
500 Command "FEAT" unrecognized.
CWD /
250 CWD OK, "/".
STAT /
502 Command "STAT /" not implemented.
PASV

See attached screen shot of error message on server.

Attachments
@cyberduck
Copy link
Collaborator Author

@ylangisc commented

You need to disable the STAT command with

defaults write ch.sudo.cyberduck ftp.sendStatListCommand false

which is described here

@cyberduck
Copy link
Collaborator Author

@ylangisc commented

Merged from #4197:

Well ran the terminal command and still the same.

I think the problem is on our server end. That a setting there is incorrect.

I can still connect with BBedit, but not Cyberduck or any other FTP client.

CyberDuck works well with all the others, except for this one. Have compared setting and all look the same but obviously overlooking something.

Suggestions on server settings that would cause this?

@cyberduck
Copy link
Collaborator Author

@ylangisc commented

Please post the new transcript and/or screenshot

@cyberduck
Copy link
Collaborator Author

alan commented

Sent screen shot

Left is the log file from Server
Right is the log file from Cyberduck client

@cyberduck
Copy link
Collaborator Author

@dkocher commented

The control connection is reset from the server immediately after sending the PASV command. It is a bug in Cyberduck that no error message is displayed.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:2 yla]:

I can still connect with BBedit, but not Cyberduck or any other FTP client.

I would be interested in the transcript if available.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:1 yla]:

You need to disable the STAT command with

That would only be needed if the response parsed is not interpreted properly and the file listing is improperly shown in the browser. In this case here where STAT is not even supported by the server, we automatically fall back to the other file listing methods available. The disabling of particular listing methods is only needed if no fallback is attempted because it is wrongly assumed that the previous method completed successfully.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [4189 alan@…]:

See attached screen shot of error message on server.

You can see that the server software says the client dropped the connection. From debugging the issue here I must say it rather looks like the server closes the socket.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
bug ftp FTP Protocol Implementation thirdparty Issue caused by third party
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dkocher @cyberduck