Hello guys,
my primary problem is that the passiv mode does not work for me.
Here is what it tells :
(000016) 5/29/2006 6:01:07 AM - (not logged in) (81.48.30.173)> Connected, sending welcome message...
(000016) 5/29/2006 6:01:07 AM - (not logged in) (81.48.30.173)> 220-FileZilla Server version 0.9.17 beta
(000016) 5/29/2006 6:01:07 AM - (not logged in) (81.48.30.173)> 220-written by Tim Kosse (Tim.Kosse@gmx.de)
(000016) 5/29/2006 6:01:07 AM - (not logged in) (81.48.30.173)> 220 Please visit http://sourceforge.net/projects/filezilla/
(000016) 5/29/2006 6:01:12 AM - (not logged in) (81.48.30.173)> USER siteupdate.example.com
(000016) 5/29/2006 6:01:12 AM - (not logged in) (81.48.30.173)> 331 Password required for siteupdate.example.com
(000016) 5/29/2006 6:01:18 AM - (not logged in) (81.48.30.173)> PASS ********
(000016) 5/29/2006 6:01:18 AM - siteupdate.example.com (81.48.30.173)> 230 Logged on
(000016) 5/29/2006 6:01:26 AM - siteupdate.example.com (81.48.30.173)> opts utf8 on
(000016) 5/29/2006 6:01:26 AM - siteupdate.example.com (81.48.30.173)> 200 UTF8 mode enabled
(000016) 5/29/2006 6:01:26 AM - siteupdate.example.com (81.48.30.173)> PWD
(000016) 5/29/2006 6:01:26 AM - siteupdate.example.com (81.48.30.173)> 257 "/" is current directory.
(000016) 5/29/2006 6:01:27 AM - siteupdate.example.com (81.48.30.173)> CWD /
(000016) 5/29/2006 6:01:27 AM - siteupdate.example.com (81.48.30.173)> 250 CWD successful. "/" is current directory.
(000016) 5/29/2006 6:01:27 AM - siteupdate.example.com (81.48.30.173)> TYPE A
(000016) 5/29/2006 6:01:27 AM - siteupdate.example.com (81.48.30.173)> 200 Type set to A
(000016) 5/29/2006 6:01:27 AM - siteupdate.example.com (81.48.30.173)> PASV
(000016) 5/29/2006 6:01:27 AM - siteupdate.example.com (81.48.30.173)> 227 Entering Passive Mode (81,81,81,81,4,205)
I would be very thankfull for any help to get this fixed !
Regards,
Fabian
Passiv mode does not work !
Moderator: Project members
I found out that the passive mode works fine in FileZilla Server Version 0.9.16c.
But in the versions 0.9.17 and 0.9.18 it don't.
I used the same configuration file for .16c up to .18.
The Problem is that .17 and .18 sends my local ip to the client at the PASC command and not my external one from the router. in all version configs i tested it with the method of an hostname (dyndns) and a skript on my domainserver to send back the ip adress. but both methods don't work.
But in the versions 0.9.17 and 0.9.18 it don't.
I used the same configuration file for .16c up to .18.
The Problem is that .17 and .18 sends my local ip to the client at the PASC command and not my external one from the router. in all version configs i tested it with the method of an hostname (dyndns) and a skript on my domainserver to send back the ip adress. but both methods don't work.
-
- 500 Command not understood
- Posts: 2
- Joined: 2006-07-13 17:29
I've been experiencing the same issue. I'm running 0.9.18 and clients keep trying to connect to the local private IP despite having PASV mode configured to send the external public IP. There is one exception. CuteFTP seems to be able to connect without any trouble. So far, this is the only FTP client I've tried that will connect and open the data channel.
I've tried what worked for you, installing 16c with the same configuration but no go. Same problem. CuteFTP works but nothing else.
Thoughts?
I've tried what worked for you, installing 16c with the same configuration but no go. Same problem. CuteFTP works but nothing else.
Thoughts?
-
- 500 Command not understood
- Posts: 2
- Joined: 2006-07-13 17:29
Thoughts?
Apparently I wasn't thinking. It turns out I mis-interpereted the field in the config where I placed the external IP. Once I used the right field, all clients connect without any trouble. The reason CuteFTP worked is because the developers were smart enough to try and connect to the same IP as the control channel if given a different IP for the data channel. Good thinking. Maybe a new feature for the Filezilla client.
Apparently I wasn't thinking. It turns out I mis-interpereted the field in the config where I placed the external IP. Once I used the right field, all clients connect without any trouble. The reason CuteFTP worked is because the developers were smart enough to try and connect to the same IP as the control channel if given a different IP for the data channel. Good thinking. Maybe a new feature for the Filezilla client.