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've got a HP DeskJet 1220C installed on my Windows Server 2003 machine, set up as a shared resource as so.
Code:
//192.168.0.4/HpDeskJe
I decided to use YaST to try and configure my desktop to print using this printer. I went through the wizard, apparently fine, but when I hit print, I just get endless sheets of paper coming out the printer. In the print queue the job comes up as Remote Downlevel Document, the whole thing spools fine but the file contains nothing. Same result when attempting to print from, say OpenOffice.org.
1-on my windows machine I clicked on My Computer and then My Network Places.
2-then I clicked on Setup a home or small office network.
3-clicked next a few times and then choose the 3rd option in Windows XP which is labled OTHER
4-chose the first one on the next page which is 'this computer connects to the internet via network hub' which is my router.
5-clicked next and just followed the directions and named a new workgroup.
6-restarted the computer and then went in and went in and unchecked the Windows XP Firewall and restarted.
7-went over to my SuSE 9.0 Pro machine and opened up controls/peripherals/printers.
8-clicked on the admin button on the lower left and went into the Yast Admin panel
9-I then just click on Add Printer at the top and followed the directions for SMB(Windows).
10-I then pressed on Scan and it found the new Workgroup that I created with my Windows XP machine and the printer.
11-Finally, I just clicked on the +'s and it does not find the printer. It sees the windows box but not the printer. And, when I click the + I get an NT authority error.
Your "endless sheets of paper" problem is caused by using an incorrect driver for the printer.
To use a network printer in windows, the other machine also needs to have a correct driver for the printer.. :roll: You can also try to configure the windows machine so it accepts standard "postscript" data.
Hmm, it's a flaw in the UI design. Is there a good reason why there is a button to test printing BEFORE you've loaded the drivers for it? All is well and good now
Originally posted by goldfish Hmm, it's a flaw in the UI design. Is there a good reason why there is a button to test printing BEFORE you've loaded the drivers for it? All is well and good now
Maybe you can file a bug for it at suse.com (they have a feedback page for bugs!)
I have successfuly setup my windows shared printer in Suse 10 RC1. I can print a test page to the windows printer, and I can even print from Open Office. But nothing I print from Firefox makes it to the printer. Neither the Suse printer job manager shows a pending print job, no the windows print manager. Isn't that wierd that some programs can print and other can't?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.