Here're some general tips to verify for Windows 7 / 8 / 10 computers:
You must have administrative rights/privileges over your domains, workstations and servers of your network.
Read more: How to get administrative rights?
The "RemoteRegistry" service must be up and running on the remote computer.
Our software needs this service to be started in order to remotely recover certain information such as IP addresses, MAC addresses or use remote control functions.
You can automatically configure in Automatic start using a GPO:
Windows Server 2003 Domain Controller
- Open the Group Policy editor
- Navigate to, Local Computer Policy > Computer Configuration > Policies > Windows Settings > Security Settings > System Services
- In the right hand pane locate Remote Registry
- Define the policy, and set the Startup type to Automatic
- Reboot the clients to apply the policy
Windows Server 2008/2012/2016/2019 or Domain Controller
- Open the Group Policy editor
- Expand Computer Configuration > Policies > Windows Settings > Security Settings > System Services
- Find the Remote Registry item and change the Service startup mode to Automatic
- Reboot the clients to apply the policy
Network discovery need to be activated. When Network Discovery is on, the Windows 7 / 8 / 10 computer can see other network computers / devices and become also visible to other network computers and to our software.
This is in Control Panel, Network and Sharing center, Advanced sharing settings
- File and Printer sharing :
File and printer sharing need to be activated on the Windows 7 / 8 / 10 computer.
This is in Control Panel, Network and Sharing center, Advanced sharing settings
Before administrate a Windows 7 / 8 / 10 station, we strongly recommend you first to DEACTIVATE "User Access Control" aka UAC.
This is in "Control Panel" ,"User Accounts" , "Turn User Accounts Control on off".
To take the remote control of Windows 7 / 8 /10 computers with "TightVNC", you'll have to add an exception on the remote computer, into the Windows Firewall for the communication port used by the program (5900 by default) and/or for the program "\Windows\Pointdev\VNC\WinVNC.exe" (VNC Server service) if you use version 1.X of the remote control tool, or for the program "\Windows\Pointdev\VNC\tvnserver.exe" (tvncserver_Pointdev service) if you use version 2.X.
The point of creating an inboud rule on the TightVNC program is to not have to modify again this rule if you decide later to change the communication port used by TightVNC.
Control Panel -> System And security -> Windows Firewall -> Advanced Settings -> Inbound Rules -> New Rule ... -> Check "Program"
Example :

Last, check in the Network Settings if NetBIOS layer is enabled.