Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[jrak]

I've been using FTP to access files from my DNS-323 while on the road, but had a problem doing so this week.  I stopped getting e-mail alerts (which I had been receiving for several months without a hitch) and was unable to connect via Filezilla which provided the following error message:

Connection attempt failed with "ETIMEDOUT - Connection attempt timed out".
Error:   Could not connect to server

Upon arriving home, I checked the system and was able to access my files locally.  I did a reboot, but was still unable to access my files using Filezilla.  The e-mail alert tested OK.

Does anyone have any idea as to what may be wrong?

[jamieburchell]

Try rebooting your router?

[fordem]

Do you have a static public ip address?  If you don't, your public ip address may change
Are you accessing the server by it's ip or by a URL?  If it's by ip and the public ip changes you'll get a timeout.
Are you using a dynamic DNS service?  Is your dynamic DNS client updating the ip changes properly?

Just a few things that need to be considered.

[jrak]

Thanks for the guidance.  I tried rebooting my router/modem, but that did not help.

I'm using a dynamic DNS service and the service has updated the ip changes properly.  I updated them again, but that did not help.

However, I noticed that I needed to change the host address in Filezilla.  Doing so connected me to the device, but I was unable to display the directory (see below).  I have not changed any settings (other than the address).

Any other suggestions or thoughts?



Connecting to XXX.XXX.XX:21212...
Status:   Connection established, waiting for welcome message...
Response:   220---------- Welcome to Pure-FTPd [TLS] ----------
Response:   220-You are user number 1 of 10 allowed.
Response:   220-Local time is now 14:25. Server port: 21212.
Response:   220-This server supports FXP transfers
Response:   220 You will be disconnected after 2 minutes of inactivity.
Command:   AUTH TLS
Response:   234 AUTH TLS OK.
Status:   Initializing TLS...
Status:   Verifying certificate...
Command:   USER XXX
Status:   TLS/SSL connection established.
Response:   331 User XXX OK. Password required
Command:   PASS **************
Response:   230 OK. Current restricted directory is /
Command:   SYST
Response:   215 UNIX Type: L8
Command:   FEAT
Response:   211-Extensions supported:
Response:    EPRT
Response:    IDLE
Response:    MDTM
Response:    SIZE
Response:    REST STREAM
Response:    MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
Response:    MLSD
Response:    ESTP
Response:    PASV
Response:    EPSV
Response:    SPSV
Response:   211 End.
Command:   PBSZ 0
Response:   200 PBSZ=0
Command:   PROT P
Response:   534 Fallback to [C]
Status:   Connected
Status:   Retrieving directory listing...
Command:   PWD
Response:   257 "/" is your current location
Command:   TYPE I
Response:   200 TYPE is now 8-bit binary
Command:   PASV
Response:   227 Entering Passive Mode (207,237,65,195,117,62)
Command:   MLSD
Error:   Connection timed out
Error:   Failed to retrieve directory listing

[fordem]

Thanks for the guidance.  I tried rebooting my router/modem, but that did not help.

I'm using a dynamic DNS service and the service has updated the ip changes properly.  I updated them again, but that did not help.

However, I noticed that I needed to change the host address in Filezilla.  Doing so connected me to the device, but I was unable to display the directory (see below).  I have not changed any settings (other than the address).

Any other suggestions or thoughts?

I have this "problem" when dealing with people like you - you need help, you want help, you're asking for help, but then you go obscuring the information that we need to help you, and obfuscating the situation - do you really think a hacker is going to troll through the posts here to find your ip address to hack you?

Much easier for him to just scan the subnet and be done with it.

Now - If you're doing what you're supposed to be doing - and you're using a dynamic DNS service, which is updating the ip address changes correctly - there would have been no need to change the host address in Filezilla - so I'd guess you're not doing something right there - but that's not likely to be the cause of your problem - this is ...

Response:   227 Entering Passive Mode (207,237,65,195,117,62)

Anything look familiar about it?  Maybe if I explain it, you'll understand - that line tells the ftp client to connect to the server on 207.237.65.195:30014 - and I suspect that your ftp server is no longer at that address, but, because of your predeliction for concealment - I can't be certain, can I?

I suppose you now want to be told where to fix that?

[jrak]

