Some detail hoping it will help: NB - the reports above resonate with my experience, but I thing the Subject line is misleading. I am filing my report here because I believe it is easier to spot a different bug posted as the same, than to find the same bug posted as different. Be kind to me - I mean well ;)
All my samba servers have (amongst others) a public share (Samba logs me on as nobody, nogroup if credentials are not supplied) and a user share which (naturally) needs credentials. I too get the 'not mounted' message but this is a timing problem - after getting the message I invariably find the share is now mounted, whether the public share or my user share. User shares give no problem as far as I can see. My credentials are collected and it all works. Public shares give a problem if my credentials are needed. For instance, in the public share is a staff_only folder. Even when I try to connect to public giving my user name, I end up as nobody, nogroup and so, of course, I cannot get into the staff_only folder. Hardy does not ask me for credentials. If I try to connect giving the staff_only folder as well as my user share name, Hardy does ask for my credentials. However, Hardy seems not to use them, and I still end up as nobody, nogroup and still cannot get into the folder. It seems as though Hardy looks to see if credentials are required, and if not, will not present them. The change I would hope to see is a reversion to Feisty-Gutsy behaviour which I never noticed because it just worked, but I think credentials were presented to samba if they were required OR IF THEY WERE OFFERED. If I give no UserName when connecting, I expect to be nobody, nogroup If I give a user name I expect my credentials to be verified with samba (currently they are not) and then to be username,primarygroup, even when connecting to a public share. My Sambas range from an old Mandrake to the latest Debian. Let me know if you need any config files etc. Chris -- SMB error: Unable to mount location https://bugs.launchpad.net/bugs/209520 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
