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
---------------------------------------------------------------------
