Sessions "Time Out" but server still thinks active

[Guest Dan H.]

Hi,

Server 2000

We have WinXP laptops clients.

 

A user will get kicked off so I was thinking it was a timeout issue.

 

I checked to see that RDP manager was set to 1 hour and set to override

user accounts. User account is 1 hour and Policy is same (yeah I know the

override is checked but figured I provide this information as well).

 

Well I monitored a session and it showed her session as continous for ex. 30

minutes but then in the manager I would see the same person connected so it

would show she had 2 sessions going on. Then eventually session one would

end because of the time limit.

I asked her and she said she was booted as a timeout within minutes so she

had to reconnect. So the reconnect was the session two that I saw but as I

said Terminal manager still acknowledged her first session as being active.

Any ideas would be great or if you need further information please let me

know.

 

Thanks.

[Guest Vera Noest [MVP]]

Re: Sessions "Time Out" but server still thinks active

 

This can be caused by a router between the client and your server,

which sees no traffic and decides that the session must have ended

and throws it out.

 

Since this happened after only a couple of minutes of idle time, my

guess is that it is a router. The solution in that case is to

enable TS Keepalives on the server.

 

For 2003 this is accomplished via Group Policy setting:

 

Computer Configuration - Administrative templates - Windows

Components - Terminal Services

"Keep-Alive connections"

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"Dan H." <dh@nospam.com> wrote on 22 feb 2008 in

microsoft.public.windows.terminal_services:

> Hi,

> Server 2000

> We have WinXP laptops clients.

>

> A user will get kicked off so I was thinking it was a timeout

> issue.

>

> I checked to see that RDP manager was set to 1 hour and set to

> override

> user accounts. User account is 1 hour and Policy is same (yeah

> I know the override is checked but figured I provide this

> information as well).

>

> Well I monitored a session and it showed her session as

> continous for ex. 30 minutes but then in the manager I would see

> the same person connected so it would show she had 2 sessions

> going on. Then eventually session one would end because of the

> time limit. I asked her and she said she was booted as a timeout

> within minutes so she had to reconnect. So the reconnect was

> the session two that I saw but as I said Terminal manager still

> acknowledged her first session as being active. Any ideas would

> be great or if you need further information please let me know.

>

> Thanks.

[Guest Dan H.]

Re: Sessions "Time Out" but server still thinks active

 

Thank you for your response.

 

I have a dumb question that I believe I know the answer to but want to make

certain.

 

Would the "keep alive" option on the client have any bearing on the session?

My thought is NO but as said I figured I'd ask.

 

Thanks again.

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns9A4CE6266CDDFveranoesthemutforsse@207.46.248.16...

> This can be caused by a router between the client and your server,

> which sees no traffic and decides that the session must have ended

> and throws it out.

>

> Since this happened after only a couple of minutes of idle time, my

> guess is that it is a router. The solution in that case is to

> enable TS Keepalives on the server.

>

> For 2003 this is accomplished via Group Policy setting:

>

> Computer Configuration - Administrative templates - Windows

> Components - Terminal Services

> "Keep-Alive connections"

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> "Dan H." <dh@nospam.com> wrote on 22 feb 2008 in

> microsoft.public.windows.terminal_services:

>

>> Hi,

>> Server 2000

>> We have WinXP laptops clients.

>>

>> A user will get kicked off so I was thinking it was a timeout

>> issue.

>>

>> I checked to see that RDP manager was set to 1 hour and set to

>> override

>> user accounts. User account is 1 hour and Policy is same (yeah

>> I know the override is checked but figured I provide this

>> information as well).

>>

>> Well I monitored a session and it showed her session as

>> continous for ex. 30 minutes but then in the manager I would see

>> the same person connected so it would show she had 2 sessions

>> going on. Then eventually session one would end because of the

>> time limit. I asked her and she said she was booted as a timeout

>> within minutes so she had to reconnect. So the reconnect was

>> the session two that I saw but as I said Terminal manager still

>> acknowledged her first session as being active. Any ideas would

>> be great or if you need further information please let me know.

>>

>> Thanks.

[Guest Vera Noest [MVP]]

Re: Sessions "Time Out" but server still thinks active

 

