# timeout at login attempting cifs.mount

**URL:** <https://forums.suse.com/t/timeout-at-login-attempting-cifs-mount/24741>\
**Category:** SLED Configure-Administer\
**Created:** [November 11, 2013, 7:32pm UTC](https://forums.suse.com/t/timeout-at-login-attempting-cifs-mount/24741 "2013-11-11T19:32:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![hipsterical](https://avatars.discourse-cdn.com/v4/letter/h/fbc32d/32.png) [@hipsterical](https://forums.suse.com/u/hipsterical)\
**Post date:** [November 11, 2013, 7:32pm UTC](https://forums.suse.com/t/timeout-at-login-attempting-cifs-mount/24741/1 "2013-11-11T19:32:45Z")

</div>

doing a console login with my default user (not with root) , bash hangs for 15 long seconds, then returns with the message :

login:  
pam\_mount password:

mount error(113). no route to host  
refer to the mount.cifs(8) manual page (e.g.man mount cifs)

basically when i log in , the system attempts to mount a windows share which is always down , hence the long timeout and waste of time, and the final “no route to host”.

now, i am clueless about why bash (or login?)attempts to mount a resource listed with noauto in /etc/fstab : erasing the line from fstab won’t cure this error either.  
im pretty positive about the fact that i didn’t make this setup _on purpose…_ so i don’t know how to reverse this situation. and this is very, very annoying

this problem is present just with one user so i assume that the culprit config file must be in my home directory, checked ~/.bashrc and ~/.profile but can’t find hints about what’s going on and why.

SOLUTION… i just found out that /etc/security/pam\_mount.conf is the culprit, only i’d like to discover how that directive made it into the file. i never edited that myself. at least not directly.

---

<div class="post-metadata">

**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\
**Post date:** [November 11, 2013, 8:19pm UTC](https://forums.suse.com/t/timeout-at-login-attempting-cifs-mount/24741/2 "2013-11-11T20:19:41Z")

</div>

Hi hipsterical,

> SOLUTION… i just found out that /etc/security/pam\_mount.conf is the culprit, only i’d like to discover how that directive made it into the file. i never edited that myself. at least not directly.

one thing to look at is the file modification date and check who was on the machine at that time - or to look at the zypper history (/var/log/zypp/history) in case some installer added that line.

Regards,  
Jens

---

<div class="post-metadata">

**Author:** ![mikewillis](https://avatars.discourse-cdn.com/v4/letter/m/b2d939/32.png) [@mikewillis](https://forums.suse.com/u/mikewillis)\
**Post date:** [November 12, 2013, 7:13pm UTC](https://forums.suse.com/t/timeout-at-login-attempting-cifs-mount/24741/3 "2013-11-12T19:13:50Z")

</div>

What version of SLED is this? My SLED 11 SP3 install doesn’t have a /etc/security/pam\_mount.conf It does have /etc/security/pam\_mount.conf.xml though. The change log of the pam\_mount rpm says:

[CODE]\* Mon Oct 08 2007 [mc@suse.de](mailto:mc@suse.de)

- update to version 0.29
  - pam\_mount switched to an XML configuration[/CODE]

`:~> rpm -qf /etc/security/pam_mount.conf.xml
pam_mount-0.47-13.16.1`

Worth running ‘rpm -qf’ on /etc/security/pam\_mount.conf to see which, if any, package it belongs to. I suspect the answer will be pam\_mount though.