comp.os.linux.networking

On Sun, 09 Mar 2008 22:27:10 -0700, Greg rearranged some electrons to say:

> On Mar 7, 11:18 pm, Greg wrote:
>> On Mar 6, 10:15 pm, david wrote:
>>
>>
>>
>>
>>
>> > On Thu, 06 Mar 2008 19:33:12 -0800, Greg rearranged some electrons to
>> > say:
>>
>> > > On Mar 6, 2:16 am, david wrote:
>> > >> On Wed, 05 Mar 2008 20:43:32 -0800, Greg rearranged some electrons
>> > >> to say:
>>
>> > >> > There it is.  It is weird though, anything requiring a password
>> > >> > remotely hangs a little bit.  Even when I ssh in it takes a bit
>> > >> > more time than normal.
>>
>> > >> Oh, you didn't specify the PASV port ranges.   The default
>> > >> behavior is "any port" according to the documentation.  Your
>> > >> router would need to know which ports to forward, and without a
>> > >> range specified, you would probably have to forward all of them.
>>
>> > > I limited the port by saying the min is 20 and max is 21.  It still
>> > > times out.
>>
>> > Ah, no, that's not how PASV mode works.  You need to pick another
>> > range (>1023)
>>
>> >http://en.wikipedia.org/wiki/File_Transfer_Protocolhttp://
www.slacksi...Hide
>> >quoted text -
>>
>> > - Show quoted text -
>>
>> Yeah I opened a gang of high ports and told vsftpd about them but still
>> same result.- Hide quoted text -
>>
>> - Show quoted text -
>
> Anyone have any other ideas?

Look at your log files during your failed login attempts. There may be a
clue in there.