Management of disconnected sessions

[Guest Toine]

Hello,

 

I have a problem with the management of disconnected sessions on my Server

2003 SP2.

 

When a TSE session is opened from a network station and I close it with the

cross or with Start/Disconnect session, the session is still available on

the server and I can get connected back to it.

 

On the other hand, if a network failure or a station reboot occurs, the

session is killed after about 1 minute.

 

How to keep theses disconnected sessions available for reconnection?

 

In the Terminal Services Configuration, the protocol is configured as

follows:

- End of a disconnected session: Never

- Active session limit: Never

- Inactive session limit: 1 day

- When the session limit is reached ... : Disconnection of session

 

 

Thanks!

[Guest Vera Noest [MVP]]

Re: Management of disconnected sessions

 

Have you enabled automatic reconnection?

 

323258 - Description of the Automatic Reconnection Feature in

Windows Server 2003 and Windows XP SP1

http://support.microsoft.com/?kbid=323258

 

As far as I know, rebooting the workstation will result in a broken

session.

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"Toine" <toine0(àsuppr)@gmail.com> wrote on 03 okt 2007 in

microsoft.public.windows.terminal_services:

> Hello,

>

> I have a problem with the management of disconnected sessions on

> my Server 2003 SP2.

>

> When a TSE session is opened from a network station and I close

> it with the cross or with Start/Disconnect session, the session

> is still available on the server and I can get connected back to

> it.

>

> On the other hand, if a network failure or a station reboot

> occurs, the session is killed after about 1 minute.

>

> How to keep theses disconnected sessions available for

> reconnection?

>

> In the Terminal Services Configuration, the protocol is

> configured as follows:

> - End of a disconnected session: Never

> - Active session limit: Never

> - Inactive session limit: 1 day

> - When the session limit is reached ... : Disconnection of

> session

>

>

> Thanks!

[Guest Toine]

Re: Management of disconnected sessions

 

Yes, automatic reconnection is enabled.

The main problem is when a a user is connected through the Internet and

there is an ISP disconnection on client side.

I try to understand: if the TS Client application is closed during the

disconnection or if the disconnection lasts more than 20 tries (10 min?),

will the session be irremediably killed?

 

 

Thanks!

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> a écrit dans le

message de news:Xns99BEF1A64E1B5veranoesthemutforsse@207.46.248.16...

> Have you enabled automatic reconnection?

>

> 323258 - Description of the Automatic Reconnection Feature in

> Windows Server 2003 and Windows XP SP1

> http://support.microsoft.com/?kbid=323258

>

> As far as I know, rebooting the workstation will result in a broken

> session.

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> "Toine" <toine0(àsuppr)@gmail.com> wrote on 03 okt 2007 in

> microsoft.public.windows.terminal_services:

>

>> Hello,

>>

>> I have a problem with the management of disconnected sessions on

>> my Server 2003 SP2.

>>

>> When a TSE session is opened from a network station and I close

>> it with the cross or with Start/Disconnect session, the session

>> is still available on the server and I can get connected back to

>> it.

>>

>> On the other hand, if a network failure or a station reboot

>> occurs, the session is killed after about 1 minute.

>>

>> How to keep theses disconnected sessions available for

>> reconnection?

>>

>> In the Terminal Services Configuration, the protocol is

>> configured as follows:

>> - End of a disconnected session: Never

>> - Active session limit: Never

>> - Inactive session limit: 1 day

>> - When the session limit is reached ... : Disconnection of

>> session

>>

>>

>> Thanks!

[Guest Toine]

Re: Management of disconnected sessions

 

Any idea?

 

 

"Toine" <toine0(àsuppr)@gmail.com> a écrit dans le message de

news:Ov5J5umBIHA.3848@TK2MSFTNGP05.phx.gbl...

> Yes, automatic reconnection is enabled.

> The main problem is when a a user is connected through the Internet and

> there is an ISP disconnection on client side.

> I try to understand: if the TS Client application is closed during the

> disconnection or if the disconnection lasts more than 20 tries (10 min?),

> will the session be irremediably killed?

>

>

