Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Carlos E.R." Newsgroups: comp.os.linux.misc Subject: Re: CUPS - set up printer by name instead of IP address Date: Thu, 16 Apr 2020 13:00:09 +0200 Lines: 54 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net Hyv2C0CSnvPiuOtbrIhegQjfuW7t83Lsc6OxHAEpFHciEWZBum X-Orig-Path: Telcontar.valinor!not-for-mail Cancel-Lock: sha1:wRTRDEh65UaTUAyj3Fkklw2wp3s= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 In-Reply-To: Content-Language: en-CA Xref: csiph.com comp.os.linux.misc:29796 On 14/04/2020 18.03, Charlie Gibbs wrote: > On 2020-04-14, Carlos E.R. wrote: > >> On 14/04/2020 07.10, Charlie Gibbs wrote: >> >>> I find CUPS to be nice when it works, but frustrating when it >>> doesn't - which happens often. I've tracked it down to the >>> fact that CUPS accesses my printer by its IP address - which >>> changes from time to time when the printer is powered off or >>> when its DHCP lease expires. In the CUPS web-based interface >>> (http://localhost:631), the "Printers" maintenance screen >>> currently shows: >>> >>> Connection: lpd//192.168.0.41:515/PASSTHRU >>> >>> My printer, on the other hand, is showing an IP address of >>> 192.168.0.45, so any attempts to print will fail. If I delete >>> and re-add the printer, CUPS will find the new IP address and >>> all will be well - until the printer's IP address changes again. >>> >>> Is there a way to get CUPS to access the printer by its name >>> (EPSONxxxxxx) rather than its IP address? >> >> Can you ping that name? My guess is "no". Then, of course CUPS can't >> find the printer by name. > > I can ping the printer by name. Then you should be able to refer to the printer by name in CUPS. That is what I do. http://localhost:631/printers/cp1510n_ps ... Connection: socket://bilbo.valinor:9100 > >> The usual solution is simply to assign a fixed IP to the printer. >> There are two basic methods: write the address in the printer own >> configuration panel or web page, or fixate the address in the router >> via DHCP. > > The consensus here appears to be that this is the way to go. > I've already done this with a couple of machines on my network > that act as servers, so I already have a reserved bank of > addresses. > > Thanks, everyone, for your help. :-) -- Cheers, Carlos.