Export (0) Print
Expand All

Troubleshooting Terminal Server

Updated: January 21, 2005

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?

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

Cause:  Encryption enhancements for Windows 2000 and Windows Server 2003 family operating systems cause the Windows NT 4.0 version of the Terminal Services client not to 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, check Automatic logon and type the User name, Password, and Domain.

Installation of an .msi package fails from a remote Terminal Services session.

Cause:  You must be logged in as a member of the Administrators group to install .msi packages for Terminal Services from a remote session.

Solution:  Log on as a member of the Administrators group or use Run as to install the .msi package.

See also: Install a program using Add or Remove Programs

Installed program does not work correctly.

Cause:  The program was installed before Terminal Server was installed.

Solution:  Uninstall the program, and reinstall using either Add or Remove Programs or the change user command.

See also: Starting the installation

Cause:  The program was installed using change user /execute rather than change user /install.

Solution:  Uninstall the program, and reinstall using either Add or Remove Programs or the change user /install command.

See also: Starting the installation

Cause:  Program compatibility scripts were not run properly.

Solution:  Run the program scripts again.

See also: Program Compatibility

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 filen ame are incorrect.

Solution:   Check the properties for the client connection to ensure that the program path and file name 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 file name specified for this user are correct, and that the program exists in this location on the server.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft