Systems:

3 R5D1 systems and 1 R5E50 system using same auto.master, auto.samba.mnt, and .smbpassword files.

R5D1 systems use CIFS 1.43, where as R5E50 uses CIFS 1.45.

All systems are connecting to windows shares on two different windows servers. Windows servers are configured to reject LanMan authentication.

auto.samba.mnt contents (anonymized server names):

media -fstype=cifs,credentials=/home/mythtv/.smbpassword ://fully.qualified.domain.name/media
listings -fstype=cifs,credentials=/home/mythtv/.smbpassword ://fully.qualified.domain.name/eventlist
backup -fstype=cifs,credentials=/home/mythtv/.smbpassword ://fully.qualified.domain.name/media/backup

Behavior:

R5D1 machines have worked for months using this configuration--and continue to at this moment.

R5E50 machine: When I start the autofs service, the mounted directories appear in the autofs root, but if I try to cd or ls to the mounted dirs, I get:

ls: /myth/windows/listings: No such file or directory

System log:

Feb 1 09:04:20 AV-mythtv1 automount[7414]: failed to mount /myth/windows/listings
Feb 1 09:04:28 AV-mythtv1 kernel: CIFS VFS: Send error in SessSetup = -13
Feb 1 09:04:28 AV-mythtv1 kernel: CIFS VFS: cifs_mount failed w/return code = -13
Feb 1 09:04:28 AV-mythtv1 automount[7435]: >> mount error 13 = Permission denied
Feb 1 09:04:28 AV-mythtv1 automount[7435]: >> Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

A plain "mount -t cifs..." attempt from the command line yields the same error 13.

Since it seems to be connecting but not authenticating, I have guessed that it has something to do with settings in /proc/fs/cifs, particularly /proc/fs/cifs/SecurityFlags. That file contains "0x7" and nothing more, but according to /usr/src/linux/fs/cifs/README, the default setting should be "0x07007". Could that be a problem? How can I change it, considering it's set to read-only?

The README also says you can override the default security setting above using the "sec=" command line option for mount.cifs. I tried several different settings to no effect, so maybe the security settings aren't causing the problem?


Does anyone have any suggestions on what I can check/do next?

Yababom

I use a similar setup with autofs and windows server with R5E50. This is what my auto.samba.mnt looks like.




I don't have that set, I take it that CIFS is more secure than SMB connection.

My understanding is that it supports newer authentication protocols, such as NTLMv2. I'm not quite clear on the details, but I do remember that when I set the whole thing up originally, I had trouble with smbfs, but not with CIFS.

FWIW, I retried the connection using smbfs and got the same result as with CIFS:

20311: session setup failed: ERRDOS - ERRnoaccess (Access denied.)
SMB connection failed

I'm running 2000 server if that helps.

The Windows version that I'm using is Win2003 server, but that should be irrelevant AFAIK.

What I'm looking for is help understnding why the Windows box shares with my R5D1 boxes but not the R5E50 box.

check you password file and remove any spaces you have before / after the = sign.

For example change:

to:


I copied and pasted my password file (which had spaces) when I switched from smbfs to cifs and after many hours of pulling my hair out trying to figure out why cifs didn't like my password file I found that removing the spaces did the trick.

Hope this helps!

Martian

_________________
ABIT NF-M2 nView | Athlon 64 X2 3800+ | 2GB DDR2 800 | HDHomerun | GeForce 6150 (onboard) | WD 640 GB SATA HD | DVD-RW (sata) | StreamZap IR receiver with Logitech Harmony remote

Vizio 37" LCD HDTV (1080p)

I checked that as well--no spaces. The .smbpassword file was copied from a working R5D1 box. I thought that it might have been a permissions issue, so I relaxed the permissions on the .smbpassword file with "chmod 777" and ran "chown mythtv:mythtv ./.smbpassword" to make sure that the file was accessible--No change.