Aha.  That explains the problem.  Closing a listening port doesn't kick apps
out of accept() calls.  This means WinVNC will be left listening on a socket
which it can never receive anything from, because it's closed, and will thus
appear to hang.

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

----- Original Message -----
From: "Angus Macleod" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 15, 2001 11:56 PM
Subject: Re: VNC on WinNT stops responding if routing table is changed


> I think you are right. A bit of experimentation shows it affects other
> applications in the same way. If I use the -f switch on the route command
to
> clear the routing tables of all gateway entries, if seems to reset the
> entire stack, closing all ports in use.
>
> So I won't do that with VNC.
>
> Thanks,
>
> Angus.
> ----- Original Message -----
> From: "James ''Wez'' Weatherall" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, March 15, 2001 9:25 AM
> Subject: Re: VNC on WinNT stops responding if routing table is changed
>
>
> > This is a TCP stack issue, not a VNC issue, I think.
> >
> > 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
> >
> > ----- Original Message -----
> > From: "Angus Macleod" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Wednesday, March 14, 2001 10:09 PM
> > Subject: VNC on WinNT stops responding if routing table is changed
> >
> >
> > > I am running VNC r3.3.7 on WinNT 4.0 SP5. If I make changes to the
> routing
> > > table (e.g. with the route add command), VNC stops responding. Is this
a
> > > known problem? Is there a workaround (other than going to the server
and
> > > stopping/restarting the VNC service)?
> > >
> > > TIA, Angus.
> > > ---------------------------------------------------------------------
> > > 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
> ---------------------------------------------------------------------
---------------------------------------------------------------------
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
---------------------------------------------------------------------

Reply via email to