> Thanks!

>

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> a écrit dans le

> message de news:Xns99BEF1A64E1B5veranoesthemutforsse@207.46.248.16...

>> Have you enabled automatic reconnection?

>>

>> 323258 - Description of the Automatic Reconnection Feature in

>> Windows Server 2003 and Windows XP SP1

>> http://support.microsoft.com/?kbid=323258

>>

>> As far as I know, rebooting the workstation will result in a broken

>> session.

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>>

>> "Toine" <toine0(àsuppr)@gmail.com> wrote on 03 okt 2007 in

>> microsoft.public.windows.terminal_services:

>>

>>> Hello,

>>>

>>> I have a problem with the management of disconnected sessions on

>>> my Server 2003 SP2.

>>>

>>> When a TSE session is opened from a network station and I close

>>> it with the cross or with Start/Disconnect session, the session

>>> is still available on the server and I can get connected back to

>>> it.

>>>

>>> On the other hand, if a network failure or a station reboot

>>> occurs, the session is killed after about 1 minute.

>>>

>>> How to keep theses disconnected sessions available for

>>> reconnection?

>>>

>>> In the Terminal Services Configuration, the protocol is

>>> configured as follows:

>>> - End of a disconnected session: Never

>>> - Active session limit: Never

>>> - Inactive session limit: 1 day

>>> - When the session limit is reached ... : Disconnection of

>>> session

>>>

>>>

>>> Thanks!

>

[Guest Soo Kuan Teo [MSFT]]

Re: Management of disconnected sessions

 

Please give this a try to see if it helps you:

1. goto tscc.msc->Connections->Rdp-Tcp->Sessions tab, check the check box

with "Override user settings when session limit is reached or connection is

broken:",

2. select Disconnect from session.

 

 

 

Thanks

Soo Kuan

 

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

 

"Toine" <toine0(àsuppr)@gmail.com> wrote in message

news:%23FzuT6pBIHA.3940@TK2MSFTNGP05.phx.gbl...

> Any idea?

>

>

> "Toine" <toine0(àsuppr)@gmail.com> a écrit dans le message de

> news:Ov5J5umBIHA.3848@TK2MSFTNGP05.phx.gbl...

>> Yes, automatic reconnection is enabled.

>> The main problem is when a a user is connected through the Internet and

>> there is an ISP disconnection on client side.

>> I try to understand: if the TS Client application is closed during the

>> disconnection or if the disconnection lasts more than 20 tries (10 min?),

>> will the session be irremediably killed?

>>

>>

>> Thanks!

>>

>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> a écrit dans le

>> message de news:Xns99BEF1A64E1B5veranoesthemutforsse@207.46.248.16...

>>> Have you enabled automatic reconnection?

>>>

>>> 323258 - Description of the Automatic Reconnection Feature in

>>> Windows Server 2003 and Windows XP SP1

>>> http://support.microsoft.com/?kbid=323258

>>>

>>> As far as I know, rebooting the workstation will result in a broken

>>> session.

>>>

>>> _________________________________________________________

>>> Vera Noest

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

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

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

>>>

>>> "Toine" <toine0(àsuppr)@gmail.com> wrote on 03 okt 2007 in

>>> microsoft.public.windows.terminal_services:

>>>

>>>> Hello,

>>>>

>>>> I have a problem with the management of disconnected sessions on

>>>> my Server 2003 SP2.

>>>>

>>>> When a TSE session is opened from a network station and I close

>>>> it with the cross or with Start/Disconnect session, the session

>>>> is still available on the server and I can get connected back to

>>>> it.

>>>>

>>>> On the other hand, if a network failure or a station reboot

>>>> occurs, the session is killed after about 1 minute.

>>>>

>>>> How to keep theses disconnected sessions available for

>>>> reconnection?

>>>>

>>>> In the Terminal Services Configuration, the protocol is

>>>> configured as follows:

>>>> - End of a disconnected session: Never

>>>> - Active session limit: Never

>>>> - Inactive session limit: 1 day

>>>> - When the session limit is reached ... : Disconnection of

>>>> session

>>>>

