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.

-Cliff


"cyclon" <cyclon@newsgroup> wrote in message
news:mn.6bec7da5542baabe.85122@newsgroup

> Hello,
>
> 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?
>
> Greetings,
>
> Cyclon
>
>

The default time for a kerberos ticket is set that way for a reason.
Changing this time too much exponentially increases your risk factor and is
an insecure way to operate. Unless it is absolutely necessary, I'd
encourage users to just log out and log back in or push back on the vendor
to fix this bug in their software.

-Cliff


"cyclon" <cyclon@newsgroup> wrote in message
news:mn.a2bd7da5107f61cd.85122@newsgroup

> Hello,
>
> the problem is solved, it was the default time for the kerberos ticket
> that caused the problem. Now we have changed this time, and there is no
> longer a problem.
>
> Thank you very much,
>
> greetings,
>
> cyclon
>
>
>
> Cliff Galiher - MVP schreef op 13/05/2010 het volgende :
>
>

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

>
>

Grabbing at straws. Run the SBS BPA for SBS 2008 if you have not.
There are some clicks they may want you to do that may help with
disconnect issues.

On Fri, 21 May 2010 18:24:01 +0200, cyclon <cyclon@newsgroup>
wrote:

>
>Hello,
>
>is this something new in small business server 2008? We have been
>working with our erp program since 2001, first on small business server
>2000, then on small business server 2003 and since last year on small
>business server 2008. There was no problem with the previous versions
>of small business server.
>
>I also informed the vendor about this problem, and apparently we were
>the first who had encountered this problem. I will ask them to search
>for a solution for this problem.
>
>Greetings,
>
>cyclon
>
>
>
>Cliff Galiher - MVP schreef op 20/05/2010 het volgende :
>
>

>> The default time for a kerberos ticket is set that way for a reason. Changing
>> this time too much exponentially increases your risk factor and is an
>> insecure way to operate. Unless it is absolutely necessary, I'd encourage
>> users to just log out and log back in or push back on the vendor to fix this
>> bug in their software.
>>
>> -Cliff
>>
>>
>> "cyclon" <cyclon@newsgroup> wrote in message
>> news:mn.a2bd7da5107f61cd.85122@newsgroup

>>> Hello,
>>>
>>> the problem is solved, it was the default time for the kerberos ticket that
>>> caused the problem. Now we have changed this time, and there is no longer
>>> a problem.
>>>
>>> Thank you very much,
>>>
>>> greetings,
>>>
>>> cyclon
>>>
>>>
>>>
>>> Cliff Galiher - MVP schreef op 13/05/2010 het volgende :
>>>
>>>
>>>> 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.
>>>
>>>

>

See what SBS support is working on
http://blogs.technet.com/sbs/default.aspx
Check your SBS with the SBS Best Practices Analyzer
http://blogs.technet.com/sbs/archive...A/default.aspx