Ralph; This is a keeper tip sheet..... SuSE 6.3 to Windows 2000 Server printing is working. There is one issue that I have having trouble resolving... The printer is not resetting after the print and errors out..... Any ideas. Again thank you...... -- Kirk Moore Renton, Wa Black Holes are created when God divides by zero -----Original Message----- From: Ralph Clark [mailto:ralph_clark@bigfoot.com] Sent: Sunday, March 05, 2000 7:54 PM To: suse-linux-e@suse.com; kmoore@aa.net Subject: Re: [SLE] Samba and Windows 2000 I just got this working myself. Ironically it's a lot more complicated than setting Linux up as a Samba server! Here's what you do if another (Windows) machine acts as the Primary Domain Controller and password server (as opposed to using the Linux box itself for those functions): (i) Choose a unique Netbios host name for your Linux box. (ii) (Logged in as root) install Samba on your Linux box, configure /etc/smb.conf appropriately, including your chosen Netbios hostname and the IP addresses of the PDC and password server, set START_SMB="yes" in /etc/rc.config and run SuSEConfig. (iii) Get the NT Sysadmin to register your NetBIOS hostname on the PDC. (iv) On the Linux box (logged in as root), run # smbpasswd -j <domain> -r <pdc-host-name> to activate the client. (v) On the Linux box (logged in as root) start up the samba daemons like this: # rcsmb restart (vi) Make sure you can access shared directories on Windows boxes in that domain, from an appropriate login on the Linux box. If this doesn't work then either something went wrong in one of the previous steps or else your Windows network was set up to use Scope ID's. If it's the latter (fairly unlikely) you can contact me for a patch. (v) Use Yast to set up a remote Samba printer. This sets up an extra queue to take the output from the (not yet created) local printer queues and forward it to the print server using /usr/bin/samba_print which in turn calls smbclient. (vi) Use Yast to set up apsfilter printers in the normal way. When it asks for the name of the device where the output should be sent, you send it to /dev/null. The apsfilterrc will detect the requirement to redirect and will forward the filtered, formatted print image to the dummy queue you set up in step (v). However... wulfie wrote:
Either configure smbprint manually or use Yast/System Admin/Network config/Connect to printer using Samba.
Don't forget that you need authorisation from the Win-box so you need a valid Win username & passwd to print.
(The YaST script in step (v) will prompt you for these). There is a bit of a security issue there, unfortunately. Your Windows network password gets stored in *plain text* in the /etc/apsfilterrc.<printername> file, to be passed as a parameter to that /usr/bin/samba_print script I mentioned, because smbclient needs it. The apsfilterrc.<printername> is root-only read/write access...but even so! Beware also that if you turn on debugging in samba_print this password will appear in the debugging log file /tmp/smb-print.log. I therefore strongly suggest that if possible you create a special "printing account" for that NT domain, which has a null or trivial password and no other access privileges, and use the username and password for *that* in step (v). Ralph -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/