<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Aug 7, 2009, at 2:31 AM, Timo Strunk wrote:</div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000">...</font></div></blockquote><blockquote type="cite"><div>The bug described on the debian bug report however wants the following configuration:<br>Printer1 on Server1, published<br>Printer1 -> on Server1 listed on Server2 unpublished.<br>Client1 (ServerName Server2) has access to all printers on Server2 and remote printers on Server1.<br>This should be possible (and was possible before, too), otherwise there would be no other choice to access printers from two different printservers on a client apart from setting up a complete own cups server with two Poll addresses on each client machine, which should access both printers.<br></div></blockquote><div><br></div>That's exactly what you have to do, or use one of the regular browsing protocols that work across subnets, like LDAP. The previous behavior (allowing clients to print to remote printers) was a (security) bug and was fixed in CUPS 1.3.</div><div><br></div><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div>___________________________________________________</div><div>Michael Sweet, Senior Printing System Engineer</div><div><br></div></span><br class="Apple-interchange-newline">
</div>
<br></body></html>