From: snakedjip@yahoo.com (Snake Djip)
Subject: Re: ange-ftp in emacs behind a router/firewall stops at ls...
Date: 18 Sep 2002 08:27:08 -0700 [thread overview]
Message-ID: <3318afc0.0209180727.7d789754@posting.google.com> (raw)
In-Reply-To: vaf8z1zwuxk.fsf@lucy.cs.uni-dortmund.de
How do I find that out, this is ws_ftp on windows XP ...
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann wrote in message news:<vaf8z1zwuxk.fsf@lucy.cs.uni-dortmund.de>...
> snakedjip@yahoo.com (Snake Djip) writes:
>
> > I can reproduce the same behaviour when using the regular FTP client
> > without Passive transfers... the lights on the router are flashing,
> > and the connection is never complete (I never get a directory
> > listing).
>
> Does your ftp client grok a command line argument to make it use
> passive mode? Then you can tell ange-ftp to use that.
>
> kai
next prev parent reply other threads:[~2002-09-18 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 0:28 ange-ftp in emacs behind a router/firewall stops at ls Snake Djip
2002-09-18 8:42 ` Kai Großjohann
2002-09-18 15:27 ` Snake Djip [this message]
2002-09-19 13:35 ` Snake Djip
2002-09-20 13:45 ` Kai Großjohann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3318afc0.0209180727.7d789754@posting.google.com \
--to=snakedjip@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).