200 type set to a 227 entering passive mode ошибка при попытке ftp

mathmaniac88mathmaniac88

1111 gold badge1 silver badge8 bronze badges

answered Jul 17, 2018 at 4:47

Hi guys,

Can some one pin point what is causing this error to show up when logging to qnap ftp server via window os through dydns domain?

An error occured opening that folder on the FTP Server. Make sure you have permission to acccess that folder.
Details:
200 Type set to A
227 Entering Passive Mode (192,168,0.10, 218, 101)

-I’ve used another qnap same issue;
-Attempted to disable and enabled the qnap FTP service same issue;
-Revert back to my previous modem, the ftp is working.

This error show up after I changed over to a new adsl2+ modem «port 21 pointed to my qnap» but when I’m accessing via internal IP ftp://192.168.0.10 it seems ok with no error.

With my previous Netgear modem I can access into the ftp with out any issue. FYI im using a dydns service and all the port forwardings has been done correctly. Any idea what is causing this? Thanks

Wae.

Gum wrote:Hi guys,

Can some one pin point what is causing this error to show up when logging to qnap ftp server via window os through dydns domain?

An error occured opening that folder on the FTP Server. Make sure you have permission to acccess that folder.
Details:
200 Type set to A
227 Entering Passive Mode (192,168,0.10, 218, 101)

-I’ve used another qnap same issue;
-Attempted to disable and enabled the qnap FTP service same issue;
-Revert back to my previous modem, the ftp is working.

This error show up after I changed over to a new adsl2+ modem «port 21 pointed to my qnap» but when I’m accessing via internal IP ftp://192.168.0.10 it seems ok with no error.

With my previous Netgear modem I can access into the ftp with out any issue. FYI im using a dydns service and all the port forwardings has been done correctly. Any idea what is causing this? Thanks

Wae.

Did you remember to setup the Port-Range Forwarding in your Router for Passive-FTP as well?

Testing from inside of the LAN? New DSL router (not modem only…) might not support NAT loopback.

Consider testing with a more sophisticated ftp client like FileZilla — and post the connection log.

Here is the log from filezilla

Internal IP work 192.168.0.10:21
External IP/Ddyns domain don’t work. xxx.xxx.xxx.xxx:21 / xxxxxx.dyndns-server.com:21

Status: Resolving address of xxxxxx.dyndns-server.com
Status: Connecting to xxx.xxx.xxx.xxx:21…
Status: Connection established, waiting for welcome message…
Response: 220 NASFTPD Turbo station 1.3.2e Server (ProFTPD) [192.168.0.10]
Command: USER admin
Response: 331 Password required for admin
Command: PASS **********
Response: 230 User admin logged in
Command: SYST
Response: 215 UNIX Type: L8
Command: FEAT
Response: 211-Features:
Response: MDTM
Response: MFMT
Response: MFF modify;UNIX.group;UNIX.mode;
Response: MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX.mode*;UNIX.owner*;
Response: LANG en-US*
Response: REST STREAM
Response: SIZE
Response: 211 End
Status: Server does not support non-ASCII characters.
Status: Connected
Status: Retrieving directory listing…
Command: PWD
Response: 257 «/» is the current directory
Command: TYPE I
Response: 200 Type set to I
Command: PASV
Response: 227 Entering Passive Mode (192,168,0,10,220,210).
Status: Server sent passive reply with unroutable address. Using server address instead.
Command: MLSD

I have tested from inside and outside of the LAN using the dyndns domain , port is on 21.
I have also checked with http://www.yougetsignal.com/tools/open-ports/ the port 21 is open.

Gum wrote:Here is the log from filezilla

Internal IP work 192.168.0.10:21
External IP/Ddyns domain don’t work. xxx.xxx.xxx.xxx:21 / xxxxxx.dyndns-server.com:21

I have tested from inside and outside of the LAN using the dyndns domain , port is on 21.
I have also checked with http://www.yougetsignal.com/tools/open-ports/ the port 21 is open.

That is awesome. Have you also verified that the Passive FTP Port-Range is also forwarded? I’m sure I provided a listing for it several messages ago.

You also find the ports listed on the FTP Server Setup screen.

Perhaps this will help:

Hi Patrick,

Unfortunately I have done the above steps open the ports for PFTP, and I’m still getting the same error. The modem I have is an iinet bob2 modem and it does not have the option to input the port range but I can only input a single port entry.

This what I have done:

1. I have changed the passive ftp port range to 55536 to 55537 in QNAP/Network Services/FTP Services/under Advance section
2. Open port for 55536 and 55547 point to my local qnap machine 10.1.1.8

I have also assigned the 10.1.1.8 into DMZ. What else could it be causing this issue?

Wae.

Having the same issue. Filezilla connects without a hitch, using myqnapcloud address. Windows fails with the same error message as reported by OP whenever mapping the drive. FTP is on port 2121 and I have redirected the port range as well. No joy.

Anyone have a solution?