Nepple, Bruce wrote:
OK --- I found the info on the Xvnc manpage. On the vncserver manpage
it wasn't
real obvious that I needed to also read the Xvnc manpage.
What was missing? I looked online to confirm, and the web documentation for
WinVNC server covers IdleTimeOut:
http://www.realvnc.com/v4/w
:47 PM
> To: Nepple, Bruce; [EMAIL PROTECTED]
> Subject: Re: 4.0 Client Crashes every few hours
>
>
> You're not seeing it in VNCViewer because the server is what
> drops them. The
> IdleTimeout is mentioned in the release notes
> (release-notes.htm) but most
> i
August 10, 2004 8:23 AM
To: 'Joe Perrone'
Cc: [EMAIL PROTECTED]
Subject: RE: 4.0 Client Crashes every few hours
Joe,
"The client dissappears after about 2 or 3 hours" suggests
that it's simply
the idle timeout on the connections, causing them to be
dropped. Please
read the
WHAT documentation might contain this tasty tidbit.
Bruce
> -Original Message-
> From: James Weatherall [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 10, 2004 8:23 AM
> To: 'Joe Perrone'
> Cc: [EMAIL PROTECTED]
> Subject: RE: 4.0 Client Crashes every few ho
e-
> From: Joe Perrone [mailto:[EMAIL PROTECTED]
> Sent: 10 August 2004 16:21
> To: James Weatherall
> Subject: RE: 4.0 Client Crashes every few hours
>
> No, what I meant by checking the Catalyst I mean that I
> checked the exact ports on the Cisco Catalyst switch that all
connections.
There doesn't appear to be anything crashing, from what you've described,
just a connection getting closed.
Wez @ RealVNC Ltd.
> -Original Message-
> From: Joe Perrone [mailto:[EMAIL PROTECTED]
> Sent: 10 August 2004 16:06
> To: James Weatherall
> Su
Joe,
Please provide more detail regarding VNC Viewer "crashing". Many users use
the term "crash" when they simply mean that the viewer has closed, which is
most often caused by network issues.
Wez @ RealVNC Ltd.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED
