Currently I am running a separate task to force a VNC server side connect every 20 minutes by executing WinVNC -connect <...>. I had hoped that the server, if set to ignore new connections, would ignore the connect request ... but no. (a bug ?)
So every twenty minutes my client shuts down and pops an error box. It reconnects a few seconds after I clear the error so it's more annoying than problematic. (Under Windows I get the same session since there is only one ... this wouldn't work for Linux servers ....)
I also wrote a Java program that detects if the server has hung. It opens localhost:5900 if the read fails the server is hung so I restart it with:
net stop winvnc net start winvnc winvnc -connect <...>
I realize all this is rather ugly ... that's why I'm looking for a better way!
I found a product www.firedaemon.com. It lets you set up almost anything as a service. I'm using it to run the java application to restart the VNC server if it crashes.
Anyone know how to detect if the server to client connection is down?
I already tried opening it's port (as part of the check to see if it's alive) and then I echo the version string back hoping that I would get a connection refused as the authentication message if I had it set to refuse multiple connections. But it doesn't. I guess that's implemented by refusing the authentication ... or maybe the refuse multiple connections just doesn't work ...
Does anyone know how I can check the number of active clients? Or set the viewer to refuse a second connection in listen mode? Or query the client to see if it's connected?
Any other suggestion for restoring a failed server side connection?
Thanks,
Clay _______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
