I'm behind a router and nobody can connect to my server or transfer files / directory listings
i have configured my router to forward the ftp port (21)
and i have forwarded a port range for passive mode transfers (5000-5100)
(i don't know if its correct like this ?)
then i entered my external IP address in the server options (its dynamic, but for now, i change it every time i reboot)
now logging in doesn't work (port 21, username: test, password: test)
where did i go wrong ?
btw, is there an easy way to test your own ftp server ? without having to ask other people to check
behind router - faq didn't help
Moderator: Project members
if i connect with my external IP i get an empty list
but if i connect with my internal IP it works correctly
so i guess something is wrong with forwarding port 21 ?
Code: Select all
Status: Connecting to 80.201.13.44 ...
Status: Connected with 80.201.13.44. Waiting for welcome message...
Response: 220 Inactivity timer = 120 seconds. Use 'site idle <secs>' to change.
Command: USER test
Response: 230 User 'test' OK. No password required.
Command: FEAT
Response: 500 Unknown command.
Command: SYST
Response: 215 UNIX Type: L8
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/"
Command: TYPE A
Response: 200 TYPE is now ASCII
Command: PASV
Response: 227 Passive mode OK (80,201,13,44,4,11 )
Command: LIST
Response: 150 Opening data connection for /bin/ls
Response: 226 Options: -l : 0 matches total
Status: Directory listing successful
Command: TYPE I
Response: 200 TYPE is now 8-bit binary
Code: Select all
Status: Connecting to 192.168.123.137 ...
Status: Connected with 192.168.123.137. Waiting for welcome message...
Response: 220-FileZilla Server version 0.9.18 beta
Response: 220-written by Tim Kosse (Tim.Kosse@gmx.de)
Response: 220 Please visit http://sourceforge.net/projects/filezilla/
Command: USER test
Response: 331 Password required for test
Command: PASS ****
Response: 230 Logged on
Command: FEAT
Response: 211-Features:
Response: MDTM
Response: REST STREAM
Response: SIZE
Response: MLST type*;size*;modify*;
Response: UTF8
Response: CLNT
Response: 211 End
Command: CLNT FileZilla
Response: 200 Don't care
Command: OPTS UTF8 ON
Response: 200 UTF8 mode enabled
Command: SYST
Response: 215 UNIX emulated by FileZilla
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory.
Command: TYPE A
Response: 200 Type set to A
Command: PASV
Response: 227 Entering Passive Mode (192,168,123,137,19,137)
Command: LIST
Response: 150 Connection accepted
Response: 226 Transfer OK
Status: Directory listing successful
There seems to be an entirely different server listening at your external IP address.
Possible reasons:
- Wrong external IP address (check http://filezilla.sf.net/misc/ip.php, do not use a proxy to view that page)
- Forwarding to the wrong internal address
- Router acts as (broken) FTP server itself
- Your ISP redirects port 21 to its own server
Possible reasons:
- Wrong external IP address (check http://filezilla.sf.net/misc/ip.php, do not use a proxy to view that page)
- Forwarding to the wrong internal address
- Router acts as (broken) FTP server itself
- Your ISP redirects port 21 to its own server
thx! for the response
I double checked internal and external IP
I then changed the port in fileZilla settings to port 10021
(and also forwarded this port 10021)
now i get this error when if i connect with my external IP
also, i don't understand the part about 'router acting as server' , how can i check that isn't the case ?
I double checked internal and external IP
I then changed the port in fileZilla settings to port 10021
(and also forwarded this port 10021)
now i get this error when if i connect with my external IP
Code: Select all
Status: Connecting to 81.240.81.163:10021 ...
Error: Unable to connect!
it sounds like you have 2 computers on a internal network?
and trying to connect from 1 to the other?
using an external IP
YOU CAN'T, only with internal IP's
unless you setup a DNS, some good routers/modems can do this
but with a dns you use a name not a IP
EXSAMPLE, if you have cooperspc.com on a server, on a internal network, you CAN NOT get there from another computer on a internal network
but with the DNS set up you can get there by cooperspc.com:21
and trying to connect from 1 to the other?
using an external IP
YOU CAN'T, only with internal IP's
unless you setup a DNS, some good routers/modems can do this
but with a dns you use a name not a IP
EXSAMPLE, if you have cooperspc.com on a server, on a internal network, you CAN NOT get there from another computer on a internal network
but with the DNS set up you can get there by cooperspc.com:21