Re: Disconnections with TSAC
- From: "-=D@n=-" <getbent@xxxxxxxx>
- Date: Thu, 3 Nov 2005 09:30:23 -0000
Vera Noest [MVP] wrote:
> "-=D@n=-" <getbent@xxxxxxxx> wrote on 02 nov 2005 in
> microsoft.public.win2000.termserv.clients:
>
>> Vera Noest [MVP] wrote:
>>> "-=D@n=-" <getbent@xxxxxxxx> wrote on 02 nov 2005 in
>>> microsoft.public.win2000.termserv.clients:
>>>
>>>> -=D@n=- wrote:
>>>>
>>>> But they are still getting disconnected randomly. Ok, I would
>>>> now say that this is a network problem. Does anyone know of a
>>>> tool that I could run at the client end, that would monitor
>>>> the connections to our TS here and make a log of
>>>> disconnections and perhaps reasons for them?
>>>
>>> You could start very simple, with a continuous ping (ping -t)
>>
>> Hmm, I just tried pinging and after eleven successful pings I
>> had a 'Request Timed Out'. Is it not the case that RDP should
>> be able to deal with the odd dropped 'packet'? Is this where the
>> registry changes[1] come into effect? I mentioned earlier, that
>> I hadn't rebooted the TS since making these changes. I've
>> scheduled a reboot for 23:00 tonight.
>>
>> I'm also going to run 200 pings and output the results to a text
>> file, right now.
>>
>> Thanks for your support.
>>
>>
>> Dan
>>
>> [1] http://terminal.servebeer.com/php/flaky_connections.php
>
> The EnableKeepAlive setting puts a "heartbeat" on the connection.
> That serves 2 purposes:
> a) it can help to keep the connection alive by making sure that
> routers always "see" some traffic (avoiding an idle session time-
> out on the routers)
> b) if the connection is broken, the TS will notice this much
> earlier, and will be able to respond to the situation according to
> your settings (disconnect or reset the connection).
>
> RDP is *not* very good at dealing with dropped packets (but it
> should be able to automatically reconnect if there is a very short
> connection problem).
>
> By having your users (or you) run a continuous ping, you get some
> statistics about the number of packets dropped. That could help you
> to narrow down the problem.
Thanks for your reply Vera. I rebooted the TS last night, so I guess we'll
see what happens today with this particular client.
Interestingly, I ran some tests[1] from home last night for two hours before
rebooting the server. I ran an automated test for two hours and didn't get
disconnected once. I rebooted the server at 23:30, and have been running the
automated tests since 23:47 until now (9:30) and still had no
disconnections. I will keep my 'test' login running for most of the day and
see how we get on.
I'll keep you posted!
Thanks again
Dan
[1] Signing into the TS, running our application, and carrying out most of
the tasks that the end user would.
.
- Follow-Ups:
- Re: Disconnections with TSAC
- From: -=D@n=-
- Re: Disconnections with TSAC
- References:
- Re: Disconnections with TSAC
- From: Vera Noest [MVP]
- Re: Disconnections with TSAC
- From: -=D@n=-
- Re: Disconnections with TSAC
- From: -=D@n=-
- Re: Disconnections with TSAC
- From: -=D@n=-
- Re: Disconnections with TSAC
- From: -=D@n=-
- Re: Disconnections with TSAC
- From: Vera Noest [MVP]
- Re: Disconnections with TSAC
- From: -=D@n=-
- Re: Disconnections with TSAC
- From: Vera Noest [MVP]
- Re: Disconnections with TSAC
- Prev by Date: Re: Disconnections with TSAC
- Next by Date: terminal services licensing
- Previous by thread: Re: Disconnections with TSAC
- Next by thread: Re: Disconnections with TSAC
- Index(es):
Relevant Pages
|