Well it works now, and the problem was a corrupted firewalld configuration.
The hint was when I tried the brute force approach of
telnet server.localdomain 631
and got "No route to host" indicating that the host resolution was working
but the port was blocked on the server.
One clean up an
Il giorno mar, 31/10/2017 alle 18.49 -0700, t...@sonic.net ha scritto:
> any ideas on next things to try/investigate?
seem a resolver problem (dns, suffix, domain, ecc)
Verify on server and client:
# hostname
# cat /etc/resolv.conf
# cat /etc/hosts
# for two cmd "host" "ping" do
# eval $cmd serv
>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 dec
Allegedly, on or about 30 October 2017, t...@sonic.net sent:
> The address "liberty.local:631" is suspect, as the server should be
> liberty.localdomain,
> but even adding liberty.local to /etc/hosts made no difference.
..localdomain versus .local sounds like an Avahi/ZeroConf issue to me
(the iss
On 10/30/2017 02:27 PM, t...@sonic.net wrote:
The address "liberty.local:631" is suspect, as the server should be
liberty.localdomain,
but even adding liberty.local to /etc/hosts made no difference.
Take that entry out of the hosts file, then try "ping liberty.local".
Does it work? If not, th
I'm having a cups sharing issue in what should be a straightforward
situation: an existing f26 system (the client) trying to get a
remote printer from a freshy installed f26 system (the server).
cupsd.conf on the server is set to allow sharing in general
and of the desired printer in particular,
an
