Connecting to Terminal Services takes very long time

  • Thread starter Thread starter Tobias Cederlund
  • Start date Start date
T

Tobias Cederlund

I'm using TS in Admin mode on several machines . I havn´t had any problems
before but since I put on SP4 on my workstation the other day I'm having
trouble connecting to my servers from my workstation. I can connect, but it
takes like 60 seconds. Earlier the connection was made in like 2-3 seconds.

This is what happends:
I open the TS Client, point it to the server I wish to administer (doesn't
matter which one) and then I click "Connect". A TS Client window opens up
but it's all black and it's frozen, I can´t move it and if I move another
window on top of it, that window will like "smear out" in the TS Client
window. After 60 seconds (it´s always 60 seconds, not 58 or 62...) the
logon.screen is shown and everything works like normal again, not slow or
anything...There are no entrys in any eventlogs.

Any Ideas?

-Tobias
 
Hi Tobias,

Thanks for posting here.

At begining, I want to know whether the Terminal server is based on the
Windows 2000 server. If yes, do you have also

installed the Windows 2000 SP4 on the Terminal Server? If not, please
install the Windows 2000 SP4 on the Terminal Server.

I also want to know which version TS client you are using? It's suggested
using the latest one which can be downloaded at:

http://www.microsoft.com/downloads/details.aspx?FamilyID=a8255ffc-4b4a-40e7-
a706-cde7e9b57e79&DisplayLang=en

Note: The new TS client named Remote Desktop Connection. It supports the
RDP 5.2. Windows 2000 terminal server only supports

RDP 5.0. You can see the re-direct local hard disk driver in the Remote
Desktop Connection. The function is supported by RDP

5.1 or later. Windows 2000 Terminal server does not support it. Please
don't check to use the function.

If this still does not work, let's do the following test.

First, let's reboot the client and enter the Safe Mode with Networking.
Then, connect to the TS with the new Remote Desktop

Connection and see whether this works. If the problem does not happen in
this mode, I think the problem may be caused by one

or more applications are not compatible with the Windows 2000 SP4. We can
perform the following steps to isolate the culprit.

Let's do the following steps.

1. Run msconfig to load the Microsoft Configuration Utility
2. Go to the Startup table
3. Uncheck all items
4. Click OK and restart the computer
5. Let's see whether we still encounter the error message
6. If yes, please recheck all and skip all rest steps
7. If no, let's add one item in the startup table and restart the computer
to see whether that one cause the problem
8. We can isolate the culprit very soon

Note: the msconfig.exe is not available on the Windows 2000 client. You can
copy the file from the Windows XP client. It also

works on the Windows 2000 client. The msconfig.exe can be found at:
%SystemRoot%\PCHealth\HelpCtr\Binaries folder on the

Windows XP client.

Second, you can create the new account on the TS server (Workgroup
environment) or create a new account in the domain (domain

environment). Then, logon the TS with the new account. Let's see whether
the problem is solved.

Thanks for using Microsoft Newsgroup!

Sincerely,

Steven Liu [MSFT]

Microsoft Online Partner Support

MCSE 2000

Get Secure! - www.microsoft.com/security

This posting is provided "as is" with no warranties and confers no rights.
 
Hi Steven!

That was very useful information!

To begin with, the different servers are at different sp-level. It didn´t
matter if I tried to connect to a sp2 or sp4 machine. I'm not 100% sure
which version of the TS client I was using but I think it was 5.0.2195 or
someting...old...I thought the TS client-files was updated when I applied
SP4 to my workstation. Well, I went for the new RDP-klient and all problems
went away...I can even use the old TS Client without problems...Guess it
uses the same files...

Thank You!
Tobias


"Steven Liu" said:
Hi Tobias,

Thanks for posting here.

At begining, I want to know whether the Terminal server is based on the
Windows 2000 server. If yes, do you have also

installed the Windows 2000 SP4 on the Terminal Server? If not, please
install the Windows 2000 SP4 on the Terminal Server.

I also want to know which version TS client you are using? It's suggested
using the latest one which can be downloaded at:

http://www.microsoft.com/downloads/details.aspx?FamilyID=a8255ffc-4b4a-40e7-
a706-cde7e9b57e79&DisplayLang=en

Note: The new TS client named Remote Desktop Connection. It supports the
RDP 5.2. Windows 2000 terminal server only supports

RDP 5.0. You can see the re-direct local hard disk driver in the Remote
Desktop Connection. The function is supported by RDP

5.1 or later. Windows 2000 Terminal server does not support it. Please
don't check to use the function.

If this still does not work, let's do the following test.

First, let's reboot the client and enter the Safe Mode with Networking.
Then, connect to the TS with the new Remote Desktop

Connection and see whether this works. If the problem does not happen in
this mode, I think the problem may be caused by one

or more applications are not compatible with the Windows 2000 SP4. We can
perform the following steps to isolate the culprit.

Let's do the following steps.

1. Run msconfig to load the Microsoft Configuration Utility
2. Go to the Startup table
3. Uncheck all items
4. Click OK and restart the computer
5. Let's see whether we still encounter the error message
6. If yes, please recheck all and skip all rest steps
7. If no, let's add one item in the startup table and restart the computer
to see whether that one cause the problem
8. We can isolate the culprit very soon

Note: the msconfig.exe is not available on the Windows 2000 client. You can
copy the file from the Windows XP client. It also

works on the Windows 2000 client. The msconfig.exe can be found at:
%SystemRoot%\PCHealth\HelpCtr\Binaries folder on the

Windows XP client.

Second, you can create the new account on the TS server (Workgroup
environment) or create a new account in the domain (domain

environment). Then, logon the TS with the new account. Let's see whether
the problem is solved.

Thanks for using Microsoft Newsgroup!

Sincerely,

Steven Liu [MSFT]

Microsoft Online Partner Support

MCSE 2000

Get Secure! - www.microsoft.com/security

This posting is provided "as is" with no warranties and confers no rights.
Click to expand...
 
Hi Tobias,

I'm glad to hear that the problem is solved.

If you encounter any problem again, please feel free to post here. We will
continue to help you.

Thanks for using Microsoft Newsgroup!

Sincerely,

Steven Liu [MSFT]

Microsoft Online Partner Support

MCSE 2000

Get Secure! - www.microsoft.com/security

This posting is provided "as is" with no warranties and confers no rights.
 
Back
Top