Sessions reamin active

[Guest]

I have Windows 2000 SP4 Terminal Server running in application mode on my LAN. All connecting clients are W2K Profesional SP3. Clients can connect to TS from WAN or LAN. Clients can connect, work and disconnect normally. But things change when a connection error occurs; sessions from clients from WAN remain ACTIVE (although sessions from LAN clients gets disconected as normal). Therefore, next time they log back in to TS, they can not continue to their disconnected session.
Any ideas why WAN clients remain active & not disconnect

 

[Ivan Leichtling [MSFT]]

Please see Microsoft Knowedge Base Article 187049 - Active sessions
can have no related clients

http://support.microsoft.com/default.aspx?scid=kb;en-us;187049&Product=termsvr

I have Windows 2000 SP4 Terminal Server running in application mode on my LAN. All connecting clients are W2K Profesional SP3. Clients can connect to TS from WAN or LAN. Clients can connect, work and disconnect normally. But things change when a connection error occurs; sessions from clients from WAN remain ACTIVE (although sessions from LAN clients gets disconected as normal). Therefore, next time they log back in to TS, they can not continue to their disconnected session.
Any ideas why WAN clients remain active & not disconnect?

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

 

[Matthew Harris [MVP]]

Try enabling keey alives..

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

-M

-----Original Message-----
I have Windows 2000 SP4 Terminal Server running in

application mode on my LAN. All connecting clients are W2K
Profesional SP3. Clients can connect to TS from WAN or
LAN. Clients can connect, work and disconnect normally.
But things change when a connection error occurs; sessions
from clients from WAN remain ACTIVE (although sessions
from LAN clients gets disconected as normal). Therefore,
next time they log back in to TS, they can not continue to
their disconnected session.