[SOLVED] Issues connecting to smb NAS

sea · #1 26th April 2012, 12:36 AM

Heyas

EDIT: The NAS i try to connect to: Iomega StorCenter ix2-200

After i had refused to try further by experiments, how to connect to my iomega network storage, i browsed for a solution.
2 of those many pieces were:
http://dreambox.funfiles.cc/index.ph...&postID=146167
http://www.cyberciti.biz/tips/how-to...der-linux.html
http://www.aeronetworks.ca/howtos/sa...bug-howto.html

Both of them refer to use a mount command similar to:

Code:

# mount -t smbfs -o username=usr,password=pw //ntserver/download /mnt/ntserver

However, i run this:

Code:

for NETFS in cifs nfs smb smbfs;do
    sudo mount -t $NETFS -o rw,soft,username=usr,password=pw  //192.168.10.110/Shares /mnt/nas && break || dmesg|tail
done
ping -c 1 192.168.10.110

And get:

Code:

mount: //192.168.10.110/Share is not a valid block device
[ 1936.497282] CIFS VFS: cifs_mount failed w/return code = -115
[ 1995.374815] CIFS VFS: Error connecting to socket. Aborting operation
[ 1995.374964] CIFS VFS: cifs_mount failed w/return code = -115
[ 2155.242343] CIFS VFS: default security mechanism requested.  The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.3
[ 2155.338782] CIFS VFS: cifs_mount failed w/return code = -6
[ 2176.327538] CIFS VFS: cifs_mount failed w/return code = -6
[ 2218.861173] CIFS VFS: cifs_mount failed w/return code = -6
[ 2231.198923] CIFS VFS: cifs_mount failed w/return code = -6
[ 2340.291787] CIFS VFS: cifs_mount failed w/return code = -6
[ 2403.371196] CIFS VFS: cifs_mount failed w/return code = -6
mount: wrong fs type, bad option, bad superblock on //192.168.10.110/Share,
       missing codepage or helper program, or other error
       (for several filesystems (e.g. nfs, cifs) you might
       need a /sbin/mount.<type> helper program)
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

[ 1936.497282] CIFS VFS: cifs_mount failed w/return code = -115
[ 1995.374815] CIFS VFS: Error connecting to socket. Aborting operation
[ 1995.374964] CIFS VFS: cifs_mount failed w/return code = -115
[ 2155.242343] CIFS VFS: default security mechanism requested.  The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.3
[ 2155.338782] CIFS VFS: cifs_mount failed w/return code = -6
[ 2176.327538] CIFS VFS: cifs_mount failed w/return code = -6
[ 2218.861173] CIFS VFS: cifs_mount failed w/return code = -6
[ 2231.198923] CIFS VFS: cifs_mount failed w/return code = -6
[ 2340.291787] CIFS VFS: cifs_mount failed w/return code = -6
[ 2403.371196] CIFS VFS: cifs_mount failed w/return code = -6
mount: unknown filesystem type 'smb'
[ 1936.497282] CIFS VFS: cifs_mount failed w/return code = -115
[ 1995.374815] CIFS VFS: Error connecting to socket. Aborting operation
[ 1995.374964] CIFS VFS: cifs_mount failed w/return code = -115
[ 2155.242343] CIFS VFS: default security mechanism requested.  The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.3
[ 2155.338782] CIFS VFS: cifs_mount failed w/return code = -6
[ 2176.327538] CIFS VFS: cifs_mount failed w/return code = -6
[ 2218.861173] CIFS VFS: cifs_mount failed w/return code = -6
[ 2231.198923] CIFS VFS: cifs_mount failed w/return code = -6
[ 2340.291787] CIFS VFS: cifs_mount failed w/return code = -6
[ 2403.371196] CIFS VFS: cifs_mount failed w/return code = -6
mount: unknown filesystem type 'smbfs'
[ 1936.497282] CIFS VFS: cifs_mount failed w/return code = -115
[ 1995.374815] CIFS VFS: Error connecting to socket. Aborting operation
[ 1995.374964] CIFS VFS: cifs_mount failed w/return code = -115
[ 2155.242343] CIFS VFS: default security mechanism requested.  The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.3
[ 2155.338782] CIFS VFS: cifs_mount failed w/return code = -6
[ 2176.327538] CIFS VFS: cifs_mount failed w/return code = -6
[ 2218.861173] CIFS VFS: cifs_mount failed w/return code = -6
[ 2231.198923] CIFS VFS: cifs_mount failed w/return code = -6
[ 2340.291787] CIFS VFS: cifs_mount failed w/return code = -6
[ 2403.371196] CIFS VFS: cifs_mount failed w/return code = -6
PING 192.168.10.110 (192.168.10.110) 56(84) bytes of data.
64 bytes from 192.168.10.110: icmp_req=1 ttl=64 time=1.18 ms

