Hi all
I've been having a similar problem with the Windows network. Luckily for me, the samba share is actually on a Linux server so I could log in and see what was going on.
The first thing I tested was whether it could actually find the server. I removed my details from the Gnome keyring. This would decide whether it got a response for authentication. Short answer, it did. I gave it my auth details and *then* got the dbus error message.
Since I knew the IP address I tried this:
Code:
# smbmount //<IP>/<dir> /mnt/smbdrive/<dir> -ouser=<username>,password=<pass>
smbmount complains about not being able to mount a root directory, which is why I have had to add <dir> into these.
Interesting response, however:
Code:
mount error(113): No route to host
But pinging <IP> receives responses.
It is at this point I tried again in Nautilus and lo and behold I can browse the network.
I have a feeling the dbus timeout error is not lying. The first ping back from the server was 2.6ms; the rest were of the order of 0.5ms.
I am therefore wondering whether the pinging of it (or sshing into it) did something with a cache, that then causes the server to respond within good time for dbus to mount it.
I will keep playing with this to see what I can find.
Apologies that this does not help people with local drive issues :<
Bookmarks