"Carey F. Cox" wrote:
> No, the server is not able to resolve the client hostname. However, I
> haven't seen any error messages on the server, just on the client. As most
> workstation addresses (static ips reserved for servers only) are
> dynamically allocated on this campus from one dhcp server, the possible
> addresses would be quite large. I would have to use the domain name,
> .lamar.edu. I have tried adding .lamar.edu, *.lamar.edu, 140.158., and
> 140.158.*.* to /etc/hosts.lpd with no success. Further, documentation on
> /etc/hosts.lpd is scarce. Am I doing this correctly?
The little documentation that I've found leads me to believe that lpd need
explicit IP addresses or resolvable hostnames. I've tried network numbers
and network/netmask combos without success. There just doesn't seem to be a
good solution for this.
One possibility is to share the printer using Samba, which can use hostname,
domain(?), network, or network/netmask to specify authorized client
addresses. The client machines do not have to run Samba, but I don't know
which packages are necessary. If the clients run Red Hat, their printtool
makes it easy to configure lp as a network printer on a Samba server. I did
exactly this to allow my home Linux box to print to an NT server in the
office over a dialup PPP link. Works like a charm.
Tony
--
Anthony E. Greene <[EMAIL PROTECTED]> <http://www.pobox.com/~agreene/>
PGP Key: 0x6C94239D 7B3D BD7D 7D91 1B44 BA26 C484 A42A 60DD 6C94 239D
Linux: The choice of a GNU Generation.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