--- 192.168.10.110 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.182/1.182/1.182/0.000 ms

After the installation of:

Code:

sudo yum install cifs-utils, samba4, fuse-smb, cntlm

The errors look a bit better, but still not very promising for a new bee in networks...

Code:

mount: unknown filesystem type 'smbfs'
[ 2176.327538] CIFS VFS: cifs_mount failed w/return code = -6
[ 2218.861173] CIFS VFS: cifs_mount failed w/return code = -6
[ 2231.198923] CIFS VFS: cifs_mount failed w/return code = -6
[ 2340.291787] CIFS VFS: cifs_mount failed w/return code = -6
[ 2403.371196] CIFS VFS: cifs_mount failed w/return code = -6
[ 2526.971623] CIFS VFS: cifs_mount failed w/return code = -6
[ 2533.246870] CIFS VFS: cifs_mount failed w/return code = -6
[ 2545.667813] CIFS VFS: cifs_mount failed w/return code = -6
[ 2620.529803] CIFS VFS: cifs_mount failed w/return code = -6
[ 2620.590951] CIFS VFS: cifs_mount failed w/return code = -6

Any help or hint is very welcome.
Thanks in advance.

***DBelton*** · #2 26th April 2012, 03:44 AM

try something like this:

Code:

mount -t cifs //192.168.10.110/Shares /mnt/nas -o rw,soft,user=usr,password=pw,domain=domainorworkgroupname

You need to specify the workgroup (or domain) name that your NAS is in. You can specify it either with the domain= parameter, or you can specify it as a part of the user parameter, for example, user=workgroup/user

flyingfsck · #3 26th April 2012, 04:04 AM

BTW, I have found that the best way to debug Samba connections is with smbclient. It provides better error messages.

sea · #4 26th April 2012, 09:07 AM

Weird, i had set the name of the NAS to "Ocean", so i assumed adding "domain=Ocean" should work..

Code:

sudo mount //192.168.10.110/Shares /mnt/nas -t cifs -o rw,soft,username=usr,password=pw,domain=Ocean

Results in:

Quote:

mount.cifs: bad UNC (192.168.10.110/Shares)
[ 542.352085] wlan0: authenticated
[ 542.352324] wlan0: associate with 00:14:d1:22:7e:52 (try 1)
[ 542.354819] wlan0: RX ReassocResp from 00:14:d1:22:7e:52 (capab=0x411 status=0 aid=1)
[ 542.354826] wlan0: associated
[ 542.354832] wlan0: moving STA 00:14:d1:22:7e:52 to state 1
[ 542.354836] wlan0: moving STA 00:14:d1:22:7e:52 to state 2
[ 542.367938] wlan0: moving STA 00:14:d1:22:7e:52 to state 3
[ 549.621264] CIFS VFS: Error connecting to socket. Aborting operation
[ 549.621397] CIFS VFS: cifs_mount failed w/return code = -113
[ 553.163650] wlan0: no IPv6 routers present

So i had a look at smbclient.. after the first few tries, i thought I add this line to /etc/hosts:

Code:

192.168.10.110  Ocean Ocean localhost4 localhost4.localdomain4

But on:

Code:

smbclient -I 192.168.10.110 -D /mnt/nas -W Ocean -N

Code:

Usage: smbclient [-?EgBVNkPeC] [-?|--help] [--usage]
        [-R|--name-resolve NAME-RESOLVE-ORDER] [-M|--message HOST]
        [-I|--ip-address IP] [-E|--stderr] [-L|--list HOST]
        [-m|--max-protocol LEVEL] [-T|--tar <c|x>IXFqgbNan] [-D|--directory DIR]
        [-c|--command STRING] [-b|--send-buffer BYTES] [-p|--port PORT]
        [-g|--grepable] [-B|--browse] [-d|--debuglevel DEBUGLEVEL]
        [-s|--configfile CONFIGFILE] [-l|--log-basename LOGFILEBASE]
        [-V|--version] [--option=name=value] [-O|--socket-options SOCKETOPTIONS]
        [-n|--netbiosname NETBIOSNAME] [-W|--workgroup WORKGROUP]
        [-i|--scope SCOPE] [-U|--user USERNAME] [-N|--no-pass] [-k|--kerberos]
        [-A|--authentication-file FILE] [-S|--signing on|off|required]
        [-P|--machine-pass] [-e|--encrypt] [-C|--use-ccache] service <password>

