Book
- Basic setup of a SOHO server
- SoHo - Software repositories
- SoHo - Alias of loopback interface
- SoHo - IPtables configuration example
- SoHo - Webmin
- SoHo - DNS
- SoHo - VMWare
- SoHo - Windows
- SoHo - OpenVPN
- SoHo - Remote Desktop
- Nameserver on Windows XP forwarding to public DNS with private zones
- SoHO - NTP
- SoHo - SSH
- SoHo - Ubuntu prerequisites
- How to strengthen SSH
- Fixing Nessus complaints
- Java installation on RHEL 4
- Installing vsFTPd on CentOS
- How to setup CA (certificate authority)
- Installation of VIM X11 and archivers on RHEL 4 x86_64
- SoHo - MS & Open-Office
- User management
- CommuniGate Pro
- Backup
- Issue tracking for small groups
- Jabber setup and configuration
- Monitoring & Statistics
- Printing in SOHO
- Faxes in SOHO
- T38 Modem
- PostScript fonts for faxes
- Installing Brother MFU drivers on Ubuntu
- Installing Hylafax client on RHEL4 and Fedora
- Installing Hylafax server on RHEL4
- Installing Hylafax server on Ubuntu
- Integrating Hylafax with CUPS
- Integrating Hylafax with CommuniGate
- Managing Hylafax from Ubuntu client
- Sending and receiving faxes over internet (links)
- How to test faxing
- Drivers for Brother MFUs
- Brand new idea about faxing
- External faxing resources
- Antivirus & Antispam
- External SOHO References
- Supplementary SOHO procedures
How to enable printer browsing
in
Browsing problems
- TUN-based VPN network does not support broadcasts, so we use polling.
- Host names set by ServerName directive in cupsd.conf should be primary DNS host names. Otherwise receiving site will detect both advertised and DNS-normalized name and two printers will be registered, e.g. PDF and PDF@cups.
- CUPS does not inherit user-level protection (-u) and error policy settings upon browsing. Imported printer will allow access from all users and will retry failed jobs upon error. And the error will be job rejected by exported printer due not user not authorized. This is hard to detect because lpq does not show error status, it only reflects job being active (however, lpinfo -p shows the status). THe solution is to add prninters manually, like lpadmin -v ipp://REMOTEHOST/printers/REMOTEPRINTER -o printer-error-policy=abort-job -u allow:root,remroot,@printlords -o printer-is-shared=true
- CUPS in RHEL4 does not by default update printcap, so we configure this explicitly
- The Listen directive in cupsd.conf does not let set listening on interface, only on address. Thus configuration file would be different between clients if we wanted to say listen only on tun0 (i.e. local LAN). Will set it to *:631 for now, though that less secure.

Comments
Post new comment