HomeVirtualizationVMwareUnable to Access the VCSA 6.7 via WinSCP

Unable to Access the VCSA 6.7 via WinSCP

One of the many and easiest ways to get the logs from the ESXi hosts and vCenter Server Appliance (VCSA), is accessing directly to the files directory using tools such as WinSCP, which helps to transfer the files between a local and a remote computer ( Ex. VCSA).

"SCP is an older protocol but almost universally supported on Unix-like platforms as part of an SSH protocol suite. It is rarely supported on other platforms. SCP is a descendant of the ancient rcp.”

Here, you can download WinSCP.

I never have had issues with the ESXi hosts and WinSCP, however, trying to access the VCSA is a different story.


Unable to Access the VCSA via WinSCP

Trying to establish a connection to the VCSA 6.7 using WinSCP client, I was getting the following error: "Host is not communicating for more than 15 seconds. Still Waiting..."

- Advertisement -
Unable to Access the VCSA via WinSCP

And after a few seconds, I got this other message: "Received too large SFTP packet. Max supported packet size is 1024000 B"

Unable to Access the VCSA 6.7 via WinSCP


The default Appliance Shell cannot be used to access remotely via WinSCP. You must enable the Bash shell on the appliance.

There are two workarounds to solve this issue, and the first one is easier than the second. However, the first option didn’t work for me.

If you have the same issue, try first option one.

Option one

  1. Open WinSCP and open a new session.
  2. On the new session Login window, click Advanced...
WinSCP SFTP Advanced
  1. Select SFTP under Environment.
  2. On SFTP server input: shell /usr/lib64/ssh/sftp-server
  3. Click OK.
WinSCP Advanced Settings SFTP server

Update from the comments: On the SFTP server field, the input should be: shell /usr/libexec/sftp-server. I haven't tried, but it should work. This is the quickest and ideal option. If you still have an issue, try option two.

- Advertisement -

If you try the connection to VCSA again, you should be able to connect. I couldn't, so I used the below option two.

Option two

  1. Access to the (VCSA) the Appliance Management. https://vcsa_ip:5480
  2. Navigate to Access and click Edit under Access Settings.
VCSA 6.7 Appliance Management
  1. Switch on Enable SSH Login and click OK.
Enable SSH Login VCSA 6.7

Note: Enabling the Bash Shell here is not going to work.

  1. Access to the VCSA via SSH.
  2. Type: Shell
  3. Change the default Shell to Bash typing: chsh -s /bin/bash root
VCSA 6.7 change Shell to Bash

After enabling Bash Shell, you could use WinSCP to access your files in the VCSA.


Juan Mulford
Juan Mulford
I have been active in IT for over fourteen years now. I am a solutions architect, working with storage, virtualization, and VDI solutions. For the past ten years, I have been living and working in Taiwan.


  1. Hi Juan,
    Thanks for your explenation. I had to go for the second as well.
    Afterwards I felt pretty stupid since the Nuggetslab I was using explained.
    Anyhow this made me solve it.

  2. For VCSA 6.5 and 6.7 you have to use “shell /usr/libexec/sftp-server” in the WinSCP SFTP Server field, not the one shown above. Login as the VCSA root user, this removes the requirement to enable the shell. Hope this helps.

    • Thanks Juan, 2nd method worked on one of my 6.7 VCSA but using JV's SFTP server, that worked on another VCSA without making the 2nd change.

Leave a Reply

- Advertisement -

Popular Articles


Raspberry Pi OS in a Virtual Machine with VMware

Although the Raspberry Pi OS is designed and optimized for the Raspberry Pi module, it is possible to test and use it without its hardware, with VMware. This solution can be useful if you are a developer (or just a curious guy) and don't have a Raspberry Pi module with you
Unable to delete inaccessible datastore

Unable to delete an "inaccessible" datastore

I was switching my storage array, so I migrated the VMs from that old datastore/storage to a new datastore/storage. The old datastore was shared by 3 ESXi hosts, no cluster. After migrating the VMs and unmount/delete the datastore, it was still presented in two of the ESXi hosts and was marked as inaccessible.
This is not a valid source path / URL

This is not a valid source path / URL - SourceTree and Gitlab

I have been working on a project with a friend who set up a repository in Gitlab but even though I was able to view all projects on it, I couldn’t really join the repository. I was using SourceTree and Gitlab.

How to export a Virtual Machine using the VMware OVF Tool

The VMware OVF Tool is implemented by VMware for easily importing and exporting virtual machines in Open Virtualization Format (OVF) standard format. Here, I want to show you how to download and install it, and then how to use it from a Windows machine.
Couldn't load private key - Putty key format too new

Couldn't load private key - Putty key format too new

couldn't load private key - Putty key format too new.” This issue happens when you use PuTTygen to generate or convert to a ppk key. Here is how to fix it. 
- Advertisement -

Recent Comments