Changes

You can either install the Adobe PostScript driver and basically follow the instructions for the other Windows versions, or you can install the cups-samba package, which contains a free PostScript driver for Windows NT4/2000/XP from the makers of CUPS, and use the cupsaddsmb command as explained below. The cupsaddsmb command exports the PostScript driver from the cups-samba package and the PPD('s) associated with your filtering CUPS queues to the Samba printer drivers directory, making them available for semi-automatic download to Windows NT4/2000/XP hosts.

You can either install the Adobe PostScript driver and basically follow the instructions for the other Windows versions, or you can install the cups-samba package, which contains a free PostScript driver for Windows NT4/2000/XP from the makers of CUPS, and use the cupsaddsmb command as explained below. The cupsaddsmb command exports the PostScript driver from the cups-samba package and the PPD('s) associated with your filtering CUPS queues to the Samba printer drivers directory, making them available for semi-automatic download to Windows NT4/2000/XP hosts.

<ol><li></li>Make sure that you've added at least one filtering queue and that you've "synchronized the printer lists" from the server-manager's printer panel.

<ol></li><li>Make sure that you've added at least one filtering queue and that you've "synchronized the printer lists" from the server-manager's printer panel.

<li></li>Install the cups-samba package, which provides a freely distributable PostScript driver for Windows NT4/2000/XP, with yum (this assumes you have added the 'rvandenaker-cups' repository to your yum configuration).

</li><li>Install the cups-samba package, which provides a freely distributable PostScript driver for Windows NT4/2000/XP, with yum (this assumes you have added the 'rvandenaker-cups' repository to your yum configuration).

  yum install cups-samba

  yum install cups-samba

<li></li>Set "use client driver = no" in smb.conf through the UseClientDriver database property.

</li><li>Set "use client driver = no" in smb.conf through the UseClientDriver database property.

  db configuration setprop smb UseClientDriver no

  db configuration setprop smb UseClientDriver no

  service smb restart

  service smb restart

<li></li>Run cupsaddsmb from the root prompt to "export" your printers. You can export individual printers with the command line

</li><li>Run cupsaddsmb from the root prompt to "export" your printers. You can export individual printers with the command line

  cupsaddsmb -U admin -v printer1 [printer2...printerX]

  cupsaddsmb -U admin -v printer1 [printer2...printerX]

These command lines connect to the samba server as admin, so you need to supply the admin password when prompted.

These command lines connect to the samba server as admin, so you need to supply the admin password when prompted.

<li></li>Printer setup on your Windows NT4/2000/XP hosts should now be a "Point 'n Print" affair. Just browse to a printer on your SME Server share, right click on it and select "Install..." or "Connect..." (depending on Windows version).

</li><li>Printer setup on your Windows NT4/2000/XP hosts should now be a "Point 'n Print" affair. Just browse to a printer on your SME Server share, right click on it and select "Install..." or "Connect..." (depending on Windows version).

<li></li>Repeat the previous step for all printers.</li></ol>

</li><li>Repeat the previous step for all printers.</li></ol>

====Printing from Windows 2000/XP over IPP====

====Printing from Windows 2000/XP over IPP====