>>>>

>>>> Thanks!

>>

>

[Guest Toine]

Re: Management of disconnected sessions

 

Hello,

 

This parameter is already in this position.

I wrote this in my first message, but my translation was not exact, sorry.

 

Thank you anyway!

 

 

"Soo Kuan Teo [MSFT]" <sookuant@online.microsoft.com> a écrit dans le

message de news:e%23A5M9qBIHA.4568@TK2MSFTNGP02.phx.gbl...

> Please give this a try to see if it helps you:

> 1. goto tscc.msc->Connections->Rdp-Tcp->Sessions tab, check the check box

> with "Override user settings when session limit is reached or connection

> is broken:",

> 2. select Disconnect from session.

>

>

>

> Thanks

> Soo Kuan

>

>

> --

> This posting is provided "AS IS" with no warranties, and confers no

> rights.

>

> "Toine" <toine0(àsuppr)@gmail.com> wrote in message

> news:%23FzuT6pBIHA.3940@TK2MSFTNGP05.phx.gbl...

>> Any idea?

>>

>>

>> "Toine" <toine0(àsuppr)@gmail.com> a écrit dans le message de

>> news:Ov5J5umBIHA.3848@TK2MSFTNGP05.phx.gbl...

>>> Yes, automatic reconnection is enabled.

>>> The main problem is when a a user is connected through the Internet and

>>> there is an ISP disconnection on client side.

>>> I try to understand: if the TS Client application is closed during the

>>> disconnection or if the disconnection lasts more than 20 tries (10

>>> min?), will the session be irremediably killed?

>>>

>>>

>>> Thanks!

>>>

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

>>> le message de news:Xns99BEF1A64E1B5veranoesthemutforsse@207.46.248.16...

>>>> Have you enabled automatic reconnection?

>>>>

>>>> 323258 - Description of the Automatic Reconnection Feature in

>>>> Windows Server 2003 and Windows XP SP1

>>>> http://support.microsoft.com/?kbid=323258

>>>>

>>>> As far as I know, rebooting the workstation will result in a broken

>>>> session.

>>>>

>>>> _________________________________________________________

>>>> Vera Noest

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

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

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

>>>>

>>>> "Toine" <toine0(àsuppr)@gmail.com> wrote on 03 okt 2007 in

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

>>>>

>>>>> Hello,

>>>>>

>>>>> I have a problem with the management of disconnected sessions on

>>>>> my Server 2003 SP2.

>>>>>

>>>>> When a TSE session is opened from a network station and I close

>>>>> it with the cross or with Start/Disconnect session, the session

>>>>> is still available on the server and I can get connected back to

>>>>> it.

>>>>>

>>>>> On the other hand, if a network failure or a station reboot

>>>>> occurs, the session is killed after about 1 minute.

>>>>>

>>>>> How to keep theses disconnected sessions available for

>>>>> reconnection?

>>>>>

>>>>> In the Terminal Services Configuration, the protocol is

>>>>> configured as follows:

>>>>> - End of a disconnected session: Never

>>>>> - Active session limit: Never

>>>>> - Inactive session limit: 1 day

>>>>> - When the session limit is reached ... : Disconnection of

>>>>> session

>>>>>

>>>>>

>>>>> Thanks!

>>>

>>

>

[Guest Vera Noest [MVP]]

Re: Management of disconnected sessions

 

This is how I read KB 323258:

20 tries to reconnect at 5 seconds intervals = less than 2 minutes.

If the network problem isn't solved by then, the session is closed.

 

You could try to increase the number of reconnection attempts:

AutoReconnect Max Retries:i:number

 

and then perform some testing, by pulling the network cable and

plug it in again, within the time-limit (i.e. number of

reconnection attempts limit). Then the session should be

reconnected.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"Toine" <toine0(àsuppr)@gmail.com> wrote on 04 okt 2007 in

microsoft.public.windows.terminal_services:

> Yes, automatic reconnection is enabled.

> The main problem is when a a user is connected through the

> Internet and there is an ISP disconnection on client side.

> I try to understand: if the TS Client application is closed

