ARD has blocked VNC?
Yesterday, I installed ARD 3.7.2 on both my MacBook Pro (late 2013, retina) as well as my Mac mini (early 2009) which I run as a server. Since rebooting after the installation I can no longer access the machine over VNC locally or remotely, via the ARD client, OS X, or third party VNC clients such as Screens. Both machines have 10.10.1 installed, with the mini running OS X Server 4.
All other local and remote connections still work including SMB, AFP, SSH, FTP, VPN, Server Administration, etc. It's just VNC that will not go through.
As a server, VNC is my primary method of connection with the Mac mini, and ARD itself was installed via VNC. After installation, everything worked fine and I could still connect. After rebooting, however, the connection simply will not open; any client will stop at the "Connecting..." portion of the process.
Is there some known conflict that ARD has that can cause a VNC connection to be blocked? The mini is set up to act as Task Server, and also has Screens Connect installed, with it configured to the public port 5900 (as expected). The firewall is also allowing connections over VNC.
I've tried disabling the firewall, disabling Screens Connect and ARD Task Server (incase these were 'hogging' port 5900, if that's a thing...) to no avail. I haven't yet tried uninstalling ARD in hopes that there may be a quick fix and I don't have to start unpicking what I've set up.
Has anyone experienced this before?
Mac mini, OS X Server, OS X Yosemite (10.10) DP5