From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: curious proftpd problem
Date: Mon, 24 Feb 2003 20:04:00 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0302241957300.19444-100000@igueths> (raw)
Hi. I have since fixed most of my proftpd problems, however I just
upgraded to proftpd-1.2.7 and am noticing a very interesting occurance.
Whenever I connect with localhost and log in using ftp, it says remote
system type is Unix. I can also log in as any other system user. However,
when I ssh into another Linux machine which is a Redhat system, and I
connect I can login as ftp. However, it says "remote system type is
Windows_nt. And as a result, I get no file listings. I also can't remotely
log in as other system users. Does anyone know why Proftpd would identify
a Linux machine as windows_nt and not transfer any files once an Ascii
connection is opened? And if this is a bug in the current version, which
version should I backtrack to? Perhaps the latest Debian package? I also
tried 1.2.8RC2 and got the same problems as in 1.2.7. Anyone have any
ideas on this one? Thanks in advance!
May you code in the power of the source,
may the kernel, libraries, and utilities be with you,
throughout all distributions until the end of the epoch.
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0302241957300.19444-100000@igueths \
--to=igueths@attbi.com \
--cc=speakup@braille.uwo.ca \
/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).