VMware Cloud Community
projectja
Contributor
Contributor
Jump to solution

Unable connect from winscp to esxi 5.0

SCENARIO:

HI guys, I am trying to test with a small lab. This is the conf_

Lab:

Computer  1: Windows 7. Firewall off

Computer 2:  Esxi 5.0 / ssh enabled

From Windows 7 with Winscp I try to connect to the server with the ip address. Root and password. It is not possible, I get (Network error, expired time),

I run ping command from windows 7, it is ok.

Any idea, please?

1 Solution

Accepted Solutions
durakovicduro83
Enthusiast
Enthusiast
Jump to solution

Yes tray to telnet 22 port

Or if use winascp the file protocol must be "SCP"

Capture.JPG

Cheers,

Denis

To err is human - and to blame it on a computer is even more so

View solution in original post

9 Replies
weinstein5
Immortal
Immortal
Jump to solution

Welcome to the Community - Have you enaled SSH access to your ESXi host?

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
projectja
Contributor
Contributor
Jump to solution

Thanks for the reply,
Yes, I have enable SSH in Esxi host,and I have restarted the services. Any aditional configuration is requiered from client side?
0 Kudos
a_p_
Leadership
Leadership
Jump to solution

Windows 7. Firewall off

Did you disable the Firewall service or just disable the firewall? This may make a difference. I'd suggest you let the firewall service run and make sure the port for SSH is open.

André

myatthu9
Enthusiast
Enthusiast
Jump to solution

Try with telnet first

telnet [ESXi 5  IP address] 22

Steps to enable telnet client at Windows7

  1. Start
  2. Control Panel
  3. Programs And Features
  4. Turn Windows features on or off
  5. Check Telnet Client
  6. Hit OK

Cheer

share knowledge, extend knowledge [RHCE,MCITP]
0 Kudos
durakovicduro83
Enthusiast
Enthusiast
Jump to solution

Yes tray to telnet 22 port

Or if use winascp the file protocol must be "SCP"

Capture.JPG

Cheers,

Denis

To err is human - and to blame it on a computer is even more so
projectja
Contributor
Contributor
Jump to solution

Hi again,

Thanks you very much for your replies..

First I would like to point out I am using ESXI 5

Replying to your recomendations:

Before sending my first post and in response to all of you:

yes, I had turned off the firewall.

yes, I had enabled telnet command in windows 7.

yes, I had enabled SCP conection -from the list option in WinScp GUI)

However the problem was as follows:

- I had enabled SSH at Esxi console, locally, in the System Costimization console

- However, I had not enabled SSH thorugh vsphere client, so I've connected thorugh vsphere client, and in security proporties I've enabled SSH in configuration + security profile + services: SSH service.

I dont really understand why is necessary to enable SSH in those both options (through esxi console and vsphere client) .

After that, now I try to log with winscp -with root- and I log in succesfully , however I get this Error:

1882501.png

I am not sure whether this error is because I am using root user and this root user is not enabled yet to access. However I get logged in.
0 Kudos
myatthu9
Enthusiast
Enthusiast
Jump to solution

You definitely not need to enable at both Console and vSphere client.

Actually, it is same function. If you enable or disable at one of them, it will reflect at the other gui.

Once you enable the SSH access at either one. You can directly SSH or SCP with root account by default. Unless, someone configure it to "not" allow with root id for security reason.

Otherwise, you don't need to specify -with root switch.

You need to select SFTP and check Allow SCP failback.

temp.JPG

If you select SCP, it will receive warning but you can click OK and go ahead.

temp2.JPG

share knowledge, extend knowledge [RHCE,MCITP]
0 Kudos
projectja
Contributor
Contributor
Jump to solution

Yeah man!
I've just logged in suscesfully.
Myatth9, Yes, you're right! It is not necessary to enable SSH access in both places "Esx host onsole" and "Vsphere client". I made a mistake in Esx
console options. I set "Esx Shell" to enabled, however I completely forgot to enabled "Enable SSH"
This KB helped me as well:
On the other hand, I log in with option "sftp" and "scp" in Winscp GUI, and it work with no error.
Nevertheless I would like to know that that error means.
,
0 Kudos
myatthu9
Enthusiast
Enthusiast
Jump to solution

What I can guess, vmware only allow ssh protocol for their trained engineer to go in remotely and troubleshoot.

VMware doesn't like you maniputate the directory structure or whatever using tools like WinSCP. So that they put warning or error.

I am agree with them in some sense that if user doesn't know what he doing, it will mess up the VMware OS.

share knowledge, extend knowledge [RHCE,MCITP]
0 Kudos