What about your defualtrouter and DNS setup, is that all correct? I assume that you can open a browser and get to the web ok (logged in as root, of course)?
Also one lat thing to try ... Create a user that's in your authentication system but put the home directory local on the workstation and see if that works? I'm wondering if there is some issue with write permissions in the authentication process.
-brian
Brian D. McGrew { brian@xxxxxxxxxxxxxxxxxxx || pacemakertaker@xxxxxxxxx }
--
> YOU! Off my planet!
On Aug 26, 2004, at 10:46 AM, Oliver Aaltonen wrote:
Using RHEL3's defaults.
[guest@ibmlnx21 guest]$ cat .bashrc # .bashrc
# User specific aliases and functions
# Source global definitions if [ -f /etc/bashrc ]; then . /etc/bashrc fi [guest@ibmlnx21 guest]$ cat .bash_profile # .bash_profile
# Get the aliases and functions if [ -f ~/.bashrc ]; then . ~/.bashrc fi
# User specific environment and startup programs
PATH=$PATH:$HOME/bin
export PATH
unset USERNAME
[guest@ibmlnx21 guest]$ echo $PATH
/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/ guest/bin
Oliver
On Thu, 26 Aug 2004 10:34:57 -0700, Brian D. McGrew <brian@xxxxxxxxxxxxxxxxxxx> wrote:Show us your .bash_profile and .bashrc files. Are all the users using
default system files or are any of these customized? Also, is
/usr/X11R6/bin in your path and /usr/X11R6/lib in your LD_LIBRARY_PATH?
-brian
Brian D. McGrew { brian@xxxxxxxxxxxxxxxxxxx || pacemakertaker@xxxxxxxxx } --YOU! Off my planet!
On Aug 26, 2004, at 10:32 AM, Oliver Aaltonen wrote:
Yes, I should have mentioned that as well. KDE sits at the same blank
screen with cursor after successfully authenticating the user via GDM.
As I mentioned previously, the "failsafe" session works fine.
Oliver
On Thu, 26 Aug 2004 10:24:40 -0700, Brian D. McGrew <brian@xxxxxxxxxxxxxxxxxxx> wrote:Those two lines look good. The only reason for the automounter would
be a matter of simplicity not functionality.
Have you tried logging in with KDE or any other window manager besides
gnome?
-brian
Brian D. McGrew { brian@xxxxxxxxxxxxxxxxxxx || pacemakertaker@xxxxxxxxx } --YOU! Off my planet!
On Aug 26, 2004, at 10:19 AM, Oliver Aaltonen wrote:
Relevant line from server's /etc/exports: /home 128.119.158.0/24(rw,sync)
Relevant line from client's /etc/fstab:
128.119.163.32:/home /home nfs rw,hard,intr
0 0
I did not consider using the automounter, since I assumed a simple mount via fstab would do the trick. I will look into this.
Oliver
On Thu, 26 Aug 2004 10:08:59 -0700, Brian D. McGrew <brian@xxxxxxxxxxxxxxxxxxx> wrote:Ok ... so if it occurs with a brand new user with nothing special in
the login, (unlike my login environment which is going 14 years old
now) then lets have a look at your /etc/fstab on the client and the
/etc/exports file from the server.
Also, if I may ask, why aren't you using the automounter (amd) instead of hard mounting the in the fstab?
-brian
Brian D. McGrew { brian@xxxxxxxxxxxxxxxxxxx || pacemakertaker@xxxxxxxxx } --YOU! Off my planet!
On Aug 26, 2004, at 10:00 AM, Oliver Aaltonen wrote:
Brian,
I should mention this happens with all of the users. I've even created some "fresh" accounts, using RHEL3's defaults, and the same problems occur.
Here are the permissions under one of the test accounts:
drwx------ 5 guest guest 4096 Aug 26 16:20 .
drwxr-xr-x 5 root root 4096 Aug 25 14:13 ..
-rw------- 1 guest guest 60 Aug 26 14:32
.bash_history
-rw-r--r-- 1 guest guest 24 Sep 18 2003
.bash_logout
-rw-r--r-- 1 guest guest 191 Sep 18 2003
.bash_profile
-rw-r--r-- 1 guest guest 124 Sep 18 2003 .bashrc
drwx------ 3 guest guest 4096 Aug 25 18:00 .gconfd
drwxr-xr-x 2 guest guest 4096 Aug 25 18:00 .gnome2
-rw-r--r-- 1 guest guest 120 Aug 20 2003 .gtkrc
-rw-rw-r-- 1 guest guest 11 Aug 26 14:31
guest_test.txt
drwxr-xr-x 3 guest guest 4096 Aug 24 14:01 .kde
-rw------- 1 guest guest 607 Aug 26 14:31 .viminfo
-rw------- 1 guest guest 0 Aug 26 16:20 .Xauthority
-rw------- 1 guest guest 0 Aug 26 16:20
.xsession-errors
Oliver
On Thu, 26 Aug 2004 09:50:41 -0700, Brian D. McGrew <brian@xxxxxxxxxxxxxxxxxxx> wrote:I would have a look in the users home directory and make sure that
you
have correct permissions on all the dot files (.gnome, .gtkrc,
etc)
and
that the correct ownership is set. I saw this problem once on
Solaris
with Sun's gnome recently.
-brian
Brian D. McGrew { brian@xxxxxxxxxxxxxxxxxxx || pacemakertaker@xxxxxxxxx } --YOU! Off my planet!
On Aug 26, 2004, at 9:48 AM, Oliver Aaltonen wrote:
I am experiencing a problem logging onto the GNOME desktop with the following setup:
Server (RHEL3 AS) is exporting /home via NFS and running an LDAP
server for authentication. Client (RHEL3 WS) is mounting /home
via
an
entry in /etc/fstab.
The mount works fine, and client is set up for LDAP authentication correctly. I can log in through the console or SSH into the client machine and access the user's home directory and work perfectly normally.
The only problem I have is when I try to log onto the client
machine
using GDM to run X locally. If I log in as one of the users on
the
server, with their home directory in the mounted share, the user
is
authenticated and the screen turns blank with a cursor and sits
there,
not bringing up a GNOME desktop. I can log in through GDM into a
"failsafe" session, but not GNOME. If I log in as root on the
client
machine, everything works fine, and the GNOME desktop comes up
correctly.
There are no obvious errors in the logs that I can find.
Any thoughts? Thanks in advance,
Oliver
-- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
-- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
