We have been using Putty with ESX i 4.0 and ESX 3.5 without problems.
Now, we have gone into ESX 4.0.1, but Putty logons are rejected again and again.
Any clue or document or pointer or URL ?
Thanks. Sebastian.
Are you logging in as root? Root SSH is disabled by default.
Can you log in with a non-root user from the console of the ESX server?
VI3 VCP
Make sure the firewall didn't get reset and is blocking SSH connections.
SSH to root over the network is disabled by default in ESX 4.0 update 1 (turkina has already mentioned this). You can enable SSH if you should choose to. Although best practice suggests that you should create a non-privileged account, then use su or sudo after you have logged into the console.
If you should want to enable SSH here is how to do it:
Go to the service console on the physical server and log in
vi /etc/ssh/sshd_config
Change the line that says PermitRootLogin from “no” to “yes”
restart the sshd service by typing: service sshd restart
Thanks for your interest, Mike.
My laptop's Firewall(s) have been disabled, and I can use Putty and WinSCP to go into ESX 3.5 and ESX i v4.
Is there a Firewall in ESX ???
Best luck.
I did know that very good "best practice" and never user remote root login.So, I am trying with "sebas" user, and it fails.
Anyway, I shall check SSH is enabled !
Dennis - you did not say it but you almost knew it, now I know !
Thanks a lot.
Try to temporally enable the root access to see if the problem is in SSH configurarion/connection or on user configuration.
The user has a valid shell and password? Or are you using a key authentication?
Andre
Hey, André - thanks for you time.
a) I dont like enabling "root" access - let me fix that using "normal" user putty and/or ssh.
b) shell and pwd - I will verify, thanks. It's one of those "stupid" items you dont know how to explain when it comes to be your fault ....
c) keu auth - no, thanks. Not yet. JeJeJe
a) I dont like enabling "root" access - let me fix that using "normal" user putty and/or ssh.
I agree, but it could be only for testing.
If if works then the problem is on your user configuration.
If if not works then there is a networking/firewall/configuration problem.
Andre