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