In another step, i tried to connect to my NAS on boot time with and edited /etc/fstab:

Code:

//192.168.10.110/Shares /mnt/nas cifs username=usr,password=pw,uid=1000,gid=1000 0 0

Quote:

Retrying with upper case share name
mount error(6): No such device or address
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

flyingfsck · #5 26th April 2012, 09:16 AM

Howdy,

Always use lowercase for names. That includes hostnames and domain names. If you use lower case, then the resulting name will be case insensitive, so both http://google.com and http://GoOgLe.CoM will work.

if you define a name with mixed case, then your mileage will vary depending on the OS you are using.

***DBelton*** · #6 26th April 2012, 02:08 PM

also, it appears you may be mixing up NetBIOS names and Domain/Workgroup names. They are different names.

For example, in Windows, it allows you to give your computer a name (That would be your netbios name) and when you set up your network, it asks you for another name, a workgroup name (if it's not part of a domain). The workgroup/domain name is not unique to just that one computer, all computers wishing to share information over the network must have the same workgroup/domain name.

NetBios name - Should be a unique name for a computer on the network

Workgroup/Domain name - All computers on the network wishing to share information should have the same Workgroup/Domain name specified.

sea · #7 26th April 2012, 08:50 PM

Ok, so i have changed the domain of the NAS device to "ocean", and its name to "ocean" too.
The IP is fixed to 192.168.10.110.

Still, i cant connect, as the error message remain the same:
Command:

Code:

sudo mount -t cifs //192.168.10.110 /mnt/nas -o rw,soft,credentials=/home/simon/.NASconfig

Configfile:

Code:

            username=usr     # replace usr with actual user name of the NAS
            password=pw      # replace pw with actual password of user of the NAS
            domain=ocean

Error Message:

Code:

Retrying with upper case share name
mount error(6): No such device or address
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

Soooo, since i still recieve the same error, but the commands look like on the articles,
i've started to write a script for my personal dummy use

It works great, as i get the same error as already mentioned above

However, since the commands look like those i had read, and been told so here, i'd like to share the script.

I really would like to know if it works for your NAS?
This is also to know, that if it works for you, it should work for me.

Code:

#!/bin/bash
# |
# |     Connect to NAS
# |
# |     Tries to ease the usage of Network Storage devices
# |     As one ususaly has only one NAS, the script should not overwrite other configuration.
# |     Allthough the script has been written with best will and intention, use it at your own risk.
# |     I herby deny any responsibility for any cause of harm to your computer, network or anything else linked,
# |         if you execute the script you accept this.
# |
# |     April 2012, by Simon A. Erat (sea)
# |
# | Variables
    usrN=                                   # Empty Username
    usrP=                                   # Empty Password
    dom=                                    # Empty Domain
    ip=                                     # Empty IP Adress
    mp=                                     # Empty Mount Point
    secstr=                                 # Empty security string
    NASconfig="$HOME/.NASconfig"            # File where the configuration info is stored
    targetscript="$HOME/connect-nas.sh"     # Script that gets written
    fstype="cifs nfs smb smbfs"             # Select one of the remote filesystems... smb and smbfs dont work for me
                                            # but they are shown/used in articles i had read about this toppic
    
# |
# | Subs
    GetLoginVars() {
        read -p "Enter username of the NAS: " usrN
        read -p "Enter password of the NAS: " usrP
        read -p "Enter the ip address of the NAS: " ip
        read -p "Enter the mount point: (/mnt/nas) " mp
        read -p "Enter the domain ($(hostname)), if required: " dom
        test "" = "$mp" && mp=/mnt/nas
        test ! -d $mp && sudo mkdir -p $mp
        export usrN usrP ip mp dom
    }
    createNASfile() {
		cat > $NASconfig << EOF
            username=$usrN
            password=$usrP
EOF
		
        if [ ! "" = "$dom" ]
        then    echo "            domain=$dom" >> $NASconfig
        fi
    }
    ReturnSecurityString() { # Returns either the string with either the command to load the config file, or the credentials themself (INSECURE!!)
        case $1 in
        	"file")     string="credentials=$NASconfig"     	;;
        	*)          string="usernamem=$usrN,password=$usrP"	;;
        esac
        echo $string
    }
