CentOS - Aug 2007 - SFTP error (perhaps due not to using passive mode?)

I'm getting a weird error when I try to sFTP on a CentOS box (which I
don't
have root access).

when I run:

sftp -oPort=990 user at host.domain.com

I get the following error, which I suspect is a result of not being in
"passive mode" (which works when I use Filezilla on Windows)

Connecting to host.domain.com
ssh_exchange_identification: Connection closed by remote host
Couldn't read packet: Connection reset by peer

Any suggestions?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos/attachments/20070814/10665e56/attachment-0001.html>

On Tue, 2007-08-14 at 23:07 -0700, Rogelio Bastardo
wrote:
> I'm getting a weird error when I try to sFTP on a CentOS box (which I
> don't have root access).
Are you trying to use SFTP or FTPS? They're 2 completely different
protocols. SFTP piggybacks on top of SSH, and FTPS is FTP over SSL.

-- 
Ignacio Vazquez-Abrams <ivazqueznet at gmail.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.centos.org/pipermail/centos/attachments/20070815/6d6793f3/attachment-0001.sig>

Rogelio Bastardo wrote:
> I'm getting a weird error when I try to sFTP on a CentOS box (which I 
> don't have root access).
>  
> when I run:
>  
> sftp -oPort=990 user at host.domain.com <mailto:user at
host.domain.com>
>  
> I get the following error, which I suspect is a result of not being in 
> "passive mode" (which works when I use Filezilla on Windows)
>  
> Connecting to host.domain.com <http://host.domain.com>
> ssh_exchange_identification: Connection closed by remote host
> Couldn't read packet: Connection reset by peer
>  
> Any suggestions?
passive vs active or port mode is strictly a  old school FTP thing, it 
has nothing to do with sftp which is part of the ssh protocol.

are you running a ssh server on port 990?  it normally runs on port 22.