Forum » Support and Bug Reports »

Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: same problem with OpenSSH for Windows

gluswul wrote:

any news on that?

here the log without shell or with any unixlike path: (cancels with "Can't detect command return code.")

Your problems is the same. In your case Windows command line (cmd.exe) is run, WinSCP needs UNIX emulation.
gluswul

same problem with OpenSSH for Windows

any news on that?

here the log without shell or with any unixlike path: (cancels with "Can't detect command return code.") 
. --------------------------------------------------------------------------

. WinSCP Version 2.2.3 (Build 139)

. Login time: Donnerstag, 17. April 2003 22:48:31

. --------------------------------------------------------------------------

. Session name: gluswul@hal9000

. Host name: hal9000 (Port: 22)

. User name: gluswul (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 "hal9000"

. Connecting to 192.168.0.192 port 22

. Server version: SSH-2.0-OpenSSH_3.5p1

. We claim version: SSH-2.0-PuTTY-Local: Apr 12 2003 19:00:49

. Using SSH protocol version 2

. Doing Diffie-Hellman group exchange

. Doing Diffie-Hellman key exchange

. Host key fingerprint is:

. ssh-rsa 1024 e1:96:11:20:36:de:f9:48:ac:91:d1:52:4b:f6:5e:97

. Initialised AES-256 client->server encryption

. Initialised AES-256 server->client encryption

! Using username "gluswul".

. Keyboard-interactive authentication refused

. 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"

! Could not chdir to home directory /home/gluswul: No such file or directory

< Microsoft Windows XP [Version 5.1.2600]



< (C) Copyright 1985-2001 Microsoft Corp.



< 



< C:\Programme\OpenSSH>"WinSCP: this is end-of-file:0"



* (ECommand) Error skipping startup message.

. Closing connection.

my next try was to enter the "windows shell" cmd:
but "Connection has been unexpectedly closed." 
. --------------------------------------------------------------------------

. WinSCP Version 2.2.3 (Build 139)

. Login time: Donnerstag, 17. April 2003 22:43:50

. --------------------------------------------------------------------------

. Session name: test

. Host name: hal9000 (Port: 22)

. User name: gluswul (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: c:\winnt\system32\cmd.exe, 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 "hal9000"

. Connecting to 192.168.0.192 port 22

. Server version: SSH-2.0-OpenSSH_3.5p1

. We claim version: SSH-2.0-PuTTY-Local: Apr 12 2003 19:00:49

. Using SSH protocol version 2

. Doing Diffie-Hellman group exchange

. Doing Diffie-Hellman key exchange

. Host key fingerprint is:

. ssh-rsa 1024 e1:96:11:20:36:de:f9:48:ac:91:d1:52:4b:f6:5e:97

. Initialised AES-256 client->server encryption

. Initialised AES-256 server->client encryption

! Using username "gluswul".

. Keyboard-interactive authentication refused

. 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"

! Could not chdir to home directory /home/gluswul: No such file or directory

! c:winntsystem32cmd.exe: not found

. Server sent command exit status 0

* (ESshFatal) Error skipping startup message.

seams to me like there are problems with the backslash

thanks for your support

gluswul[/code]
martin

I have no experiences with VShell, but for OpenSSH for Windows there "exists" /ssh/sh, although there is in fact no /ssh directory. It is virtually mapped to c:\program files\openssh\ssh. Please check this.

What happens if you don't enter /bin/sh on Shell tab?

As to the PSFTP: It does not use shell, so it can work even when WinSCP does not.
czrx

Well, VShell is a Windows-SSHd. I found some config-suggestions in this board. They said: "/ssh/sh" for "Shell"-settings.

So, I am sure, "/bin/sh" or "/ssh/sh" doesnt exist. :)

mfg czrx
martin

Are you sure that /bin/sh exists on your server?
czrx

Ok, the problem has changed. I've found some configuration commendations for WinSCP with VShell in this Forum and ... . there is a different error :(:

See log:
. --------------------------------------------------------------------------

. WinSCP Version 2.2.0 (Build 122)

. Login time: Freitag, 4. April 2003 17:31:48

. --------------------------------------------------------------------------

. Session name: *******@**********

. Host name: ********** (Port: 22)

. User name: ******* (Password: Yes, Key file: No)

. SSH protocol version: 2; Compression: Yes

. 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: No

. Shell: /ssh/sh, EOL: 1

. 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 "**********"

. Connecting to *********** port 22

. Server version: SSH-2.0-VShell_2.03 VShell

. We claim version: SSH-2.0-PuTTY-Local: Jan 26 2003 11:53:20

. Using SSH protocol version 2

. Doing Diffie-Hellman group exchange

. Doing Diffie-Hellman key exchange

. Host key fingerprint is:

. ssh-rsa 2048 54:5d:dc:54:4f:c8:6e:f5:3c:1f:0e:f8:03:58:b7:0a

. Initialised zlib (RFC1950) compression

. Initialised zlib (RFC1950) decompression

. Initialised AES-256 client->server encryption

. Initialised AES-256 server->client encryption

. Sent password

. Access granted

. Opened channel for session

. Unexpected response to shell/command request: packet type 95

* (ESshFatal) Unexpected response to shell/command request: packet type 95


Packet Type 95

Hope that helps.

mfg czrx
martin

Re: WinSCP with VanDyke's VShell SShd for Windows

Please post log file.
czrx

WinSCP with VanDyke's VShell SShd for Windows

Hi,

at first: great tool!.

But: At connecting with VanDyke's VShell-Server (its a Widnows SSHd), WinSCP stops loginsequence with following errormessage:

"Can't detect command return code."

But PuTTY's "PSFTP.EXE" works fine. Any suggestions?

mfg czrx

Documentation

Support

Associations

Follow Us