| Summary: | update to cauldron: Can't mount anonymous Samba share anymore (error 13) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | R G <gemaeuer> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | cooker, martin.fiala |
| Version: | 3 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
R G
2013-02-17 13:59:36 CET
my fstab line had to be changed from: //server/freenas_share /mnt/server cifs username=%,uid=myname 0 0 to: //horst/freenas_share /mnt/horst cifs username=%,password=,uid=myname,sec=ntlmv2 0 0 and: mount -t cifs //horst/freenas_share /mnt/horst --verbose -o guest,uid=myname,sec=ntlmv2 mounts now manually. if someone would enlighten me about this problem being one of updating to cauldron or of me being stupid somewhere in the process I would be grateful. still valid ? iirc there was some bugs on systemd Version:
Cauldron =>
3 I have the same problem, except that it is not for anonymous connection, but for an authenticated one. It seems more like some upstream problem or may be a new "feature". # mount -t cifs //popcorn/Share /mnt/popcorn -o username=abc,password=123 mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) adding parameter "sec=ntlmv2" works # mount -t cifs //popcorn/Share /mnt/popcorn -o username=abc,password=123,sec=ntlmv2 CC:
(none) =>
digri
Johnny A. Solbu
2013-07-24 11:14:26 CEST
CC:
(none) =>
cooker Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad Status:
NEW =>
RESOLVED |