Remote admin using VNC.

James [Wez] Weatherall jnw "at" orl.co.uk
Fri, 20 Nov 1998 16:54:47 +0000


On Fri, 20 Nov 1998, Luis B. Almeida wrote:

> > We would install the server program as a service. We
> > would like to have something to notify the user of the
> > PC when a VNC viewer has successfully connected to the
> > VNC server -something to flash on the service tray
> > perhaps? This has two purposes, firstly, it will placate
> > those (a little) who fear covert operations by their
> > systems administrators, and secondly (given the setup
> > in the previous point is possible) it will mean we will
> > be aware of any unauthorised use of the viewer.
> 
> I'm not completely sure about this one, but I think there's no
> possibility of doing what you want in the current version of WinVNC,
> given that you run it as a service. If it is run as a user program, it
> will display an icon in the system tray area, and this icon will change
> color when a connection is active.

This should happen when running as a service, too.

> > On the test PC I have been using (Win95) with VNC
> > server installed as a service, nothing appears in the
> > service tray at all. From my reading of the documentation,
> > this doesn't seem to be correct behaviour -or perhaps I
> > missed something. Should something appear in the service
> > tray on a Win95 system when VNC server is installed as
> > a service?
> 
> I think this actually is the correct behavior, although I'm not too sure
> of what is in the docs. But I'm sure that I've always observed the
> behavior you describe: if WinVNC is run as a service, no icon is shown
> in the system tray area.
> 
> By the way, if there were an option whether to display the icon or not,
> this would solve your second problem. I think I've seen other people in
> this list mention that need too. Wez, could this be put in the wish list
> for the next revision?

There is a bug in all current releases of WinVNC that prevents the icon
appearing when run as a service under Win95.  I haven't found out what
causes it yet.  It may well just be some dumb logic, if anyone feels like
scanning through the vncMenu.cpp code and seeing if they can spot any
obvious errors?

Cheers,

James "Wez" Weatherall
--
Olivetti & Oracle Research Laboratory, Cambridge, UK - Tel : 343000
Laboratory for Communications Engineering, Cambridge - Tel : -


---------------------------------------------------------------------
The VNC mailing list     -   see http://www.orl.co.uk/vnc/intouch.html
---------------------------------------------------------------------