ssh on ESXI not working!

Hello,
 I'm very new to VMware and I'm trying to get SSH working so I can use Symantec System Recovery to Create a VM of a physical machine (I guess it says I need to have SSH enabled to copy the files.) I went through the proceedure I found online but I'm not having any luck. The machine is local on my network and I am able to ping and get to the box by using the infrastructure client. I have disabled my firewall on my PC and still no SSH. I've used putty and I keep getting a connection refused message
Here is the procedure I followed:

   1.  Go to the ESXi console and press alt+F1
   2. Type: unsupported
   3. Enter the root password(No prompt, typing is blindly)
   4. At the prompt type vi /etc/inetd.conf
   5. Look for the line that starts with #ssh (you can search with pressing /)
   6. Remove the # (press the x if the cursor is on the character)
   7. Save /etc/inetd.conf by typing :wq!
   8. Restart the management service /sbin/services.sh restart

I've restarted the machine completely and haven't had any luck.

VMware Server 3i 3.5.0 build 123629


LVL 1
jbla9028Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

vmwarun - ArunCommented:
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bleeuwenCommented:
Hi, this is the right procedure, and if you have rebooted the esx it should work (after update 2 the management service restart command does not work). Check the line #ssh, are all spaces gone in that line (before the ssh)?
Are you sure, everything is allright in your localhost (firewall)?
0
jbla9028Author Commented:
I just got in. I'm not really sure what was going on but I redid all the steps including the extra directions to kill the proc-id. I didn't see a proc-id though for anything. I restarted the server and I finally was able to get in. very strange. Thanks though.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.