Prev: How to print from network printer while on terminal server?
Next: Installation by device question - urgent !!!
From: Leythos on 8 Mar 2010 19:32
In article <4915081C-0990-4A95-8107-0FB80B7673C9(a)microsoft.com>,
zooeyhallne(a)discussions.microsoft.com says...
> Thanks for the reply. Yes, I know it is probably flakiness on the part of
> the ISP. Unfortunately, this location is out in a rural area in Western
> Nebraska and even though I have inquired about T1 for this location--and even
> though many have told me that "it's much cheaper then it used to be"--I have
> still to find one that would cost less then $500-800 /month.
>

Sorry, didn't know you were BFE on this one. I have a customer like
yours, the loop charge is around $1400/month, making it unreasonable.

They use a Wireless ISP provider, but it has problems like you describe.

--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
spam999free(a)rrohio.com (remove 999 for proper email address)
From: Rob on 9 Mar 2010 04:07
zooeyhallne <zooeyhallne(a)discussions.microsoft.com> wrote:
> Rob:
>
> Thanks for the reply. Yes...just like you say it seems as though Terminal
> Services Session/RDP just "drops dead" at the first little jiggle in the
> connection.

It is the TCP/IP connection that is failing. The Terminal Server session
is using that as a transport connection. The only thing you can do when
the TCP/IP connection has failed, is log in again.

> I had hoped that there would have been some sort of tweak to fix
> the disconnect sensitivity (or resets as you call them). But no research has
> yet turned it up for me.

I think it does not exist... it is the way Microsoft designed their TCP/IP
networking, and they think it is good.
(the standards documents about TCP/IP say it should be done differently)
From: "Gregg Hill" greggmhill at please do not spam me at yahoo dot on 10 Mar 2010 02:48
While these suggestions ultimately may not help, I'll take a stab at it.

I recommend allowing only one session from a particular user, so that if it
drops, that user can reconnect to the same session rather than have the
server create a second session and leave the first one hanging.

Keep-Alive Connections – When this setting is enabled a heartbeat is used to
keep a terminal services session alive when the session is idle, i.e. if the
application is minimized. I do not know if it will help with disconnects.

Automatic reconnection – Allows a terminal services client to reconnect to a
disconnected session, instead of creating a new session on the same server.

Create a group policy for the TS to enforce these settings.

Also, do these help?
http://support.citrix.com/article/CTX708444
http://support.microsoft.com/kb/q170359/
http://support.microsoft.com/kb/q120642/
http://support.microsoft.com/kb/q158474/

Gregg Hill





"zooeyhallne" <zooeyhallne(a)discussions.microsoft.com> wrote in message
news:C1688AF0-413A-4945-B8A8-B9FC0111678E(a)microsoft.com...
> My company has several remote offices that need to run a company
> application
> via a Terminal Server session on the server back at the Main Office.
>
> They have this application up and running all day, as basically it is used
> for all company counter sales, etc.
>
> One of our locations relies on a wireless ISP connection that is not the
> best quality.
>
> They experience frequent disconnects of the TS session. The disconnects
> are
> random and it may work fine for several hours and then start disconnecting
> every 10 minutes or so.
>
> Other company locations are able to run TS sessions with no problems (they
> can be up all day with no disconnects).
>
> My question is: Is there a setting or something I can change to make our
> remote TS connections more robust? So that they don't just "drop dead" at
> the first sign of some network flakiness? We are running Windows 2000 TS
> on
> XP Pro computers.
>
> Is Windows Server 2008 Terminal Server better at keeping stable RDP
> sessions?
>
> Thanks for any advice!
>
>
From: Rob on 10 Mar 2010 12:07
Gregg Hill <greggmhill> wrote:
> Keep-Alive Connections – When this setting is enabled a heartbeat is used to
> keep a terminal services session alive when the session is idle, i.e. if the
> application is minimized. I do not know if it will help with disconnects.

That will actually make it worse, because it will allow Windows to detect
that a link that was otherwise idle is temporarily broken, and that it
should reset the connection.

The root problem is in the unreasonable handling of temporary failures
by Windows TCP/IP.
From: "Gregg Hill" greggmhill at please do not spam me at yahoo dot on 10 Mar 2010 13:52
Rob,

Maybe I have the wrong understanding of keep-alives. I keep seeing them
recommended to be enabled to stabilize flaky WAN links.

One site mentions that "This will also help prevent disconnects by
preventing network devices from killing off sockets that it assumes to be
idle." In my experience with TS sessions that drop, enabling keep-alives has
always helped. Of course, if the WAN link is too flaky, not much will help!

Gregg Hill



"Rob" <nomail(a)example.com> wrote in message
news:slrnhpfkf5.utv.nomail(a)xs8.xs4all.nl...
> Gregg Hill <greggmhill> wrote:
>> Keep-Alive Connections – When this setting is enabled a heartbeat is used
>> to
>> keep a terminal services session alive when the session is idle, i.e. if
>> the
>> application is minimized. I do not know if it will help with disconnects.
>
> That will actually make it worse, because it will allow Windows to detect
> that a link that was otherwise idle is temporarily broken, and that it
> should reset the connection.
>
> The root problem is in the unreasonable handling of temporary failures
> by Windows TCP/IP.

First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: How to print from network printer while on terminal server?
Next: Installation by device question - urgent !!!