You may get an error stating: “Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed” when deploying VNC to remote computers or running scripts remotely.
This error goes way back to the early days of Windows networking and it’s shameful that Microsoft hasn’t corrected it, yet. A Windows computer can connect to a network resource such as a remote share only once with a single set of credentials.
For example, if I log onto the domain as boztecksteveb and map a drive to \server1share1 using that account, I can not later issue a command to connect to \server1share2 supplying alternate user credentials in the command line. My computer can only authenticate me against \server1 once. If I try, I will get the error above.
The Work Around
There’s a simple way to trick Windows into thinking that \server1 is a completely different machine, allowing you to authenticate against it a second time. If the IP address for \server1 is 10.1.1.1, you simply reference it by that IP address of \10.1.1.1share2 and pass it the set of credentials required to connect. Windows treats \server1 and \10.1.1.1 as completely different machines!
You can do this in VNCScan in a few locations depending on the scope that you wish to apply. Most people just do it globally in the main program preferences.
There’s an option there labeled, “Use IP address instead of HostName”. Checking this box will allow you to get around this error. There is a similarly worded checkbox in both the group properties and computer properties.
Maybe some day Microsoft will widen up this limitation but until then, this should get you by.