nautilus does not display samba shares for machines inside an ADS network.

I have the Exact same Problem.

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=524485

did you get asked for a password when browsing those shares in the previous version of nautilus?

Yes, when using nautilus in gutsy a password is requested for browsing the machines in cases 1 and 2, but not in case 3.
I checked it also with a gutsy live CD, because the presence of gnome-keyring does make it difficult to say if browsing a share requires or not a password.
So the problem in hardy is that nautilus does not ask for it. In case 3 it shows the shares because they are browseable without password.

Did the same steps as Renzo and I was able to recreate and confirm his findings.

I believe this bug is due to the fact that gvfs does not do any authentication for browsing a computer's shares (the smb-browse backend) whereas it does do authentication for connecting to a share (the smb backend).
I've produced a fairly hacky patch that grafts authentication into the smb-browse backend. It works for me.

I have recompiled gvfs sources with Paul's patch and indeed it works inside my ADS network.
Tested with nautilus in all the cases I have reported and found no problems. A password prompt is displayed when needed, and all the machines can be browsed.
Now I really hope that this bug can be solved before the final release of hardy, otherways it will make it difficult to use hardy inside many networks that require browsing authentication. I think also that this bug should have a high priority.

I've just applied the patch, and I can now browse using nautilus; great! Reinstalling the old packages breaks it again.

I think this bug is also responsible for not beeing able to see or browse a home share as a home share is only visible
if listing of shares is authenticated. This bug is reported upstream as
http://bugzilla.gnome.org/show_bug.cgi?id=520551

the issue is not a nautilus one

Acquiring a kerberos ticket from an AD server, using pam_winbind at login (or using kinit in a shell), allows a user to browse samba shares with its cached credentials.
This is described here:
https://help.ubuntu.com/community/ActiveDirectoryWinbindHowto#head-a1da1a136c89873cbd7c7a1e1fbd75d621d18c9a

Maybe gvfs expects to find this or other authentications, but in any case this behaviour is different from what happened with gnomevfs in previous releases. Users should be aware of this.
I still think that a gvfs patch is needed to ask for a password when it is required, indipendently of kerberos tickets.

the kerberos issue seems to be a different one, the issue described there is that smb browsing doesn't ask for credentials and those are sometime required

Sebastien: I found no issues with kerberos, I was only pointing out that acquiring a ticket at login allows subsequent browsing of password protected shares, because of the credentials already acquired. Infact this is also true after using the package likewise-open to join the AD domain, probably because it does the same type of authentication.

To darkrain42:
 Thank you very much for the patch

To darkrain42: your patch just super, thanks to great !!!!
To BeerSeller: Thanks showed that the right path and helped him pass

I have the same problem, I can't see anything inside a windows machine with smb://machine
It doesn't display anything inside. I have the latest packages for Hardy

I think Darkrains patch will solve my problem. However, I'm new to linux and ubuntu, I would be grateful if someone can advise me on how to apply this patch.

Can anyone explain how to apply this patch? Thanks!

To apply the patch you have to recompile gvfs from source. Instructions on how to do it can be found here:
http://www.debian.org/doc/manuals/apt-howto/ch-sourcehandling.html

After dowloading the sources you have to apply the gvfs.patch using the 'patch' command ('man patch', for instructions). However, some manual editing of the patch file may be needed, because it was made for an older gvfs version. But it should work also with the latest version.

I just built with the latest gvfs trunk, and applied the patch (no changes required to patch) Works great. Thank you.

For those that want to try your hand at building this yourself, I kept track of what I did to build:

1)Read gnome.org developer instructions. You need Subversion installed to start.
2)Get gvfs trunk from subversion using: "svn co http://svn.gnome.org/svn/gvfs/trunk gvfs"
3)download patch -- direct link: http://launchpadlibrarian.net/13103721/gvfs.patch
4)backup original daemon/gvfsbackendsmbbrowse.c and /usr/lib/gvfs/gvfsd-smb-browse (source and binary)
5)download and apply above patch to the daemon/gvfsbackendsmbbrowse.c source file (i.e. "man patch" if unsure)
6)run ./autogen.sh --prefix=/usr/local in gvfs source (as per gnome.org dev instructions)
7)watch autogen/configure output closely as you will have errors unless you have built gvfs or gnome before
8)get all build dependancies (quite a few, be patient and repeat autogen {steps 6-8} as needed)
9)make sure that configure is building samba (configure output should say "Samba support: yes" at end. If this is not set to yes, you need the package "libsmbclient-dev" (e.g. sudo apt-get install libsmbclient-dev)
10)after successful compile, copy the newly built "gvfsd-smb-browse" file from the daemon/.libs/ directory to the expected location (/usr/lib/gvfs) If copy fails, you will need to be root, delete original file, then copy newly built one
11)Reboot
12) Enjoy the fix!

And now you have no trouble accessing password-protected shares?

I can confirm it. With the patch applied I can browse my share as it happened in Gutsy, a password is requested when needed. Without the patch, password protected folders are simply not shown, even if I can connect to them entering the full path manually.

Hi

When can we know for sure if a fix for this will go to the hardy mainstream? Otherwise, can the person that built the patched gvfs backend post the binary somewhere?

Thanks a lot
Thanos

Being horribly impatient, I've compiled it myself following instructions from comment {https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/207072/comments/21}. Seems that it now works and my problems are solved.

If there is popular request I can provide the binary, even here, it is only 42KB gzipped.

Yes please!!!!!

Oh yeah!

Hi

Attached is the 42K gzip'ed executable compiled for i386 32bit Hardy ONLY. It is virus free and when gunzipped has the MD5SUM of 77081f6e6dcc42448c5de355132ad582
Should be copied as per instructions in #21 (steps 10,11), and works for me up to now (no updates pending).

*** HIGH RISK DISCLAIMER ***
use at your own risk, no guarantees either expressed or implied. May fit particular purpose. Do not wish to be contacted and will reject any communications with regards to this executable. Do not use if MD5 does not match.
*** HIGH RISK DISCLAIMER ***

Added screenshot verifying MD5SUM and showing size of executable.

Work for me, thanks :)

I can confirm the bug but the patch doesn't work for me (I try to go to smb://192.168.0.2/shared, it prompts me for the username and password and then it says 'Couldn't display "smb://192.168.0.2/shared/". Error: Failed to mount Windows share
Please select another viewer and try again.').

Some things to check:

1. Make sure that the executable is replaced and no "Update Manager" has
done any updates.
2. Verify MD5 of the executable I've provided vs. the executable in the
final location

File size in bytes: 108656
File name: gvfsd-smb-browse

$ file gvfsd-smb-browse
gvfsd-smb-browse: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
for GNU/Linux 2.6.8, dynamically linked (uses shared libs), stripped

File MD5: 77081f6e6dcc42448c5de355132ad582

3. Reboot machine

If all this is done, then it seems you have an updated/predated gvfs....

On Tue, May 20, 2008 at 5:20 PM, Ondřej Cífka <email address hidden> wrote:

> I can confirm the bug but the patch doesn't work for me (I try to go to
> smb://192.168.0.2/shared, it prompts me for the username and password and
> then it says 'Couldn't display "smb://192.168.0.2/shared/". Error: Failed
> to mount Windows share
> Please select another viewer and try again.').
>
> --
> nautilus does not display samba shares for machines inside an ADS network.
> https://bugs.launchpad.net/bugs/207072
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--

Thanos

With ref to comment #31, it seems that either

a) the instructions from #21 are not followed - please retry
b) the machine is not updated or is updated with newer version of gvfs....

Some things to check:

1. Make sure that the executable is replaced and no "Update Manager" has done any updates.
2. Verify MD5 of the executable I've provided vs. the executable in the final location

File size in bytes: 108656
File name: gvfsd-smb-browse

$ file gvfsd-smb-browse
gvfsd-smb-browse: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.8, dynamically linked (uses shared libs), stripped

File MD5: 77081f6e6dcc42448c5de355132ad582

3. Reboot machine

I have already retried. The two files are the same (I also compared them via cmp). My gvfs version is 0.2.3-0ubuntu5. And yes, the update manager has done an update to nautilus (installed version: 1:2.22.2-0ubuntu6).

Just to let you know I've experienced this bug on two Hardy machines in my home. I've also got XP, Vista machines that can see and access all smb shares.

My smb.conf is very similar to the guide outlined here: http://www.ubuntugeek.com/howto-setup-samba-server-with-tdbsam-backend.html

Nautilus fails at browsing any shares. Although, I can mount a non authenticated share via terminal.

In reply to thanos,

Thanks for posting the patch. I verified md5 sum and I've renamed the old executable to gvfsd-smb-browse.bak and copied your patched one into /usr/lib/gvfs and rebooted. I've got a different problem now. Now when I try to browse the network I get this error: Failed to execute child process "/usr/lib/gvfs/gvfsd-smb-browse" (Permission denied).

Apparently I screwed up the permissions along the way. Not sure how. I did everything as root, renamed old file and copied new one to the path. I do notice when I do a list in terminal it's the only file in /usr/lib/gvfs that isn't highlighted green.

Any feedback would be appreciated.

obscure detour

obscure_detour:
The file you installed is not marked as executable. As root, do:
# chown root:root /usr/lib/gvfs/gvfsd-smb-browse
# chmod 755 /usr/lib/gvfs/gvfsd-smb-browse

and that will give the file the appropriate permissions and ownership.

Ondřej Cífka:
Your problem with mounting smb://192.168.0.2/shared/ may be unrelated to the patch, as the patch should only affect the listing of shares (so smb://192.168.0.2), not actually connecting to a share.

Apologies for the omission, it was too obvious for me that the file should become chown'ed by root:root and executable...

-rwxr-xr-x 1 root root 108656 2008-05-08 12:06 /usr/lib/gvfs/gvfsd-smb-browse

#36: So that's the problem... For me, the listing of shares is correct, but their contents are not displayed. Is that another bug? I can connect to the share from Windows and Gutsy with no problems.

Thank you darkrain42 and thanos. I apologize as I'm not as experienced as the rest :) I'll try it and comment my results.

Cheers,

obscure detour

Well it fixed it for the most part. Thank you thanos for uploading the patched file. I am able to access all my shares using nautilus. However, I still have to type in the share path.

Simply browse to "Network" and then to "Windows Network" it just thinks and errors out with; "Cannot open smb:///" or if you actually do get it to browse into "Windows Network" and click on the domain, it errors out with; "There is not a known application for this file type". Nautilus also errors out if I type in "smb://".

If I simply type "smb://host/sharename" host being either the hostname or the ip address and sharename it works perfectly. Just like Gusty :) Nautilus asks me for auth, and off we go.

Thanks again.

obscure detour

Hi

Seems to me that you're referring to another bug. What I've observed is that
the "Network" is working but not "predictably". For example, if you login
and go to nautilus -> network, it is empty. If you leave things as they are
for 5-10 minutes, then try again, there are some things appearing. I dont
browse the network, I usually map the drives directly with smbfs. However, I
did notice this behavior so maybe you should watch out for it - leave it as
it is for 5-10 minutes, then open Nautilus -> Network again....

Maybe it is dependent on the number of machines on the network? For us it is
more than 200...

On Thu, May 22, 2008 at 2:47 AM, obscure_detour <email address hidden>
wrote:

