ed.greshko@greshko.com wrote:
Just remember 2 things....
1. Check the journal for more info on errors.
2. Use "smbclient -L remote_address" to find the available Sharenames.
In your case, /home/share was not on the list. It was "bobg".
And I still dunno why, what I did to make it different.
J have since dnf removed samba with the same Fedora32 lvm system, and reinstalled samba again, this time following the configuration instructions provided in the Fedora Documentation, old but it still seems to work, instead of what I found googling which claimed to be specific to Fedora-32. With that and what I have from the "Samba config" thread it mostly works, bobg still prevails instead of /home/share -
[bobg@WS1 ~]$ smbclient -L 192.168.50.149 Enter SAMBA\bobg's password:
Sharename Type Comment --------- ---- ------- print$ Disk Printer Drivers sharename Disk Insert a comment here IPC$ IPC IPC Service (Samba 4.12.5) bobg Disk Home Directories SMB1 disabled -- no workgroup available
I still have a problem with the Gigabyte mother board but am waiting for a replacement that will use the old ddr3 memory.
However my question now is why when I look at the Thunar file manager , Network browse 'SMB' is displayed but nothing more, no list of files available, if I double click on the SMB I get "Failed to open SMB The specified location is not supported"
Thunar also shows the permissions as root, but even that is grayed. Running Thunar as root produces an error also, operation not supported. I am not certain but suspect the iPhones, iPad users need that working, I have not tested that ...
Any ideas or thoughts appreciated, *Bob*
-- , Bob Goodwin - Zuni, Virginia, USA http://www.qrz.com/db/W2BOD FEDORA-32/64bit LINUX XFCE Fastmail POP3
On 2020-07-13 02:29, Bob Goodwin wrote:
ed.greshko@greshko.com wrote:
Just remember 2 things....
1. Check the journal for more info on errors.
2. Use "smbclient -L remote_address" to find the available Sharenames.
In your case, /home/share was not on the list. It was "bobg".
And I still dunno why, what I did to make it different.
J have since dnf removed samba with the same Fedora32 lvm system, and reinstalled samba again, this time following the configuration instructions provided in the Fedora Documentation, old but it still seems to work, instead of what I found googling which claimed to be specific to Fedora-32. With that and what I have from the "Samba config" thread it mostly works, bobg still prevails instead of /home/share -
[bobg@WS1 ~]$ smbclient -L 192.168.50.149 Enter SAMBA\bobg's password:
Sharename Type Comment --------- ---- ------- print$ Disk Printer Drivers sharename Disk Insert a comment here IPC$ IPC IPC Service (Samba 4.12.5) bobg Disk Home Directories SMB1 disabled -- no workgroup available
I still have a problem with the Gigabyte mother board but am waiting for a replacement that will use the old ddr3 memory.
However my question now is why when I look at the Thunar file manager , Network browse 'SMB' is displayed but nothing more, no list of files available, if I double click on the SMB I get "Failed to open SMB The specified location is not supported"
Have you succeeded in mounting bobg?
Here is what I have....
https://imgur.com/gallery/SOdsnlA
On 2020-07-12 16:16, Ed Greshko wrote:
Have you succeeded in mounting bobg?
. Yes it mounts as expected with 'mount /media/smb'
Here is what I have....
. The screen shot had to be copied so J could zoom to the maximum and is difficult to read but my fstab line presently is
'//192.168.50.149/bobg /media/smb cifs defaults,credentials=/home/bobg/cred 0 0'
I will try removing the 'defaults' and adding the uid and gid, as you have shown in the screenshot.
On 2020-07-13 05:19, Bob Goodwin wrote:
On 2020-07-12 16:16, Ed Greshko wrote:
Have you succeeded in mounting bobg?
. Yes it mounts as expected with 'mount /media/smb'
Here is what I have....
. The screen shot had to be copied so J could zoom to the maximum and is difficult to read but my fstab line presently is
'//192.168.50.149/bobg /media/smb cifs defaults,credentials=/home/bobg/cred 0 0'
I will try removing the 'defaults' and adding the uid and gid, as you have shown in the screenshot.
Oh, yes. Those are needed to make the permissions and ownership correct.
You and that correct in the previous thread.
On 2020-07-12 17:26, Ed Greshko wrote:
Oh, yes. Those are needed to make the permissions and ownership correct.
. New fstab line: //192.168.50.149/bobg /media/smb cifs uid=bobg,gid=bobg,credentials=/home/bobg/cred 0 0
I did 'systemctl daemon-reload' and umount /media/smb > mount /media/smb But Thunar still doesn't know what to do with it, says it has read/write permissions for root not for me.
id shows the following:
[bobg@WS1 ~]$ id bobg uid=1000(bobg) gid=1000(bobg) groups=1000(bobg),10(wheel)
On 2020-07-13 06:15, Bob Goodwin wrote:
On 2020-07-12 17:26, Ed Greshko wrote:
Oh, yes. Those are needed to make the permissions and ownership correct.
. New fstab line: //192.168.50.149/bobg /media/smb cifs uid=bobg,gid=bobg,credentials=/home/bobg/cred 0 0
I did 'systemctl daemon-reload' and umount /media/smb > mount /media/smb But Thunar still doesn't know what to do with it, says it has read/write permissions for root not for me.
id shows the following:
[bobg@WS1 ~]$ id bobg uid=1000(bobg) gid=1000(bobg) groups=1000(bobg),10(wheel)
What do you get for....
ll -d /media
and
ll -d /media/smb
?
On 2020-07-12 19:30, Ed Greshko wrote:
What do you get for....
ll -d /media
and
ll -d /media/smb
?
.
What do you get for....
ll -d /media
and
ll -d /media/smb
? . [root@WS1 bobg]# ll -d /media drwxrwxr-x. 7 root root 4096 Jun 29 13:04 /media [root@WS1 bobg]# ll -d /media/smb drwxr-xr-x. 2 bobg bobg 0 Jul 12 12:50
On 2020-07-13 07:46, Bob Goodwin wrote:
On 2020-07-12 19:30, Ed Greshko wrote:
What do you get for....
ll -d /media
and
ll -d /media/smb
?
.
What do you get for....
ll -d /media
and
ll -d /media/smb
? . [root@WS1 bobg]# ll -d /media drwxrwxr-x. 7 root root 4096 Jun 29 13:04 /media [root@WS1 bobg]# ll -d /media/smb drwxr-xr-x. 2 bobg bobg 0 Jul 12 12:50
If that is what it is with the share mounted then everything should work.
As user bobg, not root, what do you get when you do
touch /media/smb/x
On 2020-07-12 20:17, Ed Greshko wrote:
If that is what it is with the share mounted then everything should work.
As user bobg, not root, what do you get when you do
touch /media/smb/x
. [bobg@WS1 ~]$ touch /media/smb/x [bobg@WS1 ~]$ ll /media/smb/ total 4 drwxr-xr-x. 2 bobg bobg 0 Jul 10 17:25 dd3 drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Desktop drwxr-xr-x. 2 bobg bobg 0 Jul 10 17:59 Documents drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Downloads drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Music drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Pictures drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Public drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Templates -rwxr-xr-x. 1 bobg bobg 0 Jul 8 15:58 'Untitled Document 1' drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Videos -rwxr-xr-x. 1 bobg bobg 0 Jul 12 20:22 x
On 2020-07-13 08:26, Bob Goodwin wrote:
On 2020-07-12 20:17, Ed Greshko wrote:
If that is what it is with the share mounted then everything should work.
As user bobg, not root, what do you get when you do
touch /media/smb/x
. [bobg@WS1 ~]$ touch /media/smb/x [bobg@WS1 ~]$ ll /media/smb/ total 4 drwxr-xr-x. 2 bobg bobg 0 Jul 10 17:25 dd3 drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Desktop drwxr-xr-x. 2 bobg bobg 0 Jul 10 17:59 Documents drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Downloads drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Music drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Pictures drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Public drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Templates -rwxr-xr-x. 1 bobg bobg 0 Jul 8 15:58 'Untitled Document 1' drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Videos -rwxr-xr-x. 1 bobg bobg 0 Jul 12 20:22 x
So, the only problem you have is with Thunar, yes?
Maybe logging out and logging back in is needed.
On 2020-07-12 20:40, Ed Greshko wrote:
So, the only problem you have is with Thunar, yes?
Maybe logging out and logging back in is needed.
. Ok, it's about the end of the day here, had to stop for supper. we'll see if it works differently in the morning.
I keep wondering if it is something I dud as root when it should have been user ...
Thanks for the help.I'll report anything significant in the morning,
On 2020-07-12 21:32, Bob Goodwin wrote:
I'll report anything significant in the morning,
° The computer was shut down overnight and rebooted this morning, the servers are not shutdown. There was no difference in the Thunar smb display symptoms after restarting this morning.
i dnf installed Nautilus to see if it worked but it just produces a different error message. I also tried changing some permissions on the server in what look like paths that might contribute to my problem. no success doing that. ...
Nautilus displays:
Could Not Display "smb.local (smb)"
I can not 'locate' 'smb.local' which leaves me wondering if that is a valid error message? J also see a similar message for a Mac portable, 'a file name.local (smb)' instead or smb.local.
That's all I know at this point, not much, just another cryptic error message ....
On 2020-07-14 00:12, Bob Goodwin wrote:
On 2020-07-12 21:32, Bob Goodwin wrote:
I'll report anything significant in the morning,
° The computer was shut down overnight and rebooted this morning, the servers are not shutdown. There was no difference in the Thunar smb display symptoms after restarting this morning.
i dnf installed Nautilus to see if it worked but it just produces a different error message. I also tried changing some permissions on the server in what look like paths that might contribute to my problem. no success doing that. ...
Nautilus displays:
Could Not Display "smb.local (smb)"
I can not 'locate' 'smb.local' which leaves me wondering if that is a valid error message? J also see a similar message for a Mac portable, 'a file name.local (smb)' instead or smb.local.
That's all I know at this point, not much, just another cryptic error message ....
I'm only up for a few minutes so my response may come a few hours later.
When you use thunar or nautilius are there any messages in the journal?
And, on the client side (WS1), what do you get for
grep ^hosts /etc/nsswitch.conf
On 2020-07-13 13:29, Ed Greshko wrote:
When you use thunar or nautilius are there any messages in the journal?
And, on the client side (WS1), what do you get for
grep ^hosts /etc/nsswitch.conf
° Before I installed nautilus, thunar would display "smb" in the network browser but now it is showing the following line:
network:///dnssd-domain-SMB._smb._tcp
network:///dnssd-domain-ginette's%2520MacBook%2520Pro-Jan-2019._smb._tcp The second like is always there when her Mac portable is active.
I don not know exactly when it began showing the dnssd-domain-SMB line instead of SMB, perhaps related to nautilus installed and running now? In the server I changed a permission from root root to bobg root ...
journalctl doesn't show any activity until I start Thunar and then this: [bobg@WS1 ~]$ journalctl --since 15:24 -- Logs begin at Fri 2020-05-01 13:01:46 EDT, end at Mon 2020-07-13 15:26:03 EDT. -- Jul 13 15:26:03 WS1 dbus-daemon[1091]: [session uid=1000 pid=1089] Activating service name='org.freedeskto> Jul 13 15:26:03 WS1 dbus-daemon[1091]: [session
And nothing more when I click on Browse Network and the SMB line appears. If I double click on the SMB line displayed in thunar I get a notice Network Connection, Ethernet, Wired connection 1. Looks like Network Manager information.
[bobg@WS1 ~]$ grep ^hosts /etc/nsswitch.conf hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname
None of this seems to show anything of interest?
On 2020-07-14 04:35, Bob Goodwin wrote:
On 2020-07-13 13:29, Ed Greshko wrote:
When you use thunar or nautilius are there any messages in the journal?
And, on the client side (WS1), what do you get for
grep ^hosts /etc/nsswitch.conf
° Before I installed nautilus, thunar would display "smb" in the network browser but now it is showing the following line:
network:///dnssd-domain-SMB._smb._tcp
network:///dnssd-domain-ginette's%2520MacBook%2520Pro-Jan-2019._smb._tcp The second like is always there when her Mac portable is active.
I don not know exactly when it began showing the dnssd-domain-SMB line instead of SMB, perhaps related to nautilus installed and running now? In the server I changed a permission from root root to bobg root ...
First of all, don't be changing permissions/ownership on files and directories without a known reason.
Leave things as they are since everything *is* working fine from the command line as you've shown
The problem is *not* with permissions.
journalctl doesn't show any activity until I start Thunar and then this: [bobg@WS1 ~]$ journalctl --since 15:24 -- Logs begin at Fri 2020-05-01 13:01:46 EDT, end at Mon 2020-07-13 15:26:03 EDT. -- Jul 13 15:26:03 WS1 dbus-daemon[1091]: [session uid=1000 pid=1089] Activating service name='org.freedeskto> Jul 13 15:26:03 WS1 dbus-daemon[1091]: [session
And nothing more when I click on Browse Network and the SMB line appears. If I double click on the SMB line displayed in thunar I get a notice Network Connection, Ethernet, Wired connection 1. Looks like Network Manager information.
[bobg@WS1 ~]$ grep ^hosts /etc/nsswitch.conf hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname
None of this seems to show anything of interest?
First....Just as a *test* do
ping smb
And see if anything is returned.
No matter what the "ping" test shows,
Edit the /etc/nsswitch.conf file to change the hosts: line to
hosts: files dns myhostname
And see if thunar works any differently. It sounds, to me, like there is a network resolution issue going on.
On 2020-07-13 17:20, Ed Greshko wrote:
First....Just as a*test* do
ping smb
. [bobg@WS1 ~]$ ping smb PING smb (192.168.50.149) 56(84) bytes of data. 64 bytes from smb (192.168.50.149): icmp_seq=1 ttl=64 time=0.382 ms 64 bytes from smb (192.168.50.149): icmp_seq=2 ttl=64 time=0.342 ms 64 bytes from smb (192.168.50.149): icmp_seq=3 ttl=64 time=0.341 ms 64 bytes from smb (192.168.50.149): icmp_seq=4 ttl=64 time=0.335 ms 64 bytes from smb (192.168.50.149): icmp_seq=5 ttl=64 time=0.338 ms ^C --- smb ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4089ms rtt min/avg/max/mdev = 0.335/0.347/0.382/0.017 ms
And see if anything is returned.
No matter what the "ping" test shows,
Edit the /etc/nsswitch.conf file to change the hosts: line to
hosts: files dns myhostname
And see if thunar works any differently. It sounds, to me, like there is a network resolution issue going on.
. But how about this warning?
$ cat /etc/nsswitch.conf # Generated by authselect on Fri Jun 5 05:53:17 2020 # Do not modify this file manually.
# If you want to make changes to nsswitch.conf please modify # /etc/authselect/user-nsswitch.conf and run 'authselect apply-changes'.
On 2020-07-14 05:57, Bob Goodwin wrote:
On 2020-07-13 17:20, Ed Greshko wrote:
First....Just as a*test* do
ping smb
. [bobg@WS1 ~]$ ping smb PING smb (192.168.50.149) 56(84) bytes of data. 64 bytes from smb (192.168.50.149): icmp_seq=1 ttl=64 time=0.382 ms 64 bytes from smb (192.168.50.149): icmp_seq=2 ttl=64 time=0.342 ms 64 bytes from smb (192.168.50.149): icmp_seq=3 ttl=64 time=0.341 ms 64 bytes from smb (192.168.50.149): icmp_seq=4 ttl=64 time=0.335 ms 64 bytes from smb (192.168.50.149): icmp_seq=5 ttl=64 time=0.338 ms ^C --- smb ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4089ms rtt min/avg/max/mdev = 0.335/0.347/0.382/0.017 ms
Are you running a local DNS server with smb defined?
And see if anything is returned.
No matter what the "ping" test shows,
Edit the /etc/nsswitch.conf file to change the hosts: line to
hosts: files dns myhostname
And see if thunar works any differently. It sounds, to me, like there is a network resolution issue going on.
. But how about this warning?
$ cat /etc/nsswitch.conf # Generated by authselect on Fri Jun 5 05:53:17 2020 # Do not modify this file manually.
# If you want to make changes to nsswitch.conf please modify # /etc/authselect/user-nsswitch.conf and run 'authselect apply-changes'.
OK, do it the way it suggests. I keep forgetting that change.
On 2020-07-13 17:20, Ed Greshko wrote:
No matter what the "ping" test shows,
Edit the /etc/nsswitch.conf file to change the hosts: line to
hosts: files dns myhostname
And see if thunar works any differently. It sounds, to me, like there is a network resolution issue going on.
° I changed that following using the prescribed routine and the change appears to be as requested: ..................... # In order of likelihood of use to accelerate lookup. shadow: files sss hosts: files dns myhostname # hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname .........................
J restarted the computer since there was no improvement in the network browser display of SMB.
And years ago my isp insisted that we all use their DNS, I have used whatever they provided, presently the isp is owned by Viasat. The dns seems to work for me.
On 2020-07-15 01:04, Bob Goodwin wrote:
On 2020-07-13 17:20, Ed Greshko wrote:
No matter what the "ping" test shows,
Edit the /etc/nsswitch.conf file to change the hosts: line to
hosts: files dns myhostname
And see if thunar works any differently. It sounds, to me, like there is a network resolution issue going on.
° I changed that following using the prescribed routine and the change appears to be as requested: ..................... # In order of likelihood of use to accelerate lookup. shadow: files sss hosts: files dns myhostname # hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname .........................
J restarted the computer since there was no improvement in the network browser display of SMB.
OK, one more thing to try.....
sudo systemctl --now disable avahi-daemon.service sudo systemctl --now disable avahi-daemon.socket
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?
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?
Does
//
On 2020-07-15 03:16, Bob Goodwin 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. See https://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?
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?
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
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.
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,
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?
On 2020-07-15 08:03, Ed Greshko wrote:
The share is now, under /mnt/smb and you can access them from the command line, yes?
And the GUI for me when I use /mnt https://imgur.com/gallery/lxViRec
On 2020-07-14 20:03, Ed Greshko wrote:
The share is now, under /mnt/smb and you can access them from the command line, yes?
Yes it does that from the terminal.
On 2020-07-15 10:20, Bob Goodwin wrote:
On 2020-07-14 20:03, Ed Greshko wrote:
The share is now, under /mnt/smb and you can access them from the command line, yes?
Yes it does that from the terminal.
So, how about if you navigate from / (a.k.a. File System) to mnt and then to smb?
On 2020-07-15 13:32, Ed Greshko wrote:
On 2020-07-15 10:20, Bob Goodwin wrote:
On 2020-07-14 20:03, Ed Greshko wrote:
The share is now, under /mnt/smb and you can access them from the command line, yes?
Yes it does that from the terminal.
So, how about if you navigate from / (a.k.a. File System) to mnt and then to smb?
In the event my words are confusing..... See https://imgur.com/gallery/SN00FDq
Step 1, Step 2, and Step 3.
On 2020-07-15 01:32, Ed Greshko wrote:
On 2020-07-15 10:20, Bob Goodwin wrote:
On 2020-07-14 20:03, Ed Greshko wrote:
The share is now, under /mnt/smb and you can access them from the command line, yes?
Yes it does that from the terminal.
So, how about if you navigate from / (a.k.a. File System) to mnt and then to smb? This is what I see:
[bobg@WS1 ~]$ ll /mnt total 12 drwxr-xr-x. 2 root root 4096 Apr 29 10:43 box48 drwxr-xr-x. 2 root root 4096 Jun 3 11:50 save drwxr-xr-x. 2 bobg bobg 0 Jul 16 07:30 smb drwxr-xr-x. 2 root root 4096 Jun 3 11:50 test
[bobg@WS1 ~]$ ll /mnt/smb total 4 drwxr-xr-x. 2 bobg bobg 0 Jul 10 17:25 dd3 drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Desktop drwxr-xr-x. 2 bobg bobg 0 Jul 10 17:59 Documents drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Downloads drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Music drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Pictures drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Public drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Templates -rwxr-xr-x. 1 bobg bobg 0 Jul 8 15:58 'Untitled Document 1' drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Videos -rwxr-xr-x. 1 bobg bobg 0 Jul 12 20:22 x
Also I have made the same setup on a second computer, WS2, Fedora-31, and have the same problems when I try to view "smb" with the Network Browser in Thunar.
This delayed response is mainly due to some major mechanical changes in the setup. We got a new rack and transferred the computers, etc. in to it yesterday, back to, what I call normal, now ... I am still waiting for the replacement mother board, there must be a breakdown in the Amazon Prime system, it says delivery next week?
On 2020-07-17 00:27, Bob Goodwin wrote:
On 2020-07-15 01:32, Ed Greshko wrote:
On 2020-07-15 10:20, Bob Goodwin wrote:
On 2020-07-14 20:03, Ed Greshko wrote:
The share is now, under /mnt/smb and you can access them from the command line, yes?
Yes it does that from the terminal.
So, how about if you navigate from / (a.k.a. File System) to mnt and then to smb? This is what I see:
[bobg@WS1 ~]$ ll /mnt total 12 drwxr-xr-x. 2 root root 4096 Apr 29 10:43 box48 drwxr-xr-x. 2 root root 4096 Jun 3 11:50 save drwxr-xr-x. 2 bobg bobg 0 Jul 16 07:30 smb drwxr-xr-x. 2 root root 4096 Jun 3 11:50 test
[bobg@WS1 ~]$ ll /mnt/smb total 4 drwxr-xr-x. 2 bobg bobg 0 Jul 10 17:25 dd3 drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Desktop drwxr-xr-x. 2 bobg bobg 0 Jul 10 17:59 Documents drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Downloads drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Music drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Pictures drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Public drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Templates -rwxr-xr-x. 1 bobg bobg 0 Jul 8 15:58 'Untitled Document 1' drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Videos -rwxr-xr-x. 1 bobg bobg 0 Jul 12 20:22 x
Also I have made the same setup on a second computer, WS2, Fedora-31, and have the same problems when I try to view "smb" with the Network Browser in Thunar.
Sorry to confuse you. When I said "navigate" I was talking about Thunar.
See the pictures I posted.
In Thunar, go to "File System" and double-click on mnt and then double-click on smb.
On 2020-07-16 12:39, Ed Greshko wrote:
On 2020-07-17 00:27, Bob Goodwin wrote:
On 2020-07-15 01:32, Ed Greshko wrote:
On 2020-07-15 10:20, Bob Goodwin wrote:
On 2020-07-14 20:03, Ed Greshko wrote:
The share is now, under /mnt/smb and you can access them from the command line, yes?
Yes it does that from the terminal.
So, how about if you navigate from / (a.k.a. File System) to mnt and then to smb? This is what I see:
[bobg@WS1 ~]$ ll /mnt total 12 drwxr-xr-x. 2 root root 4096 Apr 29 10:43 box48 drwxr-xr-x. 2 root root 4096 Jun 3 11:50 save drwxr-xr-x. 2 bobg bobg 0 Jul 16 07:30 smb drwxr-xr-x. 2 root root 4096 Jun 3 11:50 test
[bobg@WS1 ~]$ ll /mnt/smb total 4 drwxr-xr-x. 2 bobg bobg 0 Jul 10 17:25 dd3 drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Desktop drwxr-xr-x. 2 bobg bobg 0 Jul 10 17:59 Documents drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Downloads drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Music drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Pictures drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Public drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Templates -rwxr-xr-x. 1 bobg bobg 0 Jul 8 15:58 'Untitled Document 1' drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Videos -rwxr-xr-x. 1 bobg bobg 0 Jul 12 20:22 x
Also I have made the same setup on a second computer, WS2, Fedora-31, and have the same problems when I try to view "smb" with the Network Browser in Thunar.
Sorry to confuse you. When I said "navigate" I was talking about Thunar.
See the pictures I posted.
In Thunar, go to "File System" and double-click on mnt and then double-click on smb.
The result is the same 'files' listed with both methods.
On 2020-07-17 02:17, Bob Goodwin wrote:
On 2020-07-16 12:39, Ed Greshko wrote:
On 2020-07-17 00:27, Bob Goodwin wrote:
On 2020-07-15 01:32, Ed Greshko wrote:
On 2020-07-15 10:20, Bob Goodwin wrote:
On 2020-07-14 20:03, Ed Greshko wrote:
The share is now, under /mnt/smb and you can access them from the command line, yes?
Yes it does that from the terminal.
So, how about if you navigate from / (a.k.a. File System) to mnt and then to smb? This is what I see:
[bobg@WS1 ~]$ ll /mnt total 12 drwxr-xr-x. 2 root root 4096 Apr 29 10:43 box48 drwxr-xr-x. 2 root root 4096 Jun 3 11:50 save drwxr-xr-x. 2 bobg bobg 0 Jul 16 07:30 smb drwxr-xr-x. 2 root root 4096 Jun 3 11:50 test
[bobg@WS1 ~]$ ll /mnt/smb total 4 drwxr-xr-x. 2 bobg bobg 0 Jul 10 17:25 dd3 drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Desktop drwxr-xr-x. 2 bobg bobg 0 Jul 10 17:59 Documents drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Downloads drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Music drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Pictures drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Public drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Templates -rwxr-xr-x. 1 bobg bobg 0 Jul 8 15:58 'Untitled Document 1' drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Videos -rwxr-xr-x. 1 bobg bobg 0 Jul 12 20:22 x
Also I have made the same setup on a second computer, WS2, Fedora-31, and have the same problems when I try to view "smb" with the Network Browser in Thunar.
Sorry to confuse you. When I said "navigate" I was talking about Thunar.
See the pictures I posted.
In Thunar, go to "File System" and double-click on mnt and then double-click on smb.
The result is the same 'files' listed with both methods.
So, you can use Thunar to display the share files.
Is this sufficient to say it is working?
On 2020-07-16 14:27, Ed Greshko wrote:
So, you can use Thunar to display the share files.
Is this sufficient to say it is working?.-
° Yes perhaps, but not the way it should and did work a week or ten days earlier, NFS still produces a usable display in Thunar, Samba has changed. I rarely need it so I could rationalize and forget it but it must work with the Apple devices. I have not worked on that yet since it involves configuring an iOS application and that is foreign territory for me. It will likely involve help from an iPhone user and I want to know my system works before involving them. Their confidence in me is low enough as it is.
On 2020-07-17 03:13, Bob Goodwin wrote:
On 2020-07-16 14:27, Ed Greshko wrote:
So, you can use Thunar to display the share files.
Is this sufficient to say it is working?.-
° Yes perhaps, but not the way it should and did work a week or ten days earlier, NFS still produces a usable display in Thunar, Samba has changed. I rarely need it so I could rationalize and forget it but it must work with the Apple devices. I have not worked on that yet since it involves configuring an iOS application and that is foreign territory for me. It will likely involve help from an iPhone user and I want to know my system works before involving them. Their confidence in me is low enough as it is.
Well, later in my day, I'll write up what I think you should do to put things back to a more sane configuration. That will include putting the share back under /media/smb.
But, it is 04:00, and the list would be a bit long. So, hope you can wait.
On 2020-07-16 16:01, Ed Greshko wrote:
On 2020-07-17 03:13, Bob Goodwin wrote:
On 2020-07-16 14:27, Ed Greshko wrote:
So, you can use Thunar to display the share files.
Is this sufficient to say it is working?.-
° Yes perhaps, but not the way it should and did work a week or ten days earlier, NFS still produces a usable display in Thunar, Samba has changed. I rarely need it so I could rationalize and forget it but it must work with the Apple devices. I have not worked on that yet since it involves configuring an iOS application and that is foreign territory for me. It will likely involve help from an iPhone user and I want to know my system works before involving them. Their confidence in me is low enough as it is.
Well, later in my day, I'll write up what I think you should do to put things back to a more sane configuration. That will include putting the share back under /media/smb.
But, it is 04:00, and the list would be a bit long. So, hope you can wait.
° Certainly it can wait.
On 2020-07-16 17:43, Ed Greshko wrote:
OK.... Will do it in a bit. I did forget to ask one question.
Your systems are all using DHCP to get their IP addresses, yes?
° Yes. I had been assigning addresses but found letting the router dhcp server do it is much more convenient. I can change them if I want and make them static so they match the mac addresses for filtering, and whatever ... Nothing is set in concrete, I can do it differently if not the best way.
On 2020-07-17 06:44, Bob Goodwin wrote:
On 2020-07-16 17:43, Ed Greshko wrote:
OK.... Will do it in a bit. I did forget to ask one question.
Your systems are all using DHCP to get their IP addresses, yes?
° Yes. I had been assigning addresses but found letting the router dhcp server do it is much more convenient. I can change them if I want and make them static so they match the mac addresses for filtering, and whatever ... Nothing is set in concrete, I can do it differently if not the best way.
No, no need to change it.
It explains why "ping smb" was able to get an IP address.
I'm pretty sure that you have the IP address of the router in your /etc/resolv.conf.
So, the DNS server your using is the same as the DHCP server. In this case, when the DHCP server supplies a lease it also adds a DNS record.
That didn't dawn on me since all of my servers use static IPv4 and IPv6 addresses and use a different DNS server than the router. So....my bad for not thinking of that.
Anyway..... I'll have my write up soon. I had my own issue here which has me side-tracked.
On 2020-07-16 20:21, Ed Greshko wrote:
Yes. I had been assigning addresses but found letting the router dhcp server do it is much more convenient. I can change them if I want and make them static so they match the mac addresses for filtering, and whatever ... Nothing is set in concrete, I can do it differently if not the best way.
No, no need to change it.
It explains why "ping smb" was able to get an IP address.
I'm pretty sure that you have the IP address of the router in your /etc/resolv.conf.
So, the DNS server your using is the same as the DHCP server. In this case, when the DHCP server supplies a lease it also adds a DNS record.
That didn't dawn on me since all of my servers use static IPv4 and IPv6 addresses and use a different DNS server than the router.
° I use hosts for convenience, as you can see it is not up to date: [bobg@WS1 ~]$ cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.50.57 WS1 ws1 192.168.2.179 ws2 WS2 192.168.50.32 nfs NFS 192.168.50.149 smb SMB
And 192.168.50.1 [bobg@WS1 ~]$ cat /etc/resolv.conf # Generated by NetworkManager
192.168.50.1 is the router, as you observed earlier I just went with the '.50' to differentiate between the system, Dish Network also added a 10.1.something a while back ... There are two Ethernet ports on the Viasat modem and I cold use a third one, I have the Dish Network router turned off, have had no complaints yet. I guess it might work to add another switch between the modem and a router, I have not tried that yet? Presently the other routers turned off so they are not contributing uncertainties.
On 2020-07-17 04:14, Bob Goodwin wrote:
Certainly it can wait.
Well, it will be yet another day since I've had time to do some research and would like you to try one more thing.
On the subject of research, I looked into the purpose of /media. I don't know when that was introduced in Fedora. I knew it was there, but I've ignored it. Anyway, in reading about it, its purpose is to be a place where removable media would be mounted. That bit of information then explains the actions of Thunar. Directory entries under /media are treated as potential mount points. Once a mount is performed the entry will appear in the Left Panel of Thunar in the Devices area. If you unmount, the entry would remain but be dimmed under certain circumstances. Strangely, to me, different types of mounts are treated differently.
All that said, and with my local testing, there should be no reason to change the server's hostname. So, leave it as smb.
I would like you to make one more test on the client side.
I would like you to revert to what a standard fstab entry should be. (Check my work. :-) )
//192.168.50.149/bobg /media/smb cifs uid=bobg,gid=bobg,cred=/home/bobg/cred 0 0
And then reboot the client.
When you login to the client as bobg and start Thunar verify that "smb" appears in the Devices section of the left panel. And, hopefully, you can click on that and display the files.
On 07/16/2020 08:46 PM, Ed Greshko wrote:
On the subject of research, I looked into the purpose of /media. I don't know when that was introduced in Fedora. I knew it was there, but I've ignored it. Anyway, in reading about it, its purpose is to be a place where removable media would be mounted.
And what, pray tell, was wrong with the already existing /mnt?
On 2020-07-17 11:20, Joe Zeff wrote:
On 07/16/2020 08:46 PM, Ed Greshko wrote:
On the subject of research, I looked into the purpose of /media. I don't know when that was introduced in Fedora. I knew it was there, but I've ignored it. Anyway, in reading about it, its purpose is to be a place where removable media would be mounted.
And what, pray tell, was wrong with the already existing /mnt?
Wrong? Nothing, except that is where Bob originally intended to place the cifs mount. As, I believe, he has done with his nfs mounts.
On 2020-07-17 12:03, Ed Greshko wrote:
On 2020-07-17 11:20, Joe Zeff wrote:
On 07/16/2020 08:46 PM, Ed Greshko wrote:
On the subject of research, I looked into the purpose of /media. I don't know when that was introduced in Fedora. I knew it was there, but I've ignored it. Anyway, in reading about it, its purpose is to be a place where removable media would be mounted.
And what, pray tell, was wrong with the already existing /mnt?
Wrong? Nothing, except that is where Bob originally intended to place the cifs mount. As, I believe, he has done with his nfs mounts.
That was an incorrectly worded statement.
What I meant was, Bob has demonstrated that he keeps all of his various mounts under /media. From a previous thread.
[root@WS1 bobg]# ls -al /media total 28 drwxr-xr-x. 7 root root 4096 Jun 29 13:04 . dr-xr-xr-x. 18 root root 4096 Apr 22 18:35 .. drwxr-xr-x. 2 root root 4096 Jun 3 15:26 mybk drwxrwxrwx. 29 bobg bobg 4096 Jul 2 13:33 nfs drwxrwxrwx. 2 root root 4096 Jun 29 13:04 smb drwxr-xr-x. 4 root root 4096 Jun 22 09:21 test drwxrwxrwx. 2 root root 4096 May 25 10:32 wd4t
So, I'm trying to honor his structure. And, since I can achieve it, I don't know why his system seems to fail in that regard. Hence, the long thread.
On 07/16/2020 10:03 PM, Ed Greshko wrote:
On 2020-07-17 11:20, Joe Zeff wrote:
On 07/16/2020 08:46 PM, Ed Greshko wrote:
On the subject of research, I looked into the purpose of /media. I don't know when that was introduced in Fedora. I knew it was there, but I've ignored it. Anyway, in reading about it, its purpose is to be a place where removable media would be mounted.
And what, pray tell, was wrong with the already existing /mnt?
Wrong? Nothing, except that is where Bob originally intended to place the cifs mount. As, I believe, he has done with his nfs mounts.
You misunderstand me. What I meant was what was wrong with /mnt that made the Fedora devs decide to create /media to do the same job?
On 2020-07-17 12:21, Joe Zeff wrote:
On 07/16/2020 10:03 PM, Ed Greshko wrote:
On 2020-07-17 11:20, Joe Zeff wrote:
On 07/16/2020 08:46 PM, Ed Greshko wrote:
On the subject of research, I looked into the purpose of /media. I don't know when that was introduced in Fedora. I knew it was there, but I've ignored it. Anyway, in reading about it, its purpose is to be a place where removable media would be mounted.
And what, pray tell, was wrong with the already existing /mnt?
Wrong? Nothing, except that is where Bob originally intended to place the cifs mount. As, I believe, he has done with his nfs mounts.
You misunderstand me. What I meant was what was wrong with /mnt that made the Fedora devs decide to create /media to do the same job?
I didn't misunderstand you. Your question wasn't clear.
I don't know the answer to your real question. It may not be a Fedora direction but a direction of Linux in general? Maybe someone who knows the history of it will answer? I'm not curious enough to research it.
On 2020-07-17 12:28, Ed Greshko wrote:
I'm not curious enough to research it.
Or so he said....
Maybe /media has been there for a long time and I just didn't notice it.
The Spec published by the Linux Foundation way back....
https://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html
(Note: Yes, I'm violating my "no tangent" rule)
On Thu, 2020-07-16 at 22:21 -0600, Joe Zeff wrote:
What I meant was what was wrong with /mnt that made the Fedora devs decide to create /media to do the same job?
It's not quite the same job.
/mnt was considered a place where you might mount one thing (such as temporarily connecting another hard drive, mounting directly onto /mnt, not subdirectories of various things mounted inside it).
/media was considered a place where various types of transient or removable media might be automatically mounted (floppies, optical discs, etc). Now they seem to end up inside /var/run/username/, and be handled by your particular desktop rather than a more general purpose daemon.
/net was considered a place where networked file systems might be automatically mounted by things like autofs.
A key distinguishable difference with various filepaths was *automated* systems being associated with some of those mount points. It lets systems monitor those paths and behave specially. But if you manually put something in there, you could be in for some confusing times.
By by "considered," I mean conventions came to be used, not hard and fast rules about their purposes.
You can almost create any directory you like in the root of the filesystem, but if you create one named the same way that something else expects to make special use of, *you* get to deal with the problems.
On 2020-07-16 22:46, Ed Greshko wrote:
All that said, and with my local testing, there should be no reason to change the server's hostname. So, leave it as smb.
I would like you to make one more test on the client side.
I would like you to revert to what a standard fstab entry should be. (Check my work.:-) )
//192.168.50.149/bobg /media/smb cifs uid=bobg,gid=bobg,cred=/home/bobg/cred 0 0
And then reboot the client.
When you login to the client as bobg and start Thunar verify that "smb" appears in the Devices section of the left panel. And, hopefully, you can click on that and display the files.
And Joe Zeff asks "And what, pray tell, was wrong with the already existing /mnt?" Nothing that I am aware of, it may have been with FC31 an instruction I read suggested /media and I did it that way for NFS, that worked as well as /mnt so I thought I would keep everything consistent and do the same with S>B, no other reason for it.
Ed, as for the changes you suggest I believe that describes what I have now for the last several days after setting things per you directions?
The active line in /etc/fstab is: //192.168.50.149/bobg /mnt/smb cifs uid=bobg,gid=bobg,credentials=/home/bobg/cred 0 0
and: [root@WS1 bobg]# cat /home/bobg/cred user=bobg password=mypassword
when I start cold in the morning both servers mount per fstab. Both smb and nfs are items in the Thunar left panel. Clicking Nfs in the left panel shows a list of files in the right panel, smb does not! Neither SMB nor NFS shows in the right panel under Network Browse now as I think it should and did in the past? Samba in FC32 looks like an unmanageable mess to me, but I am prejudiced ...
I also wonder if my ASUSRT-ACRH13 router is contributing to the problem, it also has not worked with the USB connection to an external storage device, also smb? Like Thunar it sees the USB device but never connects to it. I've began this response t 06:00 EDT.
-- The key to getting good answers is to ask good questions. ______
On 2020-07-17 23:21, Bob Goodwin wrote:
Ed, as for the changes you suggest I believe that describes what I have now for the last several days after setting things per you directions?
The active line in /etc/fstab is: //192.168.50.149/bobg /mnt/smb cifs uid=bobg,gid=bobg,credentials=/home/bobg/cred 0 0
and: [root@WS1 bobg]# cat /home/bobg/cred user=bobg password=mypassword
when I start cold in the morning both servers mount per fstab. Both smb and nfs are items in the Thunar left panel. Clicking Nfs in the left panel shows a list of files in the right panel, smb does not!
Correct me if I am wrong.....
You've not changed anything and yesterday it was working under /mnt/smb and today after powering up it is failing?
On 2020-07-17 17:41, Ed Greshko wrote:
Correct me if I am wrong.....
You've not changed anything and yesterday it was working under /mnt/smb and today after powering up it is failing?
. That seems to be a true statement, but may only be not working for either file manager?
I just restarted this computer and doing 'mount' seems to show the smb mounted without my doing anything.
The more I look at this the more confused I get/.../
On 2020-07-18 06:06, Bob Goodwin wrote:
On 2020-07-17 17:41, Ed Greshko wrote:
Correct me if I am wrong.....
You've not changed anything and yesterday it was working under /mnt/smb and today after powering up it is failing?
. That seems to be a true statement, but may only be not working for either file manager?
Well did you check with the command line?
I just restarted this computer and doing 'mount' seems to show the smb mounted without my doing anything.
Earlier, did you power on the client and the server at the same time?
If that is what you did, it is possible that the server wasn't yet fully up and running when the client tried to mount the share.
If now, you only restarted the client the server is fully ready.
The more I look at this the more confused I get/.../
When you check things you need to check both the command line and the file manager.
FWIW, in my earlier email, since you indicated /mnt/smb was now working I was asking you to change it back to /media/smb. I think you didn't notice that change request. BUT, no need to do it now until you can get it working consistently.
I hate to say this, but in your situation and the need to satisfy your Apple using family members it may be worth the extra few $ to invest in a NAS that supports NFS, SMB, and AFP. It may help you avoid headaches and keep everyone happier. :-) :-)
On 2020-07-17 18:47, Ed Greshko wrote:
On 2020-07-18 06:06, Bob Goodwin wrote:
On 2020-07-17 17:41, Ed Greshko wrote:
Correct me if I am wrong.....
You've not changed anything and yesterday it was working under /mnt/smb and today after powering up it is failing?
. That seems to be a true statement, but may only be not working for either file manager?
Well did you check with the command line?
I just restarted this computer and doing 'mount' seems to show the smb mounted without my doing anything.
Earlier, did you power on the client and the server at the same time?
. No, the smb server runs continuously and is on a UPS.
If that is what you did, it is possible that the server wasn't yet fully up and running when the client tried to mount the share.
If now, you only restarted the client the server is fully ready.
.
Yes it is ready: Press pwr on button, user name, password, startx and ll /mnt/smb in the terminal:
[bobg@WS1 ~]$ ll /mnt/smb total 4 drwxr-xr-x. 2 bobg bobg 0 Jul 10 17:25 dd3 drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Desktop drwxr-xr-x. 2 bobg bobg 0 Jul 10 17:59 Documents drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Downloads drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Music drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Pictures drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Public drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Templates -rwxr-xr-x. 1 bobg bobg 0 Jul 8 15:58 'Untitled Document 1' drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Videos -rwxr-xr-x. 1 bobg bobg 0 Jul 12 20:22 x
However Thunar or Nautilus can not display this when I click on smb. Clicking on nfs, or an external My Book when it is mounted, display their contents as expected. I have not checked the Fedora 31 computer but it did display the samba files yesterday while this FC32 did not.
I have done no manual mounts since booting today. I am beginning to think the only way to fix this computer will be to clear its system drive and do a new install
When you check things you need to check both the command line and the file manager.
I think I always do that.
FWIW, in my earlier email, since you indicated /mnt/smb was now working I was asking you to change it back to /media/smb. I think you didn't notice that change request. BUT, no need to do it now until you can get it working consistently.
It works with either, changing it adds uncertainty of a typo, whatever. I am willing to change it though ...
I hate to say this, but in your situation and the need to satisfy your Apple using family members it may be worth the extra few $ to invest in a NAS that supports NFS, SMB, and AFP. It may help you avoid headaches and keep everyone happier. :-) :-)
Yes I aware of that. I bought the MyCloud thinking it is essentially an NAS. The way the iOS stuff works all she has in her camera/iPhone when ready to save them are thumbnail images, saving to the MyCloud involved each image file being down loaded from the iCloud server which quickly burnt up half a terabyte of my Viasat 60GB allowance after which I am throttled back noticeably during prime time hours. Maybe the iOS stuff could be configured differently but I already have enough problems without poking around in that.
-- Bob Goodwin - Zuni, Virginia, USA http://www.qrz.com/db/W2BOD FEDORA-32/64bit LINUX XFCE Fastmail POP3
On 2020-07-18 23:57, Bob Goodwin wrote:
Yes it is ready: Press pwr on button, user name, password, startx and ll /mnt/smb in the terminal:
I see. Well, I've now done it this was as opposed from starting with a GUI login. I still have no problems.
[bobg@WS1 ~]$ ll /mnt/smb total 4 drwxr-xr-x. 2 bobg bobg 0 Jul 10 17:25 dd3 drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Desktop drwxr-xr-x. 2 bobg bobg 0 Jul 10 17:59 Documents drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Downloads drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Music drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Pictures drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Public drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Templates -rwxr-xr-x. 1 bobg bobg 0 Jul 8 15:58 'Untitled Document 1' drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Videos -rwxr-xr-x. 1 bobg bobg 0 Jul 12 20:22 x
However Thunar or Nautilus can not display this when I click on smb.
By clicking on "smb", you mean double-clicking on "mnt" and then double-clicking on "smb". Yes?
You *don't* mean clicking on "smb" in the left-panel under devices.
Clicking on nfs, or an external My Book when it is mounted, display their contents as expected. I have not checked the Fedora 31 computer but it did display the samba files yesterday while this FC32 did not.
I have done no manual mounts since booting today. I am beginning to think the only way to fix this computer will be to clear its system drive and do a new install
I assume you are talking about WS1?
On 2020-07-18 18:47, Ed Greshko wrote:
On 2020-07-18 23:57, Bob Goodwin wrote:
Yes it is ready: Press pwr on button, user name, password, startx and ll /mnt/smb in the terminal:
I see. Well, I've now done it this was as opposed from starting with a GUI login. I still have no problems.
[bobg@WS1 ~]$ ll /mnt/smb total 4 drwxr-xr-x. 2 bobg bobg 0 Jul 10 17:25 dd3 drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Desktop drwxr-xr-x. 2 bobg bobg 0 Jul 10 17:59 Documents drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Downloads drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Music drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Pictures drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Public drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Templates -rwxr-xr-x. 1 bobg bobg 0 Jul 8 15:58 'Untitled Document 1' drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Videos -rwxr-xr-x. 1 bobg bobg 0 Jul 12 20:22 x
However Thunar or Nautilus can not display this when I click on smb.
By clicking on "smb", you mean double-clicking on "mnt" and then double-clicking on "smb". Yes?
. No, I could triple click and still nothing, however I have an USB external drive, WD4TB, I have mounted, that requires a double click to open and display its' contents. NFS opens simply by selecting with one click, I think SMB should do the same as it does in the other, ws2, Fedora-31, computer with Thunar? I am not looking at the Network Browser, I've given up on that.
You *don't* mean clicking on "smb" in the left-panel under devices.
° WD4TB, the est. USB drive is under Devices, the servers are under Places.
Clicking on nfs, or an external My Book when it is mounted, display their contents as expected. I have not checked the Fedora 31 computer but it did display the samba files yesterday while this FC32 did not.
I have done no manual mounts since booting today. I am beginning to think the only way to fix this computer will be to clear its system drive and do a new install
I assume you are talking about WS1?
° Yes, that is where the problems are, ws2 FC31 works ...
On 2020-07-19 21:52, Bob Goodwin wrote:
On 2020-07-18 18:47, Ed Greshko wrote:
On 2020-07-18 23:57, Bob Goodwin wrote:
Yes it is ready: Press pwr on button, user name, password, startx and ll /mnt/smb in the terminal:
I see. Well, I've now done it this was as opposed from starting with a GUI login. I still have no problems.
[bobg@WS1 ~]$ ll /mnt/smb total 4 drwxr-xr-x. 2 bobg bobg 0 Jul 10 17:25 dd3 drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Desktop drwxr-xr-x. 2 bobg bobg 0 Jul 10 17:59 Documents drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Downloads drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Music drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Pictures drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Public drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Templates -rwxr-xr-x. 1 bobg bobg 0 Jul 8 15:58 'Untitled Document 1' drwxr-xr-x. 2 bobg bobg 0 Jun 28 12:22 Videos -rwxr-xr-x. 1 bobg bobg 0 Jul 12 20:22 x
However Thunar or Nautilus can not display this when I click on smb.
By clicking on "smb", you mean double-clicking on "mnt" and then double-clicking on "smb". Yes?
. No, I could triple click and still nothing, however I have an USB external drive, WD4TB, I have mounted, that requires a double click to open and display its' contents. NFS opens simply by selecting with one click, I think SMB should do the same as it does in the other, ws2, Fedora-31, computer with Thunar? I am not looking at the Network Browser, I've given up on that.
Sorry to be picky here. The next question is very important. Read carefully.
But, I need you to confirm that when talking about smb you are *not* talking about an smb entry under "Devices".
As for NFS.... Yes, if you click on an NFS entry under Devices in the Left-Panel it will open a list of files/directories in the Right-Panel. But.... To Navigate below that in the Right-Panel you'll need to double-click the directory entry.
You won't see anything under Browse Network since the SMB1 protocol is disabled due to security issues.
Ed Greshko:
I hate to say this, but in your situation and the need to satisfy your Apple using family members it may be worth the extra few $ to invest in a NAS that supports NFS, SMB, and AFP. It may help you avoid headaches and keep everyone happier. :-) :-)
Bob Goodwin:
Yes I aware of that. I bought the MyCloud thinking it is essentially an NAS. The way the iOS stuff works all she has in her camera/iPhone when ready to save them are thumbnail images, saving to the MyCloud involved each image file being down loaded from the iCloud server which quickly burnt up half a terabyte of my Viasat 60GB allowance
I've played with those WD & Seagate cloud devices. I wouldn't say that their configuration is any easier. Perhaps even harder, as the configuration options are more limited, and far less information is available for you to read about them.
They're support of networking file systems is peculiar. They don't seem to support individual ownership of files very well, it seems to be geared towards everyone can do everything to anything, *perhaps* with some confinement controls in between. On that point, I feel that configuring a normal computer to work in a predictable way is better, and you have far more control over your computer's behaviour.
And the various apps that let you back up to *your* *cloud* always seem to go out through the internet, and back in again, never just routing your backups directly through your LAN when you're home. Android does the same thing as you've found with Mac phones: It chews through your data allowance like crazy, your phone's and your home internet's. Mine was an all-or-nothing backup option, too. It'd back up all your photos and videos, you couldn't narrow it down to just some of them, and if it had any communication problems, it'd just start over again and again, dumping everything into one huge folder in an uncoordinated mess.
On 2020-07-19 03:53, Tim via users wrote:
Ed Greshko:
I hate to say this, but in your situation and the need to satisfy your Apple using family members it may be worth the extra few $ to invest in a NAS that supports NFS, SMB, and AFP. It may help you avoid headaches and keep everyone happier. :-) :-)
Bob Goodwin:
Yes I aware of that. I bought the MyCloud thinking it is essentially an NAS. The way the iOS stuff works all she has in her camera/iPhone when ready to save them are thumbnail images, saving to the MyCloud involved each image file being down loaded from the iCloud server which quickly burnt up half a terabyte of my Viasat 60GB allowance
I've played with those WD & Seagate cloud devices. I wouldn't say that their configuration is any easier. Perhaps even harder, as the configuration options are more limited, and far less information is available for you to read about them.
They're support of networking file systems is peculiar. They don't seem to support individual ownership of files very well, it seems to be geared towards everyone can do everything to anything, *perhaps* with some confinement controls in between. On that point, I feel that configuring a normal computer to work in a predictable way is better, and you have far more control over your computer's behaviour.
And the various apps that let you back up to *your* *cloud* always seem to go out through the internet, and back in again, never just routing your backups directly through your LAN when you're home. Android does the same thing as you've found with Mac phones: It chews through your data allowance like crazy, your phone's and your home internet's. Mine was an all-or-nothing backup option, too. It'd back up all your photos and videos, you couldn't narrow it down to just some of them, and if it had any communication problems, it'd just start over again and again, dumping everything into one huge folder in an uncoordinated mess.
0 Yes, their system updates do exactly that, one Little glitch and they return to the beginning and start over, with a new iPhone it usually has to be updated on another family members cable connection. In the mean time it's been eating my data usage during the night It never occurred to the Apple designers that their equipment might be used in weak signal areas, they only design for optimum operating conditions.
On Tue, Jul 14, 2020 at 07:57:59PM -0400, Bob Goodwin wrote:
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.
Since you disabled Avahi, you shouldn't expect to see anything the Mac advertises via mdns (i.e. Bonjour, Rendezvous, DNS-SD, zeroconf, etc. etc.).
On 2020-07-15 12:58, Jonathan Billings wrote:
On Tue, Jul 14, 2020 at 07:57:59PM -0400, Bob Goodwin wrote:
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.
Since you disabled Avahi, you shouldn't expect to see anything the Mac advertises via mdns (i.e. Bonjour, Rendezvous, DNS-SD, zeroconf, etc. etc.).
Ok, I guess that explains that. Thanks Bob
On Tue, 14 Jul 2020 at 14:05, Bob Goodwin bobgoodwin@fastmail.us wrote:
On 2020-07-13 17:20, Ed Greshko wrote:
No matter what the "ping" test shows,
Edit the /etc/nsswitch.conf file to change the hosts: line to
hosts: files dns myhostnamegvfs
And see if thunar works any differently. It sounds, to me, like there
is a network resolution issue going on. ° I changed that following using the prescribed routine and the change appears to be as requested: ..................... # In order of likelihood of use to accelerate lookup. shadow: files sss hosts: files dns myhostname # hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname .........................
J restarted the computer since there was no improvement in the network gvfs browser display of SMB.
Thunar 1.8 uses gvfs for cifs. Is gvfs installed? Maybe the permissions are wrong for the run directory used by gvfs. What is "ls -ld /run/user/1000/gvfs"?
And years ago my isp insisted that we all use their DNS, I have used whatever they provided, presently the isp is owned by Viasat. The dns seems to work for me.
ISPs have monitarized DNS. My ISP blocks DNS over TLS. I have been seeing ads related to web sites visited by other household members. My previous ISP mapped unknown addresses to ad pages.
On 2020-07-14 14:24, George N. White III wrote:
Thunar 1.8 uses gvfs for cifs. Is gvfs installed? Maybe the permissions are wrong for the run directory used by gvfs. What is "ls -ld /run/user/1000/gvfs"?
° [bobg@WS1 ~]$ ls -ld /run/user/1000/gvfs drwx------. 2 bobg bobg 40 Jul 14 12:21 /run/user/1000/gvfs
I dunno if those permissions are sufficient?
ISPs have monitarized DNS. My ISP blocks DNS over TLS. I have been seeing ads related to web sites visited by other household members. My previous ISP mapped unknown addresses to ad pages.
. Would Viasat stoop to that, seems a different kind of business, i get spam, routed to junk, from Newegg, Amazon, and one credit account too, they would be just one more, but I'm not aware of anything Viasat might have triggered ...
On 07/14/2020 01:28 PM, Bob Goodwin wrote:
Would Viasat stoop to that, seems a different kind of business, i get spam, routed to junk, from Newegg, Amazon, and one credit account too, they would be just one more, but I'm not aware of anything Viasat might have triggered ...
IANAL, but if Viasat is actually blocking access to other DNS providers, you should be complaining to the FCC.
On Tue, 14 Jul 2020 at 16:29, Bob Goodwin bobgoodwin@fastmail.us wrote:
On 2020-07-14 14:24, George N. White III wrote:
Thunar 1.8 uses gvfs for cifs. Is gvfs installed? Maybe the permissions are wrong for the run directory used by gvfs. What is "ls -ld /run/user/1000/gvfs"?
° [bobg@WS1 ~]$ ls -ld /run/user/1000/gvfs drwx------. 2 bobg bobg 40 Jul 14 12:21 /run/user/1000/gvfs
I dunno if those permissions are sufficient?
That looks good to me. I was worried that gvfs wasn't installed (in which case the directory shouldn't exist) or that the permissions were wrong. If time permits I will search the thunar sources for the error message, but it could mean gvfs failed to connect to the server known as smb.
ISPs have monitarized DNS. My ISP blocks DNS over TLS. I have been seeing ads related to web sites visited by other household members. My previous ISP mapped unknown addresses to ad pages.
. Would Viasat stoop to that, seems a different kind of business, i get spam, routed to junk, from Newegg, Amazon, and one credit account too, they would be just one more, but I'm not aware of anything Viasat might have triggered ...
On 2020-07-15 07:16, George N. White III wrote:
On Tue, 14 Jul 2020 at 16:29, Bob Goodwin <bobgoodwin@fastmail.us mailto:bobgoodwin@fastmail.us> wrote:
On 2020-07-14 14:24, George N. White III wrote: > > Thunar 1.8 uses gvfs for cifs. Is gvfs installed? Maybe the permissions > are wrong for the run directory used by gvfs. What is "ls -ld > /run/user/1000/gvfs"? ° [bobg@WS1 ~]$ ls -ld /run/user/1000/gvfs drwx------. 2 bobg bobg 40 Jul 14 12:21 /run/user/1000/gvfs I dunno if those permissions are sufficient?That looks good to me. I was worried that gvfs wasn't installed (in which case the directory shouldn't exist) or that the permissions were wrong. If time permits I will search the thunar sources for the error message, but it could mean gvfs failed to connect to the server known as smb.
Well that is, in part, my point. There should be no reason to connect to a server called smb by the GUI as the share is already mounted. The GUI should be treating it as any other mounted file system.
He can access the share just fine from the command line.
On Wed, 2020-07-15 at 07:55 +0800, Ed Greshko wrote:
There should be no reason to connect to a server called smb by the GUI as the share is already mounted.
Personally, I wouldn't be naming things that way. You end up using names where you expect options, that have the same spelling, etc. It makes for confusing command lines where you're not sure what parameters are being supplied where.
I had a friend who used the same computer hostname as his logon name, and that lead to all sorts of confusion.
On 2020-07-15 13:11, Tim via users wrote:
On Wed, 2020-07-15 at 07:55 +0800, Ed Greshko wrote:
There should be no reason to connect to a server called smb by the GUI as the share is already mounted.
Personally, I wouldn't be naming things that way. You end up using names where you expect options, that have the same spelling, etc. It makes for confusing command lines where you're not sure what parameters are being supplied where.
I had a friend who used the same computer hostname as his logon name, and that lead to all sorts of confusion.
Well, I would never name a host "smb" or anything like that either. But, apparently, that is what Bod did as one can see from a post from a different thread were he showed.
[root@smb bobg]# ll /media/dd2 total 0
At that time, I didn't think it was worth the effort to change it. But now...???
On 2020-07-15 01:36, Ed Greshko wrote:
Well, I would never name a host "smb" or anything like that either. But, apparently, that is what Bod did as one can see from a post from a different thread were he showed.
[root@smb bobg]# ll /media/dd2 total 0
At that time, I didn't think it was worth the effort to change it. But now...???
° I am open to suggestions, can change to whatever common practice might suggest it ought to be ...
Re: Tim's comment about not naming a server "smb"
Bob Goodwin wrote:
I am open to suggestions, can change to whatever common practice might suggest it ought to be ...
Generally speaking, give a device a hostname that's *unique* and useful for you to know what it is. You could call it fred, storage, server, basement, blackbox, five, whatever. But I'd avoid giving it the same name as anything else (i.e. not nfs, cifs, samba, smb, etc).
At one stage I had a penchant for giving Windows PCs names related to disasters. ;-) It seemed appropriate.
On 2020-07-14 19:55, Ed Greshko wrote:
Well that is, in part, my point. There should be no reason to connect to a server called smb by the GUI as the share is already mounted. The GUI should be treating it as any other mounted file system.
He can access the share just fine from the command line.
°
as it is now when I boot the computer both Samba and NFS are mounted, Doing 'mount -a' to get smb mounted, as I have routinely done, its happy with the fstab line, for some time is no longer needed.
On 2020-07-13 05:19, Bob Goodwin wrote:
The screen shot had to be copied so J could zoom to the maximum and is difficult to read
Sorry about that.
Next time I'll try to remember and increase the font size of the terminal and only take a snapshot of the relevant area.