No, KeepAlive has no effect on the client. This is what it does

(from the "Explain" text in GPMC):

 

After a terminal server client loses the connection to a terminal

server, the session on the terminal server might remain active

instead of changing to a disconnected state, even if the client is

physically disconnected from the terminal server. If the client

logs on to the same terminal server again, a new session might be

established (if Terminal Services is configured to allow multiple

sessions), and the original session might still be active. You

can use this setting to enable keep-alive connections and ensure

that the session state is consistent with the client state.

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"Dan H." <dh@nospam.com> wrote on 25 feb 2008 in

microsoft.public.windows.terminal_services:

> Thank you for your response.

>

> I have a dumb question that I believe I know the answer to but

> want to make certain.

>

> Would the "keep alive" option on the client have any bearing on

> the session? My thought is NO but as said I figured I'd ask.

>

> Thanks again.

>

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

> in message

> news:Xns9A4CE6266CDDFveranoesthemutforsse@207.46.248.16...

>> This can be caused by a router between the client and your

>> server, which sees no traffic and decides that the session must

>> have ended and throws it out.

>>

>> Since this happened after only a couple of minutes of idle

>> time, my guess is that it is a router. The solution in that

>> case is to enable TS Keepalives on the server.

>>

>> For 2003 this is accomplished via Group Policy setting:

>>

>> Computer Configuration - Administrative templates - Windows

>> Components - Terminal Services

>> "Keep-Alive connections"

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> "Dan H." <dh@nospam.com> wrote on 22 feb 2008 in

>> microsoft.public.windows.terminal_services:

>>

>>> Hi,

>>> Server 2000

>>> We have WinXP laptops clients.

>>>

>>> A user will get kicked off so I was thinking it was a timeout

>>> issue.

>>>

>>> I checked to see that RDP manager was set to 1 hour and set

>>> to override

>>> user accounts. User account is 1 hour and Policy is same

>>> (yeah I know the override is checked but figured I provide

>>> this information as well).

>>>

>>> Well I monitored a session and it showed her session as

>>> continous for ex. 30 minutes but then in the manager I would

>>> see the same person connected so it would show she had 2

>>> sessions going on. Then eventually session one would end

>>> because of the time limit. I asked her and she said she was

>>> booted as a timeout within minutes so she had to reconnect.

>>> So the reconnect was the session two that I saw but as I said

>>> Terminal manager still acknowledged her first session as being

>>> active. Any ideas would be great or if you need further

>>> information please let me know.

>>>

>>> Thanks.

[Guest Dan H.]

Re: Sessions "Time Out" but server still thinks active

 

Thanks. Correct me if I'm wrong but according to this description then it

also would not fix the Client disconnecting (as you said you suspect router)

but fix only the multiple sessions appearing on Terminal manager. Correct?

 

If this is the case, is there any thing I can do to 1-test for anything else

on that end but the router (i.e. check for something on the client machine

itself). 2-work around the dropped connection problem.

 

Unfortunately the router is not ours and they will not change its settings,

we are sort of visitors in the location.

 

Thanks for your time.

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns9A4FD70C31464veranoesthemutforsse@207.46.248.16...

> No, KeepAlive has no effect on the client. This is what it does

> (from the "Explain" text in GPMC):

>

> After a terminal server client loses the connection to a terminal

> server, the session on the terminal server might remain active

> instead of changing to a disconnected state, even if the client is

> physically disconnected from the terminal server. If the client

> logs on to the same terminal server again, a new session might be

> established (if Terminal Services is configured to allow multiple

> sessions), and the original session might still be active. You

> can use this setting to enable keep-alive connections and ensure

> that the session state is consistent with the client state.

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> "Dan H." <dh@nospam.com> wrote on 25 feb 2008 in

> microsoft.public.windows.terminal_services:

>

>> Thank you for your response.

>>

>> I have a dumb question that I believe I know the answer to but

>> want to make certain.

>>

>> Would the "keep alive" option on the client have any bearing on

>> the session? My thought is NO but as said I figured I'd ask.

>>

>> Thanks again.

>>

>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

>> in message

>> news:Xns9A4CE6266CDDFveranoesthemutforsse@207.46.248.16...

