Print

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

[fordem]

When passive ftp is being used, the ftp server will tell the ftp client to make a data connection and it will specify an ip address and a port on which the connection is to be made - and if the ftp server is not configured correctly it will specify it's private ip address, which is what you are experiencing here..

[gunrunnerjohn]

How would he change that using D-Link's configuration?  Why is it I don't see this issue using the same FTP server and the same configuration if it's a DNS-323 FTP server issue?

[P01arBear]

When passive ftp is being used, the ftp server will tell the ftp client to make a data connection and it will specify an ip address and a port on which the connection is to be made - and if the ftp server is not configured correctly it will specify it's private ip address, which is what you are experiencing here..

That is precicely what I was trying to say, you just explained it more simply than I did. ^^

How would he change that using D-Link's configuration?  Why is it I don't see this issue using the same FTP server and the same configuration if it's a DNS-323 FTP server issue?

This can be changed only in firmware 1.08, older firmwares cannot change it (like 1.07). And maybe this issue is specific when behind the DIR-655 router, I don't know...Maybe a conflict with routers that have SPI firewall? I really dunno.

[fordem]

He fixes it with that same "use external ip address for passive" check box.

Yours works because you're using active ftp - I can tell that because you said yours worked before you went to the 1.08 beta - he's using passive ftp - I can tell that from the error messages he is reporting.

Active & passive ftp are two distinctly different animals - it's either you get lucky and it works or you (not personal, but any user attempting to use ftp on a DNS-323) sit down and make a concious decision to understand how ftp works or you end up going around in circles and becoming frustrated.

It is also, at least in my opinion very important, that you (again not personal) recognize that D-Link is now fixing a "known broken" passive ftp implementation and it may still have bugs in it - I would not be surprised if the implementation was checking the "external ip" only during configuration, rather than everytime it needs to send the external ip address.

[P01arBear]

would not be surprised if the implementation was checking the "external ip" only during configuration, rather than everytime it needs to send the external ip address.

Let's hope they fix this on the next firmware. 

[gunrunnerjohn]

You're probably right, I just enabled the FTP previously and there was no problem accessing it.  I never gave active or passive a thought, since all the folks that needed access had no problems getting in.  The only thing I ever did was forward port 21 to the DNS-323.

You have to ask yourself why not use active mode...

[P01arBear]

You have to ask yourself why not use active mode...

Well, if it works with IE, then why not. I was using passive since most IE are by default in passive.

To get it working on IE, I think I have to go in the options, advanced and uncheck passive ftp right?

I'll also try that after work.

Edith: At my job, I can't edit IE's settings. The options are locked, so I've now got a good reason to stick with passive.

[fordem]

You have to ask yourself why not use active mode...

Because active mode is known to be problematic especially when the client is behind a NAT router.  The earlier NAT routers did not know how to "fixup" the ftp protocol - and believe it or not - "fixup" is an actual Cisco command.

[gunrunnerjohn]

I guess we all have "newer" routers.