Novell LINUX ENTERPRISE DESKTOP 10 SP2 - DEPLOYMENT GUIDE 08-05-2008 Deployment Manual page 834

5 If graphical login still fails, do a console login with Ctrl + Alt + F1 . Try to start
6 If the desktop could not start because of corrupt configuration files, proceed with
The following are some common reasons why network authentication for a particular
user might fail on a specific machine:
• The user might have entered the wrong password.
• The username exists in the machine's local authentication files and is also provided
by a network authentication system, causing conflicts.
• The home directory exists but is corrupt or unavailable. Perhaps it is write protected
or is on a server that is inaccessible at the moment.
• The user does not have permission to log in to that particular host in the authentica-
tion system.
• The machine has changed hostnames, for whatever reason, and the user does not
have permission to log in to that host.
• The machine cannot reach the authentication server or directory server that contains
that user's information.
• There might be problems with the X Window System authenticating this particular
user, especially if the user's home has been used with another Linux distribution
prior to installing the current one.
To locate the cause of the login failures with network authentication, proceed as follows:
1 Check whether the user remembered his password correctly before you start de-
818 Deployment Guide
an X session on another display—the first one (:0) is already in use:
startx -- :1
This should bring up a graphical screen and your desktop. If it does not, check
the log files of the X Window System (/var/log/Xorg.displaynumber
.log) or the log file for your desktop applications (.xsession-errors in
the user's home directory) for any irregularities.
Section 46.4.3, "Login Successful but GNOME Desktop Fails "
Section 46.4.4, "Login Successful but KDE Desktop Fails"
bugging the whole authentication mechanism.
(page 820) or
(page 821).