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

Jump to bottom

Data Socket connecting to wrong address #1093

Closed
cyberduck opened this issue Apr 7, 2007 · 2 comments
Closed

Data Socket connecting to wrong address #1093

cyberduck opened this issue Apr 7, 2007 · 2 comments
Assignees
@dkocher
Labels
bug ftp FTP Protocol Implementation high priority worksforme

Comments

@cyberduck
Copy link
Collaborator

86075d6 created the issue

When connecting to an ftp server (windows 2003 server) i get connected but the directory listing does not happen. The connection is then closed with "network error : connection failed / operation timed out". This happens after entering passive mode. I believe there is a solution like on other ftp clients which provide an option "use site IP for passive mode connection". This permits connections to sites behind a firewall where the host IP could differ from the ftp server returned one. I am using cyberduck 2.7.3
Please help asap
@cyberduck
Copy link
Collaborator Author

rakoth commented

I have the same problem it seems.

The last WORKING build of Cyberduck was 2608, but after later updates all connections to my server via passive mode failed.

Here's the transscript:

220 iNet ftp proxy system
USER rakoth
331---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
331-You are user number 1 of 50 allowed.
331-Local time is now 08:45. Server port: 21.
331-This is a private system - No anonymous login
331-You will be disconnected after 15 minutes of inactivity.
331 User rakoth OK. Password required
PASS ********
230-User rakoth has group access to:  10000   
230 OK. Current directory is /
SYST
215 UNIX Type: L8
NOOP
200 Zzz...
CWD /
250 OK. Current directory is /
PASV
227 Entering Passive Mode (192,168,21,1,151,245)

Here Cuberduck reports 'connection refused'.

I'm actually trying to connect to ip 192.168.200.54, while 192.168.21.1 is ip address of my gateway/proxy to the outer LAN.

Guess thats where the dog is buried.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Is this still an issue? Actually if the response from the server, like 227 Entering Passive Mode (192,168,21,1,151,245), is a site local address, Cyberduck will try to connect to the remote IP address resolved by its own.

@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 high priority worksforme
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dkocher @cyberduck