[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] [RaQ3] Cannot FTP as SiteAdmin
- Subject: Re: [cobalt-users] [RaQ3] Cannot FTP as SiteAdmin
- From: flash22@xxxxxxx
- Date: Tue Sep 4 00:12:04 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
On Tue, 4 Sep 2001, Per M Knutsen wrote:
> > > When I try to FTP as a siteadmin user (any host, any client), the login
> > > freezes after printing 2-3 lines of the welcoming message (~/.ftphelp).
> If I
> > > leave this file empty, the problem goes away.
> >
> > Try logging in with a leading dast ('-') before your password...
>
> Didn't help ("Login failed").
hmmm....heh...never even occurred to me proftp wouldn't impliment this
feature...i even tested it before replying to you, alas , on a wu-ftp
server - sigh
>
> > The status codes are probably missing....
>
> Which status codes? Is this an issue with ProFTPD?
ok, the ftp protocol requires a 3 digit status code before each command
sent to the client, for the initial messages, you are not really getting a
'message' as such, but a series of status replies, each of which has a
different line of text....the server is supposed to handle this, but i
have noticed proftp seems to get confused and forget this part, and the
clients generally don't like it....
See if this helps, in your help file, start each line with the number 220
(with a space after the 0) folloed by that line of text, make *sure* the
last line has a newline after it btw
ps: 220 is the status code for 'no problem', this the messages basiclly
are printed by repeatedly telling the client something worked ;)
The leading dash is supposed to suppress multiple 220 responses as some
older clients can't actually handle that regardless...
gsh