Jeffrey Bailey writes:
: We've been migrating users up to SSH 2.1 after the recent license change
: for universities. I have one user who cannot initiate an sftp session
: from his Windows NT platform (SSHWinSecureShell-21).
:
: The user can connect for a normal SSH to a Solaris 2.6 machine running
: SSH Secure Shell 2.1.0 (non-commercial version), using password for
: authentication. But when he tries to open a file transfer session, the
: connection immediately closes. The logs on the remote server do not
: show anything out of the ordinary. We can connect as a different user
: and have success with sftp from that same NT platform. If he moves to
: another NT machine, he still can't initiate sftp. He CAN, however, sit
: on a Sun machine and successfully use command-line sftp.
:
: The Suns on the network run NIS+ for logins, automounts of home
: directories and such. The user has tried connecting on a number of the
: platforms, including the host which has his home directory. Before he
: tried the command-line sftp, he didn't even have a .ssh2 directory in
: his home directory; neither did the successful sftp test account.
:
: Any ideas where to look for the culprit?
Do the user's shell scripts output something to stdout? This
would mess with the filexfer-protocol.
(for example,"echo foobar" in .cshrc would do something like this.)
--
[[EMAIL PROTECTED] -- Sami J. Lehtinen -- [EMAIL PROTECTED]]
[work:+358 9 85657425][gsm:+358 50 5170 258][http://www.iki.fi/~sjl]
[SSH Communications Security Ltd. http://www.ssh.com/]
