How to Install Your Printer/Scanner in Puppy
Hello, rcrsn51 & folks.
Few hours ago I discovered that my Lexmark X204n is not responding to printing tasks. It worked fine for few months but now it's silent.
My Precise 5.72 (save2dir) is set to Serbian (I recently joined Puppy Translators Team) and this might be the cause of this problem.
I've experienced some localization issues recently with a number of built-in/installed applications. It's my best guess because I haven't used my printer for a while, probably not since end of February when I switched to Serbian local settings. Well, I haven't printed any docs under Puppy,
just used scan/copy occasionally.
EDIT: 8. IV 2015. 9:57 CET
Ok, my problem was related to bad USB connector, not local settings, system etc.
Still, I decided to use Lexmark drivers and have downloaded driver for Lexmark X204n from here.
When prompted for OS, choose Ubuntu 12.04. Binaries compatible with Puppy Precise 5.7x.
Following rcrsn51 tips from the first post of this topic (Things to know - read the lines 3 and 4)
I've copied downloaded PPD-Files-LMACO.tar.Z to
/temp, opened console there and first uncompressed and then untared it. Jumped to newly created directory and started install script, like this:
That's it. CUPS immediately recognized my printer under localhost:631/admin and all I had to do was choosing newly installed driver and setting few options to my likings.
Maybe someone will find this useful.
Cheers.
P.S. This post went blank yesterday because I messed up url tags. Sorry... :/
Few hours ago I discovered that my Lexmark X204n is not responding to printing tasks. It worked fine for few months but now it's silent.
My Precise 5.72 (save2dir) is set to Serbian (I recently joined Puppy Translators Team) and this might be the cause of this problem.
I've experienced some localization issues recently with a number of built-in/installed applications. It's my best guess because I haven't used my printer for a while, probably not since end of February when I switched to Serbian local settings. Well, I haven't printed any docs under Puppy,
just used scan/copy occasionally.
EDIT: 8. IV 2015. 9:57 CET
Ok, my problem was related to bad USB connector, not local settings, system etc.
Still, I decided to use Lexmark drivers and have downloaded driver for Lexmark X204n from here.
When prompted for OS, choose Ubuntu 12.04. Binaries compatible with Puppy Precise 5.7x.
Following rcrsn51 tips from the first post of this topic (Things to know - read the lines 3 and 4)
I've copied downloaded PPD-Files-LMACO.tar.Z to
/temp, opened console there and first uncompressed and then untared it. Jumped to newly created directory and started install script, like this:
Code: Select all
./install_ppd.sh
Maybe someone will find this useful.
Cheers.
P.S. This post went blank yesterday because I messed up url tags. Sorry... :/
I'm not an expert, but I'm not a complete Linux newb... yet trying to get my networked printer working in Puppy has got me stymied!
In a nutshell, I have an HP F335 printer shared on a Linux Mint machine. I've also got Samba installed on it, and can see & print to the printer from both Linux & Windows. Other Linux Mint machines see the printer natively through the ipp protocol, and I don't even have to do anything - the printer is just "there", ready to accept jobs. Windows of course requires me to connect to it & install the driver.. but they both work.
When I try to setup the printer for Puppy, however, I'm just not having any luck. The Linux Mint host *does* have CUPS installed, and the printer shows up as shared/enabled/accepting jobs...and since it works with everything except Puppy, I don't think the host is the problem.
The printer does NOT require authentication to accept print jobs from my local network.
I've tried in both Slacko 5.6 and Tahr 6 with the same results. I have the firewall deactivated on both Puppy machines. If any of the gurus on here could give me a hint as to what I'm missing, I'd be extremely grateful!
Things that haven't worked:
This is driving me batty. I *can't* see the printer in PeasyPort, yet it's working perfectly everywhere else. If anyone has an idea of how to locate & connect to my printer, please let me know!
In a nutshell, I have an HP F335 printer shared on a Linux Mint machine. I've also got Samba installed on it, and can see & print to the printer from both Linux & Windows. Other Linux Mint machines see the printer natively through the ipp protocol, and I don't even have to do anything - the printer is just "there", ready to accept jobs. Windows of course requires me to connect to it & install the driver.. but they both work.
When I try to setup the printer for Puppy, however, I'm just not having any luck. The Linux Mint host *does* have CUPS installed, and the printer shows up as shared/enabled/accepting jobs...and since it works with everything except Puppy, I don't think the host is the problem.
The printer does NOT require authentication to accept print jobs from my local network.
I've tried in both Slacko 5.6 and Tahr 6 with the same results. I have the firewall deactivated on both Puppy machines. If any of the gurus on here could give me a hint as to what I'm missing, I'd be extremely grateful!
Things that haven't worked:
- (Installed hplip_print-3.14.10.pet. Using the Deskjet F300 Series hpcups 3.14.10 driver, since Mint uses the 3.14.3 version of the same driver)
ipp://192.168.1.114:631/printers/printer_name
ipp://MachineName:631/printers/printer_name
ipp://192.168.1.114:631/printer_name
ipp://MachineName:631/printer_name
smbc://192.168.1.114/printer_name
smbc://192.168.1.114:631/printer_name
smbc://MachineName/printer_name
smbc://MachineName:631/printer_name
smb://MachineName/printer/printer_name
smb://MachineName:631/printer/printer_name
smb://192.168.1.114/printer/printer_name
smb://192.168.1.114:631/printer/printer_name
(Installed smbw_cups_backend-1.3.pet)
smbw://192.168.1.114:631/printer_name?192.168.1.0
smbw://192.168.1.114/printer_name?192.168.1.0
smbw://MachineName:631/printer_name?192.168.1.0
smbw://MachineName/printer_name?192.168.1.0
socket://192.168.1.114:9100
socket://192.168.1.114
socket://192.168.1.114:9100/printer_name
socket://192.168.1.114/printer_name
This is driving me batty. I *can't* see the printer in PeasyPort, yet it's working perfectly everywhere else. If anyone has an idea of how to locate & connect to my printer, please let me know!
Can you ping 192.168.1.114? Since the Mint machine is also running a Samba server, you should be able to see it on Port 139.
In PeasyPort, set Network Device Speed to slow. Scan for Port 139 or use Names.
Is the Puppy firewall off because you never started it, or because you turned it off? To be sure, run
Run
Does it detect a printer?
In PeasyPort, set Network Device Speed to slow. Scan for Port 139 or use Names.
Is the Puppy firewall off because you never started it, or because you turned it off? To be sure, run
Code: Select all
lsmod | grep iptable
Code: Select all
smbclient -NL 192.168.1.114
Thanks for your reply, rcrsn51!
To answer your questions:
[edit] Ok, I ran "sudo smbd restart" and "sudo nmbd restart", and that fixed the lsmod output. Going to try connecting again now... hopefully? [/edit]
To answer your questions:
- - Yes, I can ping 192.168.1.114.
- PeasyPort does return a response for port 139 even on regular mode, but nothing on 631.
- I've tried the firewall both ways - - turned it off on Slacko 5.6, and never turned on in Tahr. I've also tried configuring the firewall to allow connection sharing as well, as shown in a different thread.
- "lsmod |grep iptable" does show a printer, though I note that it's got a typo in the name... not sure where it's getting that? I've posted a screenshot of the output below. You can see that it's got F3335 instead of F335 - - yet in the Mint CUPS and Mint Printer properties, it's showing F335?
[edit] Ok, I ran "sudo smbd restart" and "sudo nmbd restart", and that fixed the lsmod output. Going to try connecting again now... hopefully? [/edit]
- Attachments
-
- MintPropty.PNG
- (41.01 KiB) Downloaded 302 times
-
- Mintcups.PNG
- (67.89 KiB) Downloaded 299 times
-
- lscapture.png
- (31.29 KiB) Downloaded 305 times
Your firewall is off, which is good.
The CUPS name of the printer sure looks like F335 and it is visible as a Samba shared printer. So the correct setup in Puppy CUPS should be
But first, I would connect the printer to Puppy directly by USB and confirm that you have the right driver.
Also, run "cancel -a" to kill all old print jobs.
The CUPS name of the printer sure looks like F335 and it is visible as a Samba shared printer. So the correct setup in Puppy CUPS should be
Code: Select all
smbw://192.168.1.114/F335
Also, run "cancel -a" to kill all old print jobs.
Ok, the closest I've gotten so far is a "Pending" message using smbw://192.168.1.114/F335. Still no dice on actually getting it to go, however.
I also got a similar "Pending" message under smbc, but it never actually completes.
Connecting the printer directly would be a bit of a pain, since they're nowhere near each other. CUPS in Mint shows HP Deskjet F300 series hpcups 3.14.3 (which works), and Puppy shows HP Deskjet F300 series hpcups 3.14.10... which I'm assuming is a later version, so it *should* work? Couldn't find the exact same version for Puppy, though.
I'll also try it using ipp. If I still can't get it, I guess I'll drag the printer upstairs and give it a try on the Puppy 3.14.10 driver. It's definitely a puzzler why it won't work, since it's been so smooth on my other systems?
Thanks again for your assistance - - keeping my fingers crossed that I can find the magic combination to make it work!
[edit] I also get a "Connected to Printer" message when trying either ipp://192.168.1.114/printer/F335 or ipp://192.168.1.114/F335, but it seems to get stuck there. Nothing shows up in the print queue on Mint.
I'll have to try dragging the printer up to the Puppy system, and see what happens. On my way out for a few hours, so it won't be until later tonight that I can try, however.[/edit]
I also got a similar "Pending" message under smbc, but it never actually completes.
Connecting the printer directly would be a bit of a pain, since they're nowhere near each other. CUPS in Mint shows HP Deskjet F300 series hpcups 3.14.3 (which works), and Puppy shows HP Deskjet F300 series hpcups 3.14.10... which I'm assuming is a later version, so it *should* work? Couldn't find the exact same version for Puppy, though.
I'll also try it using ipp. If I still can't get it, I guess I'll drag the printer upstairs and give it a try on the Puppy 3.14.10 driver. It's definitely a puzzler why it won't work, since it's been so smooth on my other systems?
Thanks again for your assistance - - keeping my fingers crossed that I can find the magic combination to make it work!
[edit] I also get a "Connected to Printer" message when trying either ipp://192.168.1.114/printer/F335 or ipp://192.168.1.114/F335, but it seems to get stuck there. Nothing shows up in the print queue on Mint.
I'll have to try dragging the printer up to the Puppy system, and see what happens. On my way out for a few hours, so it won't be until later tonight that I can try, however.[/edit]
- Attachments
-
- connected.PNG
- (61.79 KiB) Downloaded 660 times
-
- pending.PNG
- (69.41 KiB) Downloaded 663 times
Regarding PeasyPort: I read that some CUPS versions use UDP Port 631 for printer discovery, which would explain why PeasyPort cannot detect it. It only scans for TCP ports.
However, another user was able to make this work using a manual CUPS install
So I don't know why this fails for you. I suspect that Ubuntu and its clones customize CUPS to work with their own stuff.
I suspect that the same is true for the Mint Samba-shared printer, although the smbw protocol definitely works with Windows shared printers.
However, another user was able to make this work using a manual CUPS install
Code: Select all
ipp://192.168.1.114:631/printers/F335
I suspect that the same is true for the Mint Samba-shared printer, although the smbw protocol definitely works with Windows shared printers.
Ok, so it's definitely the right driver. I hauled the printer up to the Puppy machine, plugged it in, and CUPS picked it up right away. I noted that it picked up the name as "HP_Deskjet_F300_series", so I'll add that to my printer name variations to try.
I've moved it back to the Mint host, and Puppy once again doesn't want to see it. I've tried:
BTW - I did verify that the Mint print queue showed clear, both in CUPS and in Print Manager... and I'm pretty sure disconnecting it would have helped as well.
I'm afraid you may be right about CUPS being customized, but I'm sure there's got to be some way of making it work. If Windows can see it, then there's definitely got to be a way....
I think that's it for the night. I've got a full day tomorrow, so it may be Monday before I've got time to muck with it more. But I do appreciate your help and advice! I'll update again when I've got a chance to play with it some more.
[edit] Thanks for the tip about the missing "s" in printers. Looks like I'll have to give those a try again with the right syntax![/edit]
I've moved it back to the Mint host, and Puppy once again doesn't want to see it. I've tried:
- ipp://192.168.1.114/printers/F335
ipp://192.168.1.114/printers/HP_Deskjet_F300_series
ipp://192.168.1.114/F335
ipp://192.168.1.114/HP_Deskjet_F300_series
smbw://192.168.1.114/printers/F335
smbw://192.168.1.114/printers/HP_Deskjet_F300_series
smbw://192.168.1.114:139/printers/F335
smbw://192.168.1.114:139/printers/HP_Deskjet_F300_series
BTW - I did verify that the Mint print queue showed clear, both in CUPS and in Print Manager... and I'm pretty sure disconnecting it would have helped as well.
I'm afraid you may be right about CUPS being customized, but I'm sure there's got to be some way of making it work. If Windows can see it, then there's definitely got to be a way....
I think that's it for the night. I've got a full day tomorrow, so it may be Monday before I've got time to muck with it more. But I do appreciate your help and advice! I'll update again when I've got a chance to play with it some more.
[edit] Thanks for the tip about the missing "s" in printers. Looks like I'll have to give those a try again with the right syntax![/edit]
Actually did that as well. Puppy gets stuck at "Connecting to Printer..." when I do that, both with the ipp://192.168.1.114:631/printers/F335 and ipp://192.168.1.114:631//printers/HP_Deskjet_F300_series entries.rcrsn51 wrote:You are still getting this wrong. You are missing the ":631" in the ipp versions.
The smbw versions don't use it.
But it's good to know that the :631 is needed... even if it's not working, I'm learning a lot about the CUPS protocol. (Trial by fire, I guess?)
Yes it is. I've also toyed with checking/unchecking the "Advertise Web Interface" box, but that hasn't made a difference.rcrsn51 wrote:On the Mint machine, start your web browser and go to "localhost:631/admin".
On the right side, is "Share printers connected to this system" checked ON?
I'll try to log back in this afternoon or evening to try again. Going to be out most of the day.
- Attachments
-
- mintcups2.PNG
- (129.27 KiB) Downloaded 564 times
I tested this with a Mint 11 setup and it worked exactly as expected. I attached a USB printer and set the CUPS server to share (publish) its printer across the network.
I then checked with Slacko, Tahrpup and Mint client machines. All of them auto-detected the printer, as did PeasyPort on Port 631.
It sometimes took a minute for the printer to appear, but it was eventually seen by the clients.
[Edit] I then repeated the process with Ubuntu 12. It also worked correctly.
Is there anything in your router setup that blocks Port 631 traffic to these Puppy machines?
I then checked with Slacko, Tahrpup and Mint client machines. All of them auto-detected the printer, as did PeasyPort on Port 631.
It sometimes took a minute for the printer to appear, but it was eventually seen by the clients.
[Edit] I then repeated the process with Ubuntu 12. It also worked correctly.
Is there anything in your router setup that blocks Port 631 traffic to these Puppy machines?
That is a very good question. And unfortunately, one I don't have a good answer for. My ISP recently replaced my network gateway with an NVG589 - - which quite frankly, is a giant pain in the backside to read & configure. It doesn't have a clear listing of which ports are passed/blocked, and port forwarding/ability to personalize your configuration is marginal at best.rcrsn51 wrote:Is there anything in your router setup that blocks Port 631 traffic to these Puppy machines?
On a lark, I set up a machine with Fedora. It couldn't see the printer either in CUPS, and I couldn't see a way within the printer manager to make it appear either. You may be on the right track with the router. I'll have to see if I can bypass it somehow - - maybe I can resurrect my old home router and give it a shot.
Thanks for all your efforts at troubleshooting this mess! I'll post back once I can get that stupid NVG589 bypassed to see if that's the key.
UPDATE: Still haven't gotten the chance to disassemble my network to bypass the NVG589, but it does appear that this has something to do with blocking port 631.
I ran nmap on the Mint host, and it seems that although port 631 is visible to LOCALHOST, it's not visible if I use the actual IP address of 192.168.1.114. I've attached the screenshot below.
I did turn off the Mint firewall... and have set specific rules in it to allow all traffic in/out on port 631, both for IPv4 and IPv6. It doesn't make a difference - on or off, the port isn't visible on that IP address.
I also found that my other Mint machines seem to be connecting to the printer using a form of a Windows-only protocol... but not smb? When I check the URI, it shows ipps: rather than just ipp:. And of course, CUPS claims this is an unsupported protocol.
I still don't understand why Puppy's CUPS doesn't want to connect via SMBC or SMBW, however....since my Windows systems can do it, it should be possible. If only Windows had a setting to view exactly the URI it's using to connect! (wouldn't that be nice?!)
I'll keep playing around. It's more the challenge than need to print from Puppy at this point....
I ran nmap on the Mint host, and it seems that although port 631 is visible to LOCALHOST, it's not visible if I use the actual IP address of 192.168.1.114. I've attached the screenshot below.
I did turn off the Mint firewall... and have set specific rules in it to allow all traffic in/out on port 631, both for IPv4 and IPv6. It doesn't make a difference - on or off, the port isn't visible on that IP address.
I also found that my other Mint machines seem to be connecting to the printer using a form of a Windows-only protocol... but not smb? When I check the URI, it shows ipps: rather than just ipp:. And of course, CUPS claims this is an unsupported protocol.
I still don't understand why Puppy's CUPS doesn't want to connect via SMBC or SMBW, however....since my Windows systems can do it, it should be possible. If only Windows had a setting to view exactly the URI it's using to connect! (wouldn't that be nice?!)
I'll keep playing around. It's more the challenge than need to print from Puppy at this point....
OK. Your Mint machine has Port 631 open internally on 127.0.0.1, as do all CUPS setups.
But externally, it is using encrypted, secure ipps/https to share the printer. If you run PeasyPort, you should see Port 443 open on the Mint machine.
The problem for Puppy is that you need a newer version of CUPS to support ipps. Fatdog has it. What version of Mint is this?
On Mint, can you reconfigure the shared printer to use regular ipp?
Regarding SMB, is the Samba server on Mint configured to share printers? Do you need Samba for a Windows machine to see the shared printer?
Maybe Windows is seeing the printer as shared by ipps, not by smb.
[Edit] This is strange. I looked in Ubuntu 12 with CUPS 1.5.3. When you set up the connection to a remote printer, you have the option to use ipps. But when you set up sharing of a local printer, I can find no place to select the protocol. So my Ubuntu 12 is defaulting to regular ipp on port 631, while your Mint appears to use ipps on port 443.
I can find nothing helpful on Google.
But externally, it is using encrypted, secure ipps/https to share the printer. If you run PeasyPort, you should see Port 443 open on the Mint machine.
The problem for Puppy is that you need a newer version of CUPS to support ipps. Fatdog has it. What version of Mint is this?
On Mint, can you reconfigure the shared printer to use regular ipp?
Regarding SMB, is the Samba server on Mint configured to share printers? Do you need Samba for a Windows machine to see the shared printer?
Maybe Windows is seeing the printer as shared by ipps, not by smb.
[Edit] This is strange. I looked in Ubuntu 12 with CUPS 1.5.3. When you set up the connection to a remote printer, you have the option to use ipps. But when you set up sharing of a local printer, I can find no place to select the protocol. So my Ubuntu 12 is defaulting to regular ipp on port 631, while your Mint appears to use ipps on port 443.
I can find nothing helpful on Google.
Yup, PeasyPort finds ports 139, 443, 445, and 902 - - just as nmap indicated. It could well be that the version of CUPS is just outdated to the point where it doesn't recognize the newer protocol? Slacko 5.6 contains CUPS 1.4.8, which is rather old at this point. It works fine if I attach the printer directly, and I can share a printer FROM Puppy... but getting a network printer to work IN Puppy doesn't want to cooperate.
**NOTE: I don't have another printer handy that I can attach to a Windows machine to see if it'll pick it up there... but that may be something to try?
The version of Mint I'm using is Rebecca 17.1 x64 Cinnamon, which should be the newest in that line. It's got CUPS 1.7.2, which is unfortunately locked down in the web interface. I can't seem to make any changes to it directly (such as changing the protocol from ipps: to ipp:) without some root password that I don't have - - I only installed my own administrator account on it, but that doesn't seem to work to allow changes in CUPS? All changes have to be made in the Mint Printer panel - - which is currently set to hp:/usb/Deskjet_F300_series?serial=CN68LJ536P04VQ as the URI & protocol.
I do not need anything special for a Windows machine to see the shared printer. I simply go to the network view of the shares, right-click on the printer, and choose "Connect". I confirm the driver, and that's it... easy. So I don't think Windows is seeing it by ipps:, but it's really tough to say for sure?
As I said, this is more of a challenge than a necessity. But I figure if I can get this worked out, it may help somebody else with a similar setup who needs it? I'll keep digging....
**NOTE: I don't have another printer handy that I can attach to a Windows machine to see if it'll pick it up there... but that may be something to try?
The version of Mint I'm using is Rebecca 17.1 x64 Cinnamon, which should be the newest in that line. It's got CUPS 1.7.2, which is unfortunately locked down in the web interface. I can't seem to make any changes to it directly (such as changing the protocol from ipps: to ipp:) without some root password that I don't have - - I only installed my own administrator account on it, but that doesn't seem to work to allow changes in CUPS? All changes have to be made in the Mint Printer panel - - which is currently set to hp:/usb/Deskjet_F300_series?serial=CN68LJ536P04VQ as the URI & protocol.
I do not need anything special for a Windows machine to see the shared printer. I simply go to the network view of the shares, right-click on the printer, and choose "Connect". I confirm the driver, and that's it... easy. So I don't think Windows is seeing it by ipps:, but it's really tough to say for sure?
As I said, this is more of a challenge than a necessity. But I figure if I can get this worked out, it may help somebody else with a similar setup who needs it? I'll keep digging....
Any chance that you could set up a Fatdog machine instead of Puppy? Then instead of ipp, you could use something like
Or it might be auto-detected.
Code: Select all
ipps://192.168.1.114:443/printers/F335