Adding an HDA networked printer

From Amahi Wiki
Jump to: navigation, search
Msgbox.update.png Update Needed
The contents of this page have become outdated or irrelevant. Please consider updating it.


To set up a network printer attached to the HDA from Windows, you need to perform a few simple steps. Each machine that will need access to the printer will also need the drivers installed. This will be accomplished at the time you connect them to the printer.

  • Perform steps to install and configure Cups.
  • Connect the printer to the HDA (parallel or USB) and ensure it is powered on. It should automatically detect the printer and set it up for you.
  • Samba should be set up already for serving printers
  • You can optionally create multiple queues for one printer. We recommend 4 queues, called printer (the default, set to print in black and white), color_draft, color and color_photo. Each printer queue has corresponding settings to print as desired when print jobs are sent to that queue.
  • When you created it in the server, under Local Printers, it should say the name of the queue. Make sure the State (under the Settings tab) Shared is selected. This makes sure it can be accessed remotely.
  • Next go to a machine on your network that you want to install the printer. For Windows, from the run option, enter \\hda followed by your user ID and password if required.

Printer1.PNG

  • You should see the printer now.

Printer2.PNG

  • Right click on the printer and select connect. Answer Yes to install when it prompts to install the printer.

Printer3.PNG

  • Now, it won’t find the drivers, so select OK as we will install the drivers from the printer disk.

Printer4.PNG

  • You should now see the add printer wizard. If your driver is in the list, select it. Otherwise, select Have Disk and point it to your drive where the printer driver disk is located.

Printer5.PNG

  • Once you install the driver, you can check the Printers and Faxes to see if it is installed. Although it says Access denied, unable to connect, it is working. Print a test page. If all works well, you should see it in a matter of seconds.

Printer6.PNG

Optional: The printer status message problem can be corrected by adding the following line to the /etc/samba/smb.conf file under the printers section:

Text
​[printers] use client driver = yes​

This must be done on the server using terminal. Then, restart samba by entering /etc/init.d/smb restart and the message should now display ready on the client machine.

Printer7.PNG

This worked great on my network, but may require some additional adjustments for others. For more assistance, see the FAQ (I want to add a printer to my HDA and make it a printer server, how do I do it?)

Using Amahi CUPS application (Fedora 19/21)

NOTE: For this scenario, HP DeskJet 1310 series printer connected with USB was used.

  • Install the Amahi CUPS application (currently only available by request)
  • Login credentials to the web management interface will use the root user account.
  • Navigate to Administrative pages
  • Connect the printer via USB
  • Select "find new printers"
  • You will need to install HPLIP for most HP printers
yum  install hplip
NOTE: yum (deprecated) has been replaced with dnf as the package manager for Fedora 23 and greater.
  • You will have to choose the printer from a list. If for some reason your printer model is missing, you will have to find, download and install the correct PPD file.


NOTE: For this specific example we had to download in a desktop PC and manually add the correct PPD file from HP which you can find and extract from inside the HP's linux drivers.

Once installed, you should see the message from the Printer page:

<<HP1315_SERVER hp psc 1310 series Local Printer HP PSC 1310 Series, hpcups 3.13.11 Idle>>

As everything indicates the printer should be working!

Ref: Forum Article

Troubleshooting on Vista or Windows 7 clients

  1. In some windows clients, some users see this: "windows cannot connect to the printer.operation could not be completed (error 0x0000000d)". We've seen this problem with a few printers now, not consistently between any particular makes or models. However, I have found a consistent fix to connect to any network printer from vista:
    1. Run a command prompt and type the following: "net use LPT2: \\server\printer"
      1. This sets up a behind-the-scenes connection to the printer.
    2. Then go through the add printer wizard, choose to add a local printer, and choose port LPT2... It will probably ask for a printer driver, and you can just choose whatever XP driver you might have been using before. The printer is then installed without any errors, and works just fine.
    3. From poking around, it seems when the error appears that the driver is actually installed, but something between it being installed and it actually being added to vista's list of printers breaks. Doing the above just works though.
    4. This was from this Technet page
  2. Some users may find that certain printers (for example, the Brother HL2270DW laser printer), will not print from anyone other than the admin. We will have to add permissions for each user from CUPS:
    1. From the HDA desktop go to: http://localhost:631/printers to open up the CUPS GUI interface.
    2. Click on your printer
    3. Under the menu "Administration", select "Set Allowed Users"
    4. In the text box, type in all the HDA users
      1. Ex: "user1, user2, user3"
    5. Make sure "Allow these users to print" is selected, then click "Set Allowed Users".
    6. Note: to print, each user must be logged onto the HDA using (in Windows) \\hda in Windows Explorer
  3. Certain users may also find that even though the above steps were followed with no spelling mistakes, the printer shows a "Permission needed", or similar, message. I have not found a way to fix this, except for the following:
    1. Create a new HDA account for the user effected
    2. Transfer all files over
    3. Delete the old HDA account
    4. Do Troubleshooting 2 above for the new user account. In my case, this has successfully solved the issue.