If you are on a distributed network with multiple domains,
you know the headache of performing administrative tasks and dealing
with permission issues. VNC Scan has built in user authentication
to accommodate the multiple ID badges that you must wear across your
network.
We realize that many of you are not running
a Windows domain environment so we included a %HOST% variable that you
can type in instead of a domain name. This will tell VNCScan to
authenticate you against the local security database on the computer
that you are trying to access instead of your own or a domains.
VNC Scan does this in a layered approach. You
can set the Windows administrator account in three different places.
Computer Properties - If you set the username and password at the
properties of the computer, it will override any other location.
This is helpful if you have a computer in a scan range that has a custom
Administrator password that is different than the rest in the group.
Group Properties - If you set the password here, it will apply to
any computers in the group that do not have a custom username/password
assigned to its properties.
Program Preferences - Finally, if you set the username and password
here, it will apply to any computers in any group that do not have one
specified at the group or computer level. In addition, it will
apply to any computer in the Local Network tab.
Troubleshooting
Still getting access denied errors?
Try using the IP address instead of the computer name
when connecting to computers. This is set in the VNCScan settings
in the Program Options tab. You can see the tab in the screen shot for
item 3 above.
This happens sometimes because your computer may have already
created a null session to the remote computer using your existing
Windows login credentials. In a Windows environment, you can only
log onto a computer name remotely with one token. Using an IP
address instead will create a new token that will allow you access to
the computer under a different name.
