RE: Keep-alive script available
"Philip Herlihy" <[email protected]>
| Newsgroups | gmane.network.vnc.user,gmane.network.vnc.realvnc.general |
|---|---|
| Message-ID | <[email protected]> |
No, I didn't waste my time. The parameter you refer to has a default of 1 Hr (3600 seconds) and under "difficult" network conditions connections stay up a LOT less than that! Philip Herlihy -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Philip Herlihy Sent: 27 September 2009 18:12 To: 'Alex Pelts' Cc: [email protected] Subject: RE: Keep-alive script available That might have been a wasted few hours, writing that script, then! I'd looked for a suitable configuration but hadn't found one. Do you mean to say that the connection will survive periods of network glitch/error/whatever if this setting is used? Or is there still a role for my script? Grateful for any further clarification you can offer on this - as the perceived "unreliability" of VNC connections in some situations has led me to use RDC whenever that's an option. Philip Herlihy Email: [email protected] Tel: 020 8521 9157 Mobile: 07931 546660 Fax: 0870 0511055 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Alex Pelts Sent: 27 September 2009 17:12 To: Philip Herlihy Cc: [email protected] Subject: Re: Keep-alive script available Or you can set timeout to 0 and server will not drop connection. Regards, Alex Philip Herlihy wrote: > One of the most useful features of VNC is the facility to set up a reverse > connection, initiated from the server to a listening client. Providing the > router at the client end can be configured to pass through port 5500, there > is no need to mess with firewalls and routers at the server end. As the > expertise is usually at the client end - that's a good deal! > > > > However, that leaves the job of maintaining the connection, re-connecting as > necessary, at the server end. Many times I've had someone set up a > connection only for it to drop a few minutes after they have left. > > > > I've finally (!) got a script working which provides one solution to this. > The script, which uses only built-in NT commands (tested under XP), sets up > a connection and then periodically monitors that it is still "live", > automatically re-establishing the connection if it has dropped. This > version is for a client at a location with a known IP address, but it could > be adapted to use a domain address (including one obtained via dynamic DNS). > > > > If you'd like a copy, drop me a note. Beyond keeping the attribution in the > comments, there are no strings attached. > > > > Phil Herlihy > > _______________________________________________ > VNC-List mailing list > [email protected] > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list > > _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list