Re: f26 to f26 cups sharing problem
by tar＠sonic.net
>Take that entry out of the hosts file, then try "ping liberty.local".
>Does it work? If not, then make sure you have the "nss-mdns" package
>installed.
Well this seems to be on the right track(mdns issue).
I removed the ".local" line from /etc/hosts .
The nss-mdns package is installed, so I decided to test it as suggested in
the README.
On the client, testing for the client address
getent hosts rights.local
returns
192.168.1.4 rights.local
Great, that's what we want fromnss-mdns, so now lets test for the server
address:
getent hosts liberty.local
... times out with no response and returns a status code of 2.
Which seems to match the timeout from "cups-browsed -v"
If I skip the ".local" we get
getent hosts rights
192.168.1.4 rights.localdomain rights
.. correct for the client
getent hosts liberty
192.168.1.6 liberty.localdomain liberty
.. correct for the server
And since this all depends on /etc/nsswitch.conf, the relevant line there is
hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname
I also confirmed that avahi-daemon is running on the client
and that firewalld has mdns allowed (client and server).
Thanks for the good lead, this seems to be the problem area, any ideas on
next things to try/investigate?
1 year, 7 months
- 2
- 1