Differences between current version and previous revision of SambaPrinting.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 29 | Last edited on Friday, August 4, 2006 1:20:49 pm | by CraigBox | |
| Older page: | version 28 | Last edited on Friday, August 4, 2006 12:49:02 pm | by CraigBox | Revert |
@@ -1,7 +1,7 @@
!!! Setting up Samba 3.x and [CUPS]
-Your Samba binary needs to be linked against libcups. To check this, run the following command and check that your output looks similar:
+Your Samba binary needs to be linked against libcups. It will be in all modern distributions.
To check this, run the following command and check that your output looks similar:
<verbatim>
root# ldd `which smbd`
libldap.so.2 => /usr/lib/libldap.so.2 (0x4001b000)
libcom_err.so.2 => /lib/libcom_err.so.2 (0x400c3000)
@@ -55,9 +55,8 @@
!!!Drivers for Windows clients
There are a few ways you can arrage for your Samba server to automagically offer Windows drivers for the printers it shares. The best way is uploading them using Add Printer Wizard. Other methods are covered in the [Samba printing HOWTO|http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/classicalprinting.html#id2597921], which also coveres this information in detail.
-
!!Uploading drivers with the Add Printer Wizard
Windows NT/2000/XP have an Add Printer Wizard. You can use this to add printer drivers to your (cunningly disguised) Samba 3 server.
@@ -84,8 +83,10 @@
Now, fire up the Add Printer Wizard (APW) and run through the wizard, adding appropriate drivers. You'll note that the APW prompts you with 'The server doesn't have drivers for this printer, would you like to upload them now?'. Hit ''no'', (a yes will install them locally only) and then you will get the printer properties window.
Go to the sharing tab, and click 'Additional Drivers', then select the architectures you wish to export drivers for (and you have created directories for), and it should - if its behaving - prompt for the location of the new drivers.
+
+''For some reason, this isn't working for me - I found that if I copied the drivers to the \\server\print$\w32x86 dir the copy could overwrite them, but it couldn't write to them itself, so would prompt for another location locally, thinking they were broken. I have no idea why this happened. --CraigBox''
!Troubleshooting
* Try turning <tt>log level</tt> up in the smb.conf. 3 is a good level. You can also issue <tt>smbcontrol smbd debug 3</tt>, which is cool.
