All the trace tells you is that those hosts don't respond to traceroute packets (ICMP). In some cases, depending on the problem, you could look at this and say "there's something wrong in the path from me to vmware", but in most cases it doesn't give you any solid evidence one way or the other. Many routers won't respond to ICMP traffic, due to the fact that responding to ICMP traffic diverts a router from it's intended job, which is to route "real" traffic as quickly and efficiently as possible. In addition, many web servers are configured to not respond to traceroute or ping traffic as well. I don't allow ping or traceroute traffic to any of my servers. I only allow ping and traceroute to one host on the perimeter of my network, as a basic diagnostic tool.
I ran a tracert to vmware.com and got the same results as you... because vmware.com and www.vmware.com resolve to different ip addresses in different net blocks... so your traceroute is not testing the right end point anyway. I can traceroute successfully to www.vmware.com.