Partager via

Troubleshooting Remote Desktop for Administration

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Troubleshooting

What problem are you having?

  • Client fails to connect with "This initial program cannot be started" message.

  • Cannot disconnect active RAS connections with Terminal Services.

  • The connection does not automatically log on to the server. I am prompted for my user name and password on connection.

  • The Remote Desktop connection is very slow.

  • The screen saver on my Remote Desktop is blank.

Client fails to connect with "This initial program cannot be started" message.

Cause:  The client connection might have been configured to start a program upon connection, but the program path and filename are incorrect.

Solution:   Check the properties for the client connection to ensure that the program path and filename are correct, and that the program exists in this location on the server.

Cause:  The server administrator might have specified a program to start upon connection, using Group Policy, Terminal Services Configuration, or other Terminal Services administration tools.

Solution:   Check the server configuration to ensure that the program path and filename specified for this user are correct, and that the program exists in this location on the server.

Cannot disconnect active RAS connections with Terminal Services.

Cause:  When a RAS connection is established in a Terminal Services session, the current ID of the session is added to the port. When disconnecting the RAS connection, the current session ID must match the session ID that was added to the port, or it cannot be disconnected.

Solution:  A RAS connection can only be disconnected from inside the session in which it was established.

The connection does not automatically log on to the server. I am prompted for my user name and password on connection.

Cause:  Due to encryption enhancements for Windows Server 2003 family operating systems, the Windows NT 4.0 version of Terminal Services Client does not recognize the user name and password in the automatic logon portion of the connection file.

Solution:  From the Windows NT 4.0 version of Client Connection Manager, right-click the connection and select Properties. On the General tab, select Automatic logon, and then type the user name, password, and domain.

Solution:  Upgrade the client software to Remote Desktop Connection.

Cause:  The server administrator has configured the server to deny automatic logon.

Solution:  Type your user name and password when prompted.

Cause:  User name and password information has not been added to Remote Desktop Connection.

Solution:  In Remote Desktop Connection, on the General tab, type your user name and password, and then select the Save my password checkbox.

The Remote Desktop connection is very slow.

Cause:  A low-bandwidth connection can slow Remote Desktop performance.

Solution:  On the remote computer, set the background selection to None.

Solution:   Do not run memory-intensive applications, for example, video games, over Remote Desktop.

The screen saver on my Remote Desktop is blank.

Cause:  When a screen saver is activated on Remote Desktop, it is blank. This is true regardless of whether you have previously selected a different screen saver.

Solution:  Continue to use the blank screen saver.