Skip to main content

Trendmicro Deep Security 9.5. Failed to download VIB. ESXi can't connect to DSM Port 4119

Ok. This error is experienced when using Trendmicro Deep Security 9.5 (seems to be other versions also). The problem is that the Trendmicro Deep Security manager isn't resolving DNS queries to the ESXi host. Don't get crazy with it...it really is that simple.

"Failed to download VIB. ESXi can't connect to DSMP Port 4119." This error happens when your trying to upgrade ESX Filter Driver's from one version to a later and more current version. (This is when you see the error window pop up.)

1. Don't try to manually install the VIB file in ESXi through vCLI or any other direct means.

2. Just check the DNS settings on each VMware ESXi host and confirm that your DNS settings are correct. If your getting this error, it's because something is not resolving DNS or (worst case scenario). You have some networking issues.

3. Check your vCenter settings for each ESXi host first before getting hardcore into troubleshooting. (NOTE: Yes. This is the windows vCenter client screenshot. I will only use the horrible new web client when I am absolutely forced to use that junk.)


4. Now that you have re-verified and "fixed" your DNS IP addresses and FQDN's for the domain suffix. Right-click on the "Upgrade Recommended" and run "Upgrade Filter Driver" again.


5. Now the host will enter maintenance mode, reboot and then come up as "Prepared". Be patient. Sometimes it takes a few minutes for the ESXi hosts to boot.

Popular posts from this blog

How to Fix /storage/core filesystem Out of Disk Space Error on VCSA 6.0U1

How to fix the error of "The /storage/core filesystem is out of disk space or inodes"


Step 1: Login to the new VCSA 6.0U1 HTML5 web client. https://ip address:5480



Step 2: Enable SSH and Bash Shell
Step 3: Login as root and type "shell" at Command> shell
Step 4: df -h (Check if it's out of space)
/dev/mapper/core_vg-core               50G   50G     0 100% /storage/core
Step 5: Stop the services of VCSA: 
hostname: # service vmware-vpxd stop hostname: # service vmware-vpxd status (make sure it is stopped)
Step 6:  cd /storage/core
Step 7: rm -rf *.tgz (be CAREFUL...do this in the wrong directory and you will be retrieving from a backup.)


If you need help. Go to Cybercity (http://www.cyberciti.biz/faq/delete-all-files-folder-linux/
Step 8: service vmware-vpxd restart

Step 9: history -c
Step 10: Refresh the browser (https://ip address:5480). Now it's all green


VMware KB: (

How to Configure HP ILO 4 for Active Directory Login

1. Make sure that your Windows Active Directory Domain Controller has an SSL Certificate to support port 636 (HP's authentication doesn't like 389)

2. Use Softerra LDAP Administrator (or whatever is your preferred tool to get the OU path) if you don't know how to do it by heart (which...um...sometimes its better to verify).

3. Make sure that you have a way to authenticate users by adding in the OU where your restricted accounts are located. You don't want anyone in the domain to be able to login to the server.

ILO Login > Administration > User Administration - Click New and Add the Group DN Only:



Click Add Group and then you will see your group added. (*Make sure it's a security group)


4. Add in your Windows Active Directory DC to authenticate against (Verified against 2008R2):

ILO Login > Administration > Security - Directory (*Make sure it's the OU where the security group is)


5. Sign Out (Log off) and then Log Back in (If you don't see Direct…

VCSA vmware-vpxd Service Won't Restart After Upgrading to 6.0 U2

You navigate to the VMware Web Client and you get this 503 Error:
503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x7fe4a805cc90] _serverNamespace = / _isRedirect = false _pipeName =/var/run/vmware/vpxd-webserver-pipe)
Cause:(SSL Certificates wouldn’t issue automatically after reboot for service vmware-vpxd
Compounded Problem:(Clearing logs under ~/.* **root**) – Specifically, clearing ~/.pgpass 
(Lesson Learned: NEVER EVER CLEAR FILES UNDER ~/. Except .bash_history on templates creation only!!!)
Fix: Kill all the services running vpxd
1. ps -ef | grep vpxd 2. kill ### 3. Re-add the ~/.pgpass file with the PostGreSQL password 4. vi /et c/vmware-vpx/embedded_db.cfg 5. Copy the password you see between PGUSER_PASSWORD=’password here‘ 6. Put the password back in ~/.pgpass
localhost:5432:VCDB:postgres: password here localhost:5432:postgres:postgres: password here localhost:5432:VCDB:vc: password here
7. Check /etc/hosts and make sure config is there. 10.…