Comment 96 for bug 209520

Miguel,

On Fri, Jun 06, 2008 at 06:55:13PM -0000, Miguel wrote:
> OK, after much reading and doing and undoing, I still cannot connect to
> windows (xp) server shares from Hardy but, I can from Feisty (laptop).

In what manner are you trying to connect to those shares? According to your
message, you've made a large number of changes to your configuration which
are completely unrelated to this bug report, which is specifically about
accessing SMB shares through the desktop (i.e., nautilus). To help you find
a workaround for your specific problem requires first understanding what it
is, precisely, that you're trying to achieve.

Breaking down the changes you've tried:

> 1-Add the following line to /etc/samba/smb.conf:

> client lanman auth = yes

This is only relevant when attempting to connect to servers which use old,
insecure password hashes (Win9x and earlier, or Unix-based servers running
very, very old versions of Samba - versions that, I would add, are
completely unsupported by upstream in terms of security).

> 2-installed gnome-vfs package

I'm not sure which package this refers to precisely, as there is no binary
package named 'gnome-vfs' in the archive. However, I believe this would
only be useful as a debugging tool, as the current nautilus is integrated
with gvfs rather than gnome-vfs.

> 3- remove and re-install samba and samba-common and smbclient
> using --purge

The only package in this list which is involved with share browsing on the
desktop is samba-common; but it would be extraordinary if any problems you
were experiencing were caused by a mis-installation here.

> 4- installed smbfs

This package is only relevant to kernel-level mounts; it won't help with
browsing shares from the desktop, except as a very awkward workaround.

> Only way to view the windows server shares:

> 1-typing in the server/share name in the address bar

> 2-adding a (symlink?) under Places-> Connect to Server-> Windows Share

So this leaves me absolutely puzzled as to what *isn't* working for you. If
you are able to connect to the shares by this method, then I don't believe
your problem is related to the complaint of the original user. It needs to
be addressed in a separate bug report - possibly one that's already been
opened, but without a more complete description of your problem, I don't
know which.