F13 - NIS GUI login problem

[deadcella]

Hi all,

I have a problem concerning about NIS.
I have set-up a NIS client, but I am not able to login as NIS-user by using GNOME or KDE login GUI.
However, I was able to login as NIS-user by using a terminal that's open from a local account or root. Also the NFS seems working as well.

This problem only occur on my new FC13 pc, and I don't have this problem on my FC10 pc. Both of my FC13 and FC10 PC have the same NFS and NIS setting.

Does anyone has an idea about how to fix this?
Any help would be appreciate! Thanks in advanced!

Regards,

[jpollard]

you might check the file /etc/pam.d/gdm and make sure the NIS module is included.

You can compair it (visually) with the /etc/pam.d/login file - they should be nearly
identical as far as the NIS library modules go.

[deadcella]

Thank you very much for your reply.

My /etc/pam.d/gdm, looks like the following

#%PAM-1.0
auth [success=done ignore=ignore default=bad] pam_selinux_permit.so
#auth required pam_succeed_if.so user != root quiet
auth required pam_env.so
auth substack system-auth
auth optional pam_gnome_keyring.so
account required pam_nologin.so
account include system-auth
password include system-auth
session required pam_selinux.so close
session required pam_loginuid.so
session optional pam_console.so
session required pam_selinux.so open
session optional pam_keyinit.so force revoke
session required pam_namespace.so
session optional pam_gnome_keyring.so auto_start
session include system-auth

And my /etc/pam.d/login looks like this:

#%PAM-1.0
auth [user_unknown=ignore success=ok ignore=ignore default=bad] pam_securetty.so
auth include system-auth
account required pam_nologin.so
account include system-auth
password include system-auth
# pam_selinux.so close should be the first session rule
session required pam_selinux.so close
session required pam_loginuid.so
session optional pam_console.so
# pam_selinux.so open should only be followed by sessions to be executed in the user context
session required pam_selinux.so open
session required pam_namespace.so
session optional pam_keyinit.so force revoke
session include system-auth
session optional pam_ck_connector.so

I have compared these two files with the one that I have on my FC10 pc, and they are identical. The question is why I am able to login as NIS-user from GUI login on my FC10 pc, but not on the FC13 pc?

Please let me know if you have any idea to fix the problem.
Thank you again for your time and help.

Regards,

[jpollard]

Check the /etc/nsswitch.conf configuration. Mine has:

passwd: files

But for NIS to work it must have "nis" on the line as well. The /etc/nsswitch.conf
file should have an example (commented out) that shows the other options.

You also get to select what is checked first - usually the order is "files nis" meaning
that if the user has local entries in the passwd/shadow/group files, then it will be
used instead of NIS. This is reasonable, because you don't want NIS used for
the root account. NIS can be spoofed (though you can try nisplus instead, but that
is not using the basic NIS protocol).

[deadcella]

Thank you for your quick reply.

The nis has already included in the nsswitch.conf file, but I still can't login as NIS-user using the GUI login
My /etc/nsswitch.conf looks like this:

# /etc/nsswitch.conf
#
# An example Name Service Switch config file. This file should be
# sorted with the most-used services at the beginning.
#
# The entry '[NOTFOUND=return]' means that the search for an
# entry should stop if the search in the previous entry turned
# up nothing. Note that if the search failed due to some other reason
# (like no NIS server responding) then the search continues with the
# next entry.
#
# Valid entries include:
#
# nisplus Use NIS+ (NIS version 3)
# nis Use NIS (NIS version 2), also called YP
# dns Use DNS (Domain Name Service)
# files Use the local files
# db Use the local database (.db) files
# compat Use NIS on compat mode
# hesiod Use Hesiod for user lookups
# [NOTFOUND=return] Stop searching if not found so far
#

# To use db, put the "db" in front of "files" for entries you want to be
# looked up first in the databases
#
# Example:
#passwd: db files nisplus nis
#shadow: db files nisplus nis
#group: db files nisplus nis

passwd: files nis
shadow: files nis
group: files nis

