On 2020-07-15 07:57, Bob Goodwin wrote:
On 2020-07-14 18:36, Ed Greshko wrote:
>> On 2020-07-14 14:02, Ed Greshko wrote:
>>> OK, one more thing to try.....
>>>
>>> sudo systemctl --now disable avahi-daemon.service
>>> sudo systemctl --now disable avahi-daemon.socket
>> .
>> Did that, what now? I/t has had no immediately apparent effect ... But maybe an
additional action is required?
> First a few observations.
>
> You indicated you're using your ISP DNS. This means the names of your systems
aren't available via normal
> DNS queries since I doubt you keep your ISP updated on names. So, the fact that
doing a "ping smb" and
> your mention of smb.local is indicating to me that mdns or bonjour is at work when it
comes to the
> GUI of Thunar. I can't replicate the problem so making it more difficult to
prove what I think and find a fix.
>
> As I said, this isn't a "permissions" issue since you're not
getting any "Permission denied" indications. And, you're
> able to access the share just fine from the command line.
>
>> Does "/dns myhostname" find something like bobg, I kept thinking that
was what I should put there, but having been admonished to follow instructions I resisted
the urge top do so.
> No, that has to do with how localhost is resolved.
Seehttps://www.freedesktop.org/software/systemd/man/nss-myhostname.html.
>
>
> OK, now to try something completely different. Again, a bit of explanation.
>
> When I had my mount point defined as /media/smb an file icon with the label
"smb" shows in Thunar.
> But, when I change mount point to /mnt that doesn't happen and I need to first go
to "File System" and then to
> mnt to access the share.
>
> So, could you unmount /media/smb and then change your fstab to be /mnt and then mount
/mnt
> to see if things are better?
.
sudo systemctl --now disable avahi-daemon.service
sudo systemctl --now disable avahi-daemon.socket
Do I need to undo/re-enable that stuff?
No need, at the moment.
I hope I understand correctly, fstab is now:
//192.168.50.149/bobg /mnt/smb cifs uid=bobg,gid=bobg,credentials=/home/bobg/cred
0 0
after creating /mnt/smb
I would have preferred using just /mnt since I wonder if the GUI doesn't do some
"magic" when using
the name "smb".
It looked like it was working as before using mnt instead of media but the network
browser only displayed the "SMB" with no list of files, same problem.
But, can click on "File System" and then mnt, and then smb to get to the share?
then I thought I'd better try rebooting this computer,
ws1. Now after the restart/reboot the network browser displays nothing, not even the Mac
portable which I believe is still running.
I'm stuck at this point, dunno what to look for next
The share is now, under /mnt/smb and you can access them from the command line, yes?
--
The key to getting good answers is to ask good questions.