On Mon, Jul 30, 2012 at 9:48 PM, mike cloaked <mike.cloaked@gmail.com> wrote:
On Mon, Jul 30, 2012 at 9:02 PM, Mantas Mikulėnas <grawity@gmail.com> wrote:
On Mon, Jul 30, 2012 at 10:52 PM, mike cloaked <mike.cloaked@gmail.com> wrote:
In fact I already had "BrowseLocalProtocols dnssd" in cupsd.conf in my laptop (client) - and on checking the server machine in fact avahi-daemon was already running - though I may need to change a config somewhere to allow it to broadcast dns-sd?
Can your laptop see the server machine itself?
Use `avahi-discover`, `avahi-browse --all`, or `mdns-scan`. (With nss-mdns installed, the server can also be accessed via `<hostname>.local`)
I now have avahi-daemon running in the client laptop also but I don't see any printers visible from the server in the local network - one question I don't know is what port the dns-sd traffic needs - I need to ensure that any required port is not blocked in the firewalls.
mDNS uses port 5353/udp and also relies on IP multicast (which is core part of IPv6, but sometimes breaks in IPv4).
OK I have avahi-daemon running on both client and server - and have just opened up port 5353 on both machines (mdns)
avahi-browse --all now sees the printer and opening a browser on localhost:631 and asking to find new printers now sees the cups shared printer and I can now complete a set of menu options and it has set it up nicely. Now the printer is seen on print options - so this is a great success.
I think the main key item was opening port 5353 on the firewall....
Thank you for your help.
I did not need to change any of the config in nsswitch.conf and so Mantas was perfectly correct. Mantas - thank you very much for your advice this evening. -- mike c