LinuxQuestions.org - WinXP open print sharing

- Linux - Networking (http://www.linuxquestions.org/questions/linux-networking-3/)

- - WinXP open print sharing (http://www.linuxquestions.org/questions/linux-networking-3/winxp-open-print-sharing-219486/)

WinXP open print sharing

I have a MDK10 box running on a local network of all WinXP machines, and wanted to use the Linux box as a print server. I had done it before pretty easily with another XP Pro box (P 166, slow, but worked) and thought I could eliminate a computer. I want ANYBODY on the network to be able to print with NO PASSWORDS. I already have Samba set up to share a directory with the same parameters, totally open. Now I want my printer (DeskJet 812C) to do the same thing. I have TCP/IP and IPX and all the standard Clients installed on all the XP PCs, and the Linux box is on 24/7, and the printer is on a parallel port. The printer works fine from within Linux, and the Windows XP boxes can all SEE it and make little setting changes in their own dialog boxes, but can't actually print.
Attempt to do a test page gets "Test page failed to print. Troubleshooter? Unable to create print job."
An attempt to print from Notepad gives me "A StartDocPrinter call was not issued." I pretty much let Mandrake do this all on it's own and it showed up in Windows, I looked at the cups.conf and smb.conf files to see what it might be, but I'm not really sure what I'm looking for. Any suggestions?

I'm having the same problem, I get access denied on all my winxp machines when I attempt to connect to my linux printer.

As you may already know, the Samba configuration file is /etc/samba/smb.conf

Since you are using CUPS, in the global section of the smb.conf, you need the following options

Code:

  printing = CUPS

  printcap name = CUPS

  load printers = yes

Also, the printers section should look like the following:

Code:

[printers]

  comment = All Printers

  path = /var/tmp

  printable = yes

  create mask = 0600

  browseable = no

  guest ok = yes

other than Mathieu's suggestion,

I had the same issue and a 45.00 print server solved the issue all together