> during the disconnection or if the disconnection lasts more than

> 20 tries (10 min?), will the session be irremediably killed?

>

>

> Thanks!

>

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

> écrit dans le message de

> news:Xns99BEF1A64E1B5veranoesthemutforsse@207.46.248.16...

>> Have you enabled automatic reconnection?

>>

>> 323258 - Description of the Automatic Reconnection Feature in

>> Windows Server 2003 and Windows XP SP1

>> http://support.microsoft.com/?kbid=323258

>>

>> As far as I know, rebooting the workstation will result in a

>> broken session.

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>>

>> "Toine" <toine0(àsuppr)@gmail.com> wrote on 03 okt 2007 in

>> microsoft.public.windows.terminal_services:

>>

>>> Hello,

>>>

>>> I have a problem with the management of disconnected sessions

>>> on my Server 2003 SP2.

>>>

>>> When a TSE session is opened from a network station and I

>>> close it with the cross or with Start/Disconnect session, the

>>> session is still available on the server and I can get

>>> connected back to it.

>>>

>>> On the other hand, if a network failure or a station reboot

>>> occurs, the session is killed after about 1 minute.

>>>

>>> How to keep theses disconnected sessions available for

>>> reconnection?

>>>

>>> In the Terminal Services Configuration, the protocol is

>>> configured as follows:

>>> - End of a disconnected session: Never

>>> - Active session limit: Never

>>> - Inactive session limit: 1 day

>>> - When the session limit is reached ... : Disconnection of

>>> session

>>>

>>>

>>> Thanks!

[Guest Toine]

Re: Management of disconnected sessions

 

Thank you, I will try this way.

 

This is amazing because on other servers, I'm able to connect to

disconnected sessions that were cut this way. Maybe this is because these

are remote desktop administrative sessions and the behavior is not the same

as terminal server...

Do you think it's possible?

 

 

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> a écrit dans le

message de news:Xns99BFDB1612A92veranoesthemutforsse@207.46.248.16...

> This is how I read KB 323258:

> 20 tries to reconnect at 5 seconds intervals = less than 2 minutes.

> If the network problem isn't solved by then, the session is closed.

>

> You could try to increase the number of reconnection attempts:

> AutoReconnect Max Retries:i:number

>

> and then perform some testing, by pulling the network cable and

> plug it in again, within the time-limit (i.e. number of

> reconnection attempts limit). Then the session should be

> reconnected.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> "Toine" <toine0(àsuppr)@gmail.com> wrote on 04 okt 2007 in

> microsoft.public.windows.terminal_services:

>

>> Yes, automatic reconnection is enabled.

>> The main problem is when a a user is connected through the

>> Internet and there is an ISP disconnection on client side.

>> I try to understand: if the TS Client application is closed

>> during the disconnection or if the disconnection lasts more than

>> 20 tries (10 min?), will the session be irremediably killed?

>>

>>

>> Thanks!

>>

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

>> écrit dans le message de

>> news:Xns99BEF1A64E1B5veranoesthemutforsse@207.46.248.16...

>>> Have you enabled automatic reconnection?

>>>

>>> 323258 - Description of the Automatic Reconnection Feature in

>>> Windows Server 2003 and Windows XP SP1

>>> http://support.microsoft.com/?kbid=323258

>>>

>>> As far as I know, rebooting the workstation will result in a

>>> broken session.

>>>

>>> _________________________________________________________

>>> Vera Noest

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

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

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

>>>

>>> "Toine" <toine0(àsuppr)@gmail.com> wrote on 03 okt 2007 in

>>> microsoft.public.windows.terminal_services:

>>>

>>>> Hello,

>>>>

>>>> I have a problem with the management of disconnected sessions

>>>> on my Server 2003 SP2.

>>>>

>>>> When a TSE session is opened from a network station and I

>>>> close it with the cross or with Start/Disconnect session, the

>>>> session is still available on the server and I can get

>>>> connected back to it.

>>>>

>>>> On the other hand, if a network failure or a station reboot

>>>> occurs, the session is killed after about 1 minute.

>>>>

