Fedora 16_x64 - network samba share authentication issue

auroraflame · #1 30th November 2011, 04:16 AM

hello, i had done some search on the forum and googling but to no avail. this problem has been bugging me for a few weeks (yes, weeks!!)

File Server IP : 192.168.9.100 (samba 3.5.2)
Available share :
- Public --> no problem (no need to authenticate)
- userdoc --> need authentication (failed)

as seen above, i was unable to authenticate to the 'userdoc' share using nautilus (Gnome Shell), the file server is a QNAP NAS running samba 3.5.2, and obviously it is not server side problem because i got no problem authenticate to the share using other live cd (Mint & Backtrack), and it also worked perfectly when i was using Fedora 15_x64.

some additional info :

Code:

# sestatus
SELinux status:                 disabled
# uname -r
3.1.2-1.fc16.x86_64
# rpm -qa |grep samba
samba-3.6.1-75.fc16.x86_64
samba-winbind-clients-3.6.1-75.fc16.x86_64
samba-client-3.6.1-75.fc16.x86_64
samba-common-3.6.1-75.fc16.x86_64
samba4-4.0.0-37.alpha16.fc16.x86_64
# rpm -qa |grep cifs
cifs-utils-5.0-2.fc16.x86_64
# rpm -qa |grep nautilus
gnome-disk-utility-nautilus-3.0.2-3.fc16.x86_64
totem-nautilus-3.2.1-2.fc16.x86_64
file-roller-nautilus-3.2.1-2.fc16.x86_64
nautilus-extensions-3.2.1-2.fc16.x86_64
nautilus-sendto-3.0.1-1.fc16.x86_64
evince-nautilus-3.2.1-2.fc16.x86_64
brasero-nautilus-3.2.0-1.fc16.x86_64
nautilus-3.2.1-2.fc16.x86_64
cifs-utils-5.0-2.fc16.x86_64
# cat /var/log/messages
---------------%snip%-------------------
kernel: [  745.568526] FS-Cache: Loaded
kernel: [  745.596709] FS-Cache: Netfs 'cifs' registered for caching
kernel: [  745.655068] CIFS VFS: default security mechanism requested.  The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.2
kernel: [  745.708763] CIFS VFS: cifs_mount failed w/return code = -13
---------------%snip%-------------------

sorry for my poor english, really appreciate your help. Thx before

---------- Post added at 11:16 AM ---------- Previous post was at 09:51 AM ----------

bump
any idea?

bbfuller · #2 30th November 2011, 09:18 AM

Hello auroraflame

Have you allowed samba and samba-client through your system firewall.

I don't use Gnome, but in the KDE menu structure it lives in "administration".

Should you not have it:

Code:

yum install system-config-firewall

You can also run it from the command line with:

Code:

system-config-firewall

Have you tried:

Code:

smbclient -L 192.168.9.100

From your Fedora machine? That may give some indication if it is an authentication problem.

Can you explicitly mount that share with:

Code:

mount -t cifs //192.168.0.100/userdoc /mnt -o username=<subtitute username here>

When you put in your username leave out the <> as well.

auroraflame · #3 30th November 2011, 09:59 AM

hello bbfuller,
yes , i have allowed samba and samba-client through the system firewall (see attachment)

and i am able to list share on the server, but userdoc is not listed because it is a "hidden share".
failed to mount using the above command :

Code:

# mount -t cifs //192.168.9.100/userdoc /home/auroraflame -o username=<username>
Password: 
mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

i wonder what is the username used for the mounting process? is it local system user or user on the remote server?
i try both and all of them return the same error.

thx much for your reply

auroraflame · #4 30th November 2011, 10:09 AM

here is some log message that might help :

Code:

Nov 30 16:49:43 NB-PMKRS-CXFED kernel: [  558.411103] FS-Cache: Loaded
Nov 30 16:49:43 NB-PMKRS-CXFED kernel: [  558.437686] FS-Cache: Netfs 'cifs' registered for caching
Nov 30 16:49:53 NB-PMKRS-CXFED kernel: [  568.495091] CIFS VFS: Error connecting to socket. Aborting operation
Nov 30 16:49:53 NB-PMKRS-CXFED kernel: [  568.495254] CIFS VFS: cifs_mount failed w/return code = -115
Nov 30 16:50:23 NB-PMKRS-CXFED kernel: [  597.796039] CIFS VFS: default security mechanism requested.  The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.2
Nov 30 16:50:23 NB-PMKRS-CXFED kernel: [  597.878856] CIFS VFS: cifs_mount failed w/return code = -13
Nov 30 16:50:34 NB-PMKRS-CXFED kernel: [  608.790992] CIFS VFS: cifs_mount failed w/return code = -13
Nov 30 16:51:08 NB-PMKRS-CXFED dbus[1102]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Nov 30 16:51:08 NB-PMKRS-CXFED dbus-daemon[1102]: dbus[1102]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Nov 30 16:51:08 NB-PMKRS-CXFED dbus-daemon[1102]: Launching FprintObject
Nov 30 16:51:08 NB-PMKRS-CXFED dbus[1102]: [system] Successfully activated service 'net.reactivated.Fprint'
Nov 30 16:51:08 NB-PMKRS-CXFED dbus-daemon[1102]: dbus[1102]: [system] Successfully activated service 'net.reactivated.Fprint'
Nov 30 16:51:08 NB-PMKRS-CXFED dbus-daemon[1102]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Nov 30 16:51:08 NB-PMKRS-CXFED dbus-daemon[1102]: ** Message: entering main loop
Nov 30 16:51:39 NB-PMKRS-CXFED dbus-daemon[1102]: ** Message: No devices in use, exit
Nov 30 16:51:47 NB-PMKRS-CXFED kernel: [  682.322417] CIFS VFS: cifs_mount failed w/return code = -13
Nov 30 16:51:53 NB-PMKRS-CXFED kernel: [  687.544717] CIFS VFS: cifs_mount failed w/return code = -13
Nov 30 16:52:14 NB-PMKRS-CXFED kernel: [  709.194564] CIFS VFS: cifs_mount failed w/return code = -13
Nov 30 16:52:20 NB-PMKRS-CXFED kernel: [  715.286190] CIFS VFS: cifs_mount failed w/return code = -13
Nov 30 16:52:29 NB-PMKRS-CXFED kernel: [  723.569284] CIFS VFS: cifs_mount failed w/return code = -13
Nov 30 16:52:37 NB-PMKRS-CXFED kernel: [  732.295775] CIFS VFS: cifs_mount failed w/return code = -13
Nov 30 16:52:42 NB-PMKRS-CXFED kernel: [  737.409705] CIFS VFS: cifs_mount failed w/return code = -13
Nov 30 16:52:47 NB-PMKRS-CXFED kernel: [  741.972978] CIFS VFS: cifs_mount failed w/return code = -13