>>> This can be caused by a router between the client and your

>>> server, which sees no traffic and decides that the session must

>>> have ended and throws it out.

>>>

>>> Since this happened after only a couple of minutes of idle

>>> time, my guess is that it is a router. The solution in that

>>> case is to enable TS Keepalives on the server.

>>>

>>> For 2003 this is accomplished via Group Policy setting:

>>>

>>> Computer Configuration - Administrative templates - Windows

>>> Components - Terminal Services

>>> "Keep-Alive connections"

>>> _________________________________________________________

>>> Vera Noest

>>> MCSE, CCEA, Microsoft MVP - Terminal Server

>>> TS troubleshooting: http://ts.veranoest.net

>>> ___ please respond in newsgroup, NOT by private email ___

>>>

>>> "Dan H." <dh@nospam.com> wrote on 22 feb 2008 in

>>> microsoft.public.windows.terminal_services:

>>>

>>>> Hi,

>>>> Server 2000

>>>> We have WinXP laptops clients.

>>>>

>>>> A user will get kicked off so I was thinking it was a timeout

>>>> issue.

>>>>

>>>> I checked to see that RDP manager was set to 1 hour and set

>>>> to override

>>>> user accounts. User account is 1 hour and Policy is same

>>>> (yeah I know the override is checked but figured I provide

>>>> this information as well).

>>>>

>>>> Well I monitored a session and it showed her session as

>>>> continous for ex. 30 minutes but then in the manager I would

>>>> see the same person connected so it would show she had 2

>>>> sessions going on. Then eventually session one would end

>>>> because of the time limit. I asked her and she said she was

>>>> booted as a timeout within minutes so she had to reconnect.

>>>> So the reconnect was the session two that I saw but as I said

>>>> Terminal manager still acknowledged her first session as being

>>>> active. Any ideas would be great or if you need further

>>>> information please let me know.

>>>>

>>>> Thanks.

[Guest Vera Noest [MVP]]

Re: Sessions "Time Out" but server still thinks active

 

Since the server detects that the session isn't active and puts it

in the disconnected state, the user will be able to connect to the

same session again and continue where she was before.

 

But there's more to it, and more parameters to manipulate :-)

Check this:

 

How to make your intermittent or flaky terminal services connection

a little more stable

http://terminal.servebeer.com/php/flaky_connections.php

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"Dan H." <dh@nospam.com> wrote on 25 feb 2008 in

microsoft.public.windows.terminal_services:

> Thanks. Correct me if I'm wrong but according to this

> description then it also would not fix the Client disconnecting

> (as you said you suspect router) but fix only the multiple

> sessions appearing on Terminal manager. Correct?

>

> If this is the case, is there any thing I can do to 1-test for

> anything else on that end but the router (i.e. check for

> something on the client machine itself). 2-work around the

> dropped connection problem.

>

> Unfortunately the router is not ours and they will not change

> its settings, we are sort of visitors in the location.

>

> Thanks for your time.

>

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

> in message

> news:Xns9A4FD70C31464veranoesthemutforsse@207.46.248.16...

>> No, KeepAlive has no effect on the client. This is what it does

>> (from the "Explain" text in GPMC):

>>

>> After a terminal server client loses the connection to a

>> terminal server, the session on the terminal server might

>> remain active instead of changing to a disconnected state, even

>> if the client is physically disconnected from the terminal

>> server. If the client logs on to the same terminal server

>> again, a new session might be established (if Terminal Services

>> is configured to allow multiple sessions), and the original

>> session might still be active. You can use this setting to

>> enable keep-alive connections and ensure that the session state

>> is consistent with the client state.

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> "Dan H." <dh@nospam.com> wrote on 25 feb 2008 in

>> microsoft.public.windows.terminal_services:

>>

>>> Thank you for your response.

>>>

>>> I have a dumb question that I believe I know the answer to but

>>> want to make certain.

>>>

>>> Would the "keep alive" option on the client have any bearing

>>> on the session? My thought is NO but as said I figured I'd

>>> ask.

>>>

>>> Thanks again.

>>>

>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>

>>> wrote in message

>>> news:Xns9A4CE6266CDDFveranoesthemutforsse@207.46.248.16...

