We ran into this same exact problem. It happened only on one of our VCHB instances, our handful of other instances did not have this problem. After much poking around, we noticed that the problem VCHB virtual/public name had a Computer Object entry in AD, while (most of) the others did not. We wondered if this was somehow related to the problem. We checked with VMware support, and were eventually told that it would be OK to delete the AD Computer Object for the virtual\public name. We deleted the AD object, waited for about an hour, and (somewhat to our surprise) this actually fixed the problem--we were able to RDC to the virtual/public name without any trouble.
↧