Thank you Thierry and Braam.
Thierry, I didn't try all the tricks you linked to above, some were
speculative or more difficult than the CLI or fstab mount work-around.
The earlier version of the Iomega firmware did not work for me.
Braam, I confirm your good result with an installed version of 9.
Bad news in "real-life" network (not the controlled experiment in bug
report):
Running Intrepid, desktop and laptop on network, each with own Samba
server (i.e. three total, including NAS), Nautilus
Location>smb://192.168.1.66/ does not work. It shows shares, but does
not mount them on desktop, a
Thank you. I confirm your summary.
"smbtree -b -N" returns no output
Opening the location as specified creates browse-able locations in
Nautilus, and mounts them on the Desktop. This is somewhat easier (in
my situation) than using the command line or modifying fstab. I will
test this in my "re
Addendum to Comment 18:
Other differences from previous trial, along with setting static IP
address on the NAS, I set host name to "IOMEGA-36AE" (was "STORAGE-
36AE") and domain name to "UTOPIA_BEACH" (was "WORKGROUP"). I'm going
to guess that when the domain names match, the shares are displayed
I was able to "sudo gedit /etc/samba/smb.conf" and "killall x-session-
manager" as requested, but there is no change in diagnostics, see
attachment.
** Attachment added: "Screen003.png"
http://launchpadlibrarian.net/25211477/Screen003.png
--
Nautilus fails to browse any share on network to wh
To run a command as administrator (user "root"), use "sudo ".
See "man sudo_root" for details.
ubu...@ubuntu:~$ smbtree -N
ubu...@ubuntu:~$
--
Nautilus fails to browse any share on network to which Iomega Home Network Hard
Drive (MDHD500-N, firmware K108.W15) is attached.
https://bugs.launchpad
Thank you for addressing the specific case I have set up. In answer to
your first five assumptions, "YES" except I failed to recreate the
browser result shown in the attachment to Comment 4. Now, the NAS
shares do not show, only "Windows Network". Double-clicking on "Windows
Network" yields "Fai
Given the confusion introduced by my Comment 9, I will restrict my
further comments to the original case of Bug 354243: a LIVE SESSION run
from a "Ubuntu 9.04 beta Desktop i386" CD.
That being the case, I ask: Once I have edited and saved
/etc/samba/smb.conf, how am I to restart smbclient? The
Whoa - stop!
Comment 9 does not describe Bug 354243 directly, but rather, a related
situation. That's what all those words I typed into Comment 9 mean. I
had hoped the the additional information would be helpful. I'm sorry it
wasn't.
I opened Bug 354243 specifically because of the "confusion" e
Just want to make sure it's understood that smbtree doesn't browse the
share when run under specific conditions outlined above - particularly
the fact that it was in a live CD session. Under my current, evolving
(implementing work-arounds) configuration, smbtree does produce output,
listed below.
10 matches
Mail list logo