D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: SciencePiggy on July 31, 2010, 02:02:10 PM
-
I'm trying to configure my FTP server and since I don't have access to an outside network at the moment I've been using ftptest.net to test. My current setup is...
DNS-323: firmware 1.09
Port: 21
Passive Mode: Use default range
Report External Ip in Passive Mode: Checked
Ports 21, 55536 - 55663 are forwarded to the NAS (Router: Linksys - WRT54G)
External Ip is set to my external IP
My results from ftptest are...
Status: Resolving address of XX.XXX.XXX.XX
Status: Connecting to XX.XXX.XXX.XX
Status: Connected, waiting for welcome message
Reply: 220---------- Welcome to Pure-FTPd [TLS] ----------
Reply: 220-You are user number 1 of 10 allowed.
Reply: 220-Local time is now 15:43. Server port: 21.
Reply: 220-This server supports FXP transfers
Reply: 220 You will be disconnected after 2 minutes of inactivity.
Command: CLNT http://ftptest.net on behalf of XX.XXX.XXX.XX
Reply: 530 You aren't logged in
Command: USER XXXX
Reply: 331 User Test OK. Password required
Command: PASS XXXX
Reply: 230 OK. Current restricted directory is /
Command: SYST
Reply: 215 UNIX Type: L8
Command: FEAT
Reply: 211-Extensions supported:
Reply: EPRT
Reply: IDLE
Reply: MDTM
Reply: SIZE
Reply: REST STREAM
Reply: MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
Reply: MLSD
Reply: ESTP
Reply: PASV
Reply: EPSV
Error: Carriage return without line feed received
Error: Carriage return without line feed received
The replies sent by your server are violating the FTP specifications.
You have to upgrade to a proper server.
Anyone else have success with ftptest.net and your DNS-323? Anything I'm obviously doing wrong? (noob alert)
Cheers,
SP
-
I'd never heard of ftptest before so I decided to try it - I got the exact same error message ...
Error: Carriage return without line feed received
The replies sent by your server are violating the FTP specifications.
You have to upgrade to a proper server.
However, I KNOW my ftp server is fully functional, and externally accessible - I have kids at college in a different country who use it to get "stuff from home" when they need to, so all I'll say at this point is I'm not impressed with ftptest.
Let's look at your particular issue though - I like to test "local access" as the first step, so, uncheck the "report external ip in passive mode" box, and try to access the ftp server by it's internal ip address, make sure that works before you do anything else, and then recheck the box and test it from outside.
Based on the test results from ftptest.net, it looks like you have your dynamic DNS & port forwarding setup correctly, I see no reason why it should not work.
-
Mh, FTPtest works fine for me ...
There's another ftp problems related thread here in the DNS-323 forums (http://forums.dlink.com/index.php?topic=13864.0). In this thread I suggested forwarding the port 22 to the NAS too because it seems to be a reply port and the traffic through this port will be blocked if you use simple port forwarding rules.
My router (AVM 7390) supports special forwarding rules, like "HTTP server", "FTP server" and some more, and seems to be able to manage the request and reply traffic for each server type in the correct way.
I tried some forwarding; using a simple "Forward port 21" rule resulted in "timed out"; adding port 22 made the server accessible.
Hope this helps.
//HSishi
-
Mh, FTPtest works fine for me ...
There's another ftp problems related thread here in the DNS-323 forums (http://forums.dlink.com/index.php?topic=13864.0). In this thread I suggested forwarding the port 22 to the NAS too because it seems to be a reply port and the traffic through this port will be blocked if you use simple port forwarding rules.
My router (AVM 7390) supports special forwarding rules, like "HTTP server", "FTP server" and some more, and seems to be able to manage the request and reply traffic for each server type in the correct way.
I tried some forwarding; using a simple "Forward port 21" rule resulted in "timed out"; adding port 22 made the server accessible.
Hope this helps.
//HSishi
If that's what it takes to get ftptest to work, then ftptest is BROKEN!
I set up my first ftp server over a decade ago, I've done quite a few since and NONE of them have port 22 forwarded, it just is NOT required.
FWIW - I just modified my router's port forwarding setup - I disabled, the predefined "ftp" service and created two separate one, the first called Port21, and the second called Port22 - these services forward the respective port to the DNS-323.
I get the "carriage return without line feed received" error mentioned above, with either the Port21 service alone enabled, or both Port21 & Port22 services enabled - in short, it makes no difference.