VMWare Server Firewall Exceptions
After spamming some netsatat -ano | find "my.srv.ip" I found the required firewall exceptions for remote management of VMWare instances remotely. (I was too lazy to look it up)
There's only two, and they are:
If you only get the obvious 8333 (default web management port), it will throw somthing like this: error opening the remote virtual machine the host name could not be resolved.
To get around that, add the remote server's netbios name to your hosts file (e.g. server 192.168.1.10).
Next you'll hit some other error, and thats when you add TCP 902 to your firewall exceptions too. After that the VMWare player will connect normally and your VMs will be manageable without first using remote desktop. Yay!