PDA

View Full Version : [SOLVED] Unable to mount samba share, dBus error



jbox78
November 15th, 2009, 06:18 PM
Recently upgraded from Jaunty to Karmic, and when I try to mount a samba drive on my Ubuntu 8.10 server, which worked before, I now get the error message below:

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

Any ideas?

spagaggum
November 19th, 2009, 08:23 AM
how is this solved??

I got same problem..

Though... it was working even after the up to 9.10 than the power went out and my laptop shut down, upon turning it back on I can see windows shares on my network, but not access them.

mcab
November 21st, 2009, 06:07 PM
I am also puzzled by this showing as 'Solved' when no solution has been presented.

I have the same, or very similar, problem. Since upgrading to Karmic I have been unable to access one particular share on my network. All others appear to work fine.

If someone actually does have a solution for this problem it would be appreciated if it could be posted.

analyst2009
December 13th, 2009, 07:44 PM
Exactly the same message with Ubuntu 9.10 (My "OneTouch4 Plus" USB Hard drive is mounted on Belkin N+ Wirless Router, and works with my other Windows Machines XP and Windows 7)

Would appreciate any insight into this matter.
Thanks.

jcmhunting
December 15th, 2009, 08:29 PM
Same error message with no network access. Any ideas?

rinki1121
December 19th, 2009, 05:08 PM
I had the same problem.
In my case, I could mount samba share by using IP address of the samba server not the name.

franciscodavid
February 17th, 2010, 01:30 PM
I had this problem, too.

What I did was to remove all the passwords stored in my user keyring related to the samba host. I think nautilus was trying to use the username & password I had in the keyring which didn't have permissions to access that concrete samba folder.

In my opinion, nautilus does not handle very well different samba users on the same samba server.

johnh10000
February 21st, 2010, 06:03 PM
Well I have had hassels too. So far an iffy soloution:

on your firewall open the folowing ports

137-139
445
5353 <- not documented everywhere

if that don't do it i find letting your local lan have free reign so
192.168.1.0/24 should do it.

but samba does seem a bit flaky in karmic. I sometimes still have to just turn the firewall off !!!!!

looking for a more secure solution