# |
# | Action
    clear
    echo "Connecting to NAS (April 2012, by sea)"
    echo "--------------------------------------"
    GetLoginVars
    echo
    
    echo "Do you want to have the credentials (name, pw, domain) saved in a file, rather than plaintext in script?"
    select answer in "file" "plaintext"; do test "file" = $answer && createNASfile && break || break; done
    secstr=$(ReturnSecurityString $answer)
    echo
    
    echo "Please select the filesystem type of your NAS:"
    select ntype in $fstype unkown;do break;done
    echo
    
    echo "Generating command"
    if [ "unkown" = "$ntype" ]
    then    cmds="for netfs in $fstype; do sudo mount -t $ntype //$ip $mp -o rw,soft,$secstr; done"
    else    if [ "" = "$dom" ]
            then    domain=""
            else    domain=",domain=$dom"
            fi
            cmds="sudo mount -t $ntype //$ip $mp -o rw,soft,$secstr$domain"
    fi
    echo "$cmds" > $targetscript
    echo
    
    echo "The command looks like this: (sh $targetscript)"
    echo "$(cat $targetscript)"
    echo 
    if [ "file" = "$answer" ]
    then    echo "The NAS configuration file looks like:"
            cat $NASconfig
            echo
    fi
    
    read -p "Execute it now? (y/n)" -n1 exe 
    test y = $exe &&  printf "\nProcessing...\n" && sudo sh $targetscript
# |
# | Remove temporary used variables
    usrN=       # Empty Username
    usrP=       # Empty Password
    dom=        # Empty Domain
    ip=         # Empty IP Adress
    mp=         # Empty Mount Point
    secstr=     # Empty security string
    export usrN usrP ip mp dom

---------- Post added at 07:50 PM ---------- Previous post was at 03:09 PM ----------

Finaly found something that looked about the best option on TLDP...
I could get a list of directories from the NAS using:

Code:

smbclient -L ocean

However, if i want to login, using either the NAS' name, or its IP like:

Code:

smbclient "////ocean"
Enter simon's password: 
Connection to  failed (Error NT_STATUS_BAD_NETWORK_NAME)

http://tldp.org/HOWTO/SMB-HOWTO-8.html
But:

Quote:

One important thing to note: You must have smbfs support compiled into your kernel to use these utilities!

This brings up a new issue, which packages to install for smbfs support?
Alreay installed:

Code:

sudo yum history
[sudo] password for simon: 
ID     | Command line             | Date and time    | Action(s)      | Altered
-------------------------------------------------------------------------------
   179 | install smbios-utils-bin | 2012-04-26 21:30 | Install        |    2   
   178 | upgrade -y               | 2012-04-26 01:41 | E, I, U        |   33 EE
   177 | install samba4           | 2012-04-26 01:27 | Install        |    2   
   176 | install cifs-utils       | 2012-04-26 01:26 | Install        |    2   
   175 | install cntlm            | 2012-04-26 01:25 | Install        |    1   
   174 | install fuse-smb         | 2012-04-26 00:51 | Install        |    3

My question now is, what do i have to install now?
As i dont have the tools (smbmount|smbumount) available which are mentioned on TLDP.

Code:

yum search smb ; yum provides smbfs
========================================================================================== N/S Matched: smb ===========================================================================================
fuse-smb.x86_64 : FUSE-Filesystem to fast and easy access remote resources via SMB
libsmbclient.i686 : The SMB client library
libsmbclient.x86_64 : The SMB client library
libsmbclient-devel.i686 : Developer tools for the SMB client library
libsmbclient-devel.x86_64 : Developer tools for the SMB client library
libsmbios.i686 : Libsmbios C/C++ shared libraries
libsmbios.x86_64 : Libsmbios C/C++ shared libraries
nagios-plugins-disk_smb.x86_64 : Nagios Plugin - check_disk_smb
python-smbc.x86_64 : Python bindings for libsmbclient API from Samba
python-smbc-doc.x86_64 : Documentation for python-smbc
python-smbios.x86_64 : Python interface to Libsmbios C library
python-smbpasswd.x86_64 : Python SMB Password Hash Generator Module
python3-smbc.x86_64 : Python3 bindings for libsmbclient API from Samba
python3-smbpasswd.x86_64 : Python SMB Password Hst Generator Module for Python 3
smb4k.i686 : The SMB/CIFS Share Browser for KDE
smb4k.x86_64 : The SMB/CIFS Share Browser for KDE
smbios-utils.x86_64 : Meta-package that pulls in all smbios binaries and python scripts
smbios-utils-bin.x86_64 : Binary utilities that use libsmbios
smbios-utils-python.x86_64 : Python executables that use libsmbios
gnome-vfs2-smb.x86_64 : Windows fileshare support for gnome-vfs
gvfs-smb.x86_64 : Windows fileshare support for gvfs
i2c-tools-eepromer.x86_64 : Programs for reading / writing i2c / smbus eeproms
libsmbios-devel.i686 : Development headers and archives
libsmbios-devel.x86_64 : Development headers and archives
nmbscan.noarch : NMB/SMB network scanner
perl-Crypt-SmbHash.noarch : Pure-perl Lanman and NT MD4 hash functions
php-pear-File-SMBPasswd.noarch : Class for managing SAMBA style password files
samba-swat.x86_64 : The Samba SMB server Web configuration program
smbldap-tools.noarch : User and group administration tools for Samba/OpenLDAP

  Name and summary matches only, use "search all" for everything.
No Matches found

EDIT: The NAS i try to connect to: Iomega StorCenter ix2-200

***glennzo*** · #8 26th April 2012, 09:59 PM

Just a though after reading briefly through this post. Have you given any thought to firewall or selinux getting in the way?

sea · #9 26th April 2012, 10:27 PM

Good point, on one hand.
On the other hand, my Android can access it without problems, so does Windblows.

But either way, Android can access it without issues using: smb://192.168.10.110, where i just get an error message with fedora

EDIT:
Just started system-config-firewall, and set everything samba and nfs4 as trusted (checkbox on).

Then i tried again: -- no changes...

Code:

smbclient -L ocean -N ; smbclient "////ocean" -N
Anonymous login successful
Domain=[OCEAN] OS=[Unix] Server=[Samba 3.5.6]

	Sharename       Type      Comment
	---------       ----      -------
	Backups         Disk      
	Linux           Disk      
	Movies          Disk      
	Music           Disk      
	Pictures        Disk      
	TimeMachine     Disk      
	pub             Disk      
	priv            Disk      
	IPC$            IPC       IPC Service (Iomega StorCenter ix2-200)
Anonymous login successful
Domain=[OCEAN] OS=[Unix] Server=[Samba 3.5.6]

	Server               Comment
	---------            -------
	OCEAN                Iomega StorCenter ix2-200

	Workgroup            Master
	---------            -------
	OCEAN                OCEAN
Connection to  failed (Error NT_STATUS_BAD_NETWORK_NAME)

Where and what would i have to check for firewall and selinux?
I start thinking that services might be the cause for this not-ending-failure-experience...

***glennzo*** · #10 26th April 2012, 11:10 PM

Turn off the firewall and seliniux. See if you can connect. SELinux can be temporarily disabled with the command

PHP Code:


			
setenforce=0

To re-enable use

PHP Code:


			
setenforce=1

The firewall can be handled with the GUI.

With SELinux enabled can you show the output of the following?

PHP Code:


			
getsebool -a | grep samba

Specifically any line the looks like this:

PHP Code:


			
samba_share_fusefs --> on

sea · #11 26th April 2012, 11:27 PM

Tried the selinux switch... didnt change anything on:

Code:

smbclient -L ocean -N ; smbclient "////ocean"

Not that used to iptables output, so i'll post it here:

Code:

sudo iptables -L
[sudo] password for simon: 
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
ACCEPT     all  --  anywhere             anywhere             state RELATED,ESTABLISHED
ACCEPT     icmp --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     tcp  --  anywhere             anywhere             state NEW tcp dpt:nfs
ACCEPT     tcp  --  anywhere             anywhere             state NEW tcp dpt:pop3s
ACCEPT     udp  --  anywhere             anywhere             state NEW udp dpt:netbios-ns
ACCEPT     udp  --  anywhere             anywhere             state NEW udp dpt:netbios-dgm
ACCEPT     tcp  --  anywhere             anywhere             state NEW tcp dpt:netbios-ssn
ACCEPT     tcp  --  anywhere             anywhere             state NEW tcp dpt:microsoft-ds
ACCEPT     udp  --  anywhere             anywhere             state NEW udp dpt:netbios-ns
ACCEPT     udp  --  anywhere             anywhere             state NEW udp dpt:netbios-dgm
ACCEPT     tcp  --  anywhere             anywhere             state NEW tcp dpt:ssh
REJECT     all  --  anywhere             anywhere             reject-with icmp-host-prohibited

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         
REJECT     all  --  anywhere             anywhere             reject-with icmp-host-prohibited

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

