Differences between version 25 and previous revision of SambaPrinting.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 25 | Last edited on Thursday, August 3, 2006 6:56:25 pm | by CraigBox | Revert |
| Older page: | version 24 | Last edited on Thursday, August 3, 2006 6:30:57 pm | by CraigBox | Revert |
@@ -50,9 +50,9 @@
lpq command = lpstat -o %p
lprm command = cancel %p-%j
</verbatim>
----
+--
---
!!!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. (Google for rpcclient or imprints if you care for the others.)
@@ -70,27 +70,30 @@
path = /home/samba/printers
guest ok = yes
browseable = yes
read only = yes
- write list = @wheel, root, daniel, admin
- admin users = @wheel, root, daniel, admin
+ write list = @wheel, user
+ admin users = @wheel, user
create mask = 0644
directory mask = 0755
</verbatim>
-The path can be anywhere, really. All that matters is that the permissions are set appropriately - the user you connect as should be able to write to the fo I set them to
777 for the purpose of
this exercise: this may not be neccesary
+The path can be anywhere, really. All that matters is that the permissions are set appropriately - the user you connect as should be able to write to the files. Try
777 if you really want to make sure.
+
+Connect to \\server\print$. You will need to create directories here
for drivers; <tt>W32X86</tt> is for NT/2000/XP, <tt>WIN40</tt> is for Windows 95/98. This is a good test to see if you can write to
the PRINT$ share.
+
+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'', and then you will get the printer properties window.
-* Join the Windows machine (the client) to your domain, if you wish.
-* Find a user you can use that has an (effective) uid of 0 on the Samba server. Note: This doesn't mean you have to use the root user, its actually ok to set a printer admin and use that.
-* Login as this user to the client.
-* 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?'
-* After you've correctly added the drivers on the client, right-click on the printer icon and select sharing. Make sure that sharing is enabled for this printer.
-* Magic time. Not sure if this is neccesary - a reboot of the NT machine may do the job instead. Remove the printer you just added.
-* Re-add the printer you just added. If things go well, it'll remember you already had the drivers intalled, and it'll just load up straight away
* Go to the properties page for the printer you just added, and go to the 'ports' section. After going through the above removal-readd rigmoral, I have only one port listed - a 'Samba Printer Port' one. Make sure this is checked.
* You can now add extra drivers - go to the sharing tab, and click 'Additional Drivers', then select the architectures you wish to export drivers for, and it should - if its behaving - prompt for the location of the new drivers.
All done.
+
+Troubleshooting:
+
+* Try turning <tt>log level</tt> up in the smb.conf. N is a good level.
+* To find local drivers, try %systemroot%\system32\spool\drivers\w32x86.
+* __Unable to install ''printer'', Intel, Windows 2000 or XP driver. Operation could not be completed__ - Did you create a W32X86 directory under print$?
You can have a look at whats happening on the server side of things with the <tt>rpcclient</tt> program:
<pre>
