After a couple of days trying to get around the "server closed
connection unexpectedly" problem, I stumbled on something that clued
me in. Unfortunately, I don't recall where I found the hint. No
matter; the solution is simple.
Thinking I'd accidently typed the "+" in the server options
Connections | Access Control list, I removed it, leaving the list
entirely empty. This caused the server to throw the "SocketManager:
unknown network event for listener" error whenever someone tried to
connect.
It wasn't easy to put the + back (it involved finding the entry in the
Windows registry and editing it), but I suspect simply adding
0.0.0.0/0.0.0.0 to the Access Control list would achieve the same
result. I'm not enough of a VNC expert to know, so I hope someone
with more knowledge will correct this if it's wrong. [I find the
documentation a little weak in this area, since what it says is "a
connection will always be rejected if it doesn't match anything in the
Hosts pattern." It doesn't say what "+" all by itself will do.]
Regards,
- Richard
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
