Re: Blue screen of death when closing connections
- From: Lefty Bigfoot <nunya@xxxxxxxxxxxxx>
- Date: Tue, 04 Oct 2005 23:43:35 GMT
Vera Noest [MVP] wrote
(in article
<Xns96E4E95095554veranoesthemutforsse@xxxxxxxxxxxxx>):
> But if you don't have any time-out limit on active or idle
> sessions, then the beginning of the problem is that the sessions
> become disconnected at all during lunch hours, isn't it?
Exactly. Although "lunch hour" is an example, not the only time
this happens. I have not been able to isolate a single cause.
> They should simply stay connected, but idle.
That's what I expected also.
> So why are your sessions broken? Are your users on a WAN or a LAN?
WAN, high speed DSL/cable between two buildings, but the
internet service seems to be reliable, with no unpexpected
downtimes.
> Another thing that you could try (to avoid routers from
> disconnecting the idle sessions) is to enable KeepAlives.
Good idea.
> How to make your intermittent or flaky terminal services connection
> a little more stable
> http://terminal.servebeer.com/php/flaky_connections.php
Thanks for this, I'll look into it.
--
_ __ _
| | ___ / _| |_ _ _
| | / _ \ |_| __| | | |
| |__| __/ _| |_| |_| |
|_____\___|_| \__|\__, |
|___/
All of God's creatures have a place..........
..........right next to the potatoes and gravy.
.
- References:
- Re: Blue screen of death when closing connections
- From: Lefty Bigfoot
- Re: Blue screen of death when closing connections
- From: Lefty Bigfoot
- Re: Blue screen of death when closing connections
- From: Lefty Bigfoot
- Re: Blue screen of death when closing connections
- Prev by Date: Re: Com Port not responding in RDCP from TS2003
- Next by Date: Re: How to deny logon for already logged on user
- Previous by thread: Re: Blue screen of death when closing connections
- Next by thread: Using PsSetCreateProcessNotifyRoutine on Terminal Services
- Index(es):
Relevant Pages
|
