Trouble copying between ESXi 5.0 servers.
- February 28th, 2012
- Posted in Documentation
- Write comment
Despite having ssh enable on both ESXi 5.0 servers, I found that I could copy to the server from a desktop client or non-ESXi server without issue. However, when I wanted to copy between ESXi servers it did not work. It would just timeout:
ssh: connect to host la-host04 port 22: Connection timed out
I have discovered that the issue is the Security Profile on each of the ESXi servers. Through the vSphere client, you need to click on the ESXi server, then click on the Configuration tab. From here, select Security Profile, and click on the Firewall Properties …
Then, you just need to check off the SSH Client under Secure Shell. This will open up ssh communication between ESXi servers. You can restrict the settings by accessing the Firewall Settings for any of the services.
UPDATE 1:
To enable from the command line using esxcli:
To list your current configuration:
# esxcli network firewall ruleset list
To enable sshClient to enable copying using ssh:
# esxcli network firewall ruleset set –ruleset-id sshClient –enabled yes
To refresh the configuration:
# esxcli network firewall refresh
UPDATE 2:
For ESXi 5.1 Update 1:
# esxcli network firewall ruleset set -e true -r sshClient
Very good. Thank’s!
Hi, this article worked just great for me. i wonder if we can enable the sshClient from command. i’m using Putty to console to my esxi for now.
thanks for your article
@hery
Actually, you can:
To list your current configuration:
# esxcli network firewall ruleset list
To enable sshClient to enable copying using ssh:
# esxcli network firewall ruleset set –ruleset-id sshClient –enabled yes
To refresh the configuration:
# esxcli network firewall refresh
nice, saved me a ton of hair pulling
thanks, good trick to know, this helped!
Thank you so much. Big help, I have been banding my head against the wall 🙂
Very useful!!!
Thanks man!
You’re my star!!!
Hallelujah! Thanks to you and my friend Google, I managed to make this work!
This is exactly the problem I was experiencing, and the fix was on target. Thanks!