I can't use the printer of a Windows XP machine, using Slackware Linux
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I can't use the printer of a Windows XP machine, using Slackware Linux
Ok, here's my issue, Im using a Slackware machine right here, with an Ethernet adapter..., in my house we have 2 computers... that are linked trough a switch, the network used to work sweet when both computers had Windows, now that I switched to Linux... I finally had achieved to mount the other computer... using mount -t cifs... but the printer... I havent been able to make it work.
Yesterday what I did was... installing CUPS and SAMBA, ok... did a smbclient to see if Samba was seeing the other computer... it worked great, all the shares appeared on the screen!!!, so well... i added the printer like this:
URI = smb://[NAME OF THE COMPUTER]/[NAME OF THE PRINTER]
But it didnt work... it says Unable to connect to SAMBA host, will retry in 60 seconds...ERROR: Connection failed with error NT_STATUS_ACCESS_DENIED.
I googled a little bit... and I found that I should use this syntax:
smb://USER:@COMPUTER/PRINTER
Ok... I did this... no more that error... but all the jobs automatically get aborted... and they never arrive to the printer... the .ppd drivers are just fine, samba, cups... everything working... I tried to see if I could do anything trough localhost:631... nothing.
I need someone thas has his Linux machine printing sweet on a Windows XP one... cause im having some trouble right here, Thanks.
The easy way would be installing on the windows machine UNIX TCP printing services
Once this work, set (under CUPS) lpd protocol. That should do. There is some glich with compatibility of pasword handling between samba and CUPS, so using LPD you will simply skip the problem (which can be resolved to by the way)
Originally posted by broch The easy way would be installing on the windows machine UNIX TCP printing services
Once this work, set (under CUPS) lpd protocol. That should do. There is some glich with compatibility of pasword handling between samba and CUPS, so using LPD you will simply skip the problem (which can be resolved to by the way)
The UNIX TCP printing services is a daemon right???
Mmm... I dont know if I can use a daemon in that computer... my brother uses it and I dont know if he is gonna like the idea.
The ideal thing would be using Samba with CUPS from here... and nothing there... that would be great.
Heheh... its just that the computer that has the printer is like... very well tweaked and if we can avoid adding another service to it... that would be nice.
If Samba doesnt work Ill try the service you mentioned.
Last edited by Shagrath239; 02-21-2005 at 10:41 AM.
At boot time with this service Windows XP is taking 65MB. Without it takes ~64MB. So what is the problem? Whatever is your windows setup I dont think that TCP services for windows will hurt.
However you can try resolve password problem by changing smb.conf as above and setting right parameters in the windows registry (allow lm passwords only)
It was a driver problem!!! all thanks to the allmighty LOG (/var/log/cups/error_log) that helped me out here. I got it working with smb protocol!!! thats right!!! no daemon in the Win XP machine!!!
And of course thanks to the only guy that gave me a hand on the issue, mr. broch.
This thing has been SOLVED baby yeah!!!, you can close this thread if you want to!!!
PS: If you wish to see the full output in the log, go to /etc/cups/cupsd.conf and look for the line that says LogLevel, edit to the value that you want. Im out of here!!!
Solution: (for the guy that used the search button and is looking at this right now):
In my case i own a HP deskjet 710C that is connected through LPT1 to a WinXP machine.
Went to linuxprinting.org, got the correct driver... then, did a script for myself in order to add the printer, here it is if you want to use it:
We are gonna call our printer "dog", you can use any name you want.
/usr/sbin lpadmin -p dog -v smb://user@pass@workgroup/IPOFTHEMACHINE/PRINTER-SHARE-NAME -P /usr/share/ppd/HP/HP-DeskJet_710C-pnm2ppa.ppd && /usr/bin/enable dog && /usr/sbin/accept dog && /usr/sbin/lpadmin -d dog
All right... everything looks sweet right??? but something is missing for our HP Deskjet 710C... the binary for pnm2ppa... so what you gotta do is go to sourceforge.net/projects/pnm2ppa, download the pnm2ppa SOURCE, do a make (just a make, nothing else), catch the file pnm2ppa that has been created, move that thing to /usr/bin (or whatever your main path is), and that's it... enjoy your printer!!! i mean remote windows printer!!!
PS: Remember creating an account in the Windows PC exclusively for remote Linux
control of the printer!!!, just create an ordinary account... it doesn't has to be administrative, just ordinary
Last edited by Shagrath239; 02-21-2005 at 04:05 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.