bbfuller · #5 30th November 2011, 11:04 AM

Hello auroraflame

What Fedora is set up for, and what I use and know, is "user" share security where you have the same username on both the remote, server, machine; and on the local machine.

I also set up samba usernames to correspond with the Linux usernames. There is a place to do that in:

Code:

system-config-samba

I'd try that first. It looks like it is a permissions problem.

Though, it may just be that your Fedora box is preventing the mounting of your share on

Quote:

/home/auroraflame

I would think that pretty likely. After all, if it succeeds then you would loose visibility of all of your home folder.

That's why I specified:

Code:

/mnt

as the mount point because that is what it is designed for.

At the minimum you would make a:

Code:

/home//home/auroraflame/mnt

folder to mount your share in to.

However, you may still have to contend with SELinux objecting so don't do that for now.

Go for the simple "/mnt" option, if that works then we can elaborate.

Don't forget also that hidden behind Linux/Samba usernames is a numerical identity. That may not be the same on both of your devices.

I've got one system where I have to specify a numeric user id as part of the mount command before I can write to a share.

Just keep that in mind for later.

To start with keep it simple and we can expand the commands later.

auroraflame · #6 30th November 2011, 11:48 AM

Hello bbfuller,
/home/auroraflame i mention above is not a my home directory, it is a separate dir created for testing mounting command above. my username is something else and the username to authenticate to QNAP NAS machine is also different (definitely not auroraflame). sorry if my explanation is a bit ambiguous.

IMHO, from what i know 'system-config-samba' is used for "serving" Samba file sharing (as the server) not the client, while my case is authenticating to server from the client side(which is me) CMIIW.
the thing is that i was unable to authenticate to the QNAP file share from my fedora 16 machine, while i can do it previously using fedora 15 or other distro (BT and Mint)

i am considering filing a bug report coz this issue is bugging me for a few weeks already.
Again thank you very much bbfuller for your help

bbfuller · #7 30th November 2011, 12:02 PM

Hello auroraflame

You could file a bug report, but I wouldn't hold your breath waiting for an answer.

Samba does work, you have it working to your "Public" share.

Samba is therefore not the problem. It's one of configuration.

"system-config-samba" does mainly set up shares on a server, but it will also allow you to set up samba users, which could be one source of your problem.

Have you actually tried the mount command onto "/mnt"?

auroraflame · #8 30th November 2011, 01:07 PM

no, i tried the mount command onto /home/auroraflame, i will try it tomorrow coz i am unable to access the share right now.
i will keep u updated, thx

--------------------
UPDATE :
still get the same error when mounting to /mnt/mnt (i have other partition mounted on subdir of /mnt)

Code:

mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

i tried system-config-samba, i wonder which part of it can help me troubleshoot my samba issue?
thx

auroraflame · #9 1st December 2011, 03:12 AM

after more than one try through nautilus, i got this message :

Code:

Error: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Please select another viewer and try again.

i am sure there is no problem with the network becoz no prob pinging the server. so it got down to this :
"the message bus security policy blocked the reply, the reply timeout expired, "
more googling to do

hvkleist · #10 6th January 2012, 07:45 PM

I am in the middle of upgrading our SSO (single sign-on) server and have run into authentication issues with FC16 and samba 1.3.6 for x86_64. The "upgrade" is actually a clean install and a move from 32 to 64 bit OS.

What has happened:

I copied my iptables rules from the old box.
I copied the /etc/samba/* files.
I copied the /var/lib/samba/private/* files.
I copied the netlogon scripts from the previous setup

First off, I needed to add smb and nmb to startup automatically

> systemctl enable smb.service
> systemctl enable nmb.service

Here began the first problem. Smb starts up on reboot, but nmb does not. For now we start by hand.

> systemctl start nmb.service

After this, running
> smbclient -L //domainserver
it gives an access error. Cannot access home shares (z: drive) but can access other shares.

After digging for a while, I realized that selinux was set to enforcing.

edit /etc/selinux/config

# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - SELinux is fully disabled.
SELINUX=disabled

SSO and all shares now work.