Browsing settings in cupsd.conf are not important, they are only important for CUPS daemons on client and server talk to each other and so the client's daemon gets the server's queues. You specify the server in client.conf which makes the client directly talking to the server's CUPS daemon and not to the local CUPS daemon. With this configuration you can even stop the local CUPS daemon as the applications do not talk to it. If there are no access permission problems the client should see the server's print queues.
What you have to check: 1. Make sure that your router (DHCP server) always assigns the same IP address to your server and to your clients. 2. Is the host name or IP in the client.conf the correct one of the server. In case of a host name, does the client resolve the name correctly (run "host <NAME>") and check whether the correct IP address gets found. 3. In cupsd.conf you choose explicit IP addresses for the clients which are allowed to connect. Check whether the addresses are correct. Run "ifconfig" on the client to find out which IP address it has. Try also allowing access to the whole local network by using @LOCAL istead of a concrete IP address. 4. Is there nothing like a firewall or similar in the way? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069671 Title: no print queues displayed in pure client mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1069671/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