Fordem, I apologize if my actions at concealment made it impossible for you provide me with assistance.  Not having any real expertise in this area, I've never felt comfortable opening up my device to the Internet and I thought it prudent to conceal the addresses.  Given your expert evaluation of the risks and my need for assistance, here is the complete text:

Connecting to 216.220.68.81:21212...
Status:   Connection established, waiting for welcome message...
Response:   220---------- Welcome to Pure-FTPd [TLS] ----------
Response:   220-You are user number 1 of 10 allowed.
Response:   220-Local time is now 17:43. Server port: 21212.
Response:   220-This server supports FXP transfers
Response:   220 You will be disconnected after 2 minutes of inactivity.
Command:   AUTH TLS
Response:   234 AUTH TLS OK.
Status:   Initializing TLS...
Status:   Verifying certificate...
Command:   USER jr579
Status:   TLS/SSL connection established.
Response:   331 User jr579 OK. Password required
Command:   PASS **************
Response:   230 OK. Current restricted directory is /
Command:   SYST
Response:   215 UNIX Type: L8
Command:   FEAT
Response:   211-Extensions supported:
Response:    EPRT
Response:    IDLE
Response:    MDTM
Response:    SIZE
Response:    REST STREAM
Response:    MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
Response:    MLSD
Response:    ESTP
Response:    PASV
Response:    EPSV
Response:    SPSV
Response:   211 End.
Command:   PBSZ 0
Response:   200 PBSZ=0
Command:   PROT P
Response:   534 Fallback to [C]
Status:   Connected
Status:   Retrieving directory listing...
Command:   PWD
Response:   257 "/" is your current location
Command:   TYPE I
Response:   200 TYPE is now 8-bit binary
Command:   PASV
Response:   227 Entering Passive Mode (207,237,65,195,117,58)
Command:   MLSD
Error:   Connection timed out
Error:   Failed to retrieve directory listing

[jamieburchell]

There's little wrong in my opinion with excersizing some caution before posting potentially sensitive information in the public domain. I often wonder why you choose to help people fordem, when often you seem to detest everyone that isn't you or doesn't have your experience and obvious expertise?

[fordem]

Connecting to 216.220.68.81:21212...
<SNIP>
:   PASV
Response:   227 Entering Passive Mode (207,237,65,195,117,58)
<SNIP>

I've quoted the two areas that pinpoint the problem - and as I initially suspected, your public ip address has changed, and the DNS-323 is still sending the old address in response to the PASV command.

ftp is different from most other protocols in that it uses two connections one to control the transfer (the control connection) and the other to transfer the data (the data connection), because of this difference in addresses, you are successfully establishing the control connection on the first address, but then failing to establish the data connection.

Go back to the ftp server settings and look for the setting that says "Report external ip in passive mode" and enter the correct address there.

FWIW - this may be a bug in the ftp server code that D-Link will need to correct in future releases - I've never had it happen, because my public ip doesn't change, but I've long been curious - I have noticed that when you check the box the DNS-323 will often "pre-enter" the required information, showing that it has a means of retrieveing the address, but apparently it does not do it on each request.

Edit - #1.

I've asked D-Link to investigate this so that if necessary it can be fixed.

Edit - #2.

Purely by coincidence ...

The local telco is also my DSL provider and I have been transferred to a new CO switch, which required a change of ip address, so I have been able to duplicate this exact situation - the dynamic DNS service was automatically updated (by the router) but the DNS-323 remained completely unaware and continued to send the old ip address until I manually edited the ftp server settings.

I wonder if using the DNS-323 to handle dynamic DNS updates fixes this?

[jrak]

Thanks for the guidance!

[gijoecam]

The local telco is also my DSL provider and I have been transferred to a new CO switch, which required a change of ip address, so I have been able to duplicate this exact situation - the dynamic DNS service was automatically updated (by the router) but the DNS-323 remained completely unaware and continued to send the old ip address until I manually edited the ftp server settings.

I wonder if using the DNS-323 to handle dynamic DNS updates fixes this?

I can confirm that using the NAS for DDNS updates does NOT solve the problem as that's how mine is currently set up.  Unfortunately mine changes a couple times a month (thanks to wind/rain/power outages).  This does not make me very happy as I'm finding this is a recurring theme with this unit...