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?
Yes tray to telnet 22 port
Or if use winascp the file protocol must be "SCP"
Cheers,
Denis
Welcome to the Community - Have you enaled SSH access to your ESXi host?
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é
Try with telnet first
telnet [ESXi 5 IP address] 22
Steps to enable telnet client at Windows7
Cheer
Yes tray to telnet 22 port
Or if use winascp the file protocol must be "SCP"
Cheers,
Denis
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:
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.
If you select SCP, it will receive warning but you can click OK and go ahead.
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.