UAC acting the maggot with VNC

Hijpo

Iv downloaded TightVNC so i can access my laptop with the android App i have.
I have my girlfriends account locked down to she cant install any stupid crap on it.
Trouble is, when the TightVNC service starts UAC dims the screen looking for my credentials. Iv changed the .exe properties to "Run As Admin" and iv also allowed the service to Log On As me through the services snap in

Am i missing something?

Sorry the OS is Windows 7 Home Premium

Hijpo

http://www.jimmah.com/vista/Administration/autostart_admin_program.aspx

Have yet to test it


no joy with that either

Fysh

I've not used TightVNC but I know that RealVNC allows this if you install the server version in Service Mode. I would be surprised if TightVNC didn't have some similar option. Edited to add: According to this, it does. According to the changelog, this should work for Vista & 7 as of version 2.0.

Hijpo

The service starts ok, but it trys to make a change when it starts and thats whats making UAC kick in. Im trying to give the service admin privileges so that it can make any changes it wants without UAC interupting it. Turning off UAC is not an option unfortunatley

Fysh

Hijpo wrote: »

The service starts ok, but it trys to make a change when it starts and thats whats making UAC kick in. Im trying to give the service admin privileges so that it can make any changes it wants without UAC interupting it. Turning off UAC is not an option unfortunatley

Is the service running as a local system account? From the FAQ it seems TightVNC 2.0.4 should work properly with Vista & 7.

You could try the free edition of RealVNC Server as an alternative, it might help pin down the issue if it turns out the same problem is happening across several VNC server packages.

Hijpo

Fysh wrote: »

Is the service running as a local system account? From the FAQ it seems TightVNC 2.0.4 should work properly with Vista & 7.

You could try the free edition of RealVNC Server as an alternative, it might help pin down the issue if it turns out the same problem is happening across several VNC server packages.

Yes it was running as a local system account, then i tried changing it to log on as mine, im not sure if that only applies to domains on a network though.
ill try RealVNC and see what happens.
thanks

RealVNC runs, but the App (Android-VNC-Viewer) wont connect to it. I only want to work over the LAN.

Fysh

Hijpo wrote: »

Yes it was running as a local system account, then i tried changing it to log on as mine, im not sure if that only applies to domains on a network though.
ill try RealVNC and see what happens.
thanks

RealVNC runs, but the App (Android-VNC-Viewer) wont connect to it. I only want to work over the LAN.

Weird. I'll see if I can reproduce it on my machine at home tonight.

Hijpo

Fysh wrote: »

Hijpo wrote: »

Yes it was running as a local system account, then i tried changing it to log on as mine, im not sure if that only applies to domains on a network though.
ill try RealVNC and see what happens.
thanks

RealVNC runs, but the App (Android-VNC-Viewer) wont connect to it. I only want to work over the LAN.

Weird. I'll see if I can reproduce it on my machine at home tonight.

At first i got an error on the app saying "null" now i get the error "connection reset by peer"

Fysh

Right, I installed TightVNC 2.0.4 on my home laptop (running Win7 Pro SP1) using the Full Install option, checked the option during install to set passwords before finishing the installation, set a password for the RFB authentication, set another password for controlling access to the TightVNC configuration window, then opened up my AV/Firewall package (F-Secure Client Security version 9) and created a rule allowing all IP traffic between the host and a defined subset of the IP addresses on my home network's subnet.

I rebooted after that, installed Android-VNC-Viewer on my G1 (rooted to run Cyanogen 6), and was able to connect to the machine. This confirmed that it was running correctly in service mode as I hadn't logged in yet, and was able to log in through the VNC connection.

So it's definitely possible. I have UAC set to always notify, I use a standard account for normal usage, and it's working exactly as you'd expect. It can't be anything to do with Home Premium's limitation to being an RDP Client only because VNC uses the RFB protocol (and to prove it my working host OS has RDP connections disabled in Windows and blocked by default at the firewall level).

Not sure what's causing your problem; hopefully the above will help you get to the bottom of it.

Hijpo

i just reinstalled TightVNC and opened the default port through my firewall, when the machine gets to the log on screen i can connect no problem. However, even after connecting, when i log into either my admin profile or my partners profile i get the UAC alert that TightVNC is trying to make changes. On my partners profile it asks for my admin password which she doesnt have and clicking No results in the connection being dropped.

Screen shot to follow: right so it turns out you can take a screen shot of a UAC window.
Anyway clicking details revealed that "[filepath]\tvnserver.exe" -controlservice -slave
Is whats trying to make changes to my computer.

Fysh

What firewall are you using? Do you have a rule specifying that tvnserver.exe can receive incoming connections from the local subnet?

Another option that might fix the problem is disabling the secure desktop, but I'm not yet convinced you need to do this. (I can't swear to it but I'm reasonably sure I have secure desktop enabled on my home machine...)

Hijpo

im using windows firewall, i have rules set for ports opend and Tvnserver is allowed connections through it.
I dont think its a firewall issue as like you it IS connecting at log on screen and its UAC thats stopping it from doing what it wants to do, if i could figure out what its trying to change i could possibly stop it trying to change whatever it is?? Ill try disable the secure desktop.

Fysh

OK, according to this page the installer creates a registry to invoke the server every time Windows starts, but since you've got it running in service mode you don't need it.

I'd say delete the registry key, reboot and try it again. That ought to sort it. If you don't want to tinker with the registry you could uncheck it from the Startup items in msconfig - preventing it from launching in application mode shouldn't interfere with it launching in service mode, AFAIK.

Hijpo

Fysh wrote: »

OK, according to this page the installer creates a registry to invoke the server every time Windows starts, but since you've got it running in service mode you don't need it.

I'd say delete the registry key, reboot and try it again. That ought to sort it. If you don't want to tinker with the registry you could uncheck it from the Startup items in msconfig - preventing it from launching in application mode shouldn't interfere with it launching in service mode, AFAIK.

Ill remove the reg key. Why would that not be the case on your machine?

Thats sorted it. Thanks very much

CptSternn

Some apps will not run with UAC enabled. TVersity is one I use that requires it to be disabled. You may find disabling UAC is the only way to get it to work.

Hijpo

CptSternn wrote: »

Some apps will not run with UAC enabled. TVersity is one I use that requires it to be disabled. You may find disabling UAC is the only way to get it to work.

I have it working now, i stopped the application running at start up. I was wondering why fysh didnt have the same problems even though hes using the same UAC options as me.