A
Alan Burstein
I have a client with one dedicated Win2K Terminal Server
and apprximently 7-8 users using TS at a given time. At
various times throughout the day some clients get
disconnected. This does not happen to all of them at once
(so its not the incoming T1) and their VPN connections
don't get disconnected (so it's not their DSL connections).
I recently starting tracking the TS Session counters using
the performance monitor and noticed many Async Overflow
errors. Per Microsoft.com this is "caused by a lack of
buffer space available on the host."
Does anyone know how to increase the buffer space
available to clients connecting into Terminal Services?
Our client and server buffers are currently set (I guess
by default) to 5x1460 bytes
and apprximently 7-8 users using TS at a given time. At
various times throughout the day some clients get
disconnected. This does not happen to all of them at once
(so its not the incoming T1) and their VPN connections
don't get disconnected (so it's not their DSL connections).
I recently starting tracking the TS Session counters using
the performance monitor and noticed many Async Overflow
errors. Per Microsoft.com this is "caused by a lack of
buffer space available on the host."
Does anyone know how to increase the buffer space
available to clients connecting into Terminal Services?
Our client and server buffers are currently set (I guess
by default) to 5x1460 bytes