server closed connection unexpectedly - another solution

[Stéphane Seignovert [FXM]]

Thanks for the tip.

I've put figures in the Access Control field and it works now !?

--
Stiphane Seignovert
FXM Traduction S`rl


> -----Original Message-----
> From: Richard Tenney [mailto:rlt "at" cs.umb.edu]
> Sent: jeudi 21 octobre 2004 07:40
> To: vnc-list "at" realvnc.com
> Cc: jnw "at" realvnc.com; sts "at" fxm.ch
> Subject: server closed connection unexpectedly - another solution
>
>
> 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