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

Interoperability with Humax #5864

Closed
cyberduck opened this issue Apr 1, 2011 · 6 comments
Closed

Interoperability with Humax #5864

cyberduck opened this issue Apr 1, 2011 · 6 comments
Labels
bug ftp FTP Protocol Implementation low priority thirdparty Issue caused by third party

Comments

@cyberduck
Copy link
Collaborator

42dea7f created the issue

After updating from 4.0.1 to 4.0.2 I get the following error when connecting to my Humax 5050C: "I/O Error: Could not parse response code". Reverting back to 4.0.1 makes the problem disappear. Between these two versions I did not change any of the settings.


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please post the transcript from View → Log Drawer.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Instead of a screenshot please copy and paste the full text of the log drawer here.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

You can workaround this issue by disabling the use of STAT.

@cyberduck
Copy link
Collaborator Author

42dea7f commented

Problem finally solved. The STAT was not the culprit. The Humax 5050C I am ftp-ing from does not like passive ftp (PASV) but an active connection (PORT) will do. Apparently the previous correct setting PORT on my version 4.0.1 copy was changed to PASV on installing the fresh copy of version 4.0.2. This explains why 4.0.1 kept working while 4.0.2 failed until I changed the connection setting on the latter.

@cyberduck
Copy link
Collaborator Author

@ylangisc commented

Thanks for letting us know.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

NOOP
200 Port command successful
CWD /mnt/hd3/Video
250 File action is successful. Proceed.
TYPE A
200 Port command successful
PASV
502 Command not implemented.
 

@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 low priority thirdparty Issue caused by third party
Projects
None yet
Development

No branches or pull requests

1 participant