4.0 Client Crashes every few hours

Fri Aug 13 01:48:00 2004

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 
importantly in winvnc.html. The GUI config is on the Connections tab for the 
server.  The actual documentation from wincnc.html below; you may way to 
just do a "find" in that page for IdleTimeout since it will be formatted 
more nicely. :)

IdleTimeout=(seconds)
Disconnect idle clients after

An idle client is one which has transmitted no keyboard or pointer events 
for more than a certain length of time. The VNC Server can be configured 
with a threshold, expressed in seconds, after which idle clients will be 
disconnected to conserve resources. If the threshold specified is zero 
seconds then connections will never timeout. The default idle timeout is one 
hour.

Note that pointer and keyboard events received from clients will prevent 
their connection timing out even if the VNC Server is configured to 
otherwiseignore those events (see below).

Nepple, Bruce wrote:
> I wish I could find it in the documentation.  Certainly can't find it
> on the
> vncserver man page, or in any windows vnc viewer documentation, or a
> entry anywhere
> in the vnc viewer options for a value or some checkbox to disable it.
> Not in the FAQ either.
>
> Be nice if you gave us a hint as to WHAT documentation might contain
> this tasty tidbit.
>
> Bruce
>
>
>
>> -----Original Message-----
>> From: James Weatherall [mailto:jnw "at" realvnc.com]
>> Sent: Tuesday, August 10, 2004 8:23 AM
>> To: 'Joe Perrone'
>> Cc: vnc-list "at" realvnc.com
>> 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 documentation for details on select a longer timeout
>> if required.
>>
>> Wez @ RealVNC Ltd.
>>
>>
>>> -----Original Message-----
>>> From: Joe Perrone [mailto:joe "at" withit.com]
>>> 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
>>> 3 pc's are connected to and none of them have any reset
>>> sockets or bad packets.  The client dissapears after about 2
>>> or 3 hours regularly.  The Host is running Win XP and the
>>> clients are W2k professional.
>>>
>>> -Joe
>>>
>>> -----Original Message-----
>>> From: James Weatherall [mailto:jnw "at" realvnc.com]
>>> Sent: Tuesday, August 10, 2004 11:17 AM
>>> To: Joe Perrone
>>> Cc: vnc-list "at" realvnc.com
>>> Subject: RE: 4.0 Client Crashes every few hours
>>>
>>>
>>> Joe,
>>>
>>> Please provide more detail regarding VNC Viewer
>>> "dissappearing", such as
>>> how long the viewer had been connected, etc.  Information on the
>>> platforms in use may also be useful.
>>>
>>> What do you mean by "the Catalyst ports"?
>>>
>>> Please read the documentation regarding shared 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:joe "at" withit.com]
>>>> Sent: 10 August 2004 16:06
>>>> To: James Weatherall
>>>> Subject: RE: 4.0 Client Crashes every few hours
>>>>
>>>> James,
>>>>
>>>> I just confirmed again that the Viewer just disspeared and
>>>> both users had "Shared" selected.  No network issues I
>>>> checked the Catalyst ports.
>>>> Is there a way to make all new connections "Shared" and what
>>>> do you think about the crashing?
>>>> -Joe
>>>>
>>>> -----Original Message-----
>>>> From: James Weatherall [mailto:jnw "at" realvnc.com]
>>>> Sent: Tuesday, August 10, 2004 9:45 AM
>>>> To: Joe Perrone; vnc-list "at" realvnc.com
>>>> Subject: RE: 4.0 Client Crashes every few hours
>>>>
>>>>
>>>> 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: vnc-list-admin "at" realvnc.com
>>> [mailto:vnc-list-admin "at" realvnc.com]
>>>
>>>>> On Behalf Of Joe Perrone
>>>>> Sent: 10 August 2004 13:18
>>>>> To: vnc-list "at" realvnc.com
>>>>> Subject: 4.0 Client Crashes every few hours
>>>>>
>>>>> Hello,
>>>>>
>>>>> I have a client (w2k) that controls a server (running XP)
>>> They both
>>>>> have the latest service packs on them.  The VNC Viewer
>>> app crashes
>>>>> regularly every 3-4 hours.  I tried it on another
>> client with the
>>>>> same results.  Is their a bug in the VNC server or a
>> service pack
>>>>> for the VNC server for XP?
>>>>> Otherwise, perhaps the connection settings we are using are
>>>>> the problem.  BTW, the old version 3.x version of VNC used in
>>>>> this exact situation never crashed in this exact environment.
>>>>> Any suggestions?
>>>>>
>>>>> Any help would be greatly appreciated as we use VNC clients
>>>> every day.
>>>>>
>>>>> [Using VNC Viewer Version 4.0 6/15/04 build. With
>> associated 4.0
>>>>> server. Color level = Low, ]
>>>>>
>>>>>
>>>>>
>>>>> -Joe
>> _______________________________________________
>> VNC-List mailing list
>> VNC-List "at" realvnc.com
>> To remove yourself from the list visit:
>> http://www.realvnc.com/mailman/listinfo/vnc-list
> _______________________________________________
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list 