Ubuntu

Unable to mount location - Windows/SMB share

Reported by predrag balorda on 2009-10-29
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

I was able to browse network in nautilus without any problems untill yesterday. I don't exactly remember this error started appearing after I've upgraded about 150MB of packages that became available for upgrade yesterday or after installing something new.
Basically, before I was able to "browse" shares on my windows 2008 server without problems, and I can still browse shares on other windows XP machines, but on this particular windows 2008 server it started giving me this error:

Unable to mount location
DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

I have installed Smb4K and I can browse as well as mount shares with it, go back to Nautilus and access those shame mounted shares, but cannot browse those same shares from within Nautilus. Now, the laptop did go into hibernate and standby a few times since 2 days ago so I don't know if this has anything to do with it - if there is some stale lock is somewhere - but it leads me to believe that it does since it only happens with this windows 2008 server. I even tried restarting the server but the error is still there.
If I access it with its IP address ("Connect to server", "Windows share" and enter IP address instead of WINS/DNS name) then it works fine, but if I just click on the server from within Nautilus the error is there and I cannot access it.

pele@peleubuntu:~$ lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10
pele@peleubuntu:~$ apt-cache policy nautilus
nautilus:
  Installed: 1:2.28.1-0ubuntu1
  Candidate: 1:2.28.1-0ubuntu1
  Version table:
 *** 1:2.28.1-0ubuntu1 0
        500 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
pele@peleubuntu:~$

ProblemType: Bug
Architecture: amd64
CheckboxSubmission: 31b4b0c81f080c7d492c1b4bfc669a7c
CheckboxSystem: b8f3ec504801f13fc208edb5c785b099
Date: Thu Oct 29 13:36:54 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091020.3)
NonfreeKernelModules: nvidia
Package: nautilus 1:2.28.1-0ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: nautilus
Uname: Linux 2.6.31-14-generic x86_64

predrag balorda (pele-balorda) wrote :
predrag balorda (pele-balorda) wrote :

on a (possibly) related note, if I do "ping 10.1.1.1" the ping replies are immediately displayed, if I do "ping hmelj" (hmelj being the name of my windows 2008 server) the replies take 3-4 seconds to start, and also 3-4 seconds betwee replies. No dropped packets or anything funny like that, just takes time to get the replies on the console. Could this have anything to do with it? Name resolution, I don't know...I've even manually added "10.1.1.1 hmelj" to /etc/hosts and ping is ok now but Nautilus still gives me that error.

Sebastien Bacher (seb128) wrote :

Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

affects: nautilus (Ubuntu) → gvfs (Ubuntu)
Changed in gvfs (Ubuntu):
importance: Undecided → Low
affects: gvfs (Ubuntu) → nautilus (Ubuntu)
affects: nautilus (Ubuntu) → gvfs (Ubuntu)
Changed in gvfs (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
affects: gvfs (Ubuntu) → nautilus (Ubuntu)
affects: nautilus (Ubuntu) → gvfs (Ubuntu)
predrag balorda (pele-balorda) wrote :

I've found a fix!

if I go to Accessories->Passwords and encryption keys and find the entry for "hmelj" (my windows 2008 server) under Passwords->default and delete that then Nautilus will prompt me for user name and password for the server once again (Guest) and let me in, everything works ok. This, however, lasts only for the duration of the session. If I restart the ubuntu machine and go back to nautilus the problem comes back. Well, it's good enough as it is but I suspect some new users will not catch this.

So basically, you must NOT have nautilus remember your user name (and password) for windows shares!

Eneko Gonzalez (perreko) wrote :

Thanks predrag, your fix works for me (using Karmik Koala 64bits).

I hope it'll be fixed soon.

PhilippeDePass (depassp) wrote :

This bug also affects me on Ubuntu 10.04 lucid beta2, using nautilus 1:2.30.0-0ubuntu3

The workaround of NOT remembering the password works, but is non-optimal

Dante (gregory-brutsches) wrote :

I'm having the same problem in lucid (not the beta, the full release; beta was never installed on the system.)

using nautilus 1:2.30.1-0ubuntu1

Workaround works, but is not ideal.

Interestingly, this only affects one of my laptops (the toshiba). The other laptop (inspiton 800m) also has lucid but is unaffected my this bug. Both laptops are accessing the same windows machine. Before upgrade on karmic I had no trouble.

The only reason I can think of for this is that the inspiron, beung the local DNS server, somehow beats the timeout.

Not sure what logs are needed, but if asked I'll post 'em.

Arthur Wiebe (artooro) wrote :

There's a samba bug here: https://bugzilla.samba.org/show_bug.cgi?id=7250 that I'm not sure but looks like it might resolve this issue.

Was fixed in samba 3.5.3 which ubuntu 10.04 has 3.4.7

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gvfs (Ubuntu):
status: New → Confirmed
Baditaflorin (baditaflorin) wrote :

I have the latest samba with Ubuntu 12.04 and it`s still imposible to connect to widnows share and printers.

I get an error massage, when i do testparm -s:
" rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) "

Changed in gvfs (Ubuntu):
status: Confirmed → In Progress
status: In Progress → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.