[SOLVED] Cannot connect to SMB shares [OMV 0.5]

  • Hello there,


    Hardware: HP ProLiant N54L
    OMV Version: 0.5.21
    Kernel: Linux 2.6.32-5-amd64


    I've problem to connect to my SMB shares ... after creating a shared folder and share it through SMB/CIFS I can see the share on the Windows (win7, win8 and android) network overview, but when trying to access the folder I always get the error message:


    Code
    error code: 0x80070035
    network path cannot be found


    or (if trying via DOS and "net use")

    Code
    net use x:\ \\HPSERVER\share1 /USER:user1
    #or
    net use x:\ \\HPSERVER\IPC$\share1 /USER:user1
    
    
    System error 67 has occured. The network name cannot be found.


    Any idea?
    I've redo the OMV installation and only do the config for SMB and user (to be sure that there is no sideeffect from plugins)- still the same error...



    Samba Config:

  • What happens when you try to access your NAS with the IP instead of the hostname?


    How did you setup permissions when you created the shared folder in the first time?


    Greetings
    David

    "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"


    Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

    Upload Logfile via WebGUI/CLI
    #openmediavault on freenode IRC | German & English | GMT+1
    Absolutely no Support via PM!

  • davidh2k:
    Access with IP or Hostname is the same. Normally I would use the IP as I have only a small home network...


    The user has been set up very simple, just name "user1" and password. Then give access via Access Right Management | Shared Folders. No ACL has been set.


    @tekkbebe:
    here you are

    Code
    stat data
      File: „data“
      Size: 4096            Blocks: 16         IO Block: 4096   Verzeichnis
    Device: 97fh/2431d      Inode: 140509187   Links: 3
    Access: (2775/drwxrwsr-x)  Uid: (    0/    root)   Gid: (  100/   users)
    Access: 2013-11-17 11:35:57.257494949 +0100
    Modify: 2013-11-17 11:00:33.201670518 +0100
    Change: 2013-11-17 14:10:25.362571713 +0100


    Code
    stat shares
      File: „shares“
      Size: 4096            Blocks: 8          IO Block: 4096   Verzeichnis
    Device: 97fh/2431d      Inode: 140509185   Links: 4
    Access: (0700/drwx------)  Uid: (    0/    root)   Gid: (    0/    root)
    Access: 2013-11-17 12:07:40.981464689 +0100
    Modify: 2013-11-17 10:47:54.484114402 +0100
    Change: 2013-11-17 10:47:54.484114402 +0100
  • Additional info:


    if I try to map the network drive in Windows (Explorer) and set the option "sign in with a different account" - I can't log in to the HP Server - after trying the logon "user1" three times I get the network error message again... :/


    Note: I have no problem with SMB and my old Synologic DS in the same network ...

  • The "shares" folder is not root:users and is chmod 700.


    Did you not want some users to access it? How many users on your system? If there is just you and the share does not need 700 chmod....


    chown -R root:users shares
    chmod -R 775 shares


    I saw you just have 1 user. The shares folder is likely the issue. If you these commands it should work.

  • Sorry - "shares" is just a sub-folder for my shared directories


    Looks like:
    hdb /hdc -> raid1 -> mounted on media/<uid>/
    shares
    -> data (that is my folder which I like to share for my pc and laptop)


    So no one needs access to the "shares" folder. And for "data" the access is given to the user "user1" already if I get this right...

  • Yes, but do you want to access the shares subfolder??? As it is setup right now in your data folder you will not be able to access it. If you data folder is the main one and you want to access all of it's subdirectories do this:


    chown -R root:users data (these 2 commands are normally setup via the dropdown when you create a shared folder)
    chmod -R 775 data


    Again be one leve up from the data folder so you can list it before you run these commands.


    To give a user access rights go to:


    Access Rights Management/Shared Folders/ then on right highlight the folder and click on privileges or acl.

  • Thats why I asked what did you set it up in the first place when creating the share. I guess you used administrator R/W only and deny all other access. This sets the chmod to 700 which tekkebebe already explained is just wrong.


    Greetings
    David

    "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"


    Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

    Upload Logfile via WebGUI/CLI
    #openmediavault on freenode IRC | German & English | GMT+1
    Absolutely no Support via PM!

  • Yes, that is what it looks like David. He was probably thinking just he wants access (owner). But his user is not root user. So he needs chmod 760 at a minimum.


    Your data folder is inside the shares folder, yes? If you have chmod 700 and root:root ownership on the shares folder you will not be able to get inside it to the data folder.


    chown -R root:users shares
    chmod -R 775 shares


    Then make sure you give read/write privileges to your user1 in the:


    Access Rights Management/Shared Folders/ then on right highlight the folder and click on privileges or acl.

  • Works!


    I'm still confused why I have to give the user manual access to the sub-folder - but that solved the problem...


    But If I start thinking... ok as an user with no access I can't perform any action - that is one of the big differences between Windows and Unix. But shouldn't this be set automatically when I share a folder in the ARM?


    Many thanks both of you for your help!

  • I added to my last post. Read it again and do what I say and you should be good.



    You just need to learn the proper steps to setup the shared folder. When you create a shared folder use the default.


    Administrators: read/write Users: read/write Others: read only


    This gives the shared folder
    chown root:users (root is owner and users is the group. a user created in the web-gui is automatically part of the users group)
    chmod 775 (permissions)


    Remember that if you can't access a folder you will not be able to access anything in it either.


    Here is a chmod (permissions) calculator to help you understand permissions numbers faster ( read , write , execute)


    http://www.javascriptkit.com/script/script2/chmodcal.shtml

  • Thanks again. I know the logic of the unix access a little ;) - but in this case I've leaned back and thought all of it would be set up with one click... a little too lazy.


    I can start to copy my data now...

  • Remember if you use Putty to create a folder in a shared folder you are going to have to chown and chmod the new folder. Otherwise it will not work via SMB/CIFS. If you use a Windows machine to connect to the share create any new folders via the share on your windows machine. That is much easier.

  • Using Fedykin 0.4 on HP54 server loaded with data, music and videos for a small home network of 3 or 4 PC's - all fine with Win7 machines but have now added a Win8 system from which cannot see the OMV at all. All the PC's have the same user name and password. But the win8 system has Microsoft email address and different password but I am not sure that this is relevant when accessing the OMV system. I would like to try to keep everything as simple as possible - it seems to me that the problem is probably in the user set-up and access rights on the OMV system but do I need to upgrade the OMV to 0.5 to be compaible with Win8?

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!