SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Your problem sounds like the cupsd daemon may not be running. Usually "/etc/rc.d/rc.cups start".
Have you checked to see if you can still print from the Linux box recently?
Did the Linux box queue the job or was it stuck at the Win box? On your last attempt, the message would indicate it is stuck at the Win box.
With Win2K there could also be security issues, but if Samba is set to "share" level rather then "user" then it shouldn't be an issue. Except write permission to queue the file in the spool directory.
If you have file/printer sharing enabled in Win2K then there could be master browser issues. You could try shutting down both boxes and then starting the Linux box first, followed by the Win box. Samba has settings that can be increased to raise the level when a master browser is challenged.
Perhaps some of the above will help identify your problem area. I haven't used Samba for quite awhile, so I am not that familar with any of the new options or problems. But I used to run a Win2K box that used Samba share level OK for files and printing.
You might want to review the cups log files in /var/log/cups. (Edit: That may be the error_log you mentioned.) You can also see if cups will print a test page correctly. Uninstall the printer in cups and then reinstall perhaps.
If you still have the prior kernel you boot that and see if the devices change. If it was a default kernel, that can be reloaded from the CD. If you were running the default kernel before then the printer port was a module. I think the module was parport or lp. You could use lsmod and see if the module is loaded.