> From: "James ''Wez'' Weatherall"
> > This sounds like an issue with your network.
>
> you can call these "network issues" but it is tcp after all and packets do
> get lost.
TCP is designed to retransmit lost packets and to drop connections if packet
loss prevents data being transferred, which is exactly the situation
described. A 56k network is almost certainly via modem to an ISP, or is
wireless, and in either situation periods of packet loss are common.
> also noticed that other types of tcp-based connections stay alive (ftp,
> ssh, and ping).
TCP connections which are not actively transferring data will tend to stay
alive even when the network connecting them is behaving poorly. Ping is
neither connection-oriented, nor operates over TCP or UDP. The only
reliable comparison is to have a continuous bi-directional stream of data
over the same network interface as VNC is using and see whether that closes
when VNC does.
> using VNC for long time , I just learned to live with it:
> close the connection (from viewer side) and reopen it.
We're talking about the VNC connection being closed in the middle of a
session. This will implicitly cause the viewer to close. Why would you
have to close it manually? Are you experiencing some other effect?
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
---------------------------------------------------------------------