FTP Problem -- WarFTPd 1.82.00-RC2 on the other end

Using the command line "ftp" on Linux, when I connect to one
particular ftp server, it identifies itself as "WarFTPd 1.82.00-RC2 July
13, 2003". I'm getting logged in OK but when I do a "dir" (or "ls"), the
connection just seems to hang. "binary" and "prompt" get the expected
responses but then "mget *" also hangs.
Note that running CuteFTP on a Windows box and connecting to this
same server seems to work OK (until Windows crashes from not being booted
often enough [grrrr]).
Any idea what I need to do on Linux to make it work with this server?
TIA

On Thu, 16 Jun 2005 07:56:45 -0700, Ed Skinner wrote:

> Using the command line "ftp" on Linux, when I connect to one
> particular ftp server, it identifies itself as "WarFTPd 1.82.00-RC2 July
> 13, 2003". I'm getting logged in OK but when I do a "dir" (or "ls"), the
> connection just seems to hang. "binary" and "prompt" get the expected
> responses but then "mget *" also hangs. [...]

> Any idea what I need to do on Linux to make it work with this server?

Try using passive-mode data transfer. As in the "-p" option. If that also
fails, try enabling "-v" (verbose) and maybe "-d" (debug).

Another thing might be looking at the connection with a packet sniffer
like "tcpdump", "ngrep", "tethereal" or whatever.

--
-Menno.

On Thu, 16 Jun 2005 17:10:22 +0200, Menno Duursma wrote:

> On Thu, 16 Jun 2005 07:56:45 -0700, Ed Skinner wrote:
>
>> Using the command line "ftp" on Linux, when I connect to one
>> particular ftp server, it identifies itself as "WarFTPd 1.82.00-RC2 July
>> 13, 2003". I'm getting logged in OK but when I do a "dir" (or "ls"), the
>> connection just seems to hang. "binary" and "prompt" get the expected
>> responses but then "mget *" also hangs. [...]
>
>> Any idea what I need to do on Linux to make it work with this
>> server?
>
> Try using passive-mode data transfer. As in the "-p" option. If that also
> fails, try enabling "-v" (verbose) and maybe "-d" (debug).
>
> Another thing might be looking at the connection with a packet sniffer
> like "tcpdump", "ngrep", "tethereal" or whatever.


Thanks but didn't help.
Elsewhere someone suggested using "lftp" and, bingo, works like a champ.
I'll still probably use ethereal, etc., just to figure out what was going
on so, thanks for the suggestions.