Secure Global Desktop Administration Guide > Users and authentication > Using Windows Terminal Services, users are prompted for usernames and passwords too often

Using Windows Terminal Services, users are prompted for usernames and passwords too often

Is the wrong username or password cached?

The user may have typed the wrong username or password for the application server or Windows domain when prompted, and checked Save This Password to save the information in the password cache.

To fix, the user should press Shift when clicking the link to start (not resume) the application. This displays the authentication dialog again, and the user can correct their username and password.

Why does this happen?

Secure Global Desktop sends username and password information to Windows Terminal Services to authenticate the user. If authentication fails, Windows prompts the user again. No information is returned to Secure Global Desktop indicating whether authentication succeeded or failed, and the details remain in the Secure Global Desktop password cache whether correct or incorrect.

Is Windows 2000/2003 configured to always prompt?

By default, a Windows 2000 Server application server always prompts for a password when users log in, whether or not Secure Global Desktop supplies the password for the application server from its password cache. By default, a Windows 2003 Server does not prompt for passwords.

To fix, see Configuring Windows Terminal Services for use with Secure Global Desktop.

Copyright © 1997-2006 Sun Microsystems, Inc. All rights reserved.