Re: [Proftpd-user] Directory listing fails

> This issue is happing on multiple networks with multiple different FTP 
> clients trying to access the same account/directory, so we can rule out 
> network/client issues.

Not so fast.

The fact that your FTP client can send out an RFC 1918 non-publicly
routable address (192.168.x.y) in a PORT command to a server -- and have
that active data transfer succeed -- says that something in front of
your client machine is translating/handling that FTP control connection,
and changing the IP addresses that the FTP server receives.  Otherwise,
the active data transfer wouldn't work at all.  (Or proftpd's handling
of "buggy" clients which do as your client is doing is in effect --
this, too, would show in the proftpd debug logging.)

So we know that there's a possibility of at least one network middlebox,
probably closer to the client side of things, which could also be
imposing a timeout...

Could you provide the proftpd debug logging, debug level 10, for one of
these failed directory listings, please?

TJ

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
ProFTPD Users List   <[email protected]>
Unsubscribe problems?
http://www.proftpd.org/list-unsub.html