Plea for help - Default timeout for accept incoming connecti ons, automatically reject

[FAHY Ronan]

Thanks for the reply.  Haven't tied that - at the moment we're editing the
code to make it do what we want it seems to be a simple enough change
(hopefully) and will recompile and try it.  might try your suggestion anyway
as it seems like a good workaround if it will allow us install twice.
 
Thanks
Ronan

-----Original Message-----
From: rsmmail04-realvnc "at" yahoo.com [mailto:rsmmail04-realvnc "at" yahoo.com]
Sent: 15 September 2004 17:44
To: VNC-List "at" realvnc.com; FAHY Ronan
Subject: Re: Plea for help - Default timeout for accept incoming
connections, automatically reject


Okay, I don't know if RealVNC can do what you want, but here's a possible
work-around if it can't.
 
Have you tried installed TWO instances of the server on each machine, using
different sets of port addresses?  The first instance offers the prompt to
the user.  If you get an acceptance from the user on the connection, then
great.  If not, you then connect on the 2nd instance of the Server on which
there is no prompt to the user.
 
If you cannot run two instanced of RealVNC, then maybe you can use another
VNC program like TightVNC.  i.e. you have one instance of each running in
Server mode.
 
NOTE:  I have not tried any of this and have no idea if it is doable, but it
should be fairly easy to test.
 
Robert

FAHY Ronan <RonanFahy "at" transport.ie> wrote:

Hi again - sorry to be persistent but does anyone know if VNC is capaple of
doing this? All i need is a yes or no answer then we can figure out how to
do it ourselves hopefully, if the answer is yes???



Hi - we're thinking about implementing VNC 4 as our remote access solution
for desktops (about 500). We have two issues that might prevent us from
picking VNC though - I wonder if anyone has looked into this before or has
any ideas:

We want to give users a warning prior to connection, plus time to close off
any sensitive documents etc. before we connect.
We can use the option in VNC to prompt the local user to accept the incoming
connection however this is where the two issues are. The time is only 10
seconds, we would usually set it to 30. From looking at the registry keys
it appears you should be able to adust the QueryTimeout value to whatever
setting you like however when we tried this it had no effect.

Secondly, the default behaviour is that when the timeout expires, the
connection is refused. This means that we would have no way of connecting
to machines that were currently logged off etc. or machines whose users were
away from their desks etc.

What we want is the best of both worlds i.e. a time delay on connections
giving users the time to close down what they don't want adminstrators to
see, or the option to reject the connection, but once the time limit
expires, the connection is accepted.

Our current remote access solution gives us these options, however we are
upgrading to XP and are faced with a cost of around 15 thousand dollars to
get the latest release of their software compatible with XP - VNC is just as
good and in many ways better now that event logging and host only
installations are possible, however these two areas are of concern to us.

Has anyone got any ideas?

Thanks
Ronan Fahy
Network and Systems Adminstrator
Department of Transport
Ireland


***********************************************************
The information in this email is confidential and may be 
legally privileged. It is intended solely for the addressee.
Access to this email by anyone else is unauthorised.

If you are not the intended recipient, any disclosure, 
copying, distribution or any action taken or omitted to 
be taken in reliance on it is prohibited and may be
unlawful.
***********************************************************
_______________________________________________
VNC-List mailing list
VNC-List "at" realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list




***********************************************************
The information in this email is confidential and may be  
legally privileged. It is intended solely for the addressee.
Access to this email by anyone else is unauthorised.

If you are not the intended recipient, any disclosure, 
copying, distribution or any action taken or omitted to 
be taken in reliance on it is prohibited and may be
unlawful.
***********************************************************