The time now is Sat 25 May 2013, 10:05
All times are UTC - 4 |
| Author |
Message |
steve_s

Joined: 26 May 2008 Posts: 1543 Location: Austin, TX, USA
|
Posted: Wed 20 May 2009, 19:50 Post subject:
|
|
Well, it wasn't the first time, and certainly won't be the last: it was me, not 4.2. I must have used the wrong sym link or something, but it was me.
Just now I booted in 4.2, set up the internet connection, made sure the link was there (it was) and looked for the picture that you submitted, rcrsn51, as that was a little different than the initial instructions and, of course, it was exactly like you showed.
So, in this case, it was user error. Nice catch and nice job and, above all else in this case, thank you for your patience.
|
|
Back to top
|
|
 |
steve_s

Joined: 26 May 2008 Posts: 1543 Location: Austin, TX, USA
|
Posted: Sun 24 May 2009, 09:10 Post subject:
|
|
Well, I've probably overstayed my welcome here on this thread and rcrsn51 probably hates me by now, but I have to at least ask.
I upgraded to 4.2.1. It killed my connection.
don't know why. When I use 4.2.1 by itself I have no problem setting up the connection.
If I use rcrsn51's smbspool download I don't have any luck; if I use the smbspool with 4.2.1 I don't have any luck...just can't get it to go. And by that I mean that the Windows shared SMB Printer is not on the list, only the "Unknown SMB printer" is on the list. I've changed the smbspool a couple of times, redid the link, rechecked that a couple of times, then restarted cups, can't get it to go.
But unless there is some special item in 4.2.1 then i can't imagine what it would be...I had to at least ask if anyone knew...thanks.
|
|
Back to top
|
|
 |
steve_s

Joined: 26 May 2008 Posts: 1543 Location: Austin, TX, USA
|
Posted: Sun 31 May 2009, 20:46 Post subject:
|
|
Well, can't tell you why it worked, but I followed this murga link and it killed the smbspool link. So, redid the link, everything works.
Don't know why. Something about how it over wrote the current cups kicked it, perhaps? Not sure. Even though I had installed other ways and other cups and redid the link and the smbspool multiple times, this was the one that had done it.
|
|
Back to top
|
|
 |
growler

