title: After moving server to new VM, VisualVM remote connection can't see Monitor tab or application mbeans
body: <p>I've had a Spring 3.x application running on Solaris (5.10) in a VMWare VM for quite a while. My application registers some mbeans. I've been able to connect remotely to the VM from VisualVM and view data in the "Monitor" tab, and I've been able to see and manipulate my application mbeans in the MBeans tab.</p>
  
  <p>My server was recently moved to another VMWare VM, although the host name and IP address didn't change. We got it all working, I thought, until I noticed some odd behavior when I tried to connect to the VM from VisualVM on my desktop. When I first tried it, I thought it was working fine, but when I looked closer I noticed that there was no "Monitor" tab, and when I looked at the MBeans tab, it didn't have any of my application mbeans.</p>
  
  <p>I can run a local WebLogic instance, and I don't see these issues when I connect locally with VisualVM.</p>
  
  <p>It doesn't seem like it would be a firewall problem. The connection succeeded. In the "Overview" tab I can see all the basic property settings.</p>
  
  <p>Why would my remote connection have "degraded" functionality?</p>