>>>> This can be caused by a router between the client and your

>>>> server, which sees no traffic and decides that the session

>>>> must have ended and throws it out.

>>>>

>>>> Since this happened after only a couple of minutes of idle

>>>> time, my guess is that it is a router. The solution in that

>>>> case is to enable TS Keepalives on the server.

>>>>

>>>> For 2003 this is accomplished via Group Policy setting:

>>>>

>>>> Computer Configuration - Administrative templates - Windows

>>>> Components - Terminal Services

>>>> "Keep-Alive connections"

>>>> _________________________________________________________

>>>> Vera Noest

>>>> MCSE, CCEA, Microsoft MVP - Terminal Server

>>>> TS troubleshooting: http://ts.veranoest.net

>>>> ___ please respond in newsgroup, NOT by private email ___

>>>>

>>>> "Dan H." <dh@nospam.com> wrote on 22 feb 2008 in

>>>> microsoft.public.windows.terminal_services:

>>>>

>>>>> Hi,

>>>>> Server 2000

>>>>> We have WinXP laptops clients.

>>>>>

>>>>> A user will get kicked off so I was thinking it was a

>>>>> timeout issue.

>>>>>

>>>>> I checked to see that RDP manager was set to 1 hour and set

>>>>> to override

>>>>> user accounts. User account is 1 hour and Policy is same

>>>>> (yeah I know the override is checked but figured I provide

>>>>> this information as well).

>>>>>

>>>>> Well I monitored a session and it showed her session as

>>>>> continous for ex. 30 minutes but then in the manager I would

>>>>> see the same person connected so it would show she had 2

>>>>> sessions going on. Then eventually session one would end

>>>>> because of the time limit. I asked her and she said she was

>>>>> booted as a timeout within minutes so she had to reconnect.

>>>>> So the reconnect was the session two that I saw but as I

>>>>> said Terminal manager still acknowledged her first session

>>>>> as being active. Any ideas would be great or if you need

>>>>> further information please let me know.

>>>>>

>>>>> Thanks.

[Guest Dan H.]

Re: Sessions "Time Out" but server still thinks active

 

Thank you very much for the time you took to respond to this thread and

provide help. It is very much appreciated!

 

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns9A4FE2B641763veranoesthemutforsse@207.46.248.16...

> Since the server detects that the session isn't active and puts it

> in the disconnected state, the user will be able to connect to the

> same session again and continue where she was before.

>

> But there's more to it, and more parameters to manipulate :-)

> Check this:

>

> How to make your intermittent or flaky terminal services connection

> a little more stable

> http://terminal.servebeer.com/php/flaky_connections.php

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> "Dan H." <dh@nospam.com> wrote on 25 feb 2008 in

> microsoft.public.windows.terminal_services:

>

>> Thanks. Correct me if I'm wrong but according to this

>> description then it also would not fix the Client disconnecting

>> (as you said you suspect router) but fix only the multiple

>> sessions appearing on Terminal manager. Correct?

>>

>> If this is the case, is there any thing I can do to 1-test for

>> anything else on that end but the router (i.e. check for

>> something on the client machine itself). 2-work around the

>> dropped connection problem.

>>

>> Unfortunately the router is not ours and they will not change

>> its settings, we are sort of visitors in the location.

>>

>> Thanks for your time.

>>

>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

>> in message

>> news:Xns9A4FD70C31464veranoesthemutforsse@207.46.248.16...

>>> No, KeepAlive has no effect on the client. This is what it does

>>> (from the "Explain" text in GPMC):

>>>

>>> After a terminal server client loses the connection to a

>>> terminal server, the session on the terminal server might

>>> remain active instead of changing to a disconnected state, even

>>> if the client is physically disconnected from the terminal

>>> server. If the client logs on to the same terminal server

>>> again, a new session might be established (if Terminal Services

>>> is configured to allow multiple sessions), and the original

>>> session might still be active. You can use this setting to

>>> enable keep-alive connections and ensure that the session state

>>> is consistent with the client state.

>>>

>>> _________________________________________________________

>>> Vera Noest

>>> MCSE, CCEA, Microsoft MVP - Terminal Server

>>> TS troubleshooting: http://ts.veranoest.net

