I've searched the lists, found things similar but not quite the same as what
I've
encountered and got some clues but no solutions to be found.
I am running the VNC server on Red Hat Linux and the VNC viewer on WinXP Pro
and Win2K.
Most of the time it works fine, but once in a while someone will logout from
Linux,
causing the VNC viewer to terminate. Then when they try to connect again, they
can't and get the 10061 error.
I am running Xvnc in -inetd mode so that xinetd is listening on the ports for
the
connection and then starts the vnc server and hands the port over to the
server. As
I understand it, the Xvnc/vncserver runs on the port until the connection is
broken
(normally by logging out) at which time the vnc server hands the port back to
xinetd
who waits for another connection request. Also, when the vnc viewer is
terminated
without logging out of Linux the vncserver stays alive and continues on the
port
such that the vnc viewer connecting to that port sees the Linux session as it
was
when the viewer was terminated. (Exactly the behavior I want.)
Once a port cannot be connected to, only a restart of xinetd will restore
connectability for that port. Meanwhile, connections to other ports work fine.
I've got xinetd running in debug mode, spewing out lots of info, waiting for it
to
happen again. I suspect that I won't see much because xinetd probably doesn't
see
the connect request.
Any suggestions on what this problem might be and how to fix it or how to
investigate it further?
Help!
Dana
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