> Well it fixed it for the most part. Thank you thanos for uploading the
> patched file. I am able to access all my shares using nautilus.
> However, I still have to type in the share path.
>
> Simply browse to "Network" and then to "Windows Network" it just thinks
> and errors out with; "Cannot open smb:///" or if you actually do get it
> to browse into "Windows Network" and click on the domain, it errors out
> with; "There is not a known application for this file type". Nautilus
> also errors out if I type in "smb://".
>
> If I simply type "smb://host/sharename" host being either the hostname
> or the ip address and sharename it works perfectly. Just like Gusty :)
> Nautilus asks me for auth, and off we go.
>
> Thanks again.
>
> obscure detour
>
> --
> nautilus does not display samba shares for machines inside an ADS network.
> https://bugs.launchpad.net/bugs/207072
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--

Thanos

I swapped in the smb-browse binary from comment 28. Seems to work, but the only thing is it doesn't do is to save the passwords into the keyring. Another big problem I discovered was that if you bookmark any windows server (eg. smb://server ) that requires password in nautilus, you will SLOW DOWN your save/save as/open dialogs in programs such as gimp, openoffice, and practically any gtk programs. It will take around 5 seconds for the dialog to appear. When I removed those bookmarks, the save/save as/open file dialogs became zippy again. Having the actual share bookmarked (eg. smb://server/share) doesnt slow things down. Anyone else experiencing this?

Could someone from the delopers or maintainer group look into this bug report and act according to it's importance?!
This Bug is already open for 2 months and there is a working patch for almost as long as the bug is open. Or do we have
to wait until 8.04.1?

Please read this as a more direct "Ping!"...

the patch attached to the bug has been discussed with upstream during the ubuntu submit some days ago and has some issues, the bug is still on the list of issues to work for 8.04.1 though so it should be fixed before that but the desktop team is short in manpower and that's why it's taking a while

Hi Sebastien

Thanks a lot for the update. Please consider that it is a very fundamental
bug for all of us that use Ubuntu in a corporate Windows network - and get
daily trouble from the "wiseguys" for something "as trivial as" ... To me
bugs as this one are considered showstoppers - would be a serious reason to
switch back to the "other" OS - something I've fought off for the last 1 1/2
year.

Thanks again for listening

On Mon, May 26, 2008 at 3:34 PM, Sebastien Bacher <email address hidden> wrote:

> the patch attached to the bug has been discussed with upstream during
> the ubuntu submit some days ago and has some issues, the bug is still on
> the list of issues to work for 8.04.1 though so it should be fixed
> before that but the desktop team is short in manpower and that's why
> it's taking a while
>
> --
> nautilus does not display samba shares for machines inside an ADS network.
> https://bugs.launchpad.net/bugs/207072
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--

Thanos

And Sebastien Bacher spake on May 26, 2008 at 05:34, saying:
> the patch attached to the bug has been discussed with upstream during
> the ubuntu submit some days ago and has some issues, the bug is
> still on
> the list of issues to work for 8.04.1 though so it should be fixed
> before that but the desktop team is short in manpower and that's why
> it's taking a while

Sebastien, do you have notes on the issues somewhere? I checked the
upstream bug report and Gnome's GVFS ml. I would be quite happy to
rework the patch and, if it would be advantageous, I can work with
upstream to make it more acceptable.

Thanks for your time,
~Paul

The GVFS developers tend to hang out in #nautilus on gimpnet (IRC). I believe the issue was discussed there earlier this week, but I don't have a precise log of it. If you're really interested in working on this, please either mail our list (include the upstream bug number as a reference) or come into IRC and say hi. Be aware that it might take a while to get a reply, be patient, we work in very different timezones. For gvfs-smb, the person to talk to would be Tomas Bzatek (tbzatek on IRC), he's been doing most of the maintenance on that code. Thanks.

with latest update (27/05) bug still present. But usign nautilus->Go->position and typing smb://pc/share works.

Hi

I've re-tested after all updates (incl. kernel update) and the patch still
works. Suggest that you check the folder /usr/lib/gvfs/ for the patched
executable.

On Wed, May 28, 2008 at 10:23 AM, cRoW2k <email address hidden> wrote:

> with latest update (27/05) bug still present. But usign
> nautilus->Go->position and typing smb://pc/share works.
>
> --
> nautilus does not display samba shares for machines inside an ADS network.
> https://bugs.launchpad.net/bugs/207072
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--

Thanos

Dear John Kuang,
thanks for the solution!

>if you bookmark any windows server (eg. smb://server ) that requires password in nautilus, you will SLOW DOWN your save/save as/open dialogs in programs such as gimp, openoffice, and practically any gtk programs.

The content of my .gtk-bookmarks was this:
/media

This causes that any gtk application can not save. Not slowly, in no way.
The error was only at one user, so it seems to be a config problem, but i could not find any solution, until now... :)
If i clear the content of the file, everything works: openoffice, gimp can save (which is sometimes useful :))

Thanks again,
Steve

I had a hard time collecting all the dependencies and getting autogen to work, but after about an hour of Googling and tinkering I was finally able to get it the patched version of gvfsd-smb-browse compiled and installed. I'm sure just getting the binary posted here would have worked fine, but I generally prefer compiling things to binaries as an old Linux server administrator.

The only problems I've noticed are there is no option to save the username/password to the Gnome keyring, as has already been noted. I also noticed a definite slowdown in accessing the shares, although I'm assuming that is because of the extra overhead of determining if they need authentication. Also- when I double-click on a server, I get the username/domain/password dialog, but when I enter them- nothing appears to happen. I need to double-click on the server again to actually open it. This is probably related to the bogus "Unable to mount." issue that is in another bug.

Just my observations. Thank you so much for coming up with this patch Paul! It makes Ubuntu a lot more usable for me again.

Manual patching fails for me.. (i fail as well). Is there a chance to make an executable for hardy 64bit?

I guess I should have mentioned the other reason I didn't use the binary posted earlier- I'm running 64-bit Ubuntu.

I need to compile it on another machine, so I will try to better document the packages and steps I used to get the compile to work. I'll post that here when I can. Unfortunately there are a lot of variables in system configuration, so it is hard to give complete step-by-step instructions that will work for everyone.

I have compiled gvfs 64-bit from source, as I have described in comment 20. If you follow the instructions given here:
http://www.debian.org/doc/manuals/apt-howto/ch-sourcehandling.html
it is not that hard. Essentially you do this (you must have the deb-src lines active in /etc/apt/sources.list):

$ sudo apt-get update
$ apt-get source gvfs

... apply the patch properly, then

$ sudo apt-get build-dep gvfs

(this takes care of installing all the build dependencies).
Finally, from inside the gvfs source directory):

$ sudo dpkg-buildpackage -uc -b

(this generates all the new .deb packages)

The most difficult part is installing the patch, the other commands take care of everything else.

@Renzo-

Couldn't have said it better myself. Somewhere along the line- I missed the "build-dep" command. I was able to compile it, but it took close to an hour to track down all the dependencies by hand. Thanks for posting this.

I followed Renzo's instructions and the two problems I reported earlier have gone away. There were obviously some dependencies I missed the first time. It accesses my keyring now once I have saved my login, and opens the server when I double-click on it.

To clarify his steps for anyone new:
To apply the patch- cd to the "deamon" directory under the gvfs directory created by "apt-get source gvfs". Copy the gvfs.patch file to this folder, and then enter:
$ patch <gvfs.patch
(You can also just specify the path to the patch, it's just a bit easier to put it in the source directory.)

The "dpkg-buildpackage" command will create several new .deb files in your home folder (or wherever you started this process from): gvfs_0.2.4-0ubuntu1_amd64.deb
gvfs-backends_0.2.4-0ubuntu1_amd64.deb
gvfs-bin_0.2.4-0ubuntu1_amd64.deb
gvfs-fuse_0.2.4-0ubuntu1_amd64.deb

Since these package versions are probably already installed, you will need to "reinstall" them, either through gdebi or using apt. For example:
$ sudo apt-get install -y --reinstall gvfs gvfs-backends gvfs-bin gvfs-fuse

Just a final note to the last post of wolfwitch:
The apt-get install command does not work for local packages, to install the new debs you have to use this:

$ sudo dpkg -i gvfs_0.2.4-0ubuntu1_amd64.deb gvfs-backends_0.2.4-0ubuntu1_amd64.deb gvfs-fuse_0.2.4-0ubuntu1_amd64.deb libgvfscommon0_0.2.4-0ubuntu1_amd64.deb

Yep, it works now that's patched (using gvfs 0.2.3). The only thing different i've noticed is a slightly slow access time, as wolfwitch stated (about 3~4 seconds).
Many thanks to the patch maker, poster, and all users that helped. Hope to see this officially fixed soon.

Patch works great here, thanks guys. Somebody needs to get on the ball and get this pushed into the updates, this was killing me on my work network.

Unfortunately a gvfs update hit the repositories in the last couple of days. This "fixed" my patched version, and the version in the repositories is still broken. I can't believe this is taking this long to fix.

I'm not blacklisting gvfs from updates because I keep hoping it will get fixed, but for now- I need to go through the patch process again.

upstream spotted issues in the current changes but nobody is actively working on gvfs smb or knowing the code well enough to fix that easily at the moment apparently

On Mon, Jun 09, 2008 at 02:28:45PM -0000, Sebastien Bacher wrote:
> upstream spotted issues in the current changes but nobody is actively
> working on gvfs smb or knowing the code well enough to fix that easily
> at the moment apparently

Well, this issue has been discussed on the Samba upstream mailing list, so I
think someone is working on it. I don't know the current status though, the
mailing list thread died out a few days ago.

Hi, that's me working on http://bugzilla.gnome.org/show_bug.cgi?id=529277 but it touches this too. I don't really have much time and failed to find a fix that doesn't require moderate to major code shuffling :( There is an interesting message on the gvfs mailing list http://mail.gnome.org/archives/gvfs-list/2008-May/msg00005.html if you're interested.

Hi

Just to add I've used the latest instructions on this thread (apt-get source
etc, comment from Renzo Bagnati above) to download the latest gvfs source
code, and guess what; *the original patch still works*....

I suggest that anyone still experiencing the problem and his patched
executable got overwritten, goes the same way....

--

Thanos

I have a question that does not directly concern this bug but is somewhat related. On my system, there is some inconsistency in the way the icons of the machines containing the shares are displayed in Nautilus. Most of the time, they are displayed correctly, i.e. inside the workgroup. However, sometimes they also appear alongside the Windows Network icon, i.e. just after clicking on "Network".

Can anybody explain this inconsistency? Could it possibly point to another bug in Ubuntu 8.04?

darkrain42, I've had an opportunity to review your patch, and it looks altogether correct to me (with one quibble over the error message presented on authentication failure). Although upstream has expressed concern about code duplication in the implementation, the two backends already share more than half their code, and this patch brings them closer to parity. Eliminating this code duplication is not something we should strive for in an SRU; though for my part, I wonder why this was ever done as two separate backends in the first place given the obvious overlap.

However, even with this patch applied, I don't see correct behavior for the share list when trying to connect to a samba server joined to an AD realm.

TEST CASE:

1. install the samba, smbclient, and winbind packages.
2. configure your system to act as a member of an AD realm, and enable the [homes] autoshares; e.g., in smb.conf:
  [global]
        workgroup = CANONICAL
        realm = CANONICAL.LOCAL
        security = ADS
        idmap backend = tdb
        idmap uid = 10000-20000
        idmap gid = 10000-20000
        template shell = /bin/bash
  [homes]
        comment = Home Directories
        valid users = %S
        create mask = 0700
        directory mask = 0700
        browseable = No