EDIT:
Yes, for now, i prefer to handle firewall from gui

Quote:

Originally Posted by getsebool samba_share_fusefs

samba_share_fusefs --> off

***glennzo*** · #12 27th April 2012, 08:34 AM

In one case, in order to view folder content on my Windows partition I needed to set getsebool_samba_share_fusefs to on.

PHP Code:


			
setsebool samba_share_fusefs on

Note that these (this and firewall/selinux) are just a few things that I can think of to help you access your NAS. I'm not sure if they are preventing access, but one or more could be.

sea · #13 27th April 2012, 12:24 PM

ok, providing another summary:

system-config-firewall: disabled
setsebool samba_share_fusefs on
setenforce=0

/etc/hosts

Code:

127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

/etc/fstab

Code:

#
# /etc/fstab
# Created by anaconda on Tue Feb 14 00:00:52 2012
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/sda6               /                       ext4    defaults        1 1
/dev/sda7               /home                   ext2    defaults        1 2
/dev/sda3               swap                    swap    defaults        0 0

Services:

Code:

blame|grep ip ; blame|grep fs;blame|grep smb
   253ms ip6tables.service
   253ms iptables.service
  2112ms remount-rootfs.service
  1357ms autofs.service
  1228ms systemd-remount-api-vfs.service
   920ms netfs.service
     0ms sys-fs-fuse-connections.mount

This is set, going to reboot, and then try again and edit this post.

EDIT:
Still, i can get a list with smbclient -L, but cant mount/connect it.. see as below:

Code:

[simon@l670 /]$ sudo mount -t cifs //192.168.10.110 /mnt/nas -o rw,soft,credentials=/home/simon/.NASconfig
[sudo] password for simon: 
Retrying with upper case share name
mount error(6): No such device or address
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
[simon@l670 /]$ smbclient -L ocean -N ; smbclient "////ocean"
Anonymous login successful
Domain=[OCEAN] OS=[Unix] Server=[Samba 3.5.6]

	Sharename       Type      Comment
	---------       ----      -------
	IPC$            IPC       IPC Service (Iomega StorCenter ix2-200)
	priv            Disk      
	pub             Disk      
	TimeMachine     Disk      
	Pictures        Disk      
	Music           Disk      
	Movies          Disk      
	Linux           Disk      
	Backups         Disk      
Anonymous login successful
Domain=[OCEAN] OS=[Unix] Server=[Samba 3.5.6]

	Server               Comment
	---------            -------
	OCEAN                Iomega StorCenter ix2-200

	Workgroup            Master
	---------            -------
	OCEAN                OCEAN
Enter simon's password: 
Connection to  failed (Error NT_STATUS_BAD_NETWORK_NAME)

The try to connect using: smbclient ////ocean -U=username on nas (which is the same as $USER (all lower chars)) results in the same.

EDIT2:
As i get a list of the dirs, i dont think its a selinux or a firewall issue, as i had the same results with enabled firewall (smb ports open), and selinux enabled|disabled doesnt matter either...
smbclient calls directories services.. so i tried:

Code:

smbclient "////ocean" Movies
Connection to  failed (Error NT_STATUS_BAD_NETWORK_NAME)

I can however, access it using the browser, but there i cant move anything, and dont open a complete directory to play all music inside, only single files

EDIT3:

Code:

dmesg|tail
[   37.339788] fuse init (API version 7.17)
[   37.351074] SELinux: initialized (dev fusectl, type fusectl), uses genfs_contexts
[   37.353446] wlan0: no IPv6 routers present
[   38.154703] SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
[   45.694473] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
[  103.874424] FS-Cache: Loaded
[  103.878105] FS-Cache: Netfs 'cifs' registered for caching
[  103.889500] CIFS VFS: default security mechanism requested.  The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.3
[  103.990169] CIFS VFS: cifs_mount failed w/return code = -6
[  104.051292] CIFS VFS: cifs_mount failed w/return code = -6
[simon@l670 /]$ uname -r
3.2.6-3.fc16.x86_64

