Secure Global Desktop 4.40 Administration Guide > Users and Authentication > Using Windows Terminal Services, Users Are Prompted for User Names and Passwords Too Often

Using Windows Terminal Services, Users Are Prompted for User Names and Passwords Too Often

The user might have typed the wrong user name 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 must press Shift when clicking the link to start (not resume) the application. This displays the authentication dialog again, and the user can correct their user name and password.

SGD sends user name and password information to Windows Terminal Services to authenticate the user. If the authentication fails, Windows prompts the user again. No information is returned to SGD indicating whether authentication succeeds or fails, and the details remain in the SGD password cache whether correct or incorrect.

Is the Windows Terminal Server Configured to Always Prompt?

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

To fix, see Configuring Windows Terminal Services for use with SGD.

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