A couple of months ago we started using vnc at work, and it works great, but
twice now we have noticed some strange behavior, and we are not sure how quite
to diagnose it.

We are running a slightly modified version of 3.3.5 on windows. We just made a
couple of minor changes to customize its behavior. We changed the port number
to transverse our firewall better.

The clients can connect alright, but once in a while, the server mucks up when
a client connects to it. I turned on the log files for both the viewer and
server.

on the server the log looks like this..

winvnc.cpp : message 49280 received
vncclient.cpp : vncClient() executing...
vncserver.cpp : AddClient() done
winvnc.cpp : message 1026 received
vncclient.cpp : client connected : 10.10.10.33 (1)

and everything is fine. But a little later in the log..

winvnc.cpp : message 49280 received
vncclient.cpp : vncClient() executing...
vncserver.cpp : AddClient() done
winvnc.cpp : message 1026 received
vncclient.cpp : client connected : 10.10.10.33 (2)
vncserver.cpp : removing unauthorized client
vncserver.cpp : RemoveClient() done
vncclient.cpp : ~vncClient() executing...
vncclient.cpp : deleting socket
vsocket.cpp : closing socket

 After that point, the client is never allowed to connect back into the host
successfully. The first connection does not have a matching ~vncClient where
it should, and from the log, it shows that it is only closed when the server
is shut down. This appears in the log for every client that was left open:

vncdesktop.cpp : quitting desktop server thread
vncservice.cpp : SelectHDESK to Default (40) from 40
vncservice.cpp : SelectHDESK failed to close old desktop 40 (Err=170)
vncserver.cpp : RemoveClient() done
vncclient.cpp : ~vncClient() executing...


On the viewer end, whenever we close the viewer, with logging turned on we get
an rdr::SystemException 10006 every time. Does this have anything to do with
the server not cutting the connection off?

By restarting the viewer Daemon, sometimes it will allow the host to connect
to it again, other times it takes a full restart of the viewer machine.

I have been source diving, trying to find out what is going wrong, but I have
not found anything as of yet. Any help is much appreciated.

Paul
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to