Unable to Access the VCSA 6.7 via WinSCP

Juan Mulford

5 years ago

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.

In This Article:

Problem:

Unable to Access the VCSA via WinSCP

Solution:

Option one

Option two

References

Problem:

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..."

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

Solution:

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

Open WinSCP and open a new session.
On the new session Login window, click Advanced...

Select SFTP under Environment.
On SFTP server input: shell /usr/lib64/ssh/sftp-server
Click OK.

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.

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