Windows Forum

Ask something
Discussion Locked

Terminal Server

0 helpful
9 replies

by skc2

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have 2 problems but they might be one issue. I have a TS running on a W2K server. I have a couple of users that are complaining that they get timed out when they try to connect. They are getting the following message: 'Terminal Services client disconnect. The connection to the server has timed out, try connecting to the Terminal again.' I also have a couple of users that are getting disconnected after a short while after they are connected. The idle and disconnected session time out value is set much longer than a few minutes. These people that are having problem are connecting using DSL and Cable Modem. The funny thing is, I have another user that connect daily using cable modem and I haven't heard any complain from her. Any help would be greatly appreciated.

Kit

9 replies

by dcb311

What kind of connection so you have into the T/S and what is your server config (CPU type& # , mem, etc.).

How many total remote users do you have at any one time.

Don Boling
dcb311@netzero.net

by avswamy

configure in server having more connection to ts and create never disconnect to connected users and disconnected session will be closed immediately. i hope this will solve ur problem.

by skc2

I only one connection type comming in since it's Microsoft's TS and it's the RDP-TCP. My server's config is dual 500 MHz and 1 GB of RAM. Currently, I have no more than 5 users connected at one time. In the near future, we are looking to increasethat number to no more than 10.

Thanks for you respond.

Kit

by flan

depends on how the terminal server is setup. do you have the appropriate number of licenses? or is it set up in admin mode? does the server have a static ip?

by cdue

I'm pretty sure your server are working just fine.

You actually explained it yourself: DSL and Cable Modem. Both RDP and ICA are pretty delay sensitive and will, when connected using a public access path (internet), often drop and timeout when connecting. There is nothing you can do about that. It seem like this hurts if the delay (ping) constantly exceeds 120-150 ms.

Do you have dialup users as well ? On a < 28k line you will perfom just fine and alsmot never drop

For the users that are getting disconnected: There is one typical scenario here: You are idle and the traffic have been idle for a while. When you go back to the session it might take a second or two to get it going again. If you include delay and the fact that most users are getting anxiuos to make things work: moving the mouse or hitting the keyboard repeatedly. this will cause the RDP packet/session buffer to flow over and will discsonnect the session. There are limits to how much input you can give the client without any feedback from the server. To minimize this, try to make theese uses understand just this (its like flooding a car that will not start) and make them do just one single mouse movement or keystroke and wait until the response is seen on thescreen.

(If you problem internally as well. Lock down Speed duplex on both the server side and Switch side to the same values (100 / full)

cd..

This discussion is closed to new replies.