NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

unkerjay's avatar
unkerjay
Aspirant
Mar 25, 2017
Solved

readyshare mount error(13): Permission denied

I'm using Linux Mint 18.1 Mate.  This WAS working.

Used: sudo mount -t cifs //###.###.###.###/USB_storage /media/public -o sec=ntlm

 

Prompted for password and I'm in.

That's NOT WORKING anymore. 

 

Nothing I've tried seems to work.


I'm NOT using Windows, connecting to ANYTHING Windows.  This is STRICTLY a LINUX problem.

I CAN connect directly to the USB drive.

In, plain english (please), what can I do to troubleshoot this and fix it?

Thanx

  • Ok, I've tried recommendations from the sidebar (excepting those for Windows as noted).  I've tried what I've found on the web.
    And I've tried shumaku's recommendations.

    NOTHING has made a difference.

    So, I've connected it to a remote laptop and will access it from there when I remote connect to that laptop.

    Either that or I may try USB over IP on a raspberry pi I've got set up in another room.

    Readyshare works great, when it works.

    Thanx

6 Replies

Replies have been turned off for this discussion
  • schumaku's avatar
    schumaku
    Guru - Experienced User

    Hm, not sure ... was this command line copied? Isn't the default share of the first USB drive /USB_Storage ?

     

    Without authentication required:

     

     

    # mount -t cifs //192.168.1.1/USB_Storage /mnt/readyshare/ -o guest

     

    With a username and a password (another shared folder on the same Nighthawk):

     

    # mount -t cifs //192.168.1.1/other /mnt/readyother -o user=admin,password=password,sec=ntlm

     

    If uncertain, try --verbose or -vvv ...

     

    # mount --verbose -t cifs //192.168.1.1/other /mnt/readyother -o user=admin,password=password,sec=ntlm
    mount.cifs kernel mount options: ip=192.168.1.1,unc=\\192.168.1.1\other,sec=ntlm,user=admin,pass=********

     

    You might want to provide the password on the command line - still specifying a username is suggested:

     

    # mount --verbose -t cifs //192.168.1.1/other /mnt/readyother -o user=admin,sec=ntlm
    Password for admin@//192.168.1.1/other:
    mount.cifs kernel mount options: ip=192.168.1.1,unc=\\192.168.1.1\other,sec=ntlm,user=admin,pass=********

     

    If you are using the same username, you can do it without the username:

     

    # mount --verbose -t cifs //192.168.1.1/other /mnt/readyother -o sec=ntlm
    Password for admin@//192.168.1.1/other:
    mount.cifs kernel mount options: ip=192.168.1.1,unc=\\192.168.1.1\other,sec=ntlm,user=admin,pass=********

    But wait, you are sudo ... and then you become root

    # sudo whoami
    root

     

    Hope this gives some ideas. And then ... I've seen Linux distros breaking simple NFS mounts as well as mount.cifs.

     

    -Kurt

    • unkerjay's avatar
      unkerjay
      Aspirant

      Ok, I've tried recommendations from the sidebar (excepting those for Windows as noted).  I've tried what I've found on the web.
      And I've tried shumaku's recommendations.

      NOTHING has made a difference.

      So, I've connected it to a remote laptop and will access it from there when I remote connect to that laptop.

      Either that or I may try USB over IP on a raspberry pi I've got set up in another room.

      Readyshare works great, when it works.

      Thanx

      • schumaku's avatar
        schumaku
        Guru - Experienced User

         

        The ReadSHARE is a plain simple (and outdated, vulnerable, ...) SAMBA 3.0.24 serving SMB 1.0 protocol, and max ntlm auth security on all Nighthawk routers.

         

        Well, I'm still convinced it's either a problem between keyboard and chair, or a problem with your Linux distro, the SAMBA Kernel module in place, the SAMBA utilities in place, .. 

         

  • I checked my permissions.

     

    I reset them using:

     

    sudo chmod -R 777

     

    I then went in and tried modifying files and I double checked that the permissions settings
    matched the chmod.

    Check on all counts.

     

    I checked the permissions and chmod on the folder to which I was assigning the networked drive.

    Check.

     

    So, I'm running out of locations for checking the appropriate permissions.  Something I missed?

    (Apparently.)  What?

    • unkerjay's avatar
      unkerjay
      Aspirant

      P.S.  I'm here to try to solve a problem.  Not to win a popularity contest. So, all the notifications to my ego

      aren't working.  And this probably won't help.  

       

      Just saying.