yes, this will definitely cause problems. WinVNC has to connect to itself
in order to correctly kick the incoming connection thread out of the
accept() call, because the BSD side of the Winsock API is completely and
utterly brain-dead.(*)
Cheers.
James "Wez" Weatherall
--
"The path to enlightenment is /usr/bin/enlightenment"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T Labs Cambridge, UK - Tel : 343000
(*) That's my personal opinion, not necessarily the opinion of AT&T Labs or
anyone else. I just think that if you close a socket it's common sense to
abort all pending operations on that socket in other threads, including
accept() calls. But what would I know?
----- Original Message -----
From: "Steven Danz" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 19, 2001 5:08 PM
Subject: Re: WinVNC R9 doesn't go away on Close?
> Hi again
>
> With DebugLevel=12 and DebugMode=2 I get a WinVNC.log in the C:\Windows
> directory with the following. When I select Close, the last line of
'closing socket'
> appears, and when I look at the process list from Ctrl-Alt-Del, Winvnc is
still there.
>
> And while I type this the solution comes to me... I've been running the
ZoneAlarm
> software and looking at the configuration it was allowing WinVNC to access
the
> local network but not the 'Internet' (in ZoneAlarm's terms anyway).
Turning on
> 'Internet' access allows WinVNC to shutdown correctly since it looks like
WinVNC
> needs to be able to access 127.0.0.1 to be able to shutdown (if I'm
reading the log file
> from a 'normal' shutdown correctly). I don't know why ZoneAlarm doesn't
allow
> 127.0.0.1 access when 'Internet' is turned off, but that is what it looks
like.
>
> Thanks
>
> Steven
>
> D:\ORL\vss\winvnc\vncServer.cpp : authhosts set to "<removed>"
> D:\ORL\vss\winvnc\vncProperties.cpp : clearing user settings
> D:\ORL\vss\winvnc\vncPasswd.h : PASSWD : FromClear called
> D:\ORL\vss\winvnc\vncProperties.cpp : loading DEFAULT local settings
> D:\ORL\vss\winvnc\vncProperties.cpp : loading "stevend" global settings
> D:\ORL\vss\winvnc\vncServer.cpp : trying port number 5900
> D:\ORL\vss\winvnc\VSocket.cpp : closing socket
> D:\ORL\vss\winvnc\VSocket.cpp : closing socket
> D:\ORL\vss\winvnc\VSocket.cpp : closing socket
> D:\ORL\vss\winvnc\vncSockConnect.cpp : started socket connection thread
> D:\ORL\vss\winvnc\vncHTTPConnect.cpp : started HTTP server thread
> D:\ORL\vss\winvnc\vncPasswd.h : PASSWD : ToText called
> D:\ORL\vss\winvnc\vncMenu.cpp : tray icon added ok
> Thu Apr 19 10:37:02 2001
> D:\ORL\vss\winvnc\WinVNC.cpp : message 275 recieved
> D:\ORL\vss\winvnc\vncMenu.cpp : tray icon added ok
> Thu Apr 19 10:37:04 2001
> D:\ORL\vss\winvnc\WinVNC.cpp : message 273 recieved
> D:\ORL\vss\winvnc\WinVNC.cpp : message 16 recieved
> D:\ORL\vss\winvnc\WinVNC.cpp : shutting down server
> D:\ORL\vss\winvnc\vncMenu.cpp : tray icon added ok
> D:\ORL\vss\winvnc\vncServer.cpp : shutting down server object
> D:\ORL\vss\winvnc\VSocket.cpp : shutdown socket
> D:\ORL\vss\winvnc\VSocket.cpp : closing socket
>
>
> James ''Wez'' Weatherall wrote:
>
> > > I've uninstalled WinVNC R7, installed R9, to keep up to date.
> > > Now I can reboot my Win98 system (so everything is 'clean'),
> > > startup WinVNC (appMode), then select the icon and choose 'Close VNC'.
> > > The icon will go away but the process doesn't, ever. Clients can
still
> > > attach to it, but since the icon is gone you can't try to 'close' it
> > again.
> > > If you hit Ctrl-Alt-Del the Winvnc process shows up in the 'Close
Process'
> > > list, so using that to 'End Task' is possible, but not desirable. I
don't
> > have
> > > 'AllowShutdown' set in the registry, is it required to be a 1 for the
> > server to
> > > go away?
> >
> > Strange. AllowShutdown is set to 1 by default. The Close option would
be
> > greyed out otherwise. Can you enable debug logging to see what the
server
> > is trying to do when you select "Close"?
> >
> > Cheers,
> >
> > James "Wez" Weatherall
> > --
> > "The path to enlightenment is /usr/bin/enlightenment"
> > Laboratory for Communications Engineering, Cambridge - Tel : 766513
> > AT&T Labs Cambridge, UK - Tel : 343000
> > ---------------------------------------------------------------------
> > To unsubscribe, send a message with the line: unsubscribe vnc-list
> > to [EMAIL PROTECTED]
> > See also: http://www.uk.research.att.com/vnc/intouch.html
> > ---------------------------------------------------------------------
> ---------------------------------------------------------------------
> To unsubscribe, send a message with the line: unsubscribe vnc-list
> to [EMAIL PROTECTED]
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
