# Fail to login via windowing system if user is on NFS file system **URL:** \ **Category:** Rocky Linux Help & Support\ **Created:** [December 5, 2024, 1:56pm UTC](https://forums.rockylinux.org/t/fail-to-login-via-windowing-system-if-user-is-on-nfs-file-system/16750 "2024-12-05T13:56:27Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![hmg](https://avatars.discourse-cdn.com/v4/letter/h/9fc29f/32.png) [@hmg](https://forums.rockylinux.org/u/hmg)\ **Post date:** [December 5, 2024, 1:56pm UTC](https://forums.rockylinux.org/t/fail-to-login-via-windowing-system-if-user-is-on-nfs-file-system/16750/1 "2024-12-05T13:56:27Z")
BS"D I have installed Rocky 9.5 on a workstation which is an NFS client to a 9.3 nfs server. I did execute setsebool -P use\_nfs\_home\_dirs 1. The client runs IPA for user credentials. When I try to log in as a user whose home directory is on the server, an error screen appears (after acceptance of the password), and you have to press return and log out. But using ssh into the client from another machine works fine, and I can modify files as the user. I disabled IPA, and created a local entry in the passwd file, but to no avail. So users with local home directories can log in on the console into Gnome, but not users with NFS home directories (unless you just use ssh from another machine). Any ideas? Thanks ---
**Author:** ![hs303](https://avatars.discourse-cdn.com/v4/letter/h/e47774/32.png) [@hs303](https://forums.rockylinux.org/u/hs303)\ **Post date:** [December 6, 2024, 6:52am UTC](https://forums.rockylinux.org/t/fail-to-login-via-windowing-system-if-user-is-on-nfs-file-system/16750/2 "2024-12-06T06:52:29Z")
So when you ssh into the machine the home directories get mounted just fine? To rule out selinux completely, set it to permissive mode `setenforce 0` and try to log in. If it works, you need to examine selinux logs in `/var/log/audit` or with `aureport -a`. Don’t forget to set the enforcing mode back. You can also login to the console and observe the logs as they are generated with `journalctl -f` and simulnatously try to login with your nfs user and see if there is anything interesting in the logs. ---
**Author:** ![hmg](https://avatars.discourse-cdn.com/v4/letter/h/9fc29f/32.png) [@hmg](https://forums.rockylinux.org/u/hmg)\ **Post date:** [December 8, 2024, 12:13pm UTC](https://forums.rockylinux.org/t/fail-to-login-via-windowing-system-if-user-is-on-nfs-file-system/16750/3 "2024-12-08T12:13:01Z")
BS"D Thanks for the suggestions. Yes, the nfs mount is fine, and using ssh for the nfs user is fine. Turning off SELINUX did not help. Looking at the journal helped solve the problem: as the users were logging in, in their .cshrc file, we had "source"d a GROMACS setup file, that was built using a non-standard gcc version, so the library path had this custom gcc’s paths added, which several GNOME programs found first, and crashed. Thanks for the suggestion… ---
**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\ **Post date:** [February 6, 2025, 12:13pm UTC](https://forums.rockylinux.org/t/fail-to-login-via-windowing-system-if-user-is-on-nfs-file-system/16750/4 "2025-02-06T12:13:21Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.