***glennzo*** · #14 27th April 2012, 01:05 PM

Try adding the ip of the NAS to /etc/hosts. See if that makes any difference.

Code:

192.168.10.110   ocean

Restart samba

Code:

systemctl restart smbd.service
systemctl restart nmbd.service

Also, any time you make a change to /etc/samba.smb.conf you need to restart those services. You should also check the file for typos with testparm.

Code:

testparm

sea · #15 27th April 2012, 01:32 PM

I guess thats the point:

Quote:

[simon@l670 /]$ sudo systemctl restart nmbd.service
Failed to issue method call: Unit nmbd.service failed to load: No such file or directory. See system logs and 'systemctl status nmbd.service' for details.
[simon@l670 /]$ sudo systemctl restart smbd.service
Failed to issue method call: Unit smbd.service failed to load: No such file or directory. See system logs and 'systemctl status smbd.service' for details.

EDIT:
Weird, yum provides smbd tells to install samba (had samba4 installed)...
After install and reboot, i still cant enable/start/restart the smbd.service

Code:

 sudo yum history
ID     | Command line             | Date and time    | Action(s)      | Altered
-------------------------------------------------------------------------------
   184 | install samba            | 2012-04-27 14:34 | Install        |    1   
   183 | upgrade -y               | 2012-04-27 13:38 | Update         |   12   
   182 | upgrade -y               | 2012-04-26 22:28 | E, I, U        |   32 EE
   181 | remove smbios-u*         | 2012-04-26 22:23 | Erase          |    3   
   180 | install smbios-utils     | 2012-04-26 22:10 | Install        |    3   
   179 | install smbios-utils-bin | 2012-04-26 21:30 | Install        |    2   
   178 | upgrade -y               | 2012-04-26 01:41 | E, I, U        |   33 EE
   177 | install samba4           | 2012-04-26 01:27 | Install        |    2   
   176 | install cifs-utils       | 2012-04-26 01:26 | Install        |    2   
   175 | install cntlm            | 2012-04-26 01:25 | Install        |    1   
   174 | install fuse-smb         | 2012-04-26 00:51 | Install        |    3   
   173 | install gtk2.i686        | 2012-04-19 23:50 | I, U           |   35   
   172 | upgrade -y               | 2012-04-17 00:47 | Update         |    2   
   171 | upgrade -y               | 2012-04-15 11:41 | E, I, U        |   18   
   170 | upgrade -y               | 2012-04-13 01:48 | E, I, U        |  103 EE
   169 | install cmospwd          | 2012-04-09 15:38 | Install        |    1   
   168 | install faac             | 2012-04-07 19:07 | Install        |    2   
   167 | upgrade -y               | 2012-03-12 15:07 | E, I, U        |   61 EE
   166 | install php-pear-XML-RSS | 2012-02-28 16:24 | Install        |    5   
   165 | install -y -q plymouth*  | 2012-02-28 01:28 | Install        |   16   
history list
[simon@l670 /]$ sudo systemctl status smbd.service'
> ^C
[simon@l670 /]$ sudo systemctl status smbd.service
smbd.service
	  Loaded: error (Reason: No such file or directory)
	  Active: inactive (dead)
[simon@l670 /]$ sudo find / -name smbd.service
find: `/home/simon/.gvfs': Permission denied
[simon@l670 /]$

EDIT:
I changed /etc/samba/smb.conf, actualy just changed workgroup to "ocean"

Code:

[simon@l670 /]$ testparm
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[homes]"
Processing section "[printers]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

[global]
	workgroup = OCEAN
	server string = Samba Server Version %v
	log file = /var/log/samba/log.%m
	max log size = 50
	idmap config * : backend = tdb
	cups options = raw

[homes]
	comment = Home Directories
	read only = No
	browseable = No

[printers]
	comment = All Printers
	path = /var/spool/samba
	printable = Yes
	print ok = Yes
	browseable = No

Restarted: (old windows habbit)

Code:

[simon@l670 /]$ blame|grep ip ; blame|grep fs;blame|grep smb
  1684ms remount-rootfs.service
  1363ms autofs.service
   839ms systemd-remount-api-vfs.service
   810ms netfs.service
     6ms sys-fs-fuse-connections.mount
Startup finished in 2065ms (kernel) + 4631ms (initramfs) + 13057ms (userspace) = 19754ms