Error: "Can't detect command return code"

Hi.
I try to connect with

WinSCP Version 2.0.0
with my System WIN98SE

to the University Server which is running

SunOS 5.8.

With the Programm "Putty" it isnt a Problem at all.
If i try to connect with WinSCP the following Error message returns:

"Error Skipping Startup message:
Can't detect command return code"

What does this mean?
Can someone help me?
Thanks,
Marc.

Please post (or send me via email) the session log. You can delete any sensitive information if you want.

Hi again.
Ill send you the *.log file on your email from another website.
Did you recieved it?
Marc.

martin wrote:

Please post (or send me via email) the session log. You can delete any sensitive information if you want.

Hey, I am having same problem but connecting to Windows 2k server running open ssh,

"Can't detect command return code."

Haddon Bennett

Hi,

I'm also receiving the message below when trying to connect with winscp to a openssh server (win XP).
Normal ssh sessions to the same server are no problem however.

"Can't detect command return code."

Jan

hairydawgs wrote:

Hey, I am having same problem but connecting to Windows 2k server running open ssh,

Jan Lammertyn wrote:

I'm also receiving the message below when trying to connect with winscp to a openssh server (win XP).

For info how to connect to OpenSSH for Windows see this topic.

Getting the: "Can't detect command return code" error when trying to connect to the VShell (VanDyke) WinSSHd (Bitvise) server. Connecting to SSH server on Mandrake is no problem.

Verbose of the session is :

. --------------------------------------------------------------------------
. WinSCP Version 2.1.0 (Build 119)
. Login time: 17 January 2003 17:23:34
. --------------------------------------------------------------------------
. Session name: administrator@10.0.0.220
. Host name: 10.0.0.220 (Port: 24)
. User name: administrator (Password: Yes, Key file: No)
. SSH protocol version: 1; Compression: No
. Agent forwarding: No; TIS/CryptoCard: No; KI: Yes
. Ciphers: aes,blowfish,3des,WARN,des; Ssh2DES: No
. Ping interval: 0 sec (0 = off); Timeout: 15 sec
. SSH Bugs: A,A,A,A,A,A,A,
. Proxy: none
. Return code variable: Autodetect; Lookup user groups: Yes
. Shell: default, EOL: 0
. Local directory: default, Remote directory: home, Update: No
. Clear aliases: Yes, Unset nat.vars: Yes
. Alias LS: No, Ign LS warn: Yes, Scp1 Comp: No
. --------------------------------------------------------------------------
. Looking up host "10.0.0.220"
. Connecting to 10.0.0.220 port 24
. Server version: SSH-2.0-1.27 sshlib: WinSSHD 3.06
. We claim version: SSH-2.0-PuTTY-Local: Jan 12 2003 19:45:16
. Using SSH protocol version 2
. Doing Diffie-Hellman key exchange
. Host key fingerprint is:
. ssh-dss 1024 c3:e0:45:48:ca:11:4f:d0:67:d3:9e:13:1f:a7:f3:95
. Initialised AES-256 client->server encryption
. Initialised AES-256 server->client encryption
. Sent password
. Access granted
. Opened channel for session
. Started a shell/command
. --------------------------------------------------------------------------
. Doing startup conversation with host (shell).
. Skipping host startup message (if any).
> echo "WinSCP: this is end-of-file:0"
< Microsoft Windows 2000 [Version 5.00.2195]

< (C) Copyright 1985-2000 Microsoft Corp.

<

< E:\Documents and Settings\Administrator>echo "WinSCP: this is end-of-file:0"
* (ECommand) Error skipping startup message.
. Closing connection. :?


Hope this help.
Love how Winscp is coming along

guest wrote:

Getting the: "Can't detect command return code" error when trying to connect to the VShell (VanDyke) WinSSHd (Bitvise) server. Connecting to SSH server on Mandrake is no problem.

Please read this topic for information how to connect to server running Windows.

Just in case the web archive disappears I'll post the guts of the link that Martin mentioned. BTW if you follow the instructions it works great. Vielen Dank f&uuml;r die gute Arbeit, Martin.

Setup
When you run WinSCP you'll need to make some quick changes before connecting to an OpenSSH on Windows server. Unfortunately, you'll need to make these changes every time you define a new host. After making the changes, however, you can save them for that host.

When the Login dialog comes up make the following changes on the designated tabs:
Basic
Fill in the hostname, port, username, and password or key file.
Advanced
Turn on enable compression and use SSH2 as the default protocol.
Shell
Enter "/ssh/sh" as your shell. Uncheck Lookup user groups. Switch the end-of-line character to CR/LF.
Directories
Change remote directory to "/".

When connecting you may get an error message regarding pagefile.sys. Disregard this message. By default you'll get a copy confirmation dialog box. This can be disabled in the options.

If text files bloat during transfer, make sure you set the end-of-line character to CR/LF for windows servers. Unix servers should be left at the default. When downloading large, already compressed files I'd recommend disabling scp compression. It'll make things REALLY slow.

By default you'll be placed in C:\ when connecting. You can connect to other drives using the cygdrive notation. To move to the d drive go to /cygdrive/d/.

Here's a handy little trick. Go into c:\ and create a directory called "cygdrive". From then on, when connecting via WinSCP, you'll be able to open that directory and see all available drives.

I managed to get it running with the following settings:
Shell
- Shell: /bin/sh
- EOL characters: CR/LF [13/10] (Windows)
- Do not "Lookup user groups"

(note the "bin" and not "ssh"

See documentation for details about "Error skipping startup message" error.