Skip to main content

Edit CUPS Configuration File To Re-assign Network Address

The printers.conf file can be edited to change the network address a printer uses.  This can be useful to fix situations in which the printer in question has a new IP address, but the local system is trying to use the previous address.

  1. Shutdown the CUPS server
  2. Change the network address
  3. Restart the CUPS server
sudo systemctl stop cups

sudo nano /etc/cups/printers.conf

sudo systemctl start cups

NOTE The editor used in the example is nano for the sake of those who may be less comfortable in the command-line.  With nano, once the change has been made, use Control + O to save the changes, and then Control + X to quit the editor.

Ideally, this process would not be necessary.  Instead, once a printer is added, it will always be reachable at the address it was assigned when it was added to the system.  In practice, things like power outages, or breaks in network connectivity, may be enough for the DHCP server to issue a new IP address.

A tip when making the address change, is to use the printer's network name instead of the IP address.  The line below is the configuration that will need to be changed.

DeviceURI socket://10.0.1.120.local

If the printer's network name is known, use that in place of the IP address.

DeviceURI socket://PRINTER-NETWORK-NAME.local

Within a few moments, the printer should be reachable again.  Perhaps the program used to print a document may need to be restarted, or in the worst case, the system may need a restart.

Comments

Post a Comment

Popular posts from this blog

Remove control of Chrome being managed by organization on personal devices

Chrome may indicate that it's being managed by a user's organization. This warning is provided by the Chrome Policies feature of the browser. To know if an instance of Chrome is managed by an organization, there will be an entry at the bottom of the browser’s hamburger menu (three dot menu), on the right side of the browser window that reads, "Managed by your organization." This is likely due to an entry in the Chrome Policies listing, which can be found by loading this page in the browser: chrome://policy The policies listed in this section are stored in the computer's file system in one of the following locations as JSON files. /usr/share/chromium/policies/managed /usr/share/chromium/policies/recommended Remove the offending JSON files, and click the Reload policies button. The Managed by your organization entry in the browser menu should be gone. A notice like this on instances of Chrome for work, school, library, or other devices that belong to an organizati...
Post a Comment
Read more

Allow Windows authentication using SQL Server driver with DBeaver

DBeaver will allow Microsoft Windows single sign on access when connecting to Microsoft SQL Server using the SQL Server driver (rather than jTDS ).  From the driver properties settings, set the integratedSecurity flag to true . Open the Connection configuration panel and choose the Driver properties section. Set the integratedSecurity flag to true . A subtle, but important step is to not provide username and password credentials to the connection.
7 comments
Read more

Connecting to SQL Server with jTDS using Windows Authentication

UPDATE:   At one point the tip in this article to set the USENTLV2 flag to true was accurate, but it appears it is no longer necessary, at least as far as DBeaver 's use of the driver is concerned.  If it solves an authentication problem, then great.  The expectation is that, an update in one of the packages that make this sort of connection possible has resolved the issue that at one time made this flag necessary. Connecting to Microsoft SQL Server using jTDS with a username and password that's managed by the database manager is pretty straightforward.  It may become a little more problematic however, when trying to use Windows authentication when connecting from a Windows machine. Do not supply a username and password. Set the USENTLMV2 property to true. NOTE:   Step 1 assumes a connection being made from a Windows machine.  If the connection is being made from something else, user credentials may actually be necessary. If the connect...
7 comments
Read more