The firewall settings are ok now, but you may need to restart avahi-daemon
sudo systemctl restart avahi-daemon
then check
avahi-browse -art
BTW, any machine providing samba shares is acting as a samba server, and may also be a client. From a firewalld perspective, ‘samba’ service opens ports 445(tcp), 137(udp),138(udp), and 139(tcp), while ‘samba-client’ service opens ports 137(udp) and 138(udp).
Still nothing
Note I’m restartin Samba after every iteration
linux1:/home/gogalthorp # systemctl restart avahi-daemon
linux1:/home/gogalthorp # systemctl status avahi-daemon
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2019-08-12 14:41:55 EDT; 12s ago
Main PID: 25754 (avahi-daemon)
Status: "Server startup complete. Host name is linux1.local. Local service cookie is 69670634."
Tasks: 1 (limit: 4915)
CGroup: /system.slice/avahi-daemon.service
└─25754 avahi-daemon: running [linux1.local]
Aug 12 14:41:55 linux1.localdomain avahi-daemon[25754]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::f2a3>
Aug 12 14:41:55 linux1.localdomain avahi-daemon[25754]: New relevant interface eth0.IPv6 for mDNS.
Aug 12 14:41:55 linux1.localdomain avahi-daemon[25754]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.>
Aug 12 14:41:55 linux1.localdomain avahi-daemon[25754]: New relevant interface eth0.IPv4 for mDNS.
Aug 12 14:41:55 linux1.localdomain avahi-daemon[25754]: Network interface enumeration completed.
Aug 12 14:41:55 linux1.localdomain avahi-daemon[25754]: Registering new address record for fe80::f2a3:9cf7:561a:4aba on eth0.*.
Aug 12 14:41:55 linux1.localdomain avahi-daemon[25754]: Registering new address record for 192.168.1.3 on eth0.IPv4.
Aug 12 14:41:56 linux1.localdomain avahi-daemon[25754]: Server startup complete. Host name is linux1.local. Local service cookie is>
Aug 12 14:41:57 linux1.localdomain avahi-daemon[25754]: Service "linux1" (/etc/avahi/services/ssh.service) successfully established.
Aug 12 14:41:57 linux1.localdomain avahi-daemon[25754]: Service "linux1" (/etc/avahi/services/sftp-ssh.service) successfully establ>
...skipping...
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2019-08-12 14:41:55 EDT; 12s ago
Main PID: 25754 (avahi-daemon)
Status: "Server startup complete. Host name is linux1.local. Local service cookie is 69670634."
Tasks: 1 (limit: 4915)
CGroup: /system.slice/avahi-daemon.service
└─25754 avahi-daemon: running [linux1.local]
Aug 12 14:41:55 linux1.localdomain avahi-daemon[25754]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::f2a3>
Aug 12 14:41:55 linux1.localdomain avahi-daemon[25754]: New relevant interface eth0.IPv6 for mDNS.
Aug 12 14:41:55 linux1.localdomain avahi-daemon[25754]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.>
Aug 12 14:41:55 linux1.localdomain avahi-daemon[25754]: New relevant interface eth0.IPv4 for mDNS.
Aug 12 14:41:55 linux1.localdomain avahi-daemon[25754]: Network interface enumeration completed.
Aug 12 14:41:55 linux1.localdomain avahi-daemon[25754]: Registering new address record for fe80::f2a3:9cf7:561a:4aba on eth0.*.
Aug 12 14:41:55 linux1.localdomain avahi-daemon[25754]: Registering new address record for 192.168.1.3 on eth0.IPv4.
Aug 12 14:41:56 linux1.localdomain avahi-daemon[25754]: Server startup complete. Host name is linux1.local. Local service cookie is>
Aug 12 14:41:57 linux1.localdomain avahi-daemon[25754]: Service "linux1" (/etc/avahi/services/ssh.service) successfully established.
Aug 12 14:41:57 linux1.localdomain avahi-daemon[25754]: Service "linux1" (/etc/avahi/services/sftp-ssh.service) successfully establ>
linux1:/home/gogalthorp # avahi-browse -art
+ eth0 IPv6 LINUX1 _device-info._tcp local
+ eth0 IPv4 LINUX1 _device-info._tcp local
+ eth0 IPv6 LINUX1 Microsoft Windows Network local
+ eth0 IPv4 LINUX1 Microsoft Windows Network local
+ eth0 IPv6 linux1 SSH Remote Terminal local
+ eth0 IPv4 linux1 SSH Remote Terminal local
+ eth0 IPv6 linux1 SFTP File Transfer local
+ eth0 IPv4 linux1 SFTP File Transfer local
= eth0 IPv6 LINUX1 _device-info._tcp local
hostname = [linux1.local]
address = [fe80::f2a3:9cf7:561a:4aba]
port = [0]
txt = "model=MacSamba"]
= eth0 IPv4 LINUX1 _device-info._tcp local
hostname = [linux1.local]
address = [192.168.1.3]
port = [0]
txt = "model=MacSamba"]
= eth0 IPv6 LINUX1 Microsoft Windows Network local
hostname = [linux1.local]
address = [fe80::f2a3:9cf7:561a:4aba]
port = [445]
txt = ]
= eth0 IPv4 LINUX1 Microsoft Windows Network local
hostname = [linux1.local]
address = [192.168.1.3]
port = [445]
txt = ]
= eth0 IPv6 linux1 SSH Remote Terminal local
hostname = [linux1.local]
address = [fe80::f2a3:9cf7:561a:4aba]
port = [22]
txt = ]
= eth0 IPv4 linux1 SSH Remote Terminal local
hostname = [linux1.local]
address = [192.168.1.3]
port = [22]
txt = ]
= eth0 IPv6 linux1 SFTP File Transfer local
hostname = [linux1.local]
address = [fe80::f2a3:9cf7:561a:4aba]
port = [22]
txt = ]
= eth0 IPv4 linux1 SFTP File Transfer local
hostname = [linux1.local]
address = [192.168.1.3]
port = [22]
txt = ]
Now your avahi-browse output shows active services so that is progress. 
You will likely need to restart your desktop session, and you should then find that Dolphin will display these services graphically.
Network > Network (you may need to refresh/redisplay with F5 first)
or type ‘network:/’ in the location bar. You should see a folder icon representing the host(s) concerned. Click on a host and all the services (represented as icons) should show for the respective host.
Tried reboot. I agree it looks better but something is staill missing
Do you start KDE with a new session, or stay with existing session?
The ‘network:/’ KIO shows nothing when entered in to the location bar?
It does show linux1 under that there are 4 instances of linux1
unknown, SFTP, SMB, SSH servers The unknown and SMB show the local shared directory. No sign of the other two OS but they both see all others.
Never looked in the network entry which translates to remote: I have always used the shared folders(SMB)
I’m not seeing the network MSHOME which should have all the OS under it.
Great! They all represent services that 'linux’1 host provides.
No sign of the other two OS but they both see all others.
No, they won’t show up here - only Bonjour/Avahi aware (eg Linux/Mac) hosts would show up here. It would be nice if Windows 10 machines would use DNS-SD to the same. That’s why I mentioned way back in post #9…
For samba running on Linux hosts only, avahi can be employed for similar discovery…
Never looked in the network entry which translates to remote: I have always used the shared folders(SMB)
Yes, it’s for Avahi aware hosts. It relies on DNS service discovery (DNS-SD), which is what we’ve been exploring here.
I’m not seeing the network MSHOME which should have all the OS under it.
The NetBIOS-based discovery is no longer unless you explicitly enable it and have hosts still using SMBv1. For my Windows 10 shares, I can reach it by name using
smb://<hostname>.local
but as I already mentioned I generally just save the required URLs to my ‘Remote’ places in Dolphin for future access.
smb://linux1.local shows local shares
But I still don’t see the Window shares can you give me an example URL?
Downing firewall and I can see Window Machines. Something wrong there.
I don’t see any ports defined in the firewalld configs.
Ok set ports now can see base on XP but time out if I try to go to a share, Can’t see Win7 machine May very well be SMB1 being dropped. in 7 and required in XP???
Now I’m done for the moment. I can use it as is. It is irritating that I can’t get this to work correctly but copy from/too the windows and Linux machines from the windows machine works I guess I’ll live with Linux being broken
Thanks much for the help
I use Win XP & 7 (virtualized) and I need a common share supplied by Samba on my openSuse.
I don’t remember since what Samba version default value of ntlm parameter has been changed but if I want to access to a Samba share from XP I have to add this :
**ntlm auth = yes**
under [global] section.
Hope this help …
I give also my 2 years ago thread when I encountered the issue : https://forums.opensuse.org/showthread.php/526712-Can-t-join-Windows-XP-SP3-to-samba-PDC-(rpc-no-AD)
Windows 10 has implemented mDNS, you it is possible for me to ping via terminal using
ping dell.local
and browse shares via Dolphin with
smb:///dell.local
Windows 7 & XP won’t respond like that, but can still be reached by IP address of course.
Well, using SMBv1 is a major security risk, so XP should no longer be used from that POV. IIRC, Windows 7 can be configured to use SMBv2 though.
Now I’m done for the moment. I can use it as is. It is irritating that I can’t get this to work correctly but copy from/too the windows and Linux machines from the windows machine works I guess I’ll live with Linux being broken
Thanks much for the help
No, samba is not broken, just you haven’t kept up with the play. It’s working fine for me in my relatively modern multi-OS environment. From a Linux host only environment POV, it works perfectly. Go research ‘wannacry’ and ‘SMBv1’.
There are reasons for me to keep old XP machine.
In any case the Windows instance can see and connect to each other and Linux but Linux can not see MSHOME and even though I get first connection to XP (not 7)
I would consider using sftp instead.