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!