>>>> How to keep theses disconnected sessions available for

>>>> reconnection?

>>>>

>>>> In the Terminal Services Configuration, the protocol is

>>>> configured as follows:

>>>> - End of a disconnected session: Never

>>>> - Active session limit: Never

>>>> - Inactive session limit: 1 day

>>>> - When the session limit is reached ... : Disconnection of

>>>> session

>>>>

>>>>

>>>> Thanks!

[Guest Vera Noest [MVP]]

Re: Management of disconnected sessions

 

No, that doesn't make a difference.

But there could be other differences, like KeepAlive settings

(which make it easier for the server to detect that a session is

broken)

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"Toine" <toine0(àsuppr)@gmail.com> wrote on 05 okt 2007 in

microsoft.public.windows.terminal_services:

> Thank you, I will try this way.

>

> This is amazing because on other servers, I'm able to connect to

> disconnected sessions that were cut this way. Maybe this is

> because these are remote desktop administrative sessions and the

> behavior is not the same as terminal server...

> Do you think it's possible?

>

>

>

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

> écrit dans le message de

> news:Xns99BFDB1612A92veranoesthemutforsse@207.46.248.16...

>> This is how I read KB 323258:

>> 20 tries to reconnect at 5 seconds intervals = less than 2

>> minutes. If the network problem isn't solved by then, the

>> session is closed.

>>

>> You could try to increase the number of reconnection attempts:

>> AutoReconnect Max Retries:i:number

>>

>> and then perform some testing, by pulling the network cable and

>> plug it in again, within the time-limit (i.e. number of

>> reconnection attempts limit). Then the session should be

>> reconnected.

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>>

>> "Toine" <toine0(àsuppr)@gmail.com> wrote on 04 okt 2007 in

>> microsoft.public.windows.terminal_services:

>>

>>> Yes, automatic reconnection is enabled.

>>> The main problem is when a a user is connected through the

>>> Internet and there is an ISP disconnection on client side.

>>> I try to understand: if the TS Client application is closed

>>> during the disconnection or if the disconnection lasts more

>>> than 20 tries (10 min?), will the session be irremediably

>>> killed?

>>>

>>>

>>> Thanks!

>>>

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

>>> écrit dans le message de

>>> news:Xns99BEF1A64E1B5veranoesthemutforsse@207.46.248.16...

>>>> Have you enabled automatic reconnection?

>>>>

>>>> 323258 - Description of the Automatic Reconnection Feature in

>>>> Windows Server 2003 and Windows XP SP1

>>>> http://support.microsoft.com/?kbid=323258

>>>>

>>>> As far as I know, rebooting the workstation will result in a

>>>> broken session.

>>>>

>>>> _________________________________________________________

>>>> Vera Noest

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

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

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

>>>>

>>>> "Toine" <toine0(àsuppr)@gmail.com> wrote on 03 okt 2007 in

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

>>>>

>>>>> Hello,

>>>>>

>>>>> I have a problem with the management of disconnected

>>>>> sessions on my Server 2003 SP2.

>>>>>

>>>>> When a TSE session is opened from a network station and I

>>>>> close it with the cross or with Start/Disconnect session,

>>>>> the session is still available on the server and I can get

>>>>> connected back to it.

>>>>>

>>>>> On the other hand, if a network failure or a station reboot

>>>>> occurs, the session is killed after about 1 minute.

>>>>>

>>>>> How to keep theses disconnected sessions available for

>>>>> reconnection?

>>>>>

>>>>> In the Terminal Services Configuration, the protocol is

>>>>> configured as follows:

>>>>> - End of a disconnected session: Never

>>>>> - Active session limit: Never

>>>>> - Inactive session limit: 1 day

>>>>> - When the session limit is reached ... : Disconnection of

>>>>> session

>>>>>

>>>>>

>>>>> Thanks!

[Guest Toine]

Re: Management of disconnected sessions

 

Well, thank you for this advice.

I made a long research on the problem but it isn't solved yet.

As far as I understood, the KeepAliveEnable setting just sends a heartbeat.

I could enable, disable it or raise the interval, it changes nothing.