3. join your machine to the AD realm with 'net ads join' (https://help.ubuntu.com/community/ActiveDirectoryWinbindHowto#head-bbf631898fac0418a653cae2f0d4a1344ca8dfc2)
4. sudo /etc/init.d/samba restart && sudo /etc/init.d/winbind restart
5. grab a Kerberos tgt for the account in the AD realm with the same name as your login user by running 'kinit'. (You do not have to configure your local machine for AD logins for this to work, but the username must match between the AD realm and your local system.)
6. test with smbclient that the home share for the user is visible; i.e., "smbclient -L localhost -k" should return in the list of shares a share with the same name as the user. (using "smbclient -L localhost -N", i.e., anonymous connections, the share will not be visible.)
7. test whether nautilus sees this same share by running 'nautilus smb://localhost/'.

EXPECTED RESULTS: gvfsd-smb-browse will transparently use the existing Kerberos credentials when retrieving the browse list for the server, and a folder will appear in nautilus with the same name as the user.

ACTUAL RESULTS: gvfsd-smb-browse fails to use the Kerberos credentials, and the user's home share does not appear in the list.

Steve, as described in comment 12, I'm using kerberos authentication inside an ADS network and I have no problems with nautilus and gvfs. However my setup is different from yours. The smb.conf is like this:

[global]
        workgroup = LAB
        realm = MYDOMAIN.COM
        netbios name = %h-DEB
        server string = %h-DEB (Samba %v, Ubuntu)
        security = ADS
        password server = dhcpias1.mydomain.com
        restrict anonymous = 2
        client NTLMv2 auth = Yes
        client lanman auth = No
        client plaintext auth = No
        log file = /var/log/samba/log.%m
        os level = 0
        preferred master = No
        local master = No
        domain master = No
        idmap domains = LAB
        idmap config LAB: default = yes
        idmap config LAB: backend = rid
        idmap config LAB: range = 100000-1000000
        template shell = /bin/bash
        winbind separator = _
        winbind enum users = Yes
        winbind enum groups = Yes
        winbind use default domain = Yes
        winbind refresh tickets = Yes
        winbind offline logon = Yes
        invalid users = root
[Share]
       comment = %h-DEB_Share
       path = /home/LAB/adsusername/Share
       valid users = LAB_adsusername, "@LAB_domain users", @users
       force user = LAB_adsusername
       read only = No

The PAM configuration has been changed by using this line in /etc/pam.d/common-auth:

auth sufficient pam_winbind.so krb5_auth krb5_ccache_type=FILE cached_login

This means that the login user is a domain user (not a local user) and that it automatically acquires a kerberos ticket.
With this setup I'm able to browse with nautilus all network shares (including the one of the local workstation) even without the gvfs patch from darkrain42. So it seems that in my case gvfs is correctly using kerberos credentials and I wonder if your problem may be related to something else than the gvfs patch.
If necessary, I can post the complete configuration of my workstation, but at the moment I will not be able to do other test inside the ADS network until next week.

Renzo,

You're right; if I use the unmodified gvfs-backends package from hardy-updates, then I don't see this problem with AD authentication - it's only introduced when I apply Paul's patch.

I do have an updated version of that patch which restores correct behavior in AD environments.

The only question that remains is, what should the correct behavior be in the absence of kerberos credentials (prompting for username/password, vs. automatically connecting anonymously), given that we don't really want to be architecting a completely new UI in an SRU? You have argued that a username/password prompt should be presented. I'm inclined to agree.

BTW, the reason on the server side that the shares are not displayed at all when connecting to your samba server is that you're using the 'restrict anonymous = 2' option. I don't know why that's part of the Ubuntu AD howto; it's not required for AD integration, its only effect is to prevent one from retrieving a list of shares anonymously. As a workaround, you could remove this option on your samba servers, and the corresponding (and non-default) registry setting on your Windows servers, if you're comfortable with share lists being retrievable without authentication.

In any case this would still be a problem for user home autoshares, so I've attached the patch to gvfs 0.2.4 which implements this fallback sequence (kerberos -> u/p -> anonymous).

Sebastien, since I'm not seeing the issues in the current patch, it would be helpful to have a concrete reference to the problems that upstream finds with it so that we can get those resolved.

Thank you, Steve, for the patch and for your other suggestions. I think that the patch is implementing the right fallback sequence. I will be able to test it when back at work.
I will also surely remove the 'restrict anonymous = 2' option from samba configuration, although it is not causing problems after a kerberos authentication. In any case I don't have problems in allowing anonymous browsing.

I had same problem. But it seemed be solved by installing all packaged have string "gvfs" on aptitude(Package Manager).

hirameki, the only gvfs package in package manager that i didnt have was libgvfscommon-dev. So I installed that too and it still doesn't work.

uploaded to intrepid

 gvfs (0.99.1-0ubuntu2) intrepid; urgency=low
 .
   * debian/patches/80_samba_browsing_authentification.patch:
     - gnome bugzilla change to allow shares when authentification is required,
       the code try anonymous connections before asking for a password though
       so it doesn't solve the case where anonymous and login are authorized
       but give access to different ressources, see comments on
       http://bugzilla.gnome.org/show_bug.cgi?id=524485 for references
       (lp: #524485)

upstream comment:

"- code duplication is an issue but as temporary solution I'm fine with this.
There are more design changes underway and users can't wait anymore. Later I
plan to rip out some code and clean the code for both backends.
- the patch as is is bad due to recent kerberos change - yes, libsmbclient
expects *some* username, otherwise it refuses to do kerberos tries. However
removing anonymous auth attempt is preventing me to get list of workgroups and
machines at all.
- sharing active login credentials with the smbbrowse and the smb backend can
be partially handled by gnome-keyring, in case when user saves password to
keyring. This needs more work still.

I'm attaching updated patch, doing authentication tries in three stages:
  1. kerberos (current username, no password)
  2. anonymous
  3. ask for password and loop until success or cancelled

However I'm little afraid here due to number of tries we do before asking user
for credentials. This can cause account or machine being locked out or banned
for some time. Partial solution might be to look at krb5 api and somehow detect
active ticket for the particular machine we're trying to connect to.

Browsing samba network is slow due to number of attempts we do (each attempt
can take 5-10 seconds or more).

Please test this updated patch, I will backport some changes made here to smb
backend then."

Apologies if I am a) stupid, b) ill- or un-informed c) an extremely un-typical user:

It sounds OK to me provided the availability of an anonymous login doesn't stop me logging in with credentials if that is what I want to do.

In school, we have some very unsophisticated users who just need it to work. If they are pupils, an anonymous login is possibly all they require to get to the resources that have been put 'on a plate' for them by a member of staff.

We also have some very unsophisticated members of staff who just need it to work, but who need write access to the same share. So their credentials must be used. And, sadly, it does have to be the same share. We tried giving staff a back door - but then when they telling students where they had put the resources, they only knew the back door way to them......

We have a sophisticated network, with separate authentication domains for different academic departments. This has the advantage of resilience, with the ability for a department to run in the vacations when other parts of the campus may be without power if major work is being done. There is no one 'server room' the whole campus is dependent on. But in normal circumstances staff and pupils may need access to their shares on domains other than the one their client is joined to.

At present, if the credentials used by a client to log in to the 'home' domain match those required for the foreign domain (user name and password) the connection just works. If the credentials do not match, a dialogue asks for new credentials to be used for the foreign domain. Whilst a pupil does not need any privileges to read-only the public material on a foreign domain, a member of staff will if the intention is to update, edit or add to the material.

So far, we can get away without anonymous login, because pupils can log in with the foreign credentials if we make it necessary. But the problem is visitors - either substitute teachers or visiting pupils from consortium schools, or visitors to out-of-hours events (when there are no technicians on site) who bring their own laptops.

So ideally, we need anonymous access for users who do not have any credentials, and who may be working on a client computer that is not a member of one of our domains.

The current Desktop-Places dialogue "Connect to Server..." is a bit clunky, but would be OK if the mounts could be made persistent. If the mount has to be redone each time the client reboots, my unsophisticated staff will need a facility similar to that in Windows, which will remount a share in the same way it did last time, if they are to enjoy the delights of Ubuntu.

Sorry if all this is stating the obvious, but I would rather look silly now, than find out I should have said so earlier!

Thanks

Chris

Chris,

In fact, none of these patches affects authentication to the share itself; so far here we're only dealing with the authentication used when browsing share lists on servers. So I don't think this should be a problem for you?

In any case, the patch that's being considered in the end detects the case of an empty share list when connecting anonymously and prompts for authentication; so that seems to solve the case where anonymous users can't query the share list, without imposing any UI problems for those who do want to continue to connect anonymously.

Accepted into -proposed, please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

This causes a SEVERE regression for me.
Every Gnome "open" dialog hangs for about two minutes now before displaying anything. This also affects the Gnome main menu and the "Applications Places System" menu. Trying to open it for the first time freezes *all* panels, including the window list.

It looks like this is because i have SMB shares bookmarked that are unreachable right now.

Attached is tcpdump output taken when File->Open in gedit.
Notes:
192.168.42.5 is me
10.87.74.1 is a bookmarked SMB server that is unreachable (VPN not connected)
192.168.13.4 is a bookmarked SMB server that is unreachable (different physical network i'm not connected to)

what do you call gnome main menu? are you sure that's due to the update? what gvfs process are running? the change is limited to the gvfs smb browser method and should not impact on other components

Main Menu: Right-click on a panel -> "Add to panel" -> "Main Menu"
(a single-icon windows-style start menu with "Applications Places System" inside)

Yes, i'm sure.
I upgraded to hardy-proposed and experienced this. That's a bunch of updates, so i
downgraded to hardy + hardy-updates + hardy-security again (problem gone),
updated only gvfs and gvfs-backends to hardy-propsed (problem there),
downgraded them again, problem gone.

gvfs version before downgrade is
0.2.4-0ubuntu2

The "Applications Places System" menu displays bookmarks under "Places", IMO that's why it's affected.

Have you tried reproducing it? Add smb://10.58.13.6/ (or any unreachable net) to your nautilus bookmarks.

Wow!
I applied the proposed patch last week and all are working fine... but, if I reproduce Jakob case (bookmark a unreachable machine) all Gnome freezes (startup, open dialogs, etc).

This problem is like windows machines with shortcuts to unreachable machine or mapped drivers.

When I back to 0.2.4-0ubuntu1 this problem disappears, but I back to share display problem. =(

Reported upstream: http://bugzilla.gnome.org/show_bug.cgi?id=524485#c15

Jakob,

Yes, from your description alone I can clearly see where the bug is. The patch to gvfs causes an automatic retry if kerberos authentication or anonymous connections fail - without looking at why the connection failed. That means that in the event of a network timeout, the user has to wait through three separate network timeouts! So we need to be checking the value of errno here, to make sure it's set to EPERM and not to some other value before retrying.

Attached is a revised patch that fixes this particular problem. I've tested it with a simple nautilus smb://non-existent-server/ command, but I'm not a nautilus power user - could you describe to me exactly how you set up your shortcuts, so that I can test with that scenario as well?

I am also seeing an issue where I'm being prompted for a password when connecting to servers that do allow anonymous share lists, so evidently there's another bug here that still needs to be tracked down. Marking this as 'verification failed'.

Yet another updated patch; the counter in the auth callback assumed that the callback would only be called once for each smbc_opendir() attempt, which means that each authentication method (kerberos, anonymous, password) was being tried twice for no reason.

In traces, I still see a problem that the first time do_mount is called, it loops through without ever prompting the user for a username and password, so it still takes us twice as long to get to a password prompt as it should (i.e., 4 connections to the server instead of 2). I'm not sure if this is a problem with the patch or a pre-existing problem with gvfs-smb-browse; will investigate further.

WRT my earlier comment about being prompted for a password when connecting to servers that do allow anonymous share lists - I'm not now able to reproduce this problem, so I guess we should consider that part "resolved".

How to add the nautilus bookmark of death (WARNING: Do this a new user account, you will probably lose gnome settings and stuff when doing Ctrl-Alt-Backspace to recover):
1) Open any random folder with nautilus
2) menu "Bookmarks"->"Add bookmark"
3) "Bookmarks"->"Edit Bookmarks"
4) Put smb://10.58.13.6/ in "Place"
5) Select the bookmark "smb" (it's renamed automatically) from the Bookmarks menu
6) All gnome panels freeze although nautilus look okay