Joined: 24 Mar 2008 Posts: 209 Location: Kapiti - New Zealand
|
Posted: Sun 07 Jun 2009, 01:59 Post subject:
Experience with 4.2.1 |
|
I had all sorts of problems getting this to work - I have a HP Deskjet 840C on a windows XP SP2 machine which is shared on that machine as HPDesk
I had given it a static IP address of 192.168.0.3
I had an existing link in /usr/lib/cups/backend/smb that linked happily to /opt/samba/bin/smbspool
I tried another version of smbspool that I got off another forum thread - it was actually the identical size in bytes to the one I had so I don't think this was an issue.
I tried several versions of CUPS - the version that came in 4.2.1 of course, then I tried cups-1.4b2-patched-i386.pet and finally cups-1.3.10-i486.pet both from the ibiblio unleashed packages for 4 at:
ftp://ibiblio.org/pub/linux/distributions/puppylinux/pet-packages-4/
I am not sure these were the issue.
I had set up cups with the DEVICE_URI of
smb://Administrator@192.168.0.3/HPDesk
but consistently got the error:
| Code: |
/usr/lib/cups/backend/smb failed
|
The workgroup is CUDGELCONE (don't ask - it's my son's PC!!)
so I tried setting up the printers with:
smb://Adminstrator@CUDGELCONE/192.168.0.3/HPDesk
smb://CUDGELCONE/192.168.0.3/HPDesk
smb://192.168.0.3/HPDesk
for the device URI - none worked
I could print from rxvt using a little test.txt file I made up with:
| Code: |
#smbspool smb://192.168.0.3/HPDesk 111 root "test" 1 '' test.txt
|
The key was that although when adding a new printer I never got the "Windows Printer Via Samba" option.
I did get an smb option and used this to enter the DEVICE_URI manually. From the command line the command:
| Code: |
# lpinfo -v
network socket
network beh
network http
network ipp
network lpd
direct parallel:/dev/lp0
file pdf-writer:/dev/null
direct scsi
serial serial:/dev/ttyS0?baud=115200
network smb
|
showed network smb option available ok?
However, if you don't get a device option of "Windows Printer Via Samba" then there is some error with the link from /usr/lib/cups/backend/smb to /opt/samba/bin/smbspool
As suggested by steve_s post above (thanks Steve!!) I just deleted the existing link - which looked fine?? - and recreated it from ROX - you could equally use:
| Code: |
#rm /usr/lib/cups/backend/smb
#ln -s /opt/samba/bin/smbspool /usr/lib/cups/backend/smb
|
The simplest DeviceURI
smb://192.168.0.3/HPDesk
did the trick
Hope this saves someone else!
|
|
Back to top
|
|
 |
rcrsn51

Joined: 05 Sep 2006 Posts: 7758 Location: Stratford, Ontario
|
Posted: Sun 07 Jun 2009, 06:58 Post subject:
|
|
It's strange how this symlink is corrupted on some people's installs. Did you do a fresh install of 4.2.1 or did you upgrade a pup_save from a previous version?
|
|
Back to top
|
|
 |
growler

Joined: 24 Mar 2008 Posts: 209 Location: Kapiti - New Zealand
|
Posted: Sun 07 Jun 2009, 15:45 Post subject:
|
|
I did a manual copy across of the 3 files from the CD over the existing ones.
The symlink looked fine and definitely linked to /opt/samba/bin/smbspool - but didn't work obviously for some reason which I cannot understand.
|
|
Back to top
|
|
 |
growler

Joined: 24 Mar 2008 Posts: 209 Location: Kapiti - New Zealand
|
Posted: Mon 24 Aug 2009, 03:37 Post subject:
Another solution |
|
I got into trouble again ... same details as above... I could not get the CUPS web interface to give me a
Windows Printer Via SAMBA
option. No amount of deleting the link and re-linking worked so I simply copied /opt/samba/bin/smbspool to /usr/lib/cups/backend/smb rather than linking the file et voila ... all back in business.
|
|
Back to top
|
|
 |
bee_pipes

Joined: 23 Jan 2010 Posts: 15 Location: Podunk, Tn.
|
Posted: Mon 15 Feb 2010, 10:25 Post subject:
|
|
Hi!
Just a quick word of thanks for this thread. I had just gotten an ASUS eeePC (1005PE) and have found everything needed on these forums to get the windows desktop to share folders and devices (CD & DVD drives) with this netbook. The last shared device to get up was the printer. This thread was invaluable. The instructions posted by rcrsn51 were easily followed. I was not immediately successful on the first try and followed suggestions for getting the printer to produce a test page.
I am running puppy 4.3.1 on the ASUS netbook mentioned above. The printer on the desktop (windows XP) was set to shared on properties. Connecting via pnethood samba shares brought up shared folders and devices. The printer appeared as print$. The printer, a canon pixma mp610, was present on the cups list and was identified as a "windows printer via samba". Tinkering with the uri finally made it work. Following the suggestions I had no luck until specifying the uri by the IP address:
smb://nnn.nnn.n.n/printer
I realize this thread is old as moses, relative to software updates and such, just wanted to say thanks for taking the time to put it down in writing. If any other new folks are getting discouraged trying to get a shared printer on a windows box to work, just keep at it. The instructions in this thread are excellent.
Regards,
Pat
|
|
Back to top
|
|
 |
Wognath
Joined: 19 Apr 2009 Posts: 60
|
Posted: Wed 21 Apr 2010, 13:07 Post subject:
Password hidden? |
|
rcrsn51,
Thanks for the great instructions. I used them to network a lab/classroom computer to a windows printer. To allow the connection, I had to include my login and password to the university domain in the printer uri. Can someone confirm that the login/password are well hidden in this semipublic computer? (I tried "modify printer" in CUPS and the password does not appear in the uri.) Thanks.
|
|
Back to top
|
|
 |
rcrsn51

Joined: 05 Sep 2006 Posts: 7758 Location: Stratford, Ontario
|
Posted: Wed 21 Apr 2010, 16:23 Post subject:
|
|
As a test, I set up a dummy printer using a password. I then looked at the file /etc/cups/printers.conf and unfortunately the password was visible in plain text.
There are settings in /etc/cups/cupsd.conf that support encryption, but I know nothing about them. And Googling wasn't very helpful.
I'm sure this is not what you want to hear. I suspect that in a true multiuser environment, the printers.conf file is only readable by the root user, so there would not be a security problem like you have with Puppy.
|
|
Back to top
|
|
 |
Wognath
Joined: 19 Apr 2009 Posts: 60
|
Posted: Thu 22 Apr 2010, 15:56 Post subject:
Password |
|
I was able to use a local login to share the windows printer. Thanks again for this information about passwords and for the instructions.
|
|
Back to top
|
|
 |
ragaman
Joined: 14 Jan 2007 Posts: 186
|
Posted: Sat 01 May 2010, 23:00 Post subject:
|
|
Thanks to the TS for the info. Saved me from a lot of headaches.
|
|
Back to top
|
|
 |
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|