Strange SAMBA behaviour

1st Official Post

    Hello there,


    im running an OMV7 NAS with Snapraid and mergerfs. I created SMB share for "/media" and movies(media/movies), series(media/series) and scans(media/scan).

    Everything was doing fine on my Kodi, windows11 and my brother printer. i have a user with full access to all shares. all was working fine till a few days ago.

    when pushing files from my linux via FTP to the OMV some files got mangeld files names. so i put "mangeld names = no" into the smb options and it worked.

    today i realized, that i cant access my shares from the LAN Tab in RS FileExplorer on my android. it wasnt accepting my login data. i thought no big deal, and just wanted to restart the NAS but even the weblogin wasnt accepting my login. so i had to hard reboot.

    after that the weblogin was working, but i could not find any error. but i still could not connect the android app.

    Now i was afraid that non of my share would work, but my existing shares in Kodi and win11 are working without problems. but i cant connect newly created folders. nor add the old ones to other devices. only my printer tells me that he cant access the old folder. (folder corect, folder not write protected, ECODE: 0x0C002032, -29, STATUS_NOT_SUPPORTE

    i ran the omv-firstaid without any issues. but i have no idea what to do now.


    Try to change the accepted SMB versions

    Thread
    OMV6 - can SMB1 be enabled
    Hi,

    Short version - is there any way of enabling SMB1 on OMV6, or do I have to go back to OMV5?

    Long version - I've been running OMV5 for over a year, but had to reinstall, so grabbed the OMV6 image for my Pi. Current version is 6.0.7-1 (Shaitan). All works fine again (shared drives to Windows machines, Plex in docker / Portainer etc.), except my SMB shares can no longer be seen by my RISC OS machines. I'm pretty sure this is because RISC OS only supports SMB1 (yes, I know, insecure... they're…
    DavidLowe
    • Official Post
    Quote from datawh0re

    when pushing files from my linux via FTP to the OMV some files got mangeld files names. so i put "mangeld names = no" into the smb options and it worked.

    First, it's best to pull files into OMV, using OMV. What is "my linux"? A host, a server?

    Quote from datawh0re

    today i realized, that i cant access my shares from the LAN Tab in RS FileExplorer on my android.

    I can't speak to this. "My android" is probably a smart phone or a tablet. The security measures OEM's use to protect them are different among the various OEM's. They march to the beat of their own drum.

    Quote from datawh0re

    and just wanted to restart the NAS but even the weblogin wasnt accepting my login. so i had to hard reboot.

    after that the weblogin was working, but i could not find any error. but i still could not connect the android app.

    You could have SSH'ed into your server (like you did with using omv-firstaid) and shut it down on the command line.

    Quote from datawh0re

    Now i was afraid that non of my share would work, but my existing shares in Kodi and win11 are working without problems. but i cant connect newly created folders. nor add the old ones to other devices. only my printer tells me that he cant access the old folder. (folder corect, folder not write protected, ECODE: 0x0C002032, -29, STATUS_NOT_SUPPORTE

    I'm not sure what you're talking about; "folders"? Are you really talking about SMB shares? If you need a Shared Folder / SMB permissions primer, see -> this.

    The short cut is:
    - Set Shared Folders to Others Read,Write,Execute and Users to Read/Write/Execute
    - Set SMB Shares to Read Only - Off and "Guests Allowed"

    ________________________________________________________________________________________________


    The likely reason that no one answered your post is, it's a technical rabbit hole. You're talking about multiple clients, running differing OS platforms, push FTP files transfers and there's no way to know if you've introduced Linux permissions and / or created permissions conflicts by checking ACL boxes. Adding to that, you're using KODI (a media server), in some capacity, which introduces another set of factors. There are numerous details involved with your issue(s) and nowhere near enough information to even begin.

    The best that could be done, if someone is inclined to take this up, is to get your Windows box access to OMV's SMB shares.

    Thanks for you response. you are right i should be more specific.

    1. i have a linuxMX host n which i organize my files and send them to the OMV with filezilla. i dont know why files transferred with ftp got mangled names in the folders. but disabling it in SMB options fixed it.

    2. My android is just a smartphone, the RS Filemanager App has a tab for lan. Where you can see SMB shares of the hosts he finds in the network (192.168.178.XXX) this worked flawlessly from the first time setting it up. Just enter the User and PW and i had no problem accessing the files. Now i can't get any User to work.

    3. When i realized the error on the android and that i could not access via the webui, i tried to SSH but it won't work either. i could only SSH after a hard reboot.

    4. More Detail on my Setup:

    i have 28TB pool called /media

    subdirectories are /media/movies

    /media/series

    /media/scan

    these are all shared folders. SMB (SMB3) and FTP enabled with basic setting.

    In Windows i have the folder connected individually m:\movies s:\series ........

    Kodi has the SMB share /media connected with the subfolder movies and series being mapped as movies or series

    My brother printer has a network-scan configured in the webui ui to IP\scan with the same User as for the other shares, and it worked.

    The created user for the shares is basically a root user with full access. As i already mentioned, all worked perfectly from the start when i set up the system a few weeks ago.

    - Set Shared Folders to Others Read,Write,Execute and Users to Read/Write/Execute (only my user has RWE, and i t worked for weeks)

    - Set SMB Shares to Read Only - Off and "Guests Allowed" (read only is off, but quests are not allowed)


    Now the shares still work in Win11 and Kodi. But not for the Android App nor the Printer.

    I also created a new share (/media/test). But i can't connect the /media/test nor /media to any other device. he just dont accept the login data and always asks for it again.

    I also disabeld the SMB service saved, rebooted, enabeld it, saved and rebooted again. But nothing changed. The "old" SMB shares in Kodi and Win11 are still working, but i can't connect new ones or get the "old" ones to work again in the Android App or the Network-Scan.

    • Official Post
    Quote from datawh0re

    - Set Shared Folders to Others Read,Write,Execute and Users to Read/Write/Execute (only my user has RWE, and i t worked for weeks)

    - Set SMB Shares to Read Only - Off and "Guests Allowed" (read only is off, but quests are not allowed)


    I'm surprised you haven't at least tried the above. From a permissions perspective, that's all I have for you.

    If you have something that "looks like a permissions problem" the first thing to do is open everything up:

    - Take notes on what you have.
    - Open permissions.


    If it works, go from there. If it doesn't work, nothing is lost.
    ____________________________________________________________

    You might give some thought to the previous post of Stryker . While it's nothing but speculation on my part, it's remotely possible that a SMB security update changed Samba's operation. Enabling a specific protocol level of NT1 or SMB2 might be worth looking at. This is another item that's easy to try and, if it doesn't work, it's easy to remove.

    To lock in a specific protocol level the following statements would be needed in SMB's extra options:

    min protocol = NT1

    max protocol = NT1


    (OR)

    min protocol = SMB2

    max protocol = SMB2

    Quote from Stryker

    Try to change the accepted SMB versions

    Thread
    OMV6 - can SMB1 be enabled
    Hi,

    Short version - is there any way of enabling SMB1 on OMV6, or do I have to go back to OMV5?

    Long version - I've been running OMV5 for over a year, but had to reinstall, so grabbed the OMV6 image for my Pi. Current version is 6.0.7-1 (Shaitan). All works fine again (shared drives to Windows machines, Plex in docker / Portainer etc.), except my SMB shares can no longer be seen by my RISC OS machines. I'm pretty sure this is because RISC OS only supports SMB1 (yes, I know, insecure... they're…
    DavidLowe

    That fixed the Issue.

    thanks crashtest and Stryker

  • datawh0re

    Added the Label resolved
    • Official Post
    Quote from datawh0re

    That fixed the Issue.

    thanks crashtest and Stryker

    For the best security, it would be best to go to the highest level possible. Since you're nailing down the protocol level, going with the highest that will work would allow for a bit of "future proofing".


    Currently, the highest protocol, that I'm aware of, is SMB3_11 (The Windows 10 variant.)

    If SMB3 will run, that's the Windows 8 variant, that's what I would use.

    yeah but then i had to check it for the printer and the android app every time i go up in the protocol.

    now i have only one user allowed to connect to it. i believe it to be something with the last updates in OMV. thats the only thing that changed within the timeframe.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login