TightVNC Prompt

[ninjafish]

Hi All,

 

I am trying to setup TightVNC for use around the School so that we can attempt to fix errors much quicker. i have got TightVNC deploying via GPO and script and it importing settings via adding a reg key. my only issue is i have set it all up to prompt the user when there is a connection request but this does not seem to work, it just lets me login.

 

the bottom rule i am told will block all other requests from unauthorized vnc viewers, the top rule is currently set to deny but this also does not work. Is there something i am missing?

[pantscat]

I wonder if it doesn't like 0.0.0.0 and 255.255.255.255 as the IP range. Can you try it with something that reflects your subnet?

[ninjafish]

Cheers for the reply,

 

i have tried a number of different IP ranges and have even just had it witha rule to block my ip but it doesnt seem to follow the rules

[DavetheITguy]

You'll be better using ultra vnc, its free and easy to use. You can also deploy it via a free program called Skeepvnc. Take a look, it's so much better than TightVNC.

[ninjafish]

Got tightvnc working but will have a look at ultraVNC and Skeep. the deployment part sounds good. Is ultravnc still free for use in schools?

 

Issue with tightvnc resolved by reinstalling and manually removing all reg keys related to tightvnc

[ninjafish]

As mentioned i got the original TightVNC working by reinstalling and removing the reg keys. however i have changed plan not and on the recommendation of David i am using Skeep and UltraVNC its really easy to setup and works great with AD (based on testing so far)

[Duke5A]

I did something similar to this, but didn't like the idea of TightVNC being installed and running on machines all the time (lots of staff laptops that get taken home here). So I wrote a .Net app that handles dropping TightVNC on a client machine via the administrative share, creating registry keys for configuration (includes a randomly generated password for the session), registering and starting TightVNC as a service and then finally launching the connection app on your end and connecting to the host. Upon closing the app it will deleted and remove keys on the other end. In the event the connection is lost and it doesn't have a chance to cleanup it will also create a script that runs on the next start up of the client that will take care of the cleanup. I can post the source if you're interested.

[ninjafish]

I did something similar to this, but didn't like the idea of TightVNC being installed and running on machines all the time (lots of staff laptops that get taken home here). So I wrote a .Net app that handles dropping TightVNC on a client machine via the administrative share, creating registry keys for configuration (includes a randomly generated password for the session), registering and starting TightVNC as a service and then finally launching the connection app on your end and connecting to the host. Upon closing the app it will deleted and remove keys on the other end. In the event the connection is lost and it doesn't have a chance to cleanup it will also create a script that runs on the next start up of the client that will take care of the cleanup. I can post the source if you're interested.

 

 

This sounds really cool. I am only installing it on devices which are fixed and stay in school but i may come back to you about the script in the future as it does sound awesome

[ass17]

We use it on all PCs in school, sits as a hidden service, with connection password and specific connection port. It installs updates on shutdown VB script.

[wensleydale]

I did something similar to this, but didn't like the idea of TightVNC being installed and running on machines all the time (lots of staff laptops that get taken home here). So I wrote a .Net app that handles dropping TightVNC on a client machine via the administrative share, creating registry keys for configuration (includes a randomly generated password for the session), registering and starting TightVNC as a service and then finally launching the connection app on your end and connecting to the host. Upon closing the app it will deleted and remove keys on the other end. In the event the connection is lost and it doesn't have a chance to cleanup it will also create a script that runs on the next start up of the client that will take care of the cleanup. I can post the source if you're interested.

 

We are using a program called RemoteControl by Chris Tschantz. It works similar to your .net app. Here is the authors "How it works" Info.:

>This program is written in Visual Studio (2012) using .Net Framework 3.5.

>It currently uses TightVNC server along with RealVNC viewer.

>It also uses WMI to run actions on the remote device via command line. This is an acceptable approach since we dont need anything on the remote device to have >Desktop Interaction. (Like for example starting notepad.exe and actually seeing it on screen).

 

Essentially it copies and starts a VNC server and connects to it. Requires domain admin rights and all that. Obviously, hooks directly into the user session, no warning or indication. At the end of the session it uninstalls the VNC server. Works most of the time and saved me lots of walking.

There are several version's floating on the internet, I have got Version 1.7.4 which is from 2013.