Connect-VIServer -- Network Connectivity Error

If you are using Connect-VIServer from vSphere PowerCLI to connect to your vCenter but you encounter network connectivity error, this might be caused by Tomcat server in your vCenter is not running.

To solve this problem, we need to start Tomcat service in your vCenter.

Click on Monitor Tomcat

 And you can start the service through the Tomcat icon in the system tray.

After that, you should be able to connect to your vCenter using Connect-VIServer

ESX 4.1 - initialization of module ipmi_si_drv failed

If you encounter such problem and you are sure your system doesn't support ipmi, you can disable it by editing this file /etc/vmware/init/init.d/72.ipmi

Add in the following line (italic) and save the file.

return ${SUCCESS}

Exec esxcfg-init -I || {
return ${NON_CRITICAL_FAILURE}
}

VMware ESX 4.1 smb - mount error 111 = connection refused

If you encounter the following error when you try to mount to a CIFS share on a windows server from service console as shown below:

[root@esx41 mnt]# mount -t cifs //192.168.44.88/shared /mnt/CIFS -o user=administrator
Password:
mount error 111 = Connection refused
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

This is probably caused by the ESX firewall issue, to enable Samba client connections:

[root@esx41 samba]# esxcfg-firewall -e smbClient

And this should fix the mount error 111 problem.

How to enable VMware Web Access

Go to the console and log in. First check the status of VMware web access service by typing this

service vmware-webAccess status

if the service is stopped, just type

service vmware-webAccess start

and you should be able to login to web access.

To have web access enabled every time you start your ESX server, type the following command:

chkconfig --level 345 vmware-webAccess on