10 hours is the default time that a kerberos ticket is issued for in a
windows Active Directory network. That glitch is not the network dropping,
but is the server replying with an explicit access denied to the client
because the ticket is expired. The client automatically requests a renewal
of the ticket, which is granted, so for most network activities, you never
"see" that renegotiation. A network application *should* be able to
anticipate and accommodate this as this is standard practice in any network.
If, however, this is a non-network app that has been forced into a networked
situation, you'll want to consider setting up a terminal server instead.
"cyclon" <cyclon@newsgroup> wrote in message
> we have an SBS2008 server, and vista professional pc's.
> Our ERP program is based on advantage database server from sybase. This
> program is completely installed on SBS2008, to start it on a vista pc, you
> only have to doubleclick on the start-icon that is on a network drive. The
> program then starts on the vista pc. The only requirement is that there
> has to a continuous connection between the vista pc and the sbs2008 server
> at all time.
> Now it occurs that this program crashes, apparently because this
> connection is lost briefly somehow. We have determined that this crash
> happens 10 hours after the user has logged on to windows on his vista pc.
> It doesn't matter when the ERP program is started. If for example you log
> your vista pc on to the sbs2008 server at 8:00 AM, the crash will happen
> at +/- 18:00. It does not matter if you have started the ERP program at
> 8:30 or at 17:55, if it is running at 18:00, it will crash.
> Our ERP program is the only program that has a problem. Outlook has no
> problem when it is connected on exchange server. Word, excel, autocad, all
> these programs work fine. Internet explorer : no problem.
> The connection between the server and the pc must apparently be broken
> very shortly, and be restored immediately.
> Does anybody have any idea that could explain this?