unclear error when lanman authentication is refused on the server

[Tien Nguyen]

Binary package hint: nautilus

I just updated Ubuntu 8.04.
Whenever I make a connection to the Window share, I got this error dialog:

Unable to mount location
Failed to mount Windows share

With and OK button.

ProblemType: Bug
Architecture: i386
Date: Sun Mar 30 21:19:59 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.22.1-0ubuntu1
PackageArchitecture: i386
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
Uname: Linux 2.6.24-12-generic i686

TEST CASE:

1) install the samba package
2) configure 'security = share' and 'lanman auth = yes' in the [globals] section of /etc/samba/smb.conf
3) add a user account to the server (e.g., with 'sudo adduser user')
4) set a password for this (insecure!) account with 'sudo smbpasswd user'
5) add a share which points to this user, e.g.:
  [user]
        comment = Test share
        path = /home/user
        writable = yes
        guest ok = no
        user = user
6) with the hardy version of the libsmbclient package installed, test the following:
  a) smbclient //localhost/user
        should return
     Server not using user level security and no password supplied.
     Server requested LANMAN password (share-level security) but 'client use lanman auth' is disabled
  b) nautilus smb://localhost/user
        should prompt for a password, and, even when entered correctly, return
     Couldn't display "smb://localhost/user"
     Error: Failed to mount Windows share
     Please select another viewer and try again.
7) install the libsmbclient package from hardy-proposed
8) both of the above two tests should now succeed
9) set 'client lanman auth = no' in /etc/samba/smb.conf
10) confirm that both of the above tests again fail when the config is overridden

[Wilco Baan Hofman (wilco)]

I can confirm this problem on hardy.

It may be caused by me not getting a username/password dialog when connecting to smb://server. When not using kerberos I see no shares (could be because I only allow users to view shares *after* authentication) and samba server-side has "restrict anonymous" set to "1". Which means that listing the shares requires a logon.

I can only view the shares if I create a kerberos ticket. After that I can see the shares, but when I click on one, I get the above mentioned error.

With kerberos:
gnomevfs-ls smb://server works.
After that gnomevfs-ls smb://server/share also works.

without kerberos:
gnome-vfs-ls smb://server asks for username and password
After that gnome-vfs-ls smb://server/share also works.

It would appear that nautilus smb support is broken in hardy somehow, at least for authenticated smb support.

Note that this used to work in feisty and gutsy.

[Wilco Baan Hofman (wilco)]

Just seen that this problem occurs because of the switch to gvfs in nautilus.

gvfs-ls smb://server shows absolutely nothing. Even after mounting smb://server or smb://username@server. Same for gvfs-ls smb://username@server.

Browsing doesn't work in nautilus at all. Even when using kerberos mounting smb://server/share doesn't work. Only smb://username@server/share works.

After this is mounted gvfs-ls smb://username@server/share shows the proper directories. However in nautilus this doesn't work.

Browsing from "computer:" using the "share on server.mount" doesn't work with nautilus. Could be because the username isn't supplied in the mount file.

gvfs-mount -l shows "Mount(0): share on server -> smb://server/share" instead of smb://username@server/share. Not that I think username@ should be needed in this case, it's just plain stupid IMHO.

[Tien Nguyen (tienhn)]

May I also add that:
1/ It used to work fine on 7.10
2/ I still can use smbmount command to mount the Windows shares and then browse the folders/files using nautilus. Works fine.
3/ Not all Windows share give me the same problem. I have shares served by a Windows 2003 server and it works but shares served by the file server box (DLink DGM-660) are having problem. Even though they all work fine under 7.10.

[sgabinato (sgabinato)]

I confirm this problem exactly to user Wilco Baan Hofman.

Nautilus stopped to work after the 8.04-alfa-3 release.
If I mount the shareres folders in the shell, nautilus work fine.

No problem to works on Debian unstable (sid) and Gutsy.

My shares served is debian 4.0r1 stable version.

[piercleo (pcleaud-deactivatedaccount)]

I confirm the exact same problem. Used to work in 7.10, just upgraded to test 8.04 and unable to mount windows share.

It seems a quite important problem for users who are running ubuntu at work when the network is a windows one.

[cbrfahm (cbrahm)]

I can browse WIndows Share, but hen i try my server running ubuntu 7.1 I can see all the share foldes but cant mount them.

[Simon Wenner (nowic)]

I confirm this problem with Nautilus 2.22.2-0ubuntu3.

My debian server runs with "security = share". All public directories work fine but the shared home directories which require authentication don't work anymore with nautilus in ubuntu hardy. Windows XP has no problems with these shares.

[homes]
comment = Home Directories
valid users = %S
read only = No
browseable = No

[pclapham (paul-bpages)]

I can verify that this is also happening for me. It used to work in the previous version but not for Hardy.