Notes: The panels don't even recover after 2 minutes when triggering the bug like that.
When you Ctrl-Alt-Backspace and login again, the panels are gone, yes GONE, icons on the desktop but no panels. Had to rm -Rf ~/.* to recover.
So... *** ONLY TRY IT ON A EMPTY USER ACCOUNT ***

ok. I can reproduce the lockup problem; it appears that something related to the bookmarks is triggering constant attempts to remount the bookmarked resource when the mount fails, and unlike in earlier versions of gvfs, the patched version will return a failure when the mount fails - before it would just fail silently.

What's not clear to me is why the same problem doesn't occur if you create a bookmark pointing to an smb /share/ as opposed to an smb /server/. Evidently there is some key difference between the smb and smbbrowse backends that has been overlooked.

The problem of having to make four SMB connections to get to a password prompt, instead of two, is a matter of deep dbus magic, from what I can tell; the first run through, a dbus ID is missing that's needed in order to spawn the dialog, so the connection fails until the second time when this dbus ID is provided.

No luck figuring out why bookmarking of shares and servers behaves so differently.

Thanks for your commitment, Steve.
IMO another key point is that the panels SHOULD NOT FREEZE when some gvfs operation takes longer than usual. (usual: so short, the user won't even notice it, that's < 50msec).

Even when you bookmark an unreachable share (say, smb://10.11.12.13/asfd/) and select it from the "Places" menu, EVERY PANEL hangs until you get some timeout dialog box. I can't use the window list because i clicked a slow smb server? ZOMG.

So the (a?) key difference between smbbrowse and smb seems to be that smbbrowse declares its sub-entries as "mountable". Other unavailable bookmarks don't cause stalls, and neither does smbbrowse if I comment out the mountable support. On the other hand, if I comment out the mountable support, the shares are no longer browseable, so that's not much of a solution!

I think that the correct fix here may be to not actually perform the full login check at the "mount" stage and returning a simple success, deferring the password handling until the cache update stage. Since an smbbrowse record is flat, the two should be nearly equivalent in the general case, possibly differing only here in the panel's bookmark handling.

However, I'm not sure I have time to implement such a revised patch in time for the 8.04.1 point release. I fear we may have to roll back the gvfs fixes in the short term and try again after .1 is out.

I'm not sure why the shared need to be mounted to query the display name but that seems to be buggy, delaying the password handling when it's really required would make sense though.

 the gnome-panel code should also use the async gio api to avoid such issues, the changes should not be too complicated but that's not likely going to be changed before 8.04.1 now, and libgnomeui seems to have similar issues too

the blocking call is smbc_opendir apparently, if the code can't be easily changed maybe one option would be to revert to the patch variant which tries authentification before anonymous for 8.04.1, that would create an usuability regression for users who browse network which don't require authentification though since they would get lot of password prompts not required

further comments:
- my earlier attempt at reducing the number of authentication attempts was a red herring. The authentication callback is called twice for each connection attempt, for some reason, so my suggested patch could actually cause problems for kerberos auth.
- the auth callback is called regardless of whether Kerberos tickets are currently available. This is, arguably, a bug in libsmbclient; since the callback deals only in domain/username/password, the current method of "forcing" kerberos authentication results in a spurious username-based authentication attempt. We can work around this by playing with smbc_setOptionFallbackAfterKerberos() before and after the first connection attempt.
- after far too much time looking at this code, I now have a handle on how to try to move the connection out of the mount operation. Patch to follow shortly (I think).

So that patch was a failure; it successfully postpones the authentication, but a) nautilus will open an empty window and spin if you try to connect to a server, before the authentication is completed and therefore leaves a blank window behind, and b) it will never give you a password prompt so the only authentication methods available are kerberos and anonymous - putting us back where we were at the beginning anyway. The lack of password prompt may be the dbus ID issue mentioned earlier, which prevents the password request from being passed up correctly.

I'm going to hang on to this patch in case someone wants it, but I'm not going to pursue that approach any further myself; I don't even know where to begin on the dbus ID question (though that seems like it's also an important bug to fix), and I think the empty-nautilus-window-on-failure issue is probably inherent to this solution, which is undesirable.

Sebastien, you mentioned that the mounting is being done in order to query the display name. Is there somewhere I could read up on exactly what's happening here when querying the display name, that might suggest another solution? From what I see, the do_mount call is setting the display name, but I guess gnome-panel isn't satisfied with that because the mount job as a whole fails.

At any rate, attached is a replacement version of the 80_samba_browsing_authentification.patch, which incrementally improves on the previous versions by reducing the number of TCP connections needed to complete password authentication. It doesn't improve things enough to be worth pushing to -proposed on its own, though, without some resolution of the gnome-panel issue.

I have same problems.
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....

gvfs 0.2.4-0ubuntu2 is now rejected out of hardy-proposed due to the unresolved regressions.

"I have same problems.
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...."

i have the same problem it very anoying
i have 3 ubuntu hardy machines that share that problem
also i can not see the computer (MSserver 2003) when opening the workgroup
it seems fine when browsing XP computers (computers on workgroup and shares)

I have also the same problems. Very anoying!
Nautilus does not display the windows shares when opening the workgroup.
Typing smb://servername/sharename in ubuntu works, also mounting is no problem.

Is there a solution for this problem?

Not sure if this bug is going down a different track from its 'duplicate' 241578?

Just a hint that 241578, as described, worked absolutely fine in the LTS release of Hardy and stopped working after a specific automatic update.
It might be worth looking at the changes made in that update - provide that they are not massively different of course.

I have put this message here in case 241578 is no longer being looked at.

Gareth,

Bug #241578 is marked as a duplicate of bug #207072 because the former bug is actually fallout from the attempt to fix the latter, in gvfs 0.2.4-0ubuntu2. If you have this version of gvfs installed, please downgrade to the version of gvfs in hardy-updates, 0.2.4-0ubuntu1.

If your issue does not go away with the downgrade of gvfs, then it's not the same as the bug reported by the submitter of bug #241578. In that case, please open a separate bug report for your issue.

thanks Steve
I am on gvfs 0.2.4-0ubuntu1 and Windows Network now shows MSHOME and WORKGROUP and I can access the Windows shares within MSHOME successfully. I also no longer get the duplicated mount icons on the desktop when clicking on one of them.
A couple of small 'wrinkles' remain - not a problem to me but might help refine the solutions?

1. I still could not see one of my NAS drives in WORKGROUP but changed it to MSHOME and can now see it as well.

2. Thunderbird used to share its configuration and mail files from the Windows machine automatically - I now have to browse to/mount the windows share first - then it works OK.

A workaround while waiting for this to be patched is to use via a terminal
smbtree -U=trichardson%PASSWORD -k

The % sign is just that: a % sign
put your domain password in place of PASSWORD

This let's me see the shares.

This bug is more severe than the title implies. This affects not only Active Directory networks but also any standalone Windows XP (possibly all Windows versions) machines that share files with authentication turned on. By default, Windows XP shares are configured in "simple file sharing" mode which has no authentication. If you need write access to your shares and leave the default "simple file sharing" mode enabled (which it seems most everyone does), then any computer on your network can access and delete all the files in your share. It may be thought of as a bit overkill to require authentication on a small LAN that is in your control, but consider all the laptops that are set up with unprotected shares and then are taken to a public network such as at a coffee shop.

Instead of opening a new bug, I will add to this one. With Intrepid A3, I can browse some servers on our AD network but no shares are shown. If I try to map a connection manually, it is unsuccessful.

Confirmed on Ubuntu 8.04.1 I have not tried the patch fix, primarily because i am not competent with compiling source, and I do not have proposed enabled because of a bad kernel in proposed. I can see all of the computers in the Workgroup, but I have to manually type in the path to the folder to see it. Willing to add any necessary files or pastes to help fix the problem.

After a recent GVFS update the fix posted here doesn't work anymore and the update itself did not fix problem with samba shares either :((

I'm a little confused. This seems like a pretty major bug. Has it been fixed? I'm using intrepid and still have this problem. Is there a good chance it will be fixed by the final release?

Danny, you are right, its an upstream major bug. See http://bugzilla.gnome.org/show_bug.cgi?id=524485#c26

The 2.24.0 gvfs version is planned to be released on September 24th.

Please correct me if I'm wrong: We will have to wait until Gnome release this and then wait ubuntu to propagate the changes.

If this bug has a 'final' proposed fix is there a chance someone could create a binary of the patch for i386 and post it (along with instructions on how to 'install' the patched library on ubuntu 8.04.1)?

That way we all could be testing the fix now and confirming it fixes all the issues, not just part of the problem.

I do not feel confident enough myself to build and install the patched library, although I know it should be possible. I am sure others would like to help test the fix as well.

Thank You.

I don't where you are about this bug repairing , I just want to say , it 's seem problem is ntfs

Hi everyone.

I'm very sad with this. Several months ago I was trying to impress my boss, showing the benefits of Ubuntu and the good integration with AD networks... He was quite happy until I couldn't find the way to see the shared folders in WinXP computers. Now, Ubuntu 8.10 is closer than ever and this problem is still alive. Every day I update my Ubuntu 8.04, just hoping to see THIS BUG exterminated for once and all...

Regards.

Turbo.

Me too.

After the fantastic performance of Gutsy I stuck my neck out and said the Linux desktop, with all the advantages of open source and collaborative technology, was now suitable for my workplace.
The various problems with Samba access have set back my credibility as well as the idea of client Linux systems. The only good news is that I froze everybody else on Gutsy, and have stopped any new installations. So people can still see how good it can be.
It is a real shame to see something so right develop into something so wrong that then takes so long to get right again. And the fact that something can go wrong so permanently leaves end users worried that they cannot rely on Open Source brands.

Apologies for putting this on the bug thread - but however and wherever it went wrong, you guys and gals are the ones who can mend it - or get it mended. Thank you for being there, and for the work you do.

The gvfs patch mention above also fixed this for me. No other solutions worked. I used the binary replacement method.

Does anyone think that they can get the working patch to the repos? I too
am not confident in compiling things for the most part; and it seems that
this patch works; so why not just stick it in now, and then work on it from
there? At least this way we will be able to use Samba while the problem is
being worked on, just my $0.02. Thanks.

In our Lord Jesus Christ,
Louie Cunningham

It is for us to become holy here and now, for we cannot be certain whether
we will be here this evening.
- St. Maximillian Kolbe

On Wed, Sep 17, 2008 at 12:07, Tab <email address hidden> wrote:

> The gvfs patch mention above also fixed this for me. No other solutions
> worked. I used the binary replacement method.
>
> --
> nautilus does not display samba shares for machines inside an ADS network.
> https://bugs.launchpad.net/bugs/207072
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in gvfs: Confirmed
> Status in "gvfs" source package in Ubuntu: Triaged
> Status in "nautilus" source package in Ubuntu: Invalid
> Status in gvfs in Ubuntu Hardy: In Progress
> Status in nautilus in Ubuntu Hardy: Invalid
>
> Bug description:
> Binary package hint: nautilus
>
> Using hardy beta, when I browse with nautilus other machines in an Active
> Directory (ADS) network, some of them do not show their shared folders.
> The ADS integration of the hardy box was done using winbind, kerberos and
> PAM libraries, essentially as described here:
> https://help.ubuntu.com/community/ActiveDirectoryWinbindHowto
> The network contains mostly windows clients, but also several linux boxes,
> which were joined to the ADS domain with the command: 'net ads join'.
> Machines running windows XP, windows 2003 and samba show '0 objects' in
> nautilus, but after inserting the complete path (eg.: smb://server/share)
> the folders can be accessed after the password prompt.
> Machines running windows 2000 show their folders regularly.
>
> Here is a detailed description of what happens:
>
> Case 1
> ---------------------------------------------------------------------------------
> Browsing from hardy-beta a machine running ubuntu-gutsy server.
>
> In a terminal window:
>
> renbag@vm-hardy:~$ smbclient -L gutsy-server
> Password: (password inserted here)
> Domain=[LAB] OS=[Unix] Server=[Samba 3.0.26a]
> Sharename Type Comment
> --------- ---- -------
> IPC$ IPC IPC Service (gutsy-server (Samba 3.0.26a, Ubuntu))
> share Disk gutsy-server_share
> Domain=[LAB] OS=[Unix] Server=[Samba 3.0.26a]
>
> In Nautilus:
>
> Open Network --> Double-click on the 'LAB' icon (Domain) --> All machines
> are displayed;
> Double-click on the 'gutsy-server' icon --> after a while, Nautilus returns
> '0 objects', without asking for a password;
> Insert the full address (smb://gutsy-server/share) --> a password is
> requested and the share content is displayed.
>
> Case 2
> ---------------------------------------------------------------------------------
> Browsing from hardy-beta a machine running Windows XP
>
> In a terminal window:
>
> renbag@vm-hardy:~$ smbclient -L XP-ACQ
> Password: (password inserted here)
> Domain=[LAB] OS=[Windows 5.1] Server=[Windows 2000 LAN M...

Does anyone think that they can get the working patch to the repos? I too am not confident in compiling things for the most part; and it seems that this patch works; so why not just stick it in now, and then work on it from there? At least this way we will be able to use Samba while the problem is being worked on, just my $0.02, on the thought.... Because at least we can get samba to work correctly if the patch is up in the repos...

finally, the v2.24 released.
http://blogs.gnome.org/metacity/2008/09/22/2-24/

now i'm curious if they fixed this bug (and of course lot more bugs too)

Here is a compiled binary for <b>amd64</b> of the first issue in this thread. It does not solve the whole issue but might help some people get by until an actual fix is released. Again this only only solves the issue of browsing shares on a Windows machine from a Ubuntu workstation that is not joined to the domain and using kerberos.

I am running Ubuntu 8.04.1 32 bit and this bug hit me suddenly this morning. Up till now, I was able to browse my office networks smb shares without difficulty. As of this morning, none of them work. All 4 of my ubuntu workstations are affected. I have saved bookmarks to places on the network that stopped working. I found that I had to change the network path, for example, from smb://server/pictures to smb://10.0.0.5/pictures that finally got all of them working again. I am still unable to browse my network with the Places > Network GUI. It shows the network and then the workgroup, but nothing beyond that. It eventually times out. I was not planning to upgrade my office machines to 8.10, preferring to stay with the LTS version, but if I need to upgrade to fix this, I will. This is a nasty regression that needs to be fixed.

That sounds like a different issue. Maybe a browser master problem. This bug affect specificly browsing the shares on the machines not the entire domain/workgroup.

----- Original Message -----
From: Martin G Miller <email address hidden>
To: <email address hidden>
Sent: Thu, 25 Sep 2008 15:34:33 -0500 (GMT-05:00)
Subject: [Bug 207072] Re: nautilus does not display samba shares for machines inside an ADS network.

I am running Ubuntu 8.04.1 32 bit and this bug hit me suddenly this
morning. Up till now, I was able to browse my office networks smb
shares without difficulty. As of this morning, none of them work. All
4 of my ubuntu workstations are affected. I have saved bookmarks to
places on the network that stopped working. I found that I had to
change the network path, for example, from smb://server/pictures to
smb://10.0.0.5/pictures that finally got all of them working again. I
am still unable to browse my network with the Places > Network GUI. It
shows the network and then the workgroup, but nothing beyond that. It
eventually times out. I was not planning to upgrade my office machines
to 8.10, preferring to stay with the LTS version, but if I need to
upgrade to fix this, I will. This is a nasty regression that needs to
be fixed.

--
nautilus does not display samba shares for machines inside an ADS network.
https://bugs.launchpad.net/bugs/207072
You received this bug notification because you are a direct subscriber
of the bug.

Still not working in Intrepid Beta. This is ridiculous.

Agreed/Ditto. I've pretty much given up on it. The best "solution" I've found is to set up shortcuts to every share I use, since browsing is pretty much impossible. This isn't really Ubuntu's fault since it is a problem with an upstream vendor, but it's a bit ridiculous that this bug has been know about for almost seven months now and hasn't been fixed. It's been reworded and duped all over the place, and it seems it's being spun more than fixed.

fusesmb is a fairly decent work around from the home user perspective. In
light of the fact that upstream isn't addressing the fix or at least it
isn't available yet, does anyone know of a way to ask Canonical to downgrade
to the version of samba that worked properly in Gutsy? Would it be THAT
much of a dependency problem?

On Wed, Oct 8, 2008 at 15:03, wolfwitch <email address hidden> wrote:

> Agreed/Ditto. I've pretty much given up on it. The best "solution" I've
> found is to set up shortcuts to every share I use, since browsing is
> pretty much impossible. This isn't really Ubuntu's fault since it is a
> problem with an upstream vendor, but it's a bit ridiculous that this bug
> has been know about for almost seven months now and hasn't been fixed.
> It's been reworded and duped all over the place, and it seems it's being
> spun more than fixed.
>
> --
> nautilus does not display samba shares for machines inside an ADS network.
> https://bugs.launchpad.net/bugs/207072
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
I've discovered the key to success is to never give up. You either learn
the right way, or you run out of ways to do it wrong. A win/win situation!

changing GNOME to use gnomevfs rather than gvfs would basically means downgrading some hundred applications and the GNOME desktop to its gutsy version, you can as well use gutsy if that's to do that change

On Wed, Oct 08, 2008 at 07:15:52PM -0000, John Toliver wrote:
> fusesmb is a fairly decent work around from the home user perspective. In
> light of the fact that upstream isn't addressing the fix or at least it
> isn't available yet, does anyone know of a way to ask Canonical to downgrade
> to the version of samba that worked properly in Gutsy? Would it be THAT
> much of a dependency problem?

This is not a Samba bug, it's a gvfs bug. There is no version of gvfs
available that handles this case correctly, and the previous VFS layer for
GNOME, gnome-vfs, is also not an option because it's abandoned and lacks
integration with the current releases of GNOME.

--
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>

On Wed, 2008-10-08 at 19:58 +0000, Sebastien Bacher wrote:
> changing GNOME to use gnomevfs rather than gvfs would basically means
> downgrading some hundred applications and the GNOME desktop to its gutsy
> version, you can as well use gutsy if that's to do that change
>
Or use the about to be released Debian Lenny, which has kept gnomevfs
probably because of some still open bugs in gvfs. I used Hardy, so I
miss some features of gvfs after moving to Lenny, but I think the Debian
developers made on balance the right choice for their release. Certainly
for me: I use my laptop in an office with a Windows server.

I might just give that a try... thank you.

On Wed, Oct 8, 2008 at 18:13, Tim Richardson <email address hidden> wrote:

> On Wed, 2008-10-08 at 19:58 +0000, Sebastien Bacher wrote:
> > changing GNOME to use gnomevfs rather than gvfs would basically means
> > downgrading some hundred applications and the GNOME desktop to its gutsy
> > version, you can as well use gutsy if that's to do that change
> >
> Or use the about to be released Debian Lenny, which has kept gnomevfs
> probably because of some still open bugs in gvfs. I used Hardy, so I
> miss some features of gvfs after moving to Lenny, but I think the Debian
> developers made on balance the right choice for their release. Certainly
> for me: I use my laptop in an office with a Windows server.
>
> --
> nautilus does not display samba shares for machines inside an ADS network.
> https://bugs.launchpad.net/bugs/207072
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
I've discovered the key to success is to never give up. You either learn
the right way, or you run out of ways to do it wrong. A win/win situation!

Another option would be using konqueror with KDE instead of gnome and
friends for browsing windows shares. I sometimes use konqueror, that
works too.

But I also wish, that this problem gets fixed.

On Thu, 2008-10-09 at 06:36 +0000, gerstrong wrote:
> Another option would be using konqueror with KDE instead of gnome and
> friends for browsing windows shares. I sometimes use konqueror, that
> works too.

Yes I briefly looked at KDE as well. Problem with it is when you try to
stream a video etc. across your network, KDE tries to download the whole
thing in cache before beginning to play it. Really annoying.
--
I've discovered the key to success is to never give up. You either
learn the right way, or you run out of ways to do it wrong. A win/win
situation!

Bug is also in Ubuntu daily-live of october 11th.

Hope that gvfs will be fixed! On Samba workstations, the shares can be viewed and you can still write manually the direction to enter...

I just got an update to samba and it seems to have fixed this for me. I
don't want to get everyone's hopes up but give it a try. The update also
came with a bunch of things, like a kernel update, etc.

On Sat, 2008-10-11 at 08:59 +0000, gerstrong wrote:
> Bug is also in Ubuntu daily-live of october 11th.
>
> Hope that gvfs will be fixed! On Samba workstations, the shares can be
> viewed and you can still write manually the direction to enter...
>
--
I've discovered the key to success is to never give up. You either
learn the right way, or you run out of ways to do it wrong. A win/win
situation!

On Sat, Oct 11, 2008 at 12:10:01PM -0000, John Toliver wrote:
> I just got an update to samba and it seems to have fixed this for me.

If a samba update fixed anything for you, it was not this bug. This is not
a bug in samba.

--
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>

I know this has been stated repeatedly, however when I use the ubuntu (or
nautilus) network icon to browse (instead of the one created by fusesmb), I
no longer have the problem viewing the shares on other machines. Nothing
else on my setup has changed. I will continue to test my network browsing
as I move between different networks. In any case, thank you much for the
update.

On Sat, Oct 11, 2008 at 13:19, Steve Langasek
<email address hidden>wrote:

> On Sat, Oct 11, 2008 at 12:10:01PM -0000, John Toliver wrote:
> > I just got an update to samba and it seems to have fixed this for me.
>
> If a samba update fixed anything for you, it was not this bug. This is not
> a bug in samba.
>
> --
> 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>
>
> --
> nautilus does not display samba shares for machines inside an ADS network.
> https://bugs.launchpad.net/bugs/207072
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
I've discovered the key to success is to never give up. You either learn
the right way, or you run out of ways to do it wrong. A win/win situation!

In my case, the problem still remains. All Samba-Shares even from other
Linux-Computers can be viewed, but all the Shares of Windows-PCs are not
seen. In Konqueror, both can be viewed.

What I don't understand, that it requests the password after entering
into the share, not before browsing to PC. In Konqueror you must type it
when you enter into the Computer to view all the shares, instead of
entering into the share and typing then.

Am Samstag, den 11.10.2008, 18:37 +0000 schrieb John Toliver:
> I know this has been stated repeatedly, however when I use the ubuntu (or
> nautilus) network icon to browse (instead of the one created by fusesmb), I
> no longer have the problem viewing the shares on other machines. Nothing
> else on my setup has changed. I will continue to test my network browsing
> as I move between different networks. In any case, thank you much for the
> update.
>
> On Sat, Oct 11, 2008 at 13:19, Steve Langasek
> <email address hidden>wrote:
>
> > On Sat, Oct 11, 2008 at 12:10:01PM -0000, John Toliver wrote:
> > > I just got an update to samba and it seems to have fixed this for me.
> >
> > If a samba update fixed anything for you, it was not this bug. This is not
> > a bug in samba.
> >
> > --
> > 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>
> >
> > --
> > nautilus does not display samba shares for machines inside an ADS network.
> > https://bugs.launchpad.net/bugs/207072
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
>
> --
> I've discovered the key to success is to never give up. You either learn
> the right way, or you run out of ways to do it wrong. A win/win situation!
>
> --
> nautilus does not display samba shares for machines inside an ADS network.
> https://bugs.launchpad.net/bugs/207072
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in gvfs: Confirmed
> Status in “gvfs” source package in Ubuntu: Triaged
> Status in “nautilus” source package in Ubuntu: Invalid
> Status in gvfs in Ubuntu Hardy: In Progress
> Status in nautilus in Ubuntu Hardy: Invalid
>
> Bug description:
> Binary package hint: nautilus
>
> Using hardy beta, when I browse with nautilus other machines in an Active Directory (ADS) network, some of them do not show their shared folders.
> The ADS integration of the hardy box was done using winbind, kerberos and PAM libraries, essentially as described here:
> https://help.ubuntu.com/community/ActiveDirectoryWinbindHowto
> The network contains mostly windows clients, but also several linux boxes, which were joined to the ADS domain with the command: 'net ads join'.
> Machines running windows XP, windows 2003 and samba show '0 objects' in nautilus, but after inserting the complete path (eg.: smb://server/share) the folders can be accessed after the password prompt.
> Machines running windows 2000 show their folder...

I was in the office on a separate network and the problem still exists.
False alarm. Sorry.

On Sat, Oct 11, 2008 at 14:52, gerstrong <email address hidden> wrote:

> In my case, the problem still remains. All Samba-Shares even from other
> Linux-Computers can be viewed, but all the Shares of Windows-PCs are not
> seen. In Konqueror, both can be viewed.
>
> What I don't understand, that it requests the password after entering
> into the share, not before browsing to PC. In Konqueror you must type it
> when you enter into the Computer to view all the shares, instead of
> entering into the share and typing then.
>
> Am Samstag, den 11.10.2008, 18:37 +0000 schrieb John Toliver:
> > I know this has been stated repeatedly, however when I use the ubuntu (or
> > nautilus) network icon to browse (instead of the one created by fusesmb),
> I
> > no longer have the problem viewing the shares on other machines. Nothing
> > else on my setup has changed. I will continue to test my network
> browsing
> > as I move between different networks. In any case, thank you much for
> the
> > update.
> >
> > On Sat, Oct 11, 2008 at 13:19, Steve Langasek
> > <email address hidden>wrote:
> >
> > > On Sat, Oct 11, 2008 at 12:10:01PM -0000, John Toliver wrote:
> > > > I just got an update to samba and it seems to have fixed this for me.
> > >
> > > If a samba update fixed anything for you, it was not this bug. This is
> not
> > > a bug in samba.
> > >
> > > --
> > > 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>
> > >
> > > --
> > > nautilus does not display samba shares for machines inside an ADS
> network.
> > > https://bugs.launchpad.net/bugs/207072
> > > You received this bug notification because you are a direct subscriber
> > > of the bug.
> > >
> >
> >
> > --
> > I've discovered the key to success is to never give up. You either learn
> > the right way, or you run out of ways to do it wrong. A win/win
> situation!
> >
> > --
> > nautilus does not display samba shares for machines inside an ADS
> network.
> > https://bugs.launchpad.net/bugs/207072
> > You received this bug notification because you are a direct subscriber
> > of a duplicate bug.
> >
> > Status in gvfs: Confirmed
> > Status in "gvfs" source package in Ubuntu: Triaged
> > Status in "nautilus" source package in Ubuntu: Invalid
> > Status in gvfs in Ubuntu Hardy: In Progress
> > Status in nautilus in Ubuntu Hardy: Invalid
> >
> > Bug description:
> > Binary package hint: nautilus
> >
> > Using hardy beta, when I browse with nautilus other machines in an Active
> Directory (ADS) network, some of them do not show their shared folders.
> > The ADS integration of the hardy box was done using winbind, kerberos and
> PAM libraries, essentially as described here:
> > https://help.ubuntu.com/community/ActiveDirectoryWinbindHowto
> > The network contains mostly windows clients, but also several linux
> boxes, which were joined to the ADS domain with the command: 'net ads join'.
> > Machines run...

I have just installed the 8.10 and Nautilus can easily access samba shares on other Ubuntu, but fails to display old Samba 2.2.8 shares (we run it on old Slack 7 in our work place). It connects without errors, but then display nothing.

A new version of the patch has been made upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=524485#c35
It seems to work in my AD network, but the severe unreachable smb bookmark regression is still present for me, as I reported there.

Still broken on 8.10 RC. This version of Gnome should have never been used for Hardy or Intrepid with this untested gvfs junk.

i used to have that problem but since i formated the machine and installed the 8.10 beta
it is gone never to come back so far

I installed Debian Etch on a test machine, and this problem doesn't exist. Either they figured out how to fix it, or they didn't use the same buggy gvfs implementation that Ubuntu is. I haven't tried a "from scratch" install of Intrepid, but I do know the two machines I ran a distro-upgrade on to Intrepid Beta still have this problem.

IIRC, Debian Etch ship with the older GnomeVFS instead of the newer GVFS, which would explain why you do not get the problem using it.

etch is still using gnomevfs, you can also install dapper

Sort-of the Microsoft philosophy on operating systems- if you don't like our shiny new broken one- please feel free to use the old rusty one that still has the feature(s) you need...

Seriously though- anything from upstream on this yet? It's been 6+ months, and there have certainly been enough people complaining about it. As has already been said by more than a few people- gvfs should have never been used in the first place, especially on an LTS version. It is almost unforgivable that it is being used in Intrepid, especially since upstream doesn't seem to be in any hurry to fix it, and Ubuntu has known about it being broken since Hardy.

I gave up and switched to KDE. I suspect I'm not the only one.

This issue has also caused me to switch to KDE. I was surprised an issue such as this existed on an LTS release and I'm even more surprised that it STILL exists. I was hoping this would be fixed for Intrepid, but unfortunately it's not. Who do we have to pay to get this done? There's no excuse for this still being a problem after 7 months so maybe throwing money at it will get it fixed. We can now mount archives (which is awesome btw), but we can't do something as simple as look at SMB shares on a server.

Sorry for the little mini-rant, but I hope you can understand the frustration of this still being broken. Any word from upstream on this?

This bug was reported upstream since the beginning. At last, it seems that now someone has really started working on this.
See http://bugzilla.gnome.org/show_bug.cgi?id=524485#c35 and following comments.
If you do not have unreachable bookmarks in nautilus, you can use, in intrepid, the temporary patch they have produced.

the users frustration there is understandable but those comment are not really constructive, the ubuntu team doesn't have the ressources to do the upstream work and you are having rude comments for contributors which are doing a lot of work for free to try to make ubuntu a system which is nice to use

Have we heard anything from Canonical about why gvfs was included in the
first place? I mean I've heard Debian Lenny which is about to be released
still uses the older gnome-vfs.

On another note, I would like to know how I might apply the patch made by
Darkrain42(I think) which fixes this.

On Mon, Oct 27, 2008 at 05:13, Sebastien Bacher <email address hidden> wrote:

> the users frustration there is understandable but those comment are not
> really constructive, the ubuntu team doesn't have the ressources to do
> the upstream work and you are having rude comments for contributors
> which are doing a lot of work for free to try to make ubuntu a system
> which is nice to use
>
> --
> nautilus does not display samba shares for machines inside an ADS network.
> https://bugs.launchpad.net/bugs/207072
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
I've discovered the key to success is to never give up. You either learn
the right way, or you run out of ways to do it wrong. A win/win situation!

canonical is paying people to work on ubuntu but is not taking the decision for the project though so there is no reason canonical should be giving some explanation about the choice, anyway some context:

- upstream decided to push gvfs in GNOME 2.22 after the stable of the 2.21 cycle, by the time that was clear hardy unstable already had a GNOME 2.21 version
- gnomevfs is known to have issues too, to be buggy and is not maintained upstream, better to support for years a clean codebase which is maintained upstream and by other distribution
- not using gnomevfs would have meant downgrading to GNOME 2.20 which is something not easy to do, which would have brought lot of other issues back, which is not easy to do technically and which would have mean ubuntu couldn't count on upstream work since GNOME only work on his current version
- lot of ubuntu users expect the current GNOME to be available in ubuntu, intrepid would still be stucked to the gutsy version if the upgrade was blocked on gvfs-smb working for everybody
- nobody signaled an issue in gvfs-smb during most of the unstable cycle and the issue is limited to some configurations

the issue might be annoying but the way forward is rather to get gvfs fixed than to hold GNOME to a one year old version ignoring hundred of bug fixes and improvement only for the benefit of some samba users

Sebastien,

I understand the reasoning behind shipping the current GNOME version.

I think that the frustration about this bug results from the fact that we "some samba users" are often early adapters in former Windows-only environments, and these regressions make our position often very difficult. It is hard to argue for a more diverse IT landscape when basic interoperability just stops working.

Anyway, I'm really looking forward to this issue to go away, and I think we are all fully aware of and grateful for the effort that developers and volunteers put into Ubuntu and upstream projects every day.

Sebastien-

If you are referring to my earlier comment- I apologize. I very much appreciate ALL of the work that the volunteer developers and organizers put into Ubuntu. Without all of you, Ubuntu wouldn't happen, and I'm pretty sure we all realize this. My frustration lies in the fact that this has been a known bug for over 7 months that DOES affect a lot of people, and makes Ubuntu a complete failure in the corporate desktop and many small business markets. I suppose in Ubuntu's goal of being a Linux for the masses, that may not matter, as I will concede that many home users won't encounter this problem.

I also realize this is an upstream issue. Ubuntu's only real fault here lies in using a faulty Gnome release to make what was believed to be the majority of people happy. The problem is- I believe you (collectively, not personally) are doing the opposite. System administrators, network managers, and geeks in general (who DO work in ADS environments) are the ones "selling" and distributing Ubuntu within their organizations and among their friends. How am I supposed to tell the non-geek secretary for a non-profit I work for that she needs to "patch her gvfs" just so she can browse a network resource?

All that said- this bug was reported one month prior to the release of Hardy. Several similar/duplicate bugs were reported within days of it, including one of my own. It can't be said that it wasn't known about prior to Hardy's release, and it is certainly known now, less than a week before Intrepid gets release with the same bug.

At least it appears upstream finally took notice (they haven't touched it since July until late last week).

Once again, Sebastien and others, I DO appreciate your work on this. My goal is to convey my frustration in hopes that maybe someone takes notice and fixes this problem, and I believe that is where others who are complaining here are at too. I will be happy to help with testing or any other information that might push this along.

the bug is really an annoying one for some users no discussion about that and I agree that it's not nice to have it in a lts, we did test gvfs-smb before switching to gvfs and it was working the active directory case has been reported weeks after the switch and rolling back was not really an option as explained before. the issue is not having people noticing the issue, if you read the bug you will notice that some people are well aware of it and patches have been worked, the issue is just not a trivial one and the ubuntu team has limited ressources and no gvfs hacker

I just can't help wondering... Canonical sells commercial support on desktops. What does Canonical say to customers who run into this problem (which I have no doubt they will)? Or is there an official workaround? If so, why hasn't this solution been made available?

By the way - I just tried Kubuntu 8.10 RC and our fileserver (IBM iSeries running i5 OS) is still (or also?) showing the problem in this bug. All Windows clients in our network can work with the same server without any problems. So perhaps this bug isn't entirely limited to gvfs...

On Mon, Oct 27, 2008 at 01:42:49PM -0000, Matthijs ten Kate wrote:

> So perhaps this bug isn't entirely limited to gvfs...

Yes, it is. If you're experiencing problems with other clients, those are
unrelated bugs and should be filed separately.

--
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>

Here are some workarounds that I have been using on 2 networks with mixed Ubuntu and winxp sp2 machines.

Workaround #1) If you want to stay all gnome...
gksu gedit /etc/samba/smb.conf (you need to be sudo to do this) scroll to the area that says:
# What naming service and in what order should we use to resolve host names
# to IP addresses
 ; name resolve order = lmhosts host wins bcast

and remove the leading ; from the name resolve order line and change the order of the entries to read:
   name resolve order = lmhosts wins bcast host

Save the file, log off and back on.

You will find the first time per session that you browse the network, it will take a while for the shares to show up, but subsequent browses will be fast.

Workaround #2) If you don't mind installing some kde software.

sudo apt-get install smb4k

It will put itself into Applications > Accesories > Smb4K

This uses kde browsing conventions, but seems to work almost instantly.

Workaround #3) As noted in earlier posts, if you put smb:/"numerical ip address" in the nautilus browser window, it will work instantly, but don't make a mistake because an unresolvable ip address may cause a hang.

Hope this helps a few people till the bug is finally resolved.

One last follow up. Although I have enabled workaround #1 above on all my machines, I usually use workaround #3 (carefully) to go to all the shares I need. Once I am at the shared folder, I save it as a bookmark in nautilus. On subsequent sessions, The shares are all listed in my Places menu in the top panel and they open instantly.

I don't know if this is helpful, I do not have a solution but. I have the same problem in Intrepid with a Samba server but not on another Samba server. I do not know what difference causes the problem. So it has to something with the way Samba is configured.

@Peter van Heun: Is the server/share you are having trouble with requiring authentication? That's where this problem creeps up. It (Nautilus/gvfs) works just fine on open shares, but anything requiring authentication will fail (and in an MS ADS network- will generally get your account locked-out).

There's a patch fixing the bug on upstream (http://bugzilla.gnome.org/show_bug.cgi?id=524485#c37). Lets hope it gets released on GNOME 2.24.2 scheduled for Nov 26.

After that, how long does it normally takes to Ubuntu guys to package it for us?

---

Peter van Heun, so you can list through nautilus (Intrepid) the shares from machines on an ADS network but cannot list them if are over a Samba server? Maybe you're facing a different bug.

@wolfwitch you're right... its all about authentication to get the listing. Nothing specific to ADS or any other Samba server.

There is now an upstream "near-final patch" for gvfs that is working well in intrepid and which does not have the problems with unreachable bookmarks. It requires an additional small patch to nautilus to work properly, though.
Details may be found at the upstream bug report (starting from comment 46):
http://bugzilla.gnome.org/show_bug.cgi?id=524485

If you compile gvfs yourself it works again. Let's hope it will be
intregrated to the ubuntu repo soon.

Am Donnerstag, den 04.12.2008, 17:09 +0000 schrieb Renzo Bagnati:

> There is now an upstream "near-final patch" for gvfs that is working well in intrepid and which does not have the problems with unreachable bookmarks. It requires an additional small patch to nautilus to work properly, though.
> Details may be found at the upstream bug report (starting from comment 46):
> http://bugzilla.gnome.org/show_bug.cgi?id=524485
>
> --
> nautilus does not display samba shares for machines inside an ADS network.
> https://bugs.launchpad.net/bugs/207072
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in gvfs: Confirmed
> Status in “gvfs” source package in Ubuntu: Triaged
> Status in “nautilus” source package in Ubuntu: Invalid
> Status in gvfs in Ubuntu Hardy: In Progress
> Status in nautilus in Ubuntu Hardy: Invalid
>
> Bug description:
> Binary package hint: nautilus
>
> Using hardy beta, when I browse with nautilus other machines in an Active Directory (ADS) network, some of them do not show their shared folders.
> The ADS integration of the hardy box was done using winbind, kerberos and PAM libraries, essentially as described here:
> https://help.ubuntu.com/community/ActiveDirectoryWinbindHowto
> The network contains mostly windows clients, but also several linux boxes, which were joined to the ADS domain with the command: 'net ads join'.
> Machines running windows XP, windows 2003 and samba show '0 objects' in nautilus, but after inserting the complete path (eg.: smb://server/share) the folders can be accessed after the password prompt.
> Machines running windows 2000 show their folders regularly.
>
> Here is a detailed description of what happens:
>
> Case 1 ---------------------------------------------------------------------------------
> Browsing from hardy-beta a machine running ubuntu-gutsy server.
>
> In a terminal window:
>
> renbag@vm-hardy:~$ smbclient -L gutsy-server
> Password: (password inserted here)
> Domain=[LAB] OS=[Unix] Server=[Samba 3.0.26a]
> Sharename Type Comment
> --------- ---- -------
> IPC$ IPC IPC Service (gutsy-server (Samba 3.0.26a, Ubuntu))
> share Disk gutsy-server_share
> Domain=[LAB] OS=[Unix] Server=[Samba 3.0.26a]
>
> In Nautilus:
>
> Open Network --> Double-click on the 'LAB' icon (Domain) --> All machines are displayed;
> Double-click on the 'gutsy-server' icon --> after a while, Nautilus returns '0 objects', without asking for a password;
> Insert the full address (smb://gutsy-server/share) --> a password is requested and the share content is displayed.
>
> Case 2 ---------------------------------------------------------------------------------
> Browsing from hardy-beta a machine running Windows XP
>
> In a terminal window:
>
> renbag@vm-hardy:~$ smbclient -L XP-ACQ
> Password: (password inserted here)
> Domain=[LAB] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
> Sharename Type Comment
> --------- ---- -------
> IPC$ IPC Remote IPC
> Data Disk
> Domain=[LAB] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
>
> In Nau...

So it sounds like this is working in both Hardy, and Intrepid... Will it come out for Hardy too, because it is also an issue still in Hardy, and I know that it was being worked on under Hardy in the Gnome bug. It's almost there.

I have been researching this and trying to figure out how to apply the patch that has been mentioned above that includes authentication in browsing of shares.

So the way to apply this patch is this:

"sudo patch [options]<file-to-be-patched> <patch-file-from-launchpad>"

I need to know the file that is supposed to be patched.

This would make the first time I'm trying this so do I need to know anything else?

Can I back up the original file before the patch in case things go south?

Any help is appreciated.

I agree with John; I have no idea how to apply the patch, but would love to know how, anyone help? 8.04.1 here. Thanks

On Tue, Dec 30, 2008 at 16:44, FAJALOU <email address hidden> wrote:

> I agree with John; I have no idea how to apply the patch, but would love
> to know how, anyone help? 8.04.1 here. Thanks
>

JT - Yeah. I figured out why everyone ignored me. Apparently Linux has
this nice little command called "patch" which 'patches' an original file
with the 'new.patch' file. I didn't do the patch as it's for an older
version of gvfs than what I have and I didn't know how that would affect my
system, nor did I know how to update it for my version, but basically you
say "patch [options] <original file> <patch file> at the CLI. So basically
the originally installed file that isn't authenticating when browsing gets
all the additions from the text file darkrain42 made. You select all text
and save it as "whatever.patch". I still don't know which original gvfs
file to patch but you can get an idea, I think from looking in synaptic at
the gvfs files, and then look at the tab that lists where all the installed
files are.

For more reading do "man patch" at the CLI and it tells you how .patch files
are made but I'm waiting on an official backport (or until I figure out how
to safely patch my system ;-p) as it's not a show stopper for me at the
moment.

HTH

JT

Please, read comments 54 to 57, they already contain instructions on how to apply a patch and to compile packages from source.
You can use these instructions to apply the latest patches which were made upstream for gvfs and nautilus.

Renzo,

Thanks for the reply. I completely missed 54-57 and they helped much. Just
as a note in case someone else runs into this:

I downloaded the source which placed a folder called "gvfs-0.2.5". Then
moved to ~/gvfs-0.2.5/daemon/ folder and downloaded and saved the patched
titled "patch to prefer kerberos, then fall back to password" with the
filename "authent.patch" in the daemon folder.

I ran this command "$ patch <gvfs.patch" and the error I received was"

patching file gvfsbackendsmbbrowse.c
patch: **** malformed patch at line 218: failed */

I then went back to line 218 in authent.patch and apparently it had a NL in
it instead of a line beginning with "+" of course I removed that NL and
saved and the patch went properly. The point was copying and pasting the
line out of the browser may not respect the CR and NL's that the file was
orignially written in so manually touching up the file may be needed.

I then created all the .debs and dpkg -i *.deb 'd them all. I'm waiting
until I move to a network other than my home network to test and see how it
works out.

Thanks again for the push,
John

The upstream developer Tomas Bzatek has committed a gvfs-smb-browse-auth.patch to gvfs-1.1.3:

        * daemon/gvfsbackendnetwork.c:
        * daemon/gvfsbackendsmbbrowse.c:
        * daemon/smb-browse.mount.in:
        SMB browsing authentication support (#524485)
        Make smb-browse backend not automounted
        Mount smb root on network backend automount

(http://bugzilla.gnome.org/show_bug.cgi?id=524485#c67)

This patch requires another already committed patch to nautilus to work properly.
The upstream bug report is now marked as RESOLVED - FIXED.

It remains to be seen if these patches can be backported to intrepid or to hardy (8.04.2 ?) ...

Agreed... How easily will it be able to upgrade to this newest Gnome version... Especially in Hardy :\ I have wanted to do this before, but have never found decent instructions on how to do that... however, I recognize that this (a bug report) is not the best place to discuss this?

the issue has been fixed upstream now, the fixed version will be uploaded to jaunty this week and backports will be considered once this one has been tested and confirmed to work and not bring other issues

Thanks Sebastien. Just as one final note... Will it come up in Hardy backports... Or Intrepid only?

FAJALOU [2009-01-08 0:27 -0000]:
> Thanks Sebastien. Just as one final note... Will it come up in Hardy
> backports... Or Intrepid only?

We definitively aim for hardy-proposed and then hardy-updates, so that
everyone will get it. Intrepid, too, of course.

This bug was fixed in the package gvfs - 1.1.3-0ubuntu1

---------------
gvfs (1.1.3-0ubuntu1) jaunty; urgency=low

  * New upstream version:
    - ftp: fix limited number of connections causes commands to fail
    - trash: fix parallel build doesn't work
    - trash: add trash::orig-path and trash::deletion-date info
    - trash: set files to mode 700 before deleting to deal with users trashing
      read-only directories
    - smb-browse: browsing authentication support (lp: #193232, #207072)
    - smb-browse: make backend not automounted anymore
    - New trash backend (lp: #7560, #187565, #201393, #206747, #207835, #216739)
    - Use the new shadow mount facility in gio
    - gphoto2: Use shadow mounts
    - obex: Fix icon for root directory
    - http: Fix major memory leak (lp: #225615)
    - http: Support proxies
  * debian/patches/01_maintainer_mode.patch,
    debian/patches/90_relibtoolize.patch:
    - commented debian change for now since it's not really required and create
      build issue using the jaunty libtool version
  * debian/patches/90_correct_glib_use.patch:
    - the issue is fixed in the new version

 -- Sebastien Bacher <email address hidden> Wed, 07 Jan 2009 22:52:11 +0100

I have tested the new gvfs (1.1.3-0ubuntu1) and nautilus (1:2.25.2-0ubuntu4) packages in a virtual machine installed from the latest jaunty live-cd.
I found no problems inside my AD network. It works well in all the cases described in the original bug submission.

Please see the bug below showing similar behaviour on Intrepid, together with some steps to isolate the problem.

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/316862

This appears to be fixed (finally) in Jaunty.

Thanks to everyone involved.

there is some comments about the patching work on the upstream bug and one about jaunty let's give a try to the update in intrepid

Sebastien: the gvfs upstream patch requires an additional nautilus patch to work properly in intrepid and hardy, otherways "browsing smb will look like a regression".
This is described in comments #47 to #50 of the upstream bug report:
http://bugzilla.gnome.org/show_bug.cgi?id=524485#c50

thank you for your comment, see bug #251809 for the nautilus update which has been uploaded before this one and which has the required changes too

Sebastien, thanks for the backports. I looked at the gvfs change (ugh, big patch), and this looks weird:

+--- trunk/daemon/smb-browse.mount.in 2009/01/06 10:20:24 2157
++++ trunk/daemon/smb-browse.mount.in 2009/01/06 15:17:21 2158
+@@ -2,5 +2,5 @@
+ Type=smb-network;smb-server
+ Exec=@libexecdir@/gvfsd-smb-browse
+ DBusName=org.gtk.vfs.mountpoint.smb_browse
+-AutoMount=true
++AutoMount=false

Why does this SRU set AutoMount to false for SMB? Is that required to fix the bug? Or a merge error?

the automount change is required, one thing which change now that the backend is handling authentification is that calls can take a while, without this change gnome-panel which is doing sync call would block when bookmarks are not responding

Accepted gvfs into intrepid-proposed, please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Accepted nautilus into intrepid-proposed, please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

I've got proposed enabled in my sources.list. When I run sudo aptitude -t intrepid-proposed I don't see the new nautilus and gvfs packaging after refreshing my package list. Do I need to wait longer for this to hit the respositories?

On Fri, Jan 23, 2009 at 11:16:54PM -0000, NTolerance wrote:
> I've got proposed enabled in my sources.list. When I run sudo aptitude
> -t intrepid-proposed I don't see the new nautilus and gvfs packaging
> after refreshing my package list. Do I need to wait longer for this to
> hit the respositories?

The nautilus update is currently built on i386 but not amd64; likewise for
gvfs. So yes, I guess a bit longer of a wait is needed.

--
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>

Tested gvfs (1.0.2-0ubuntu2) an nautilus (1:2.24.1-0ubuntu2) from intrepid-proposed.
They work very well inside my AD network, with and without kerberos tickets.
Thanks to all the developers involved.

Works well on my network too. I get prompted for credentials as soon as I click on a server which requires them. The gvfs-mount command also works now in conjunction with the GNOME keyring, allowing me to automatically mount shares within shell scripts. Thanks!

On Intrepid and Jaunty everything work. Tanks

I added the pre-release updates to intrepid and tested browsing it works.

However, If I try to "Connect to a server" and don't specify the share name I get and error saying unable to mount. I believe in previous versions I expected to get a list of shares. Maybe this behavior change was intentional..

I liken this behavior to putting in a \\servername in windows.

----- Original Message -----
From: "max" <email address hidden>
To: <email address hidden>
Sent: Monday, January 26, 2009 12:23:49 PM GMT -05:00 US/Canada Eastern
Subject: Re: [Bug 207072] Re: nautilus does not display samba shares for machines inside an ADS network.

On Intrepid and Jaunty everything work. Tanks

--
nautilus does not display samba shares for machines inside an ADS network.
https://bugs.launchpad.net/bugs/207072
You received this bug notification because you are a direct subscriber
of the bug.

Update,

Cannot display location "smb://servername/"
The message I get is "No application is registered as handling this file"

----- Original Message -----
From: "max" <email address hidden>
To: <email address hidden>
Sent: Monday, January 26, 2009 12:23:49 PM GMT -05:00 US/Canada Eastern
Subject: Re: [Bug 207072] Re: nautilus does not display samba shares for machines inside an ADS network.

On Intrepid and Jaunty everything work. Tanks

--
nautilus does not display samba shares for machines inside an ADS network.
https://bugs.launchpad.net/bugs/207072
You received this bug notification because you are a direct subscriber
of the bug.

could you give some details on what you are doing exactly to get this error?

I can reproduce the "connect to server" GUI issue. Steps:

1. Click on "Places" menu and select "Connect to Server"
2. From "Service Type" dropdown list select "Windows Share"
3. Type server name in "Server" field
4. Press "connect"

At this point you will get the error described above. Expected behavior might be to instead prompt for authentication and then display a list of shares such as what Nautilus now does when you browse via the "Network" option in the "Places" panel.

I'd also like to add that this is not a regression, the unpatched version of nautilus/gvfs also gives the exact same results.

I am running intrepid.
My machine is not joined to any domain.

I go to Places -> Connect to Server...
Select select "Windows Share" from the service type.

Enter the:
Servername
Username
Domain

Click Connect
I get a prompt for the password
Enter the password.

Then I get the error message
Cannot display location "smb://servername/"
The specified location is not mounted

----- Original Message -----
From: "Sebastien Bacher" <email address hidden>
To: <email address hidden>
Sent: Monday, January 26, 2009 1:04:18 PM GMT -05:00 US/Canada Eastern
Subject: [Bug 207072] Re: nautilus does not display samba shares for machines inside an ADS network.

could you give some details on what you are doing exactly to get this
error?

--
nautilus does not display samba shares for machines inside an ADS network.
https://bugs.launchpad.net/bugs/207072
You received this bug notification because you are a direct subscriber
of the bug.

Tab, this is a different issue than the one being discussed here. The problem you are reporting is discussed in bug #216104.

I agree the unpatched version does have the same behavior, however I was referring to the pre-hardy version of ubuntu when this problem initially came up. Gutsy did not have this issue.

----- Original Message -----
From: "NTolerance" <email address hidden>
To: <email address hidden>
Sent: Monday, January 26, 2009 1:22:10 PM GMT -05:00 US/Canada Eastern
Subject: [Bug 207072] Re: nautilus does not display samba shares for machines inside an ADS network.

I'd also like to add that this is not a regression, the unpatched
version of nautilus/gvfs also gives the exact same results.

--
nautilus does not display samba shares for machines inside an ADS network.
https://bugs.launchpad.net/bugs/207072
You received this bug notification because you are a direct subscriber
of the bug.

While the new version works well with my Windows-hosted shares, Samba shares on Linux systems have an issue if restrict anonymous = 2 or browseable = no is set in /etc/samba/smb.conf. In this event clicking on the Samba server does not prompt for authentication and no shares are displayed because the Samba server is set to only display shares if the user has authenticated.

Ok thanks,
The browsing functionality from inside nautilus does work ok then.
Sorry.

----- Original Message -----
From: "Etienne Goyer" <email address hidden>
To: <email address hidden>
Sent: Monday, January 26, 2009 1:40:39 PM GMT -05:00 US/Canada Eastern
Subject: [Bug 207072] Re: nautilus does not display samba shares for machines inside an ADS network.

Tab, this is a different issue than the one being discussed here. The
problem you are reporting is discussed in bug #216104.

--
nautilus does not display samba shares for machines inside an ADS network.
https://bugs.launchpad.net/bugs/207072
You received this bug notification because you are a direct subscriber
of the bug.

the bug there is specifically about browsing networks which require authentification, if you have an another issue which is not specific to the candidate upgrade which has just been uploaded use and another bug to discuss the issue

another confirmation for correct authentification after accessing a share and browsing beeing possible again, but ...

1) after accessing a share (opening a document), an icon is placed on the desktop. After some time I wanted to access the share again using the desktop icon, but got an error message "no viewer available for smb://server/sharename". Accessing the same share from a nautilus window (top part, still marked as mounted, eject icon available) was successful. Afterwards the desktop icon was also functional.

2) smb://username@server is still not possible and browsing seems to be anonymous. This results in the home share beeing not visible. [My client is not joined to the domain. Server is samba 3.0 connected to an AD]

I also confirm 2) from above, I cannot browse my home directory on a remote samba server....

works fine from the command line...

I have serveral Linux stations which connect to a server, so this is essential for me, any ideas if anyone is working on it ?

Thanks to all

Adam

This bug was fixed in the package gvfs - 1.0.2-0ubuntu2

---------------
gvfs (1.0.2-0ubuntu2) intrepid-proposed; urgency=low

  * debian/patches/91_svn_change_fix_smb_browsing.patch:
    - upstream svn change to fix samba browsing issue for networks which
      require an identification (lp: #207072)

 -- Sebastien Bacher <email address hidden> Fri, 23 Jan 2009 13:46:52 +0100

Will this bugfix make it to Hardy someday?

Juan David

-----------------------
Aviso legal (disclaimer): http://www.videobase.net/disclaimer/

I described test results or problmes in comment #201 - is this still worked on and included in this bug report or should I open new ones for this?

JuanHoyos [2009-02-14 16:22 -0000]:
> Will this bugfix make it to Hardy someday?

Yes.

Today I received the updates to gvfs (1.0.2-0ubuntu2) and, finally, now I can browse the shares \o/ (nearly 1 year later).

Thanks all the patcher's!

Hi everyone.

I'm very happy! This annoying bug was finally patched. At home is harder to try but in my work place I have a full patched Ubuntu 8.10.

This morning I patched and rigth away tried to navigate several XP computer with success after Ubuntu ask me for the Domain user & pass. So far so good BUT when you try to add a new printer by navegating the SMB shares, THE PRINTERS IN XP ARE NOT VISIBLE... Quite strange as the mecanism should be the same. I ask you all to try this process and confirm.

Regards.

Turbo.

PD: If I get the chance, will try to post images.
;-)

Sorry guys, but it's still not working in our situation (connecting from a fully patched 8.10 box to our IBM iSeries running i5/OS version 6r1m0 with i5/OS NetServer).

When I try to browse the server using smb://server in nautilus, I get the following error:

Could not display "smb://server".
Error: Failed to retrieve share list from server
Please select another viewer and try again.

See attached screenshot.

Connecting from an XP box works flawlessly.

Connecting from the same 8.10 box to an Ubuntu 8.04.2 server running Samba, it works fine.

I can imagine that our problem is not fully related to the original bug since the i5/OS NetServer software wasn't compiled by our friend from Redmond, so if I need to file a new bug for our situation, please let me know.

On Mon, Mar 02, 2009 at 03:40:39PM -0000, Matthijs ten Kate wrote:
> I can imagine that our problem is not fully related to the original bug
> since the i5/OS NetServer software wasn't compiled by our friend from
> Redmond, so if I need to file a new bug for our situation, please let me
> know.

Unless your NetServer is part of an AD realm and you've also configured your
Ubuntu workstation for AD, yes, your bug is unrelated and you should file a
new bug.

But this may be bug #209520.

--
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>