If I explicitly disconnect the session, the state goes to "Disconnected" and

I can reconnect to it.

I there is a network cut, the state goes to "Down" after exactly 1 minute

and then is killed.

I think this parameter is not handled correctly: "Override user settings

when session limit is reached or connection is broken: Disconnect from

session".

 

If you have any other track...

 

 

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> a écrit dans le

message de news:Xns99C0E0B3684C7veranoesthemutforsse@207.46.248.16...

> No, that doesn't make a difference.

> But there could be other differences, like KeepAlive settings

> (which make it easier for the server to detect that a session is

> broken)

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> "Toine" <toine0(àsuppr)@gmail.com> wrote on 05 okt 2007 in

> microsoft.public.windows.terminal_services:

>

>> Thank you, I will try this way.

>>

>> This is amazing because on other servers, I'm able to connect to

>> disconnected sessions that were cut this way. Maybe this is

>> because these are remote desktop administrative sessions and the

>> behavior is not the same as terminal server...

>> Do you think it's possible?

>>

>>

>>

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

>> écrit dans le message de

>> news:Xns99BFDB1612A92veranoesthemutforsse@207.46.248.16...

>>> This is how I read KB 323258:

>>> 20 tries to reconnect at 5 seconds intervals = less than 2

>>> minutes. If the network problem isn't solved by then, the

>>> session is closed.

>>>

>>> You could try to increase the number of reconnection attempts:

>>> AutoReconnect Max Retries:i:number

>>>

>>> and then perform some testing, by pulling the network cable and

>>> plug it in again, within the time-limit (i.e. number of

>>> reconnection attempts limit). Then the session should be

>>> reconnected.

>>> _________________________________________________________

>>> Vera Noest

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

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

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

>>>

>>> "Toine" <toine0(àsuppr)@gmail.com> wrote on 04 okt 2007 in

>>> microsoft.public.windows.terminal_services:

>>>

>>>> Yes, automatic reconnection is enabled.

>>>> The main problem is when a a user is connected through the

>>>> Internet and there is an ISP disconnection on client side.

>>>> I try to understand: if the TS Client application is closed

>>>> during the disconnection or if the disconnection lasts more

>>>> than 20 tries (10 min?), will the session be irremediably

>>>> killed?

>>>>

>>>>

>>>> Thanks!

>>>>

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

>>>> écrit dans le message de

>>>> news:Xns99BEF1A64E1B5veranoesthemutforsse@207.46.248.16...

>>>>> Have you enabled automatic reconnection?

>>>>>

>>>>> 323258 - Description of the Automatic Reconnection Feature in

>>>>> Windows Server 2003 and Windows XP SP1

>>>>> http://support.microsoft.com/?kbid=323258

>>>>>

>>>>> As far as I know, rebooting the workstation will result in a

>>>>> broken session.

>>>>>

>>>>> _________________________________________________________

>>>>> Vera Noest

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

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

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

>>>>>

>>>>> "Toine" <toine0(àsuppr)@gmail.com> wrote on 03 okt 2007 in

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

>>>>>

>>>>>> Hello,

>>>>>>

>>>>>> I have a problem with the management of disconnected

>>>>>> sessions on my Server 2003 SP2.

>>>>>>

>>>>>> When a TSE session is opened from a network station and I

>>>>>> close it with the cross or with Start/Disconnect session,

>>>>>> the session is still available on the server and I can get

>>>>>> connected back to it.

>>>>>>

>>>>>> On the other hand, if a network failure or a station reboot

>>>>>> occurs, the session is killed after about 1 minute.

>>>>>>

>>>>>> How to keep theses disconnected sessions available for

>>>>>> reconnection?

>>>>>>

>>>>>> In the Terminal Services Configuration, the protocol is

>>>>>> configured as follows:

>>>>>> - End of a disconnected session: Never

>>>>>> - Active session limit: Never

>>>>>> - Inactive session limit: 1 day

>>>>>> - When the session limit is reached ... : Disconnection of

>>>>>> session

>>>>>>

>>>>>>

>>>>>> Thanks!