Shell=shell

@TheG: That worked!!! Thank you

@TheG: Thanks for sharing your solution.
You can specify the shell easier here:
https://beta.winscp.net/eng/docs/ui_login_scp

Was having this problem too with ADC/NetScaler – even though has worked in the past fine on countless upgrades and worked on another NetScaler fine on the same day.
Took a while to figure out – but I had to go into the "Raw Site Settings" in the Advanced drop down while configuring the initial connection. Then Add button -> select Shell from the list, type shell – as the Shell to use (since this is the first command to enter in NetScaler when ssh to the appliance).

Hope this helps someone.

@sridevi: Hard to tell without seeing a log file.
Your server or environment probably does not meet WinSCP requirements:
https://beta.winscp.net/eng/docs/shell_session

When trying to open WinSCP terminal the terminal is stuck at starting the session line and not proceeding further. Please help to resolve this error

@sloncer: Interactive stuff like sudo (if it prompts for a password) needs to go to .bash_profile.
For details, see a similar problem here:
Received too large (… B) SFTP packet. Max supported packet size is 1024000 B

My WinSCP session was stuck at "starting a session". The issue I had was in the .bashrc file I had a command to sudo to another user. Once I removed this line, WinSCP worked. So please make sure .bashrc doesn't have sudo or cd to a directory that has no permission for the user.

martin wrote:

Did you try SFTP?

It works.

@AdrianW: Thank you worked for me!

MorgueFLB wrote:

Regarding PuTTy, I was highlighting the fact that the server can be accessed via SSH on port XX with the supplied credentials, thereby eliminating those items as possible causes of the problem.

The "server can be accessed via SSH on port XX with the supplied credentials" even with WinSCP. You get a problem only later, when WinSCP tries to talk to the shell.

I will give the SFTP protocol a try. I'm completely positive I didn't use it before, but just in case it works, I will try any suggestion :)

Regarding PuTTY, I was highlighting the fact that the server can be accessed via SSH on port XX with the supplied credentials, thereby eliminating those items as possible causes of the problem.

I wasn't aware that it might affect the connection. As far as I know, no changes have been made to the SSH server - otherwise I don't think PuTTy would work.

Something must have changed. Either on server. Or in your WinSCP configuration. Maybe you have used SFTP protocol before. Just try to change the protocol. No other configuration should be needed.

That PuTTY works has nothing to do with your problem. PuTTY is not SCP/SFTP client.

Thanks again for your helpful response.

I connected to this server for several months using WinSCP with no problems. The server is a Windows 10 box. For SSH, it is running MobaSSH, found here: https://mobassh.mobatek.net/

I have not tried SFTP – is this simply a matter of changing the File Protocol, or will I have to make other changes?

You know WinSCP much better than I do, and you are no doubt therefore correct about the use of the 'obscure SSH server'. I wasn't aware that it might affect the connection. As far as I know, no changes have been made to the SSH server – otherwise I don't think PuTTY would work.

If you still think I should create a new thread, I'll do so.

Thanks very much Martin.

WinSCP needs a bash-line shell for SCP protocol.
Your default shell is Windows cmd.exe.
Do you have reason to believe that your server does support any bash-like shell?
I've never seen "SSH-2.0-MS_1.100" server before.
Are you sure you were ever able to use SCP protocol with WinSCP against that server?
Did you try SFTP?
In general, the log file (and your use of an obscure SSH server) just confirmed that your have a quite specific problem, that is only likely to actually confuse those coming to this thread.

Hi there Martin

Thanks for your response and your interest in helping me resolve this problem!

I would like to do as you have requested, but before doing so, I would like to motivate why continued discussion in this thread is justified:

The topic of this thread is *Stuck at "Starting the session". Please help*. Until a complete resolution to the issue is found (the issue being that WinSCP isn't logging in), creating a new thread only serves to confuse users of WinSCP that come here looking for a solution to their problem.

A guest user above suggested "in WinSCP change the shell in advanced options to shell (type in)." And @AdrianW above said:

The cause of the problem might that the remote directory does not exist anymore AND you have set
Advanced -> Environment -> SCP/Shell -> Shell: "Default"

The failure to set the current directory seems to break the shell auto-detection. So if you set an explicit shell, the problem goes away.

Other solutions:
– choose an existing directory (Advanced -> Environment -> Directories -> Remote Directory:)
– re-create the directory in a separate SSH session

I believe that he is correct. I think the remote directory no longer exists. So I have specified a directory that I know exists in the Remote Directory setting.

But I do not know how to 'set an explicit shell' or to do as the Guest user suggested (change the shell in advanced options to shell (type in))

Changing the SCP/Shell setting from "Default" has only partially solved the problem.

Let me describe the issue in more detail:

I logged into the same server regularly, then suddenly one day WinSCP would just sit at "Starting the session" and never get any further – I left it for hours to check. And I did so on multiple occasions, just to make sure that it wasn't due to some sort of temporary or intermittent communication failure somewhere on the internet.

Note that at this point, if the user chooses to cancel the login process (by clicking on the [X] in the WinSCP login dialog), the status changes to "Cancelling..." and remains in that state for several minutes before WinSCP actually cancels it's attempt. During this time, the user can no longer interact with WinSCP in any way. WinSCP cannot be closed gracefully, and has to be manually terminated.

Searching the internet, and even the WinSCP site here, produced no clues as to what might be happening. The log file, while comprehensive, is utterly useless to anyone who isn't a WinSCP expert. I have been searching for a solution to this problem for a long time.

Note: I have attached the log file to this reply, selecting the Private file option. Inside the log file, I have also changed server names and addresses and usernames and passwords.

Yesterday, I found this post from @AdrianW that recommends changing the Shell/SCP option from