#hosts: db files nisplus nis dns
hosts: files nis dns

# Example - obey only what nisplus tells us...
#services: nisplus [NOTFOUND=return] files
#networks: nisplus [NOTFOUND=return] files
#protocols: nisplus [NOTFOUND=return] files
#rpc: nisplus [NOTFOUND=return] files
#ethers: nisplus [NOTFOUND=return] files
#netmasks: nisplus [NOTFOUND=return] files

bootparams: nisplus [NOTFOUND=return] files

ethers: files
netmasks: files
networks: files
protocols: files
rpc: files
services: files

netgroup: files nis

publickey: nisplus

automount: files nis
aliases: files nisplus

I really don't know why I am able to login as NIS-user from a local account terminal (using command line), but not from the login GUI.

I would appreciate any help you can give me to solve the problem. Thanks


Regards,

[jpollard]

You might try setting

VerboseAuth=1

in the file /etc/gdm/custom.conf under the section "[security]" and restart gdm
(the command sequence telinit 3, followed by telinit 5 is the easiest).

This may give some error log information related to the problem.

There is a decent amount of documentation on /etc/gdm/custom.conf at:
http://www.ibiblio.org/oswg/oswg-nig...ence/x135.html

There may be some other reasons gdm refuses to log in - there is mention of
refusing when home directories are group/world writeable. See the part about
"RelaxPermissions".

[deadcella]

Thank you again for your reply.

I have tried the setting VerboseAuth=1, and then restart my computer. While I tried to login as NIS-user, the login window didn't give me an error log information, it only shown "Authentication Failure".

As per you suggested, I have also tried to set RelaxPermissions to 0, 1, or 2. But I still not able to login as NIS-user from the login screen.

Beside the steps I have tried above, I have also tried the following:

Case 1

1: Login as root (or local user) from the login screen
2: Open a terminal
3: From the terminal, I have successfully login in as NIS-user

Case 2

1: Login as root (or local user) from the login screen
2: Enter to virtual terminal (Ctrl + Alt + F2)
3: From the virtual terminal, I have successfully login in as NIS-user

Case 3

1: Before go through the login screen, I entered to virtual terminal
2: From the virtual terminal, I WAS NOT able to login in as NIS-user

Case 4

1: From the login screen, I WAS NOT able to login in as NIS-user using the login window

It seems that the NIS and NFS won't function correctly before I go through the login screen.
Do you have any idea what could be wrong?

I am greatly appreciate for your help.


Regards,

[jpollard]

That cleared up some backgound - I didn't realize you couldn't login using the
virtual terminal with NIS (case 3).

Is it possible to ping the target system when no one is logged in? If not, then this
may point to the network being disabled when no one is logged in, this would
imply that network manager does not have the network up (which would
prevent NIS...). There are several other threads on this problem with network
manager (there is an option):

I was able to make it available to all users by opening the terminal, and switching to su, and running the "nm-connection-editor" command. That open the connections window as root.

With this you should be able to select "allow all users".

Now if you want you could also disable networkmanager (chkconfig NetworkManager off)
and enable network (chkconfig network on). If you do
this without a reboot you can use "service NetworkManager stop" and
"service network start" to start the networks.

This should make the network available at all times (to me, this would seem
to be the normal situation, but It is possible to get the network manager module
to work properly, though it isn't as well documented).

[deadcella]

Problem solved by selecting "allow all users" in Network Configuration.
Thank you so much for your help!

[younis]

hi i hav esame problem with fedora 12 can you help me out

[stoat]

Thread closed because it is old. There often is not much point in joining a discussion that ended two years ago. And almost nobody is going to read through all that old stuff before looking at what you want now.

Thread moved to EOL (End-of-LIfe) Versions because that is what Fedora 13 is now and since your post bumped the thread back to the first page.

I recommend that you start a new thread in the EOL Versions sub-forum for your Fedora 12 issue. Describe your problem in detail. Refer to this thread if you like, but continue on in your new thread. Help will come. I'm sure.