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.

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

STAT read timeout with WFTPD Pro 3.20.1.2 Server #3086

Closed
cyberduck opened this issue Mar 25, 2009 · 2 comments
Closed

STAT read timeout with WFTPD Pro 3.20.1.2 Server #3086

cyberduck opened this issue Mar 25, 2009 · 2 comments
Assignees
Labels
bug ftp FTP Protocol Implementation high priority thirdparty Issue caused by third party

Comments

@cyberduck
Copy link
Collaborator

81177c1 created the issue

I noticed this was posted before but closed with a older version of CyberDuck. I have the lastest version (as of 3/25/09) and can not connect to our WFTPD Pro 3.20.1.2 Server on the same network.

We have Fetch on the same computer with no problem.

it seems to hang and I get I/O Error: Listing Directory Failed
/
Read timed out

The CyberDuck log reports

220-Please be sure to Stuff or Zip your files prior to sending. This will insure smooth file transfer and lessen the chance for file curruption!!!
220 WFTPD 3.2 service (by Texas Imperial Software) ready for new user
USER westchesteru
331 Give me your password, please
PASS ********
230 Logged in successfully
PWD
257 "/" is current directory
NOOP
200 No operation completed successfully
SYST
215 WIN32 A N (WFTPD by Texas Imperial Software)
STAT /
213-status of /:
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [3086 dmyers@…]:

Try to disable the use of STAT using

defaults write ch.sudo.cyberduck ftp.sendStatListCommand false

See the problem section in the wiki for details.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [3086 dmyers@…]:

That worked like a charm! I even turned it back on to make sure.
Of course I can't exactly tell a client this.... Any idea on a downloaded-able patch/copy. That way I can tell my client's which use Cyberduck to "make sure you download the latest version" (it my fav FTP client as well thou!)

Threre is no fix planed as it is essentially a server bug not responding anymore. If it does not want to implement the command it should return a 500 error response. You might want to file this bug to WFTPD.

@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.
Labels
bug ftp FTP Protocol Implementation high priority thirdparty Issue caused by third party
Projects
None yet
Development

No branches or pull requests

2 participants