From: Steve Worzman [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 27, 2005 6:48 PM To: 'vnc-list@realvnc.com' Subject: server closed connection unexpectedly - another solution
Adding the "+" did it -- after weeks of playing with every setting on my router and firewall and Norton Antivirus. THANK YOU!!!!!!!!!! However, here's some more absolutely necessary info: 1) Windows Firewall can be turned on but you must add an exception for "winvnc4.exe" and "run VNC Viewer" (otherwise "10060 connection timed out" error). 2) If you are running Norton SystemWorks Premier 2005 you must go to "Options, Norton Anitvirus, Internet Worm Protection, Program Control" and select "Permit" (as opposed to "Block") for WinVNC4 (otherwise after #1 above "10061 connection refused error"). This may apply to other versions of Norton AV. 3) Just a note that differs with the advice about the VNC Server - "Connections" - "Access Control" option of adding the "+" as written below. I clicked "Add" under "Access Control" and added a "+". The resulting value was "+255.255.255.255/0.0.0.0". I did not have to check "only accept connections from the local machine" and VNC finally worked finally no more errors. Yeah! Steve ================ 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 <hr size=2 width="100%" align=center> * Previous message: server <http://www.realvnc.com/pipermail/vnc-list/2004-October/047626.html> closed connection unexpectedly - another solution * Next message: server <http://www.realvnc.com/pipermail/vnc-list/2004-October/047682.html> closed connection unexpectedly - another solution Steven Worzman _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
