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.
--
The key to getting good answers is to ask good questions.