Hi,
get access to the console and try this command:
systemctl status avahi-daemon
Output should look like this:
[root@runeaudiorp2 ~]# systemctl status avahi-daemon
* avahi-daemon.service - Avahi mDNS/DNS-SD Stack
Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 1970-01-01 01:00:07 CET; 45 years 10 months ago
Main PID: 212 (avahi-daemon)
Status: "avahi-daemon 0.6.31 starting up."
CGroup: /system.slice/avahi-daemon.service
|-212 avahi-daemon: running [runeaudiorp2.local]
`-217 avahi-daemon: chroot helper
Jan 01 01:00:07 runeaudiorp2 avahi-daemon[212]: Loading service file /services/sftp-ssh.service.
Jan 01 01:00:07 runeaudiorp2 avahi-daemon[212]: Loading service file /services/ssh.service.
Jan 01 01:00:07 runeaudiorp2 avahi-daemon[212]: Network interface enumeration completed.
Jan 01 01:00:07 runeaudiorp2 avahi-daemon[212]: Registering HINFO record with values 'ARMV7L'/'LINUX'.
Jan 01 01:00:07 runeaudiorp2 avahi-daemon[212]: Server startup complete. Host name is runeaudiorp2.local. Local service cookie is 2654272113.
Jan 01 01:00:07 runeaudiorp2 avahi-daemon[212]: Service "runeaudiorp2" (/services/ssh.service) successfully established.
Jan 01 01:00:07 runeaudiorp2 avahi-daemon[212]: Service "runeaudiorp2" (/services/sftp-ssh.service) successfully established.
Jan 01 01:00:10 runeaudiorp2 avahi-daemon[212]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.14.
Jan 01 01:00:10 runeaudiorp2 avahi-daemon[212]: New relevant interface eth0.IPv4 for mDNS.
Jan 01 01:00:10 runeaudiorp2 avahi-daemon[212]: Registering new address record for 192.168.0.14 on eth0.IPv4.
[root@runeaudiorp2 ~]#
If avahi-daemon is running then the problem is pc side.
Frank
