Differences between version 22 and predecessor to the previous major change of SambaPrinting.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 22 | Last edited on Sunday, March 19, 2006 11:53:45 am | by CraigBox | Revert |
| Older page: | version 21 | Last edited on Thursday, January 26, 2006 9:19:46 pm | by AriSovijarvi | Revert |
@@ -6,13 +6,13 @@
* To see what resources are available in your network, on Linux one can use smbtree
----
-!!! Setting up samba
and [CUPS]
+!!! Setting up Samba
and [CUPS]
''This covers Samba 3.x, it might be similar in 2.x but be warned''.
-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. 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)
@@ -44,8 +44,10 @@
</verbatim>
As long as your cups printers are set up, you can now set them up on your windows clients and print to them via samba. You might want to investigate uploading client drivers to Samba, using the notes below.
+
+Note: on Debian, you don't seem to get a /var/spool/samba by default. Create it, and set the permissions appropriately on it - so far I haven't found any evidence that you shouldn't use 777.
!!! Using samba and [CUPS] - troubleshooting
Do not, whatever you do, set your cups spool directory and your samba printer spool directory to the same location. Printing via Samba to Cups will *not* work if you do this!
