Try this for your ssh issue, make sure your user has permission to use it.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1017910



Sent from my blackberry

From: Waldron, Michael H [mailto:mwald...@email.unc.edu]
Sent: Tuesday, May 24, 2011 07:07 AM
To: vcl-user@incubator.apache.org <vcl-user@incubator.apache.org>
Subject: VMware ESXi 4.1

Has anyone used the free version of VMware ESXi 4.1?

I started playing with it to possibly use with our VCL after it's been upgraded 
to 2.2.1, however I can't figure out how to get both our public and private 
networks defined on it. After initial install on a blade, it configures the 
public interface and I'm able to connect to it via the vSphere client. But 
everytime I try to add the private network to it, it configures a virtual mac 
address rather than using the mac address of the physical interface like it's 
doing for the public interface.

The result is this interface is getting a 169.254.0.1 IP address, rather than 
the IP it should get from the DHCP server. I also enabled SSH on the security 
profile, however it's not answering SSH connection attempts.

Just wondering if anyone has had some experience with setting this up.

Mike Waldron
Systems Specialist
ITS Research Computing
University of North Carolina at Chapel Hill
CB #3420, ITS Manning, Rm 2509
919-962-9778

Reply via email to