Error getting name of current remote directory.

AFter attempting to login I recieved this error message:

"Error getting name of current remote directory."
"Connection has been unexpectedly closed."

I know the server I am trying to connect to supports SSH (I can connect to it for email using SSH Secure Shell). What can I try to get the program to work? Or... what questions can I ask the people that administrate the servers to see if the problem is a quirk on their end?

I've already tried using /bin/bash, /bin/sh, changing the EOL, and pretty much everything else possibly mentioned in these forums(I'm sure I missed something though).

BTW, I've already ran WinSCP through SecureFX. Just not sure why it isn't working with SSH for me. Suggestions are welcome.

Can you log in to your server using SSH terminal? (like Putty).

I am having this problem as well. Anyone know the answer off the top of their head? I'm going to trouble shoot it now. It sounds like a permission problem on the users home directory or something stupid like that. If I come across the answer first, I'll post it here.

-Jim

unix_dr wrote:

It sounds like a permission problem on the users home directory or something stupid like that.

Probably not. Message "Error getting name of current remote directory" is confusing here, it just refer to the first operation WinSCP is doing after opening connection, so it is also the first operation during wich it detects that server closed connection already.
Problem is usually caused by fact that SSH or shell is configured to not accept non-PTY sessions (WinSCP case).

martin wrote:

unix_dr wrote:

It sounds like a permission problem on the users home directory or something stupid like that.

Probably not. Message "Error getting name of current remote directory" is confusing here, it just refer to the first operation WinSCP is doing after opening connection, so it is also the first operation during wich it detects that server closed connection already.
Problem is usually caused by fact that SSH or shell is configured to not accept non-PTY sessions (WinSCP case).

BTW, I have got the same problem with Winscp. Just as an additional info: I am able to connect via putty as well as via psftp (from the putty page), everything works fine. But I cannot get WinSCP connect to that host.

andi wrote:

BTW, I have got the same problem with Winscp. Just as an additional info: I am able to connect via putty as well as via psftp (from the putty page), everything works fine. But I cannot get WinSCP connect to that host.

Sure. Putty has PTY and PSFTP does not use shell at all. Have you tried /bin/bash as mentioned above?

I got it work now :D
Solution:
set the shell in the shell tab from default to the actual shell used (in my case /bin/tcsh)

Anonymous wrote:

I got it work now :D
Solution:
set the shell in the shell tab from default to the actual shell used (in my case /bin/tcsh)

Great, but I would recommend you to use /bin/bash instead. You may encounter problems with handling errors with tcsh.

I am having the same issue with WinSCP2 connecting to a FSecure SSH Server. Using the FSecure client code and puTTY work just fine also. Any help would be great.

You have tried what Prikryl suggested? In your WinSCP connection properties under "Shell" select "Enter: " and enter in /bin/bash or /bin/ksh. This worked for me. I think it's rather lame behavior, but it works. I'm now attempting to see if it's simply an environment issue with the shell my users are using.

-Jim

Thanks for the suggestion but unfortunatly I am running FSecure SSH server on Windows 2000AS and not a Unix platform. Thanks.

dustinz wrote:

Thanks for the suggestion but unfortunatly I am running FSecure SSH server on Windows 2000AS and not a Unix platform. Thanks.

WinSCP requires UNIX shell. I have no experiences with FSecure, but for example OpenSSH for Windows provides UNIX shell emulation on Windows. So /bin/bash is valid there.

The same problem exist on several different machines in Win XP with f-secure server and Vshell as well.
Whatever I try, even with fifferen shell, it keeps saying:

"Authentication log (see session log for details):
Using username "test".

Unexpected response to shell/command request: packet type 98"

I use XP as said...!
I am getting less cheerfull, so to speak.

thx, Frank

I keep getting the same error no matter what I try. I tried /bin/bash and /bin/ksh and /bin/tcsh and nothing worked.

"Error getting name of current remote directory."
"Connection has been unexpectedly closed."

Any ideas?

FireWire wrote:

I keep getting the same error no matter what I try. I tried /bin/bash and /bin/ksh and /bin/tcsh and nothing worked.

"Error getting name of current remote directory."
"Connection has been unexpectedly closed."

Please post a log file.

I also am getting :Error listing directory: I found the post about connecting to VSHELL, (from a XP),followed the steps, but get same error.

here is my log:
--------------------------------------------------------------------------
WinSCP Version 3.0.0 (Build 159)
Login time: Wednesday, July 02, 2003 10:00:20 PM
--------------------------------------------------------------------------
Session name: gpearson@xxxxxxxxxxxxx
Host name: www.xxxxxxxxx(Port: 22)
User name: gpearson (Password: Yes, Key file: No)
Transfer Protocol: SFTP
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: \, Update: No, Cache: Yes
Clear aliases: Yes, Unset nat.vars: Yes
Alias LS: No, Ign LS warn: Yes, Scp1 Comp: Yes
--------------------------------------------------------------------------
Looking up host "www.xxxxcom"
Connecting to xxxxxxxxxxx port 22
Server version: SSH-2.0-0.0
We claim version: SSH-2.0-PuTTY-Local: Jun 25 2003 07:34:56
Using SSH protocol version 2
Doing Diffie-Hellman group exchange
Doing Diffie-Hellman key exchange
Host key fingerprint is:
ssh-dss 1024 0e:a9:ce:84:35:91:78:1a:fb:d6:9f:fd:8c:e9:47:6a
Initialised zlib (RFC1950) compression
Initialised zlib (RFC1950) decompression
Initialised AES-256 client->server encryption
Initialised AES-256 server->client encryption
Using username "gpearson".
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: 94, Number: -1
Changing directory to "\".
Type: SSH_FXP_REALPATH, Size: 10, Number: 16
Type: SSH_FXP_NAME, Size: 27, Number: 16
Type: SSH_FXP_OPENDIR, Size: 12, Number: 267
Type: SSH_FXP_HANDLE, Size: 13, Number: 267
Type: SSH_FXP_CLOSE, Size: 13, Number: 516
Type: SSH_FXP_STATUS, Size: 34, Number: 516
Getting current directory name.
Listing directory "C:/C:".
Type: SSH_FXP_OPENDIR, Size: 14, Number: 779
Type: SSH_FXP_HANDLE, Size: 13, Number: 779
Type: SSH_FXP_READDIR, Size: 13, Number: 1036
Type: SSH_FXP_NAME, Size: 1683, Number: 1036
Type: SSH_FXP_READDIR, Size: 13, Number: 1292
Type: SSH_FXP_CLOSE, Size: 13, Number: 1540
Type: SSH_FXP_STATUS, Size: 44, Number: 1292
Type: SSH_FXP_STATUS, Size: 34, Number: 1540
Startup conversation with host finished

Look at the line:
Listing directory "C:/C:".

Doesnt seem right. I can create folders and files, but not see them.

Thanks

Greg

FireWire wrote:

I keep getting the same error no matter what I try. I tried /bin/bash and /bin/ksh and /bin/tcsh and nothing worked.

"Error getting name of current remote directory."
"Connection has been unexpectedly closed."

Any ideas?

Have you tried SFTP with WinSCP 3.0 beta?

Still an issue more than 15 years later.

brunis wrote:

Still an issue more than 15 years later.

Sorry, your post does not include enough information.

Please read how to troubleshoot problems with WinSCP. If it turns out that you are not able to help yourself, read how to ask for support or report bugs efficiently, so others can help you.