>>> ___ please respond in newsgroup, NOT by private email ___

>>>

>>> "Dan H." <dh@nospam.com> wrote on 25 feb 2008 in

>>> microsoft.public.windows.terminal_services:

>>>

>>>> Thank you for your response.

>>>>

>>>> I have a dumb question that I believe I know the answer to but

>>>> want to make certain.

>>>>

>>>> Would the "keep alive" option on the client have any bearing

>>>> on the session? My thought is NO but as said I figured I'd

>>>> ask.

>>>>

>>>> Thanks again.

>>>>

>>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>

>>>> wrote in message

>>>> news:Xns9A4CE6266CDDFveranoesthemutforsse@207.46.248.16...

>>>>> This can be caused by a router between the client and your

>>>>> server, which sees no traffic and decides that the session

>>>>> must have ended and throws it out.

>>>>>

>>>>> Since this happened after only a couple of minutes of idle

>>>>> time, my guess is that it is a router. The solution in that

>>>>> case is to enable TS Keepalives on the server.

>>>>>

>>>>> For 2003 this is accomplished via Group Policy setting:

>>>>>

>>>>> Computer Configuration - Administrative templates - Windows

>>>>> Components - Terminal Services

>>>>> "Keep-Alive connections"

>>>>> _________________________________________________________

>>>>> Vera Noest

>>>>> MCSE, CCEA, Microsoft MVP - Terminal Server

>>>>> TS troubleshooting: http://ts.veranoest.net

>>>>> ___ please respond in newsgroup, NOT by private email ___

>>>>>

>>>>> "Dan H." <dh@nospam.com> wrote on 22 feb 2008 in

>>>>> microsoft.public.windows.terminal_services:

>>>>>

>>>>>> Hi,

>>>>>> Server 2000

>>>>>> We have WinXP laptops clients.

>>>>>>

>>>>>> A user will get kicked off so I was thinking it was a

>>>>>> timeout issue.

>>>>>>

>>>>>> I checked to see that RDP manager was set to 1 hour and set

>>>>>> to override

>>>>>> user accounts. User account is 1 hour and Policy is same

>>>>>> (yeah I know the override is checked but figured I provide

>>>>>> this information as well).

>>>>>>

>>>>>> Well I monitored a session and it showed her session as

>>>>>> continous for ex. 30 minutes but then in the manager I would

>>>>>> see the same person connected so it would show she had 2

>>>>>> sessions going on. Then eventually session one would end

>>>>>> because of the time limit. I asked her and she said she was

>>>>>> booted as a timeout within minutes so she had to reconnect.

>>>>>> So the reconnect was the session two that I saw but as I

>>>>>> said Terminal manager still acknowledged her first session

>>>>>> as being active. Any ideas would be great or if you need

>>>>>> further information please let me know.

>>>>>>

>>>>>> Thanks.

[Guest Vera Noest [MVP]]

Re: Sessions "Time Out" but server still thinks active

 

My pleasure, Dan.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

*----------- Please reply in newsgroup -------------*

 

"Dan H." <dh@nospam.com> wrote on 26 feb 2008:

> Thank you very much for the time you took to respond to this

> thread and provide help. It is very much appreciated!

>

>

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

> in message

> news:Xns9A4FE2B641763veranoesthemutforsse@207.46.248.16...

>> Since the server detects that the session isn't active and puts

>> it in the disconnected state, the user will be able to connect

>> to the same session again and continue where she was before.

>>

>> But there's more to it, and more parameters to manipulate :-)

>> Check this:

>>

>> How to make your intermittent or flaky terminal services

>> connection a little more stable

>> http://terminal.servebeer.com/php/flaky_connections.php

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> "Dan H." <dh@nospam.com> wrote on 25 feb 2008 in

>> microsoft.public.windows.terminal_services:

>>

>>> Thanks. Correct me if I'm wrong but according to this

>>> description then it also would not fix the Client

>>> disconnecting (as you said you suspect router) but fix only

>>> the multiple sessions appearing on Terminal manager. Correct?

>>>

>>> If this is the case, is there any thing I can do to 1-test for

>>> anything else on that end but the router (i.e. check for

>>> something on the client machine itself). 2-work around the

>>> dropped connection problem.

>>>

>>> Unfortunately the router is not ours and they will not change

>>> its settings, we are sort of visitors in the location.

>>>

>>> Thanks for your time.

>>>

>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>

>>> wrote in message

>>> news:Xns9A4FD70C31464veranoesthemutforsse@207.46.248.16...

>>>> No, KeepAlive has no effect on the client. This is what it

>>>> does (from the "Explain" text in GPMC):

>>>>

>>>> After a terminal server client loses the connection to a

>>>> terminal server, the session on the terminal server might

>>>> remain active instead of changing to a disconnected state,

>>>> even if the client is physically disconnected from the

>>>> terminal server. If the client logs on to the same terminal

>>>> server again, a new session might be established (if Terminal

>>>> Services is configured to allow multiple sessions), and the

>>>> original session might still be active. You can use this

>>>> setting to enable keep-alive connections and ensure that the

>>>> session state is consistent with the client state.

>>>>

>>>> _________________________________________________________

>>>> Vera Noest

>>>> MCSE, CCEA, Microsoft MVP - Terminal Server

>>>> TS troubleshooting: http://ts.veranoest.net

>>>> ___ please respond in newsgroup, NOT by private email ___

>>>>

>>>> "Dan H." <dh@nospam.com> wrote on 25 feb 2008 in

>>>> microsoft.public.windows.terminal_services:

>>>>

>>>>> Thank you for your response.

>>>>>

>>>>> I have a dumb question that I believe I know the answer to

>>>>> but want to make certain.

>>>>>

>>>>> Would the "keep alive" option on the client have any bearing

>>>>> on the session? My thought is NO but as said I figured I'd

>>>>> ask.

>>>>>

>>>>> Thanks again.

>>>>>

>>>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>

>>>>> wrote in message

>>>>> news:Xns9A4CE6266CDDFveranoesthemutforsse@207.46.248.16...

>>>>>> This can be caused by a router between the client and your

>>>>>> server, which sees no traffic and decides that the session

>>>>>> must have ended and throws it out.

>>>>>>

>>>>>> Since this happened after only a couple of minutes of idle

>>>>>> time, my guess is that it is a router. The solution in that

>>>>>> case is to enable TS Keepalives on the server.

>>>>>>

>>>>>> For 2003 this is accomplished via Group Policy setting:

>>>>>>

>>>>>> Computer Configuration - Administrative templates - Windows

>>>>>> Components - Terminal Services

>>>>>> "Keep-Alive connections"

>>>>>> _________________________________________________________

>>>>>> Vera Noest

>>>>>> MCSE, CCEA, Microsoft MVP - Terminal Server

>>>>>> TS troubleshooting: http://ts.veranoest.net

>>>>>> ___ please respond in newsgroup, NOT by private email ___

>>>>>>

>>>>>> "Dan H." <dh@nospam.com> wrote on 22 feb 2008 in

>>>>>> microsoft.public.windows.terminal_services:

>>>>>>

>>>>>>> Hi,

>>>>>>> Server 2000

>>>>>>> We have WinXP laptops clients.

>>>>>>>

>>>>>>> A user will get kicked off so I was thinking it was a

>>>>>>> timeout issue.

>>>>>>>

>>>>>>> I checked to see that RDP manager was set to 1 hour and

>>>>>>> set to override

>>>>>>> user accounts. User account is 1 hour and Policy is same

>>>>>>> (yeah I know the override is checked but figured I provide

>>>>>>> this information as well).

>>>>>>>

>>>>>>> Well I monitored a session and it showed her session as

>>>>>>> continous for ex. 30 minutes but then in the manager I

>>>>>>> would see the same person connected so it would show she

>>>>>>> had 2 sessions going on. Then eventually session one

>>>>>>> would end because of the time limit. I asked her and she

>>>>>>> said she was booted as a timeout within minutes so she had

>>>>>>> to reconnect. So the reconnect was the session two that I

>>>>>>> saw but as I said Terminal manager still acknowledged her

>>>>>>> first session as being active. Any ideas would be great or

>>>>>>> if you need further information please let me know.

>>>>>>>

>>>>>>> Thanks.