This needs to be sorted out before the release in 5 days, or with an update asap.

[Sebastien Bacher (seb128)]

several issue seem to be described there which make the work harder now.

connecting to an user directory on a ubuntu samba server using security share works correctly once smbpasswd has been used to define the samba password for the corresponding user, not confirming the issue. could you describe exactly how you configure your server and what steps you use in GNOME? Did you try to use "gvfs-mount smb://smbname/share"? Do you have anything in the server logs? Does smbclient works correctly?

[Bálint Magyar (balintm)]

Sebastien, I have some of the info you requested in your post above in duplicate bug #215570.

[wolfwitch (wolf-mylunarden)]

I wanted to chime in since I opened a similar bug that apparently got deleted as a dupe...

For me, the situation is this:

Prior to Hardy, I could browse my corporate Active Directory SMB shares using Nautilus. I was prompted for my login and password if I hadn't previously accessed a share, saved it to my keyring, and from that point on had no problem accessing any share I needed to (and had permissions for). I could simply browse any server similar to "Network Neighborhood" in Windoze.

After upgrading to Hardy, that is no longer the case. I can see the servers, but as soon as I try to open one- I get an empty container and my AD account gets locked out. Apparently Nautilus is trying to access the shares with a bad or no password. It does still seem to be using my login name (since I'm getting locked out of the AD network). If it matters- my Ubuntu login password is different from my AD login.

Note too: While the problem with Microsoft AD is the biggest one I see, I have the same problem on my small home network that uses SMB on a LInux server. I can no longer browse shares on it either.

I CAN manually mount an SMB share, although sometimes I get an error:
Can't display location "smb://windowsserver/"
No application is registered as handling this file.

It is necessary on a manual mount to actually specify the share name. I can't just mount a server to have easy access to all shares on it, like I used to in Gutsy (and Feisty, and I believe Edgy).

Even with the error- the share shows up on my desktop (and in Places) and I can access it for a time. It seems to timeout after about a half-hour of inactivity though, and then I have to manually mount it again (something else that wasn't happening before). For example- if I open a spreadsheet on a share, and spend a half hour or so editing it, when I try to save it- I have to enter my username and password again.

I think the problem is Nautilus or gvfs doesn't seem to be prompting for user credentials if it cannot access a share like it used to. It also doesn't seem to be caching them very well anymore when it does (through a manual mount). I tried deleting my gnome keyring, so it shouldn't be using a saved password anymore (and even if it was- it should be working since I haven't changed it).

I don't know if any of this helps, but that's my experience. I'll gladly provide any information I can if it helps get this fixed. This is a big deal for anyone using or trying to use Ubuntu in a corporate environment, most of which run Microsoft AD.

[wolfwitch (wolf-mylunarden)]

Quick clarification:

This problem only seems to apply to authenticated SMB shares. Shares that do not require authentication work fine.

[Tien Nguyen (tienhn)]

Sebastian,
When I used gvfs-mount, I got:

gvfs-mount smb//my-host/my-share
Error mounting location: volume doesn't implement mount

There is nothing in the dmesg.

[Sebastien Bacher (seb128)]

the credential issues on active directory and similar is bug #207072, gvfs doesn't ask for credential to do browsing which is a known bug and something which we agree should be fixed in hardy updates

[Sebastien Bacher (seb128)]

there is a syntax error in your gvfs-mount call before

[Tien Nguyen (tienhn)]

Sebastien,
Sorry about the error! Here is the result I got:

gvfs-mount smb://my-host/my-share
Password required for share my-share on my-host
User [myuser]:
Domain [MSHOME]:
Password:
Error mounting location: Failed to mount Windows share

I have checked and the user name and passwird are correct. I use the smbmount command fine with this name and password.

[spo0ner (christopher-pace)]

Being that 8.04 is 3 days away from final release, will this issue be addressed by then?
Is there a work-around I can find for this issue?

I'm having a similar problem in that all my 7.10 systems can connect fine utilizing Places -> Connect to Server -> Windows Share but all the 8.04 systems get the aforementioned error message.

[Paolo (paolo.ambrosio)]

I have a password protected Samba (Debian Sid) share perfectly working with Windows hosts and Ubuntu Gutsy.

On Hardy...

If I use Nautilus to browse the Windows Network smb://server/ and click on the folder "homes" I get:

Unable to mount location
Failed to mount Windows share

Typing smb://server/homes/ (or smb://blues@server/homes/) on the Nautilus bar I get:

Couldn't display "smb://server/homes/".
Error: Failed to mount Windows share
Please select another viewer and try again.

gvfs-mount works good and without asking for my password, since it is already in the keyring, but the file count looks suspicious:

$ gvfs-mount smb://blues@server/homes/
$ gvfs-mount -l
[...]
Mount(0): homes on server -> smb://server/homes/
$ gvfs-ls -l smb://blues@server/homes/
osm2pgsql-0.50.20071211 0 (directory)
osm2pgsql_0.50.20071211-1.diff.gz 2632 (regular)
[...]
$ ls -l .gvfs/homes\ on\ server/
total 0
drwx------ 1 blues blues 0 2008-04-05 17:42 osm2pgsql-0.50.20071211
-rwx------ 1 blues blues 2632 2007-12-11 22:02 osm2pgsql_0.50.20071211-1.diff.gz
[...]

I see the "homes on server" icon on the desktop BUT clicking on it simply gives me the usual "Unable to mount location" error. I can unmount it from the desktop though.

Hope it helps.

Paolo

[Sebastien Bacher (seb128)]

how is the share configured? having a standard way to trigger the bug would make debugging easier. the bug is no likely to be fixed for hardy no, but it'll be fixed in hardy-updates once debugged

[Paolo (paolo.ambrosio)]

Attached you can find my samba server (3.0.28a) configuration

[Paolo (paolo.ambrosio)]

I just realized that smb://server/blues/ works from Nautlius as expected. The problem is with the special share smb://server/homes/ only!

[Joo (joo.tsao)]

me too.

[David Schaller (bach-leipzig)]

This bug is a deal-breaker for me. I do not plan to upgrade to Hardy until this is fixed. With every release since 5.10 I've had various troubles with Nautilus browsing and/or mounting samba network shares. I've found workarounds in the past, but I was hoping this stuff would all be coming together a little better by now. I can post my smb.conf file if that would help anyone to debug this. I can access my shares with 6.10, but not with 8.04.

[Sebastien Bacher (seb128)]

the bug starts collecting random doesn't work issues and is almost not workable now, could everybody open new bugs and not assume that everybody get the same issue so we can identify the bugs an duplicate things which are similar

the informations that can be useful:
- when you share an user directory, did you use smbpasswd to set a password for the corresponding user?
- can you access to the '/' directory on the server?
- do you use a directory which has different rights for anonymous and authentificated users?
- can you browse the share using an another os or ubuntu version?
- what server do you try to use?
- does smbclient on hardy success to connect?

[Wilco Baan Hofman (wilco)]

- when you share an user directory, did you use smbpasswd to set a password for the corresponding user?
I have a setup with LDAP, but same thing really. security = user. restrict anonymous = 1, share only visible and accessible for authenticated users.
- can you access to the '/' directory on the server?
If you mean smb://server/ then no, but that's the browsing issue.
- do you use a directory which has different rights for anonymous and authentificated users?
Yes. Not visible for anonymous (like homes) and also not able to connect to as anonymous user.
- can you browse the share using an another os or ubuntu version?
Yes, ubuntu < hardy, windows
- what server do you try to use?
Samba
- does smbclient on hardy succeed to connect?
Yes

See my comments about what fails and works with gvfs, as opposed to gnomevfs

[Wilco Baan Hofman (wilco)]

gvfs-mount smb://server/homes doesn't work. likely because valid users = %S is active, which means that this is as it was intended.
gvfs-mount smb://server/username works for me.

Also, I might add that it boils down to at least three (very much related) issues:

- Authenticated browsing, because:
* gvfs-mount smb://server/share doesn't work, likely because an anonymous bind on this share results in the share not found error, instead of authentication failed, because the anonymous user can't see this share.

- Authentication when connecting
* Anonymous bind should only be used as fallback.
* username@ should not be needed, because it should ask for the username and password, and current username should be default.

- nautilus cannot work with username@ mounted shares
* Should not be needed anyway

[Brian Morton (rokclimb15)]

I am also having this problem. Clean installation of Hardy shows no shares available on a Windows file server. Used to work fine with this particular file server under Gutsy.

[Mark O'Hare (mark-ohare)]

I can also confirm this problem. On Gusty could see shares on Windows file server, after upgrade to hardy can no longer see any shares.

If I explicitly browse in nautilus (e.g. smb://servername/ ) I get to see all the shares on the server but smb:/// shows no machines.

Permanent mounts in fstab also fail to work. If I browse onto the share using Nautilus via smb://servername/ then the share is automatically mounted.

[georgenazar (georgenazar-gmail)]

I am having a similar problem with Vista and XP. Ubuntu can see the Windows computers but when I click on them it fails to read the shared directories. Ubuntu shares with windows just fine. I can access all my Ubuntu shares on my Windows machines.

Also, when I try and launch Samba, it crashes. I suspect that it has something to do with it.

[nikkopt (miguang)]

Confirmed on hardy 64 bits here. Nautilus no longer asks for login information on an authenticated windows share. (NT_STATUS_LOGON_TYPE_NOT_GRANTED)
It works fine on konqueror and some smb apps like smb4k.
PS: my samba server also crashes.

[ka1axy (ka1axy73)]

Confirmed on Hardy Heron 8.04, with additional information:

If you attempt to connect to an authenticated SMB share, you get a blank window in Nautilus.

BUT:

If you append to the server name string, one of the available shared directories, you're asked if you want to allow access to the keyring. If you allow access, the directory mounts!

e.g.:

Places/Connect to Server/
Select SMB
Enter Server name

Nautilus window comes up, no subdirectories shown

append the name of one subdirectory to the "smb://servername/" in the location bar

"Allow access to keyring" box pops up, and, when "Allow" is clicked,

Contents of the specified shared directory appear, and it is shown as mounted in the "Tree" pane on the left.

[fuzzypiggy (oracledba)]

I had Gutsy, did and in place upgrade to Hardy and the problems started, I was unable to mount SMB shares from either trues Windows or Samba presented shares from a Gusty server.

If I simply enter a SMB server that is presenting shares, ie try to get a list of available shares, I get the error messges.

The only options I found worked were similar to the poster above.

Ensure you enter the correct servername/IP.
Ensure you enter the SMB share name.
Ensure you enter a username ( my internal network has no passwords for SMB shares, just usernames ).

It the comes up with the keyring dialogs and then presents the failure to mount shares on server X error dialog, but then brings up a nautilus window with the folders that are on the share! All seems very "up-in-the-air", but it usable the only niggle is you have to know the name of the shares, which means keeping a list to hand or going around back on SSH connection and listing the smb.conf.

[wolfwitch (wolf-mylunarden)]

I've noticed a couple of other things...

As said earlier- you can mount a share if you use "Places => Connect to server" and then use an actual share name. There is no way to browse shares through Nautilus. This is a real pain if you have a large network with lots of servers and shares.

After successfully authenticating, you get an error dialog:

Can't display location "smb://servername/sharename/"
The specified location is not mounted.

However- the location is in-fact mounted, and shows up in the Places menu afterwards. It also creates a desktop shortcut.

Another odd thing. If I click on the share in Places- it opens up in Nautilus, but it also creates ANOTHER entry in Places and on my desktop. So- for every share I mount and access- I get two entries in Places and two desktop shortcuts. I can unmount one of them to get rid of the clutter, but it is just really odd.

[nikkopt (miguang)]

kalaxy's "trick" does work.
I also noticed that, in my case the problem is only displaying the shared folder/drives.

Example:

smb://3rsys/ in nautilus shows a blank screen, but adding d$ (example of shared drive) or a shared folder name works.. (login window appears and the volume is mounted), without the need of using the "Connect to server" window in "Places" menu. (smb://3rsys/d$/)

[gticlayauri (gticlayauri)]

Hello,

I had the same problem in Ubuntu 8.04, try this: In smb.conf add these lines into [Global] configuration (don't forgot make backup of smb.conf):

client ntlmv2 auth = no
client lanman auth = yes
client plaintext auth = yes

Then restart samba with sudo /etc/init.d/samba restart. That works for me. If it doesn't work type in your terminal:

$ smbclient -L //server/service

and add here the response to study.

Lucky,

Giancarlo

[Mark O'Hare (mark-ohare)]

I added the changes suggested by gticlayauri to smb.conf and did a samba restart but it made no difference.

Still cannot:
- auto mount samba window shares
- nautilius smb:/// returns no machines on network

In nautilius smb://servername/ shows the available shares. Double click on a share and it is auto mounted following a keyring authentication request.

[gticlayauri (gticlayauri)]

Pls added your smb.conf

El mié, 30-04-2008 a las 16:03 +0000, Mark O'Hare escribió:

> I added the changes suggested by gticlayauri to smb.conf and did a samba
> restart but it made no difference.
>
> Still cannot:
> - auto mount samba window shares
> - nautilius smb:/// returns no machines on network
>
> In nautilius smb://servername/ shows the available shares. Double click
> on a share and it is auto mounted following a keyring authentication
> request.
>

[Mark O'Hare (mark-ohare)]

Giancarlo,

As requested I have attached my smb.conf file.

Let me know if you need any more info.

Many thanks,
Mark

[Stijn Gysemans (stijn-gysemans)]

I'm having the same issue: not able to browse or mount a windows share.
My windows share is actually a ubuntu 7.10 setup as a windows share (for other purposes).

my gutsy laptop is able to access this share!
my hardy laptop says : Failed to mount Windows share

[Tiago Faria (gouki)]

Still doesn't work for me.

[Steve Langasek (vorlon)]

Tiago,

Please file a new bug describing the issue you're experiencing, and provide the bug number here. This bug report is about a failure to connect to servers that require old password security methods, and has been resolved in hardy-updates; if you're still experiencing problems connecting to samba servers from hardy with all updates installed, that's unrelated to this bug.

[Pablo Estigarribia (pablodav)]

When access to windows 2003 server with smb://server I can't see shares, but if I try to acces my ubuntu it shows shares example, smb://localhost.
I want to know where this issue is originated and how to fix it.....

[Pablo Estigarribia (pablodav)]

When access to windows 2003 server with smb://win2003server I can't see shares, but if I try to acces my ubuntu it shows shares example, smb://localhost. Instead if I try to access some share with smb://win2003server/share it shows folders inside share correctly and I can access without errors.
I want to know where this issue is originated and how to fix it.....

[Steve Langasek (vorlon)]

On Fri, Jun 27, 2008 at 02:23:34AM -0000, Pablo Estigarribia wrote:
> When access to windows 2003 server with smb://win2003server I can't see
> shares, but if I try to acces my ubuntu it shows shares example,
> smb://localhost. Instead if I try to access some share with
> smb://win2003server/share it shows folders inside share correctly and I
> can access without errors.

That's bug #207072.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>

[Pablo Estigarribia (pablodav)]

Sorry, it's true is related to that bug.

[sefs (sefsinc)]

Hello I am unable to browse shares

1) on ubuntu 8.04 from a windows machine
2) on ubuntu 8.04 from it self
3) can see shares, but they will not mount when double clicked upon.

What am I to do here guys.

[wolfwitch (wolf-mylunarden)]

This whole mess is actually WORSE in Intrepid right now. In Hardy, there was at least the option of manually attaching to the share using the "Connect to server..." dialog. That doesn't work in Intrepid.(!) One gets the usual errant "Cannot display location..." error message, but it shows up in Places as mounted (just like in Hardy); however- double-clicking on the share to open it yields a very (un)helpful error message:

DBus error org.freedesktop.DBus.Error.InvalidArgs: Mountpoint Already registered

So now- I can't access my authenticated network shares at all.

Fortunately I'm running intrepid on a secondary machine- I realize it is only in Alpha right now, but I had expected at least SOME progress on this problem.

[Tien Nguyen (tienhn)]

IMHO, this whole smb:// access from nautilus is really not that great. It is fine for copying files but most applications are not compatible with this URL, so you can not drop the files with smb:// access into an application. Another example, if you using Google web mail to compose an e-mail and want to attach a file, you can browse to the smb:// share and click on the file URL but then Firefox does not translate the smb:// URL so it become useless!!

I might as well just use smbmount and mount it to a mount point. I really hope to see Nautilus/Ubuntu improve in this area.

:).

[oss_test_launchpad (oss-test-launchpad)]

I have the following problem, testing with Ubuntu 8.10 Alpha 4+, trying to connect to a company SMB network server share. Nautilus tells me:

----
Could not display "smb://servername/myshare$/" - Einhängen des Ortes nicht möglich.
----

This worked ok when I used 8.04. However, nautilus shows the share as mounted (gets a shortcut on the left side, as a cd would which has been inserted into a local drive). When I press the "eject" (unmount) button for this share, I sometimes get the following error message:

----
Could not display "smb://servername/myshare$/". Fehler: DBus error org.freedesktop.DBus.Error.InvalidArgs: Mountpoint Already registered - Bitte wählen Sie einen anderen Betrachter und versuchen Sie es erneut.
----
I entered my account data the first time I tried to connect. Strangely enough, in the properties you can see how many files there are on this share and how much data there is all in all, but the file list cannot be displayed.

I reported this bug under https://bugs.launchpad.net/ubuntu/+source/samba/+bug/216465. However, going more into it, I think this was the wrong thread to report this to. Is this thread I am writing in now the right one, or should I open a new one?

[gregphil (gregphil)]

I also experience the ubuntu 8.04.1 inability to display shares from WindowsXp boxes , but it displays shares from CentOS 5.2 boxes just fine. On a parallel install (on another disk) of kubuntu 8.04.1 with Samba and all the other setting as identical as I can make them, the GUI browsing works in the KDU app Konquorer. HOWEVER to make this work I had to fix the /etc/hosts files. The "new format" DOES NOT WORK, even with smbtree or smbclient. It is necessary to add the NetBios name aliases to the 127.0.0.1 line, the entry on the 127.0.1.1 line is not seen or not understood. For example I use
127.0.0.1 localhost LIVING-ROOM LIVING-ROOM.MYGROUP
127.0.1.1 LIVING-ROOM.MYGROUP

Back in the ubuntu 8.04.1 install, the GUI browsing fails, but smbclient or smbtree can report all the shares. I am using the default encrypted passwords and security = user. The gnome nautilus network file browser (ver 2.22.3) will show the computers with shares on the network, but clicking on a Windows machine icon does NOT show the shares. If I switch the nautilus "Location" dialog to text, and append a valid share name to the computer name, such as smb://laptop/C, then a full successful mount is made and I can see and use the shared files. Once mounted, if I unmount and try again to click on a Windows machine icon it still fails to mount.

I think I have tried every possible combination of smb.conf auth entries (ntlmv2 auth = etc). It is really broken. Please fix........

[Richard Rickwood (rickwookie)]

Is this not caused by the same problem that causes bug 207072, which is fixed (for me at least) using the patch supplied there: http://launchpadlibrarian.net/15554213/80_samba_browsing_authentification.patch

I applied that patch to gvfs-0.99.8 and it cured all my nautilus smb woes.

Why this patch is not yet integrated I do not know. Surely the dozens of nautilus/smb bugs filed on lauchpad must have this common root.

[Steve Langasek (vorlon)]

> Is this not caused by the same problem that causes bug 207072

No, it is not. This bug is about incompatibility with servers that negotiate weak password encryption for connections, and it has been worked around by a change to the default settings for samba in Ubuntu 8.04. If your problem was fixed by the patch from bug #207072, then your problem is unrelated to this bug report.

[Steve Langasek (vorlon)]

marking 'wontfix' for gvfs in hardy; the gvfs side of this requires UI changes to detect the incompatibility (and possibly libsmbclient API changes as well), so this is too intrusive for 8.04.

[oss_test_launchpad (oss-test-launchpad)]

Is this a problem with Ubuntu 8.10, too?

[Ed Covert (ebcovert3)]

No, I have not had this problem in 8.10

Ed

On Tue, October 28, 2008 2:07 pm, oss_test_launchpad said:
> Is this a problem with Ubuntu 8.10, too?
>
> --
> 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 direct subscriber
> of the bug.
>

--
Ed Covert
<email address hidden>

[DrC (drcowsley)]

re https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/209520/comments/142

8.04 is a lts version. Is the 'won't fix' a long term decision that we hope will be overtaken by upstream developments?

[Tien Nguyen (tienhn)]

I just upgrade to 8.10 and the problem came back:

"Unable to mount location. Failed to mount Windows share"

Is there a fix for this?

Thanks,

[RX8volution (rx8volution)]

Hi folks - I was trying to fix this for hours, and have a (albeit idiotically simple) fix that worked for me:

on the client, /etc/samba/smb.conf file

[global]

# THE LANMAN FIX
  client lanman auth = yes
  client ntlmv2 auth = no

  Notice the word CLIENT in front of both of those... try to re-mount the smb share again and it all works nicely.

Cheers.

/Rafal

[ubunturox (ubunturox-kk)]

I confirm the problem in 8.10 with Windows Server 2003 & Windows Server 2000 authenticated shares. If I open nautilus and type in the location smb://....., works fine. Using Places->Connect to server throws up the error messages "No application is configured ..."

[simtris (simtris)]

Is there any changes, any care of the developpers ? I don't see any responses.
I switched on debian lenny beacause of this bug, this issue never happened.
We have smbclient 2:3.2.5

[Sebastien Bacher (seb128)]

could you try on jaunty? bug #193232 and bug #207072 got fixed this week and once those changes get testing and are confirmed to work intrepid and hardy backported will be worked

[Steve Langasek (vorlon)]

There are numerous responses in this bug from developers. But I think you're following up to the wrong bug; this bug most certainly affects Debian lenny as well.

[nukedathlonman (areginato)]

Yes, it most certainly does effect Debian as well.

My desktop has this problem (Ubuntu Intrepid) and I cannot connect to my D-Link DNS-323 NAS unless I mount it manually from the command prompt. I did try all of the suggestions here. I can see the server, I can see the share, I get prompted for log in info, and then I see empty folder with the message about not being able to display contents of the share.

My Laptop, running Debian Etch worked fine until I did some apt-pinning to pull newer stuff in from Lenny & Sid. I ended up needing to pull Gnome in from Lenny. And now I'm having the same results - cant access the smb share unless mounted via command prompt.

For now, I'm watching and trying new things as they come up - until it's fixed I'm just using the ftp service on the DNS-323 (slightly inconvenient, but it works)

[Sebastien Bacher (seb128)]

could you try if that's still an issue in jaunty?

[nukedathlonman (areginato)]

I won't be able to try untill this weekend. I'll swap my 250G HD in my laptop over to teh original 120g one and give it a shot and let you know.

[Steve Langasek (vorlon)]

Sebastien,

As I commented in <https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/209520/comments/111>, the change needed here is for the gvfs backend to detect when the connection has failed due to mismatched security requirements. Do you know if there has been work upstream to implement this? I would expect such a change to be reflected prominently in the cahngelog.

[Sebastien Bacher (seb128)]

Right, we discussed the issue some time ago thanks for pointing the comment Steve since the bug got quite some new comments since. I was just commenting on the different samba issues to know which ones have been fixed in the recent changes concerning authentification, that one didn't get any work though so the bug should still be there

[Diver (diver)]

This is a major bug for me, I can't migrate from 7.10 until this issue is fixed.
I just checked and Fedora 10 live (gnome) also have this problem.

[Steve Langasek (vorlon)]

This bug is marked as resolved in Ubuntu 8.04; are you sure this is the bug you're seeing? You don't give any details about the problem you're having.

[Diver (diver)]

Steve, to be sure I just tested 9.04 alpha4 in VirtualBox

gvfs-mount smb://user@server/my-share
Password required for share my-share on my-host
User [myuser]:
Domain [MSHOME]:
Password:
Error mounting location: Failed to mount Windows share

After changing
security = share
to
security = user
in smb.conf on a server and restarting samba, I'm trying again:

gvfs-mount smb://user@server/my-share
Password required for share my-share on my-host
User [myuser]:
Domain [MSHOME]:
Password:

At this point my-share is mounted and all is good, but windows users can't connect to this server anymore
cmd->net view server
cause an error and I have to revert smb.conf changes.

I am sure the same happend with 8.10, when I tried it a week ago and then I found this bug and subscribed to it.
HTH.

[Steve Langasek (vorlon)]

oh - sorry, you mentioned upgrading from 7.10 so I assumed you were running 8.04. Yes, for 8.10 and above the default samba client behavior matches upstream's, and doesn't allow insecure security=share connections by default.

You can change the behavior on the client side by setting 'client lanman auth = yes' on the client's /etc/samba/smb.conf, as mentioned earlier in the bug report.

The only reason this bug is open is for gvfs to provide a better error message when trying to connect to such a server - the client will still refuse to connect to such servers by default, for security reasons.

[Diver (diver)]

Thanks Steve, it's working now,
Now if only nautilus (and gvfs) showed clear error message, or even ask to enable client lanman auth.

[Trab (trab)]

Hello All,

I had a similar issue in 9.04 trying to access a SMB NAS share. The solution I found was to add the following lines to /etc/samba/smb.conf under global (I haven't tried with only some of the lines, so one or the other may be unnecessary)

client lanman auth = Yes
lanman auth = Yes
client ntlmv2 auth = no

Hope this helps someone

[Martin Erik Werner (arand)]

Same as Trab above. Connecting to SMB NAS, on 9.04:

user@Comp:~$ smbclient //192.168.1.3/sharename -U user password
Domain=[ȇ] OS=[] Server=[���]
Server requested LANMAN password (share-level security) but 'client lanman auth' is disabled
tree connect failed: SUCCESS - 0

If adding to /etc/samba/smb.conf:
client lanman auth = Yes

Above command works (and gives me:
Domain=[ȇ] OS=[] Server=[���]
smb: \>

I have been fully able to connect to this share using nautilus (path smb://192.168.1.3/sharename)

[Sean Cleary (seanearlyaug)]

It is now Oct of 09.
The 9.10 version is coming out.
I still have this problem.
Please fix it.

[Steve Langasek (vorlon)]

You understand that the outstanding bug here is about the clarity of the error message only? lanman authentication is still insecure, and won't be re-enabled by default; if your goal is to actually connect to servers requiring lanman authentication, you will have to reconfigure your /etc/samba/smb.conf by hand.

[Sean Cleary (seanearlyaug)]

It now works, and I do not know how or why.
This is a major problem. I can not easily recommend a system that does
not have a easy way to hook up to other house hold computers.
You say solved, and after changing that file, rebooting server and PC a
few times, it did work.
Still, what a mess for anyone, as just a month ago I was trying nearly
everything and did not find your article.
There are many puzzled noob Ubuntu users with this problem out there.
Have mercy, or just give up the idea that Ubuntu is easy to use.
Is there anyway that you can use a program (windows speak= wizard) that
would configure this itself?
Maybe one that can use the info in the windows wizard generated files to
configure every machine on the local net?
Sean
On Sat, 10 Oct 2009 19:02:35 -0000 Steve Langasek
<email address hidden> writes:
> You understand that the outstanding bug here is about the clarity of
> the
> error message only? lanman authentication is still insecure, and
> won't
> be re-enabled by default; if your goal is to actually connect to
> servers
> requiring lanman authentication, you will have to reconfigure your
> /etc/samba/smb.conf by hand.
>
> --
> unclear error when lanman authentication is refused on the server
> https://bugs.launchpad.net/bugs/209520
> You received this bug notification because you are a direct
> subscriber
> of the bug.
>
> Status in gvfs: New
> Status in �gvfs� package in Ubuntu: Triaged
> Status in �nautilus� package in Ubuntu: Invalid
> Status in �samba� package in Ubuntu: Won't Fix
> Status in gvfs in Ubuntu Hardy: Won't Fix
> Status in nautilus in Ubuntu Hardy: Invalid
> Status in samba in Ubuntu Hardy: Fix Released
>
> Bug description:
> Binary package hint: nautilus
>
> I just updated Ubuntu 8.04.
> Whenever I make a connection to the Window share, I got this error
> dialog:
>
> Unable to mount location
> Failed to mount Windows share
>
> With and OK button.
>
> ProblemType: Bug
> Architecture: i386
> Date: Sun Mar 30 21:19:59 2008
> DistroRelease: Ubuntu 8.04
> ExecutablePath: /usr/bin/nautilus
> NonfreeKernelModules: nvidia
> Package: nautilus 1:2.22.1-0ubuntu1
> PackageArchitecture: i386
> ProcEnviron:
>
>
PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
:/sbin:/bin:/usr/games
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: nautilus
> Uname: Linux 2.6.24-12-generic i686
>
> TEST CASE:
>
> 1) install the samba package
> 2) configure 'security = share' and 'lanman auth = yes' in the
> [globals] section of /etc/samba/smb.conf
> 3) add a user account to the server (e.g., with 'sudo adduser
> user')
> 4) set a password for this (insecure!) account with 'sudo smbpasswd
> user'
> 5) add a share which points to this user, e.g.:
> [user]
> comment = Test share
> path = /home/user
> writable = yes
> guest ok = no
> user = user
> 6) with the hardy version of the libsmbclient package installed,
> test the following:
> a) smbclient //localhost/user
> should return
> Server not using user level security and no password supplied.
> Server requested LANMAN password (share-level security) but
> 'client use la...

[Tien Nguyen (tienhn)]

Sean,
If you don't want to deal with command line typing, check out webmin package.
Cheers

On Saturday, October 10, 2009, Sean Cleary <email address hidden> wrote:
> It now works, and I do not know how or why.
> This is a major problem. I can not easily recommend a system that does
> not have a easy way to hook up to other house hold computers.
> You say solved, and after changing that file, rebooting server and PC a
> few times, it did work.
> Still, what a mess for anyone, as just a month ago I was trying nearly
> everything and did not find your article.
> There are many puzzled noob Ubuntu users with this problem out there.
> Have mercy, or just give up the idea that Ubuntu is easy to use.
> Is there anyway that you can use a program (windows speak= wizard) that
> would configure this itself?
> Maybe one that can use the info in the windows wizard generated files to
> configure every machine on the local net?
> Sean
> On Sat, 10 Oct 2009 19:02:35 -0000 Steve Langasek
> <email address hidden> writes:
>> You understand that the outstanding bug here is about the clarity of
>> the
>> error message only?  lanman authentication is still insecure, and
>> won't
>> be re-enabled by default; if your goal is to actually connect to
>> servers
>> requiring lanman authentication, you will have to reconfigure your
>> /etc/samba/smb.conf by hand.
>>
>> --
>> unclear error when lanman authentication is refused on the server
>> https://bugs.launchpad.net/bugs/209520
>> You received this bug notification because you are a direct
>> subscriber
>> of the bug.
>>
>> Status in gvfs: New
>> Status in �gvfs� package in Ubuntu: Triaged
>> Status in �nautilus� package in Ubuntu: Invalid
>> Status in �samba� package in Ubuntu: Won't Fix
>> Status in gvfs in Ubuntu Hardy: Won't Fix
>> Status in nautilus in Ubuntu Hardy: Invalid
>> Status in samba in Ubuntu Hardy: Fix Released
>>
>> Bug description:
>> Binary package hint: nautilus
>>
>> I just updated Ubuntu 8.04.
>> Whenever I make a connection to the Window share, I got this error
>> dialog:
>>
>> Unable to mount location
>> Failed to mount Windows share
>>
>> With and OK button.
>>
>> ProblemType: Bug
>> Architecture: i386
>> Date: Sun Mar 30 21:19:59 2008
>> DistroRelease: Ubuntu 8.04
>> ExecutablePath: /usr/bin/nautilus
>> NonfreeKernelModules: nvidia
>> Package: nautilus 1:2.22.1-0ubuntu1
>> PackageArchitecture: i386
>> ProcEnviron:
>>
>>
> PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
> :/sbin:/bin:/usr/games
>>  LANG=en_US.UTF-8
>>  SHELL=/bin/bash
>> SourcePackage: nautilus
>> Uname: Linux 2.6.24-12-generic i686
>>
>> TEST CASE:
>>
>> 1) install the samba package
>> 2) configure 'security = share' and 'lanman auth = yes' in the
>> [globals] section of /etc/samba/smb.conf
>> 3) add a user account to the server (e.g., with 'sudo adduser
>> user')
>> 4) set a password for this (insecure!) account with 'sudo smbpasswd
>> user'
>> 5) add a share which points to this user, e.g.:
>>   [user]
>>         comment = Test share
>>         path = /home/user
>>         writable = yes
>>         guest ok = no
>>         user = user
>> 6) with the hardy version of the libsmbclient packa...