** Changed in: gvfs
Status: New => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/209520
Title:
unclear error when lanman authentication is refused on the server
To manage
** Changed in: gvfs
Importance: Unknown = Medium
--
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 member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
** Changed in: nautilus (Ubuntu)
Assignee: (unassigned) = nermin1001 (nermin-b)
--
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 member of Ubuntu
Desktop Bugs, which is a bug
** Changed in: nautilus (Ubuntu)
Assignee: nermin1001 (nermin-b) = (unassigned)
--
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 member of Ubuntu
Desktop Bugs, which is a bug
It is now Oct of 09.
The 9.10 version is coming out.
I still have this problem.
Please fix it.
--
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 member of Ubuntu
Desktop Bugs, which is
It is now Oct of 09.
The 9.10 version is coming out.
I still have this problem.
Please fix it.
--
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 member of Ubuntu
Desktop Bugs, which is
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
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
Sean,
If you don't want to deal with command line typing, check out webmin package.
Cheers
On Saturday, October 10, 2009, Sean Cleary seanearly...@juno.com wrote:
It now works, and I do not know how or why.
This is a major problem. I can not easily recommend a system that does
not have a easy
Same as Trab above. Connecting to SMB NAS, on 9.04:
u...@comp:~$ smbclient //192.168.1.3/sharename -U user password
Domain=[ȇ] OS=[] Server=[���]
Server requested LANMAN password (share-level security) but 'client lanman
auth' is disabled
tree connect failed: SUCCESS - 0
If adding to
Hello All,
I had a similar issue in 9.04 trying to access a SMB NAS share. The
solution I found was to add the following lines to /etc/samba/smb.conf
under global (I haven't tried with only some of the lines, so one or the
other may be unnecessary)
client lanman auth = Yes
lanman auth = Yes
** Summary changed:
- SMB error: Unable to mount location when server configured with security=share
+ unclear error when lanman authentication is refused on the server
** Changed in: gvfs (Ubuntu)
Importance: High = Low
** Changed in: gvfs (Ubuntu)
Assignee: (unassigned) = Ubuntu
** Bug watch added: GNOME Bug Tracker #578150
http://bugzilla.gnome.org/show_bug.cgi?id=578150
** Also affects: gvfs via
http://bugzilla.gnome.org/show_bug.cgi?id=578150
Importance: Unknown
Status: Unknown
--
unclear error when lanman authentication is refused on the server
** Changed in: gvfs
Status: Unknown = New
--
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 member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
14 matches
Mail list logo