I can't say how to dupe it using Samba shares, but I believe Tien's suggestion of using "security=share" would do it.
Any share requiring authentication should cause this problem to occur. Nautilus won't prompt for credentials, and displays a blank folder when one tries to access a share. In Windows AD- it apparently tries to repeatedly access the server using the Ubuntu login name without a password, which results in the user's account being locked-out (assuming the Ubuntu user name matches an AD user name). The work-around is to use the "Connect to Server" dialog, but it is necessary to specify a share name, and it falsely reports that the share could not be mounted, even though it will then show up in the Places list. Prior to Hardy- shares could be accessed with ease just by browsing them through the "Network" Place. If one tried accessing a password-protected share- they would be prompted to provide user credentials, which could optionally be saved to the Gnome Keyring. My understanding, from a previous post by Sebastien on one of the many duplicates of this bug, is that this is a problem with gvfs and it is supposedly being worked on... I really wish someone would get this fixed. It has pretty much killed my push to roll out Ubuntu in a corporate environment. -- SMB error: Unable to mount location when server configured with security=share https://bugs.launchpad.net/bugs/209520 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
