Here's my intention: I have a main system running Windows 10. I have two GUI systems running Mint 18.2 that I wish to connect to and control from the Windows system. All three systems are connected to the same router via ethernet. No router configurations have been made, so everything should be on default.
I currently use TeamViewer to connect, but this is done via an internet connection, not a LAN connection. I was never able to get LAN to work with TeamViewer. Regardless, I want to move away from TeamViewer and use an alternative.
This is what I'm currently attempting: I have TightVNC installed on the Windows computer, and tightvncserver installed on the Mint systems. When I open up TightVNCViewer on Windows, I am asked for the remote host information, which in the case of the Mint systems are 192.168.1.25 and 192.168.1.2. Connecting with this results in the following error:
Error in TightVNC Viewer: No connection could be made because the target machine actively refused it.
If I changed the addresses to 192.168.1.25:1 and 192.168.1.2:1 respectively (since the Mint systems say New 'X' desktop is machinename:1), I am asked for the password I set. I enter this, and I simply see a grey screen with a X cursor. It doesn't seem like I can interact with the systems thus far. The cursor does not move in Mint along with mine in the Windows VNC window, nor are there any responses to ctrl+alt+F7 or any of the variants of those controls. The :1 seemed like an odd addition, as I had assumed it was meant to be the port number.
From what I can see, if it accepted a password, then it must mean that I have been able to reach the Mint systems from Windows in some capacity. This seems to suggest that I need to do some more work on something on the Mint systems' ends before things function as intended.
That said, someone mentioned that tightvnc is not the solution I'm supposed to be looking for. If it isn't, what is?
Also, I don't know if it makes a difference, but the Mint systems don't run with monitors attached. If a monitor is connected after booting, I don't see the desktop, even though things are still running (assuming full load heat output is anything to go by), so I need to restart with a monitor already connected. Heard this has something to do with X and nvidia drivers or something, but I'd imagine it might affect vnc usage if im trying to connect when no monitor is present.