WINSCP3 with VShell 2.02

I am trying to use WinSCP3 with VShell 2.02 running on Windows 2000.

The profile for the W2K user is set so that the home directory is "D:\Work".

When I connect to the server using WinSCP3 (v3.1.0), I get the following error:

Unexpected directory listing line " 0 Jul 29, 2003 14:13 ./".
Invalid rights description " 0 "

I am able to use psftp (from PuTTY), as well as sftp2 (from SSH) to connect to the server and get a directory listing.

I can also as using the SFTP tool contained within the SSH Secure Shell package from ssh.com

I am assuming that it might be the "\" in "D:\Work" that could be causing the problem.

Any idea what I can do to get WinSCP3 to work with VShell?

Have you tried to select SFTP protocol on Login screen?

martin wrote:

Have you tried to select SFTP protocol on Login screen?

Yes, that is the protocol I am using.

One of the quirks with VShell is that even though the home directory of my user is "D:\Work", VShell exposes it as "D:\Work/D:\Work"

Here is a log, with security info obscured.

Login time: Friday, August 01, 2003 12:18:50 PM
--------------------------------------------------------------------------
Session name: **************
Host name: monolith (Port: 22)
User name: *********** (Password: Yes, Key file: No)
Transfer Protocol: SFTP
SSH protocol version: 2; Compression: Yes
Agent forwarding: Yes; 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, Cache: Yes
Clear aliases: Yes, Unset nat.vars: Yes, Resolve symlinks: 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.02 VShell
We claim version: SSH-2.0-PuTTY-Local: Jul 14 2003 13:14:02
Using SSH protocol version 2
Doing Diffie-Hellman group exchange
Doing Diffie-Hellman key exchange
Host key fingerprint is:
ssh-dss 1024 f2:65:fd:56:fb:86:09:6e:6a:0d:e0:b1:79:e1:28:e7
Initialised zlib (RFC1950) compression
Initialised zlib (RFC1950) decompression
Initialised AES-256 client->server encryption
Initialised AES-256 server->client encryption
Using username "********".
Sent password
Access granted
Opened channel for session
Started a shell/command
--------------------------------------------------------------------------
Using SFTP protocol
Doing startup conversation with host.
Type: SSH_FXP_INIT, Size: 5, Number: -1
Type: SSH_FXP_VERSION, Size: 106, Number: -1
Getting current directory name.
Type: SSH_FXP_REALPATH, Size: 10, Number: 16
Type: SSH_FXP_NAME, Size: 35, Number: 16
Listing directory "D:\Work/D:\Work".
Type: SSH_FXP_OPENDIR, Size: 24, Number: 267
Type: SSH_FXP_HANDLE, Size: 13, Number: 267
Type: SSH_FXP_READDIR, Size: 13, Number: 524
Type: SSH_FXP_NAME, Size: 2157, Number: 524
Type: SSH_FXP_READDIR, Size: 13, Number: 780
Type: SSH_FXP_CLOSE, Size: 13, Number: 1028
Type: SSH_FXP_STATUS, Size: 44, Number: 780
Type: SSH_FXP_STATUS, Size: 34, Number: 1028
Startup conversation with host finished.

I seems like compatibility issue. I may try to solve it, but unfortunatelly I have not access to any VShell server. Do you think you can create a test account for me?

martin wrote:

I seems like compatibility issue. I may try to solve it, but unfortunatelly I have not access to any VShell server. Do you think you can create a test account for me?

Unfortunately not; that is something I have no control over.

martin wrote:

I seems like compatibility issue. I may try to solve it, but unfortunatelly I have not access to any VShell server. Do you think you can create a test account for me?

Martin, I'm the product director for the VanDyke Software VShell Server. I'll be happy to work with you on this issue. We've had a few more customers report this in the latest VShell 2.2 for Windows and a similar problem in VShell for UNIX/Linux servers. You can download VShell for UNIX, Linux, or Windows from the following URL:

https://www.vandyke.com/products/vshell/index.html

It runs in a 30 day trial mode, or contact me at kelli.burkinshaw@vandyke.com and I'll be happy to set up up with licenses for future compatibility testing. You've got a great app which seems to be gaining in popularity. I'd love to see them work well together.

Cheers,
kelli

kelli wrote:

Martin, I'm the product director for the VanDyke Software VShell Server. I'll be happy to work with you on this issue. We've had a few more customers report this in the latest VShell 2.2 for Windows and a similar problem in VShell for UNIX/Linux servers. You can download VShell for UNIX, Linux, or Windows from the following URL:

https://www.vandyke.com/products/vshell/index.html

OK, I'll do some testing next week.