NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

shapcah's avatar
shapcah
Aspirant
Feb 09, 2013

[SOLVED] Ftp problems after moving, cannot get folder list

hi everyone as the title says im having problems accesing my ftp after i moved house. all the settings are the same exept ofc. having changed masq to the new ip address and doing the port forward in the router, i can acces everything from https and the webserver works just fine aswell, but when i try ftp it goes wrong i have googled around and tryed varius things, trying to get a log to show u i have used filezilla since they have pretty straight log, here it is: (execute me for the danish client ^ i have done a translation in ().)

Status: Forbindelse etableret, venter på velkomstbesked...
Respons: 220 ProFTPD 1.3.3g Server (NETGEAR ReadyNAS) [x.x.x.x]
Kommando: USER xxxx
Respons: 331 Password required for xxxx
Kommando: PASS **********
Respons: 230 User xxxx logged in
Kommando: SYST
Respons: 215 UNIX Type: L8
Kommando: FEAT
Respons: 211-Features:
Respons: MDTM
Respons: MFMT
Respons: TVFS
Respons: UTF8
Respons: AUTH TLS
Respons: LANG en-US.utf8*
Respons: MFF modify;UNIX.group;UNIX.mode;
Respons: MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX.mode*;UNIX.owner*;
Respons: PBSZ
Respons: PROT
Respons: SITE MKDIR
Respons: SITE RMDIR
Respons: SITE UTIME
Respons: SITE SYMLINK
Respons: REST STREAM
Respons: SIZE
Respons: 211 End
Kommando: OPTS UTF8 ON
Respons: 200 UTF8 set to on
Status: Tilsluttet
Status: Henter mappeliste... (retrieving folder list)
Kommando: PWD
Respons: 257 "/" is the current directory
Kommando: TYPE I
Respons: 200 Type set to I
Kommando: PORT 192,168,42,98,207,183
Respons: 200 PORT command successful
Kommando: MLSD
Fejl: Forbindelse mistet ved timeout
Fejl: Kunne ikke hente mappeindholdsliste (cannot retrieve folder list)

Hope someone has the easy fix :D

8 Replies

  • StephenB's avatar
    StephenB
    Guru - Experienced User
    FileZilla is attempting to connect to a private address (192.168.42.98) on port 53175.

    Are you running it on your local LAN?
  • No i was running it on a laptop using my phone as a modem, and my home lan is not a 192.168.x.x ip range :) i have tryed several settings and changin pasive ports etc. But stil no use, i am running out of ideas, the weird thing is that it has been working for a very long time with my old isp where i lived bfore

    Thank you for ur interest, hope u have some suggestions :)
  • StephenB's avatar
    StephenB
    Guru - Experienced User
    With FileZilla you don't need to set masquerade at all, so try unsetting it.

    Is 53175 an appropriate passive port?
  • StephenB's avatar
    StephenB
    Guru - Experienced User
    So the passive port is wrong, and the IP address is wrong. Are you sure you are connecting to the right external IP address?

    Also, I am wondering if there is a passive FTP proxy on the path, which is possibly corrupting the messages???

    If you are using port 21 for the initial connection (FTP default), try changing it to something else.
  • hmm yeah, i know what u mean, looks strange to me to, :) well the outside ip is the right 1 im sure, im beginning ti think it is a problem with my router,(WNDR3700v3) i have testet loads of port combos, and i finally found something that works!
    Like this

    Port: 21
    Pasive: 5000 - 8000
    Masq: my External ip

    It works when i use the routers own predefined port forward funktion thingy, where it adds the port "21" by default. If i change the port... it dont work anymore!
    Now, i do like that i works, but tbh i do not want to be using port 21 for my ftp server as it is prolly the most bottet port on theweb.. ;)
    But atleast now i know its not the readynas thats acting up, ima gonna try and google what settings i need to change in the router to make ftp work on other ports than 21
  • Right, i found out that i had to forward all my pasive ports aswell... i have no idea why, but now it works :D

    Thank you very much for replying and trying to help me out ;)
  • StephenB's avatar
    StephenB
    Guru - Experienced User
    shapcah wrote:
    ...Right, i found out that i had to forward all my passive ports as well... i have no idea why, but now it works...
    The basic principle is that any connections that are inbound (from the internet through the router to your home network) need to use forwarded ports. Outbound connections (from your home network through your router to the internet) shouldn't be forwarded (and don't need to be).

    Passive port connections are made from the client to the NAS, so the ports have to be forwarded.

    Active port connections are made from the NAS outbound to the client - they don't need to be forwarded in your router, but they won't work when you are double-firewalled (for instance, when using the client in your office).

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More