[Samba] Re: samba Digest, Vol 43, Issue 7
On Thursday 06 July 2006 13:08, [EMAIL PROTECTED] wrote: Message: 29 Date: Wed, 05 Jul 2006 11:29:23 -0500 From: Don Meyer [EMAIL PROTECTED] Subject: Re: [Samba] Print Cost Capture To: Samba User's List [EMAIL PROTECTED] [...] The catch is that it was written around LPRng. A couple times now, I have attempted to modify (update) the system to use CUPS -- but I've always been stymied by the lack of any functions to move jobs from one queue to another. Uuhmmm what makes you think that you can't move jobs from one queue to another when using CUPS? What are your exact requirements when moving jobs? Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Print Cost Capture
(Re-posting because I was too stupid to change $subject as needed) On Thursday 06 July 2006 13:08, [EMAIL PROTECTED] wrote: Message: 29 Date: Wed, 05 Jul 2006 11:29:23 -0500 From: Don Meyer [EMAIL PROTECTED] Subject: Re: [Samba] Print Cost Capture To: Samba User's List [EMAIL PROTECTED] [...] The catch is that it was written around LPRng. A couple times now, I have attempted to modify (update) the system to use CUPS -- but I've always been stymied by the lack of any functions to move jobs from one queue to another. Uuhmmm what makes you think that you can't move jobs from one queue to another when using CUPS? What are your exact requirements when moving jobs? Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Printing not working after upgrading to 3.0.4
Skip Morrow skip-samba at pelorus.org Sun May 23 10:47:12 GMT 2004 I read your mail, but I don't see anything that could cause your problem. Please re-post with a few more details. Tell us about your printer type(s), the driver(s) you use on the Win clients, which Samba version you was using previously, what the settings of your smb.conf are (please strip comments), which CUPS version you use, which OS version your Samba is installed on, etc. I have an HP, 2100M printer. The driver that I have loaded in Windows is HP Laserjet 2100 Series PS. *How* did you install that driver? And the printer you own is in fact a PostScript-enabled modell? (Sorry, I don't know by heart if that 2100M defaults to include PS, or if PS is only an upgrade option) If you installed it as a local client driver, you have to use use client driver = yes in smb.conf (this is not the recommended setting, but works also). A locally installed driver (for a shared printer) on the client can be more exposed with this commandline (in a Samba host shell), even if the test page isn't printing: rpcclient -Uwindowsuser%windowspassword -c enumdrivers 3 windowshostname This command shows up pretty much the same info as a printed testpage would do If you installed it via Point'n'Print, you should be able to use that command in a Samba host shell: rpcclient -Uroot%smbpasswd-of-root -c enumdrivers 3 localhost Unfortunately, I don't have any more information The operating system? Linux? Which distro? Who built the Samba packages? Is CUPS support compiled into the Samba binaries? about the driver becasue I can't print the test page. See above. Here are the pertinent setting from smb.conf: Is this the same smb.conf you inherited from your previous Samba installation? [global] netbios name = PELORUS server string = samba server interfaces = 192.168.0.1 bind interfaces only = yes encrypt passwords = yes log file = /var/log/samba/%m.log max log size = 0 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 dns proxy = No hosts allow = 192.168.0. 127. printing = cups load printers = yes security = SHARE Change that to security = user as the Samba HOWTO Collections suggests. (Don't forget to set Samba passwords with smbpasswd -a root and smbpasswd -a username) printcap name = cups guest ok = yes [printers] comment = All Printers path = /var/spool/samba browseable = no public = yes guest ok = yes writable = no printable = yes printer admin = skip, suzanne, sfm, root, @ntadmin, smorrow I do not remember what version of Samba I had before. I installed it so long ago, and it worked fine for so long, I really didn't think about it too much. I am using CUPS version 1.1.20 So your old Samba with the same smb.conf setup did work with CUPS-1.1.20 ?? #printers.conf DefaultPrinter HP_LJ_2100M Info HP LaserJet 2100M Location Pelorus DeviceURI parallel:/dev/lp0 State Idle Accepting Yes JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 /Printer #cupsd.conf ServerName localhost This setting doesn't work for any other host as a client. (It works for Samba, since smbd transmits the file to cupsd from localhost...). You should either comment the line out (in which case cupsd will default to use the hostname for ServerName, or use ServerName your host's IP address or explicitely go for ServerName your hostname. Classification none DefaultCharset UTF-8 DefaultLanguage en Printcap /etc/printcap PrintcapFormat BSD RemoteRoot remroot SystemGroup sys ServerCertificate /etc/cups/ssl/server.crt ServerKey /etc/cups/ssl/server.key Location / Encryption IfRequested Satisfy All Order deny,allow Deny From All Allow From 127.0.0.1 Allow From 192.168.0.* /Location Location /admin AuthType Basic AuthClass System Encryption IfRequested Satisfy All Order deny,allow Deny From All Allow From 127.0.0.1 /Location HostnameLookups On KeepAlive On KeepAliveTimeout 60 MaxClients 100 MaxRequestSize 0m Timeout 300 Listen *:631 AccessLog /var/log/cups/access_log ErrorLog /var/log/cups/error_log PageLog /var/log/cups/page_log MaxLogSize 1m LogLevel debug2 LogLevel debug2 will drown you in error messages. Considering that you have limited the error_log file size to 1 MByte, this will effectively prevent you from ever finding anything useful in the log. 1 MByte of debug2 output fills the file in seconds before it log-rotates. Better use MaxLogSize 10m LogLevel debug and have all the relevant info at your fingertips. In case there is really a severe problem, you can always go for debug2 and 50 MByte for a limited period of troubleshooting. What do you see in the /var/cups/log/error_log as noted when the job arrives at CUPS? Look for a line containing print_job: auto-typing file... and the following print_job: request file type is What is it? Also
[Samba] Printing not working after upgrading to 3.0.4
Skip Morrow skip-samba at pelorus.org Sat May 22 22:54:26 GMT 2004 I had been running Samba to share my HP printer among my Windows XP clients. When I upgraded to 3.0.4, I can no longer print. When I start the print job in Windows XP, the printer lights blinks for a few seconds, and then stops. No pages come out. The print job is shown as complete in the CUPS web intrface. Printing from the Linux box works just fine. I read the Samba pages concerning printing, and the chapter on CUPS, but I don't see anything that could cause this problem. I read your mail, but I don't see anything that could cause your problem. Please re-post with a few more details. Tell us about your printer type(s), the driver(s) you use on the Win clients, which Samba version you was using previously, what the settings of your smb.conf are (please strip comments), which CUPS version you use, which OS version your Samba is installed on, etc. The share is still listed in smbclient, and I have tried re-installing the printer from Windows. Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Having issues with rpcclient's adddriver
Tim Kent tim.kent at wkconsulting.com.au Tue May 18 01:09:20 GMT 2004 Hi, I'm trying to add a Windows NT/2000 OKI C5100 print driver to a Samba 2.2.3a server. Can't you try to use a more current Samba version? (The most current versions have support for the version tag of printer drivers...) I've been told that this driver does some server-side stuff, so I'll have to use 'adddriver' in rpcclient. I've read the manual page for rpcclient, and I printed out a 'Windows 2000 Printer Test Page' to get all the relevant information. This is probably just something simple, but I've checked this out a couple of times and keep getting a syntax error. Do I have too many files listed, and if so do I need all of these listed files? tim at test:~$ rpcclient test -U root INFO: Debug class all level = 2 (pid 9287 from pid 9287) Enter Password: session setup ok Domain=[TEST] OS=[Unix] Server=[Samba 2.2.3a-13 for Debian] rpcclient $ adddriver Windows NT x86 OKI C5100:IMFNT4.DLL:OPHCWDDM.SDD:SDNTOK.DLL:OP51ENU.HLP:\ OKI HiperC Language Monitor:RAW:ABEXPW32.DLL,CANLKN.PRF,CNNbapie.DLL,\ CNNsCore.DLL,CNPPDCE.DLL,CNXADR.DLL,CNXCOV1.EMF,CNXCOV2.EMF,\ CNXCOV3.EMF,CNXCOVL.EMF,CNXCR.DLL,CNXDMAN.DLL,CNXECR.DLL,CNXP5EE.DLL,\ CNXP5EE0.CNT,CNXP5EE0.HLP,CNXP5EEP.DLL,CNXP5EEU.DLL,CNXPRASX.DLL,\ CNZ005N.ICC,CNZ006N.ICC,CNZ007N.ICC,CNZE15N.ICC,CNZE18N.ICC,\ CNZE21N.ICC,CNZN15N.ICC,CNZN18N.ICC,CNZN21N.ICC,CNZP15N.ICC,\ CNZP18N.ICC,CNZP21N.ICC,CnP5eE.DLL,CnP5eE0.CNT,CnP5eE0.HLP,\ CnP5eEUI.DLL,CnP5eEUM.DLL,DCS.DLL,DCSTBL.DLL,GP300FK.XPD,GP300PK.XPD,\ IMF32.DLL,IMFPRINT.DLL,ML51NSAR.DLL,OK001U2H.CAP,OK009U0H.CCM,\ OK714NHE.VER,OMRDM32.DLL,OP5100.DAT,OP5100.UNZ,OP51ICB.BIN,\ OPCLB002.DLL,OPCST000.DLL,OPDMN004.DLL,OPDVA002.DLL,OPHCRENU.DLL,\ OPHCSENU.DLL,OPHCWDDM.DLL,OPHCWDUI.DLL,OPHCWINF.DAT,OPHCWM00.DAT,\ OPHCWNXS.DLL,OPHCWNXT.DLL,OPHCWS00.DAT,OPNE000C.SCR,OPRCL000.DLL,\ OPS00ENU.DLL,OPS00JPN.DLL,OPUSB000.DLL,QDPRIOK.DLL,RDMWIN32.DLL,\ SDDM.INI,SDDMOK.DLL,SDDMUK.DLL,SDIMFOK.DLL,SDNTUM4.DLL,SDOK.DLL,\ SQMCODER.DLL,SROK.DLL,ZENOCMM.DLL,ZENOICM.DLL,ZGDIOK.DLL,ZLANG.DLL,\ ZSPOOL.DLL,ZSPOOLOK.EXE,ZTAG32.DLL Usage: adddriver Environment\ Long Printer Name:Driver File Name:Data File Name:\ Config File Name:Help File Name:Language Monitor Name:\ Default Data Type:Comma Separated list of Files I know that looks like a very long list, but that's what the 'Windows 2000 Printer Test Page' told me! I'm assuming that most of those files are related to some kind of monitor that I could perhaps do without. The adddriver subcommand expects (for Windows NT/2000) to find all the files in the [print$]/W32X86/ subdirectory. It then moves the files into [print$]/W32X86/2/ and creates the fake registry entries (in the *.tdb files) for the driver. If your adddriver command fails once (for one reason or another, like mistyping anything), you can't repeat it without makeing sure that all initial files are still in [print$]/W32X86/. Your failed first adddriver command may have moved away all or part of the files. Your second attempt at the adddriver command now will fail because it doesn't find the files you reference. Lastly, I'd recommend to run the command all in one: rpcclient -Uroot%passwd -c 'adddriver Windows NT x86 OKI:yada:...' sambahostname As far as my syntax is concerned I have the files in the right order. It looks like your syntax is OK. But I remember having had problems with 2.2.3a and adddriver. If nothing else works, an upgrade to 3.0.4 should help Cheers, Tim Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] samba+cups printing a banner
Vit vmf11 at hotmail.com Mon May 17 19:46:17 GMT 2004 i set up a print server using samba and cups and it seems to be working fine but in my environment it is vital for each printjob to have a banner with netbios name on it. eg i have 700 public computers and 4 printers so i need each computer to print a banner with the hostname to distinguish who prints what. i tried to set it up on the client side but it doesnt seem to be working. any help would be greatly appreciated. 10x You should use the CUPS PostScript drivers for Win NT/2K/XP on your clients (Win 95/98/ME are not supported). They are the only ones to support CUPS banners. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] cupsaddsmb
Matteo matteo at ilteo.it Thu May 20 21:50:34 GMT 2004 HI! I've a problem with cupsaddsmb!! :-( You'd surely harvest a more definite answer if you had spiced the question seed with some version info about CUPS, Samba and the OS-s you're using... At the console I type: cupsaddsmb -U root -v printername and after some operations complete correctly appear this error: [...] Running command: rpcclient localhost -N -U'root%' -c 'adddriver Windows NT x86 eps6100l:cupsdrv5.dll:eps6100l.ppd:cupsui5.dll:cups5.hlp:NULL:RAW:NULL' cmd = adddriver Windows NT x86 eps6100l:cupsdrv5.dll:eps6100l.ppd:cupsui5.dll:cups5.hlp:NULL:RAW:NULL Printer Driver eps6100l successfully installed. Running command: rpcclient localhost -N -U'root%' -c 'setdriver eps6100l eps6100l' cmd = setdriver eps6100l eps6100l result was NT_STATUS_UNSUCCESSFUL This last error is typically showing up if your printer eps61001 is not yet known to Samba. This may happen if you just installed that printer freshly in CUPS and run cupsaddsmb before doing a kill -HUP `pidof smbd` The most recent Samba version (3.0.4) shouldn't require this any more. But older versions only learn about these printers which are available at smbd startup, and don't auto-learn new printers added during smbd runtime. Why rpcclient can't associate my shared printer with the successfully installed printer driver? Likely because the shared printer doesn't exist from Samba's point of view... Check it with rpcclient -Uroot%smbpassword -c enumprinters sambahostname What is the matter? Any idea? Thanks! ilteo -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Need help on Samba Printer Port
[Samba] Need help on Samba Printer Port Farget Vincent farget at olfac.univ-lyon1.fr Fri May 7 12:45:54 GMT 2004 Hi, I have 3 HP network printer with internal jetdirect board. One 4000N, one 4050N and one 4200N. All are share on my PDC Samba server which is under Linux Debian stable Woody (v3.0rX) : Samba v2.2.3a-13. I have a little question that I cant' answer my self : Can it be a problem if all of these printer have [Samba Printer Port] as their 'portname' ? No problem. See http://samba.vernstok.nl/htmldocs/howto/printing.html#id2570520 (Heading Samba and Printer Ports) Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] page count logging samba/cups
Kuba Leszewski k.leszewski at ce3.pl Wed Apr 28 14:57:18 GMT 2004 Hi, I know this subject appeared a few times on this list, but I've tried some of solutiuons presented there, and nothing works. I have a CUPS server and HP LaserJet 2200 printer. Which OS are you using? Which Samba version? Which CUPS version? I downloaded postscript driver for this printer from cups.org, installed it in CUPS and then installed it using cupsaddsmb in Samba. This driver now installs automatically on my Windows clients. Problem is that I need to log number of pages everyone prints. So far I can log correct numbers for users that have Linux, and use CUPS directly (without Samba). But when I use a printer shared through Samba, then every print job appears as single page. I read this: http://lists.suse.com/archive/suse-linux/2002-Jan/2508.html and this: http://lists.samba.org/archive/samba/2002-November/056520.html I understand that the print job must pass through the 'pstops' filter, in order to get logged properly. Have you checked how your job is processed by CUPS? *Does* the job pass the pstops filter or not? Which actual filtering chain is used? (set LogLevel debug in /etc/cups/cupsd.conf, restart cupsd, grep in /var/log/cups/error_log for all lines containing filter) But all the solutions I found, don't work. At least you've proofed that you searched the archives, and that you found the relevant pieces of info on your own...;-) (Too few do that.) -- Regards Kuba Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] printer server
Alexandre Carlos alexandre at redes.unb.br Tue Apr 20 17:17:30 GMT 2004 I trying to share a printer using samba, but is not working. I already share the files but the printer didn't workout. I'm using CUPS. Can anyone help me solve this problem? The configuration of smb.conf for printing is: [global] workgroup = GRUPO netbios name = LINUX server string = Servidor Samba interfaces = eth0 security = SHARE Use security = USER and try again... (You may additionally switch to printcap = CUPS, but make sure you have Printcap /etc/printcap in cupsd.conf also) Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] which print tool: CUPS vs BSD?
Joe Cipale wrote: Kurt Pfeifle wrote: Joe Cipale joec at aracnet.com Tue Apr 20 20:57:34 GMT 2004 Which printing mnechansim works best with Samba? CUPS or BSD? CUPS. libcups.so is linked into Samba (if configured with this -- default -- option). CUPS is also much more advanced and feature-rich than BSD. I suspect that BSD support in Samba is not the greatest. Don't blame Samba for that ;-) The reason is, that BSD-printing doesn't support much by itself. ;-) [] Sounds like I may have to: 1 - Reinstall Samba and make sure I have the cups option compiled in. First check your current version: ldd `which smbd` | grep cups should output something like libcups.so.2 = /usr/lib/libcups.so.2 (0x4002f000) Or, in Samba-3, use smbd -b | grep -i cups and look for HAVE_CUPS 2 - Validate whcih vers of CUPS I am using. (IS there a way to do that?) Thanks in advance, Joe Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Add printer wizard (XP)
Message: 19
Date: Wed, 14 Apr 2004 12:54:02 +0100
From: Hamish [EMAIL PROTECTED]
Subject: [Samba] Add printer wizard (XP)
To: [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii; format=flowed
Hello list
I have been really wowed by samba 3 so far, i just have one last mission
to complete... please help!
I have samba 3.0.2a-SuSE installed on a SuSE 9.0 box. It uses winbind to
authenticate against a win server 2003 box - this seems to work fine,
users can own files and this is shown when getfacl is run on the shares
(owned by DOMAIN\User).
The last problem i have is adding printers...
The add printer wizard shows for the windows domain administrator, and
he can add a printer right untill the last screen of the wizard - when
he clicks the finish button, it shows the error:
Add Printer Wizard
Unable to Install Printer. Access is denied.
You need 2 things for this to work:
1.) a setting in smb.conf add printer command = /path/to/smb-add-printer-script.sh
2.) an actual smb-add-printer-script.sh script in named path
So far, I don't know of anyone who has written a reliably working add
printer command script which works with CUPS.
By own efforts got stuck some time ago because of a weird re-naming problem
(Samba re-named my newly created printer because it executed the script a
2nd time somehow)
I will probably revisit that topic within the next few weeks.
The point is that the script needs to take the variables to run CUPS lpadmin
from what the user filled into the Add Printer Wizard fields
The only thing i can think of is that he has no permission to add a cups
printer? The driver files are correctly copied across to PRINT$, but
then straight after this the error appears.
The usefulness of the APW for you (without the add printer command) is
currently limited to add new drivers and for existing printqueues
Here is my smb.conf:
It misses the add printer command line
[global]
workgroup = MYDOMAIN
server string = samba test
security = DOMAIN
password server = pwdserver
log level = 1
syslog = 0
socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
printcap name = CUPS
os level = 2
preferred master = No
local master = No
idmap uid = 1-2
idmap gid = 1-2
admin users = MYDOMAIN\administrator
printer admin = MYDOMAIN\administrator
printing = cups
veto files = /*.eml/*.nws/riched20.dll/*.{*}/
Cheers,
Kurt
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] cupsaddsmb adobe error message
[Samba] cupsaddsmb adobe error message Sundaram Ramasamy sun at percipia.com Fri Mar 12 04:18:05 GMT 2004 Hi, I am trying to add automatic driver install, its giving me ADOBEPS5.DLL file not found error message. You should read the man page of cupsaddsmb. It would tell you that the preparation to be completed *before* running the command consists, amongst other things, to place the Windows driver files into the /usr/share/cups/drivers/ repository. (Unfortunately the license prohibits the free re-distribution of the Adobe driver files.) Where can I get these files? From any Windows 2K/XP workstation that shares a PostScript printer It will have a share named print$ where it offeres driver files for Point'n'Print installations. Try this: smbclient -U windowsusername //windowshostname/print\$ cd w32x86 cd 2 mget ADOBEPS*.* Another option is to go to the Adobe website and search for their PostScript driver. Cheers, Kurt My configuration Samba 3.0.2a with cups. # cupsaddsmb -U root -v -a Password for root required to access localhost via SAMBA: Running command: smbclient //localhost/print\$ -N -U'root%abc123' -c 'mkdir W32X86;put /var/spool/cups/tmp/4051394ee08ec W32X86/pdf.PPD;put /usr/share/cups/drivers/ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLL W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP' Domain=[TUX-NET] OS=[Unix] Server=[Samba 3.0.2a-SuSE] NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86 putting file /var/spool/cups/tmp/4051394ee08ec as \W32X86/pdf.PPD (6463.0 kb/s) (average 6463.2 kb/s) /usr/share/cups/drivers/ADOBEPS5.DLL does not exist /usr/share/cups/drivers/ADOBEPSU.DLL does not exist /usr/share/cups/drivers/ADOBEPSU.HLP does not exist Password for root required to access localhost via SAMBA: -SR -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] downloading printer drivers from W98 client
Norbert Gomes norbert.gomes at orleans-tours.iufm.fr Thu Mar 11 16:06:56 GMT 2004 Hi I've got some problems with the download of Adobe PostScript printer drivers on a Windows 98 client : On the server side (Red Hat 9 / Samba 3.0.1 / Cups 1.1.17) : I installed succesfully my printers with Cups and they work fine on Linux I ran cupsaddsmb tool to copy the Adobe files in the [print$] directory which gives this result : ./W32X86/2 : cupsdrvr.dllcups.hlpcupsui.dllhp2200.ppd hp2300.ppd ./WIN40 : ADFONTS.DLLDEFPRTR2.PPDICONLIB.DLLPSMON.DLL ./WIN40/0 : ADOBEPS4.DRVADOBEPS4.HLPhp2200.PPDhp2300.PPD On the client side (Windows 98) : I install the printer via the Network Neighbourhood but only the ADOBEPS4.DRV file is copied from the server and Windows can't print the Test Page. If I manually install the Adobe Drivers on the client, I can use the printer. Could you post the complete output of cupsaddsmb -v, please? (Remember to replace that root or other password that shows up there) Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] rpcclient and WERR_INVALID_PRINTER_NAME
[Samba] rpcclient and WERR_INVALID_PRINTER_NAME christian.loew at steyr-ssf.com christian.loew at steyr-ssf.com Sat Feb 28 08:23:56 GMT 2004 Hi, I'm trying to set up a samba-cups-pdf-printserver. samba itself is running fine, but when i try to add the cups printer-drivers for windows i got the following error: System: Debian/sarge with 2.4.20 i686 GNU/Linux samba 3.0.2-2 cupsys 1.1.20final-13 Windows-driver from cups-samba-5.0rc1.tar ssflx01_v2:~# cupsaddsmb -a -v -U Have you installed your new printer SSFP102 just before running this command? Before you did run this command -- have you checked that Samba sees the new printer SSFP102? Password for required to access localhost via SAMBA: Running command: smbclient //localhost/print\$ -N -U'uuu%' -c 'mkdir W32X86; put /var/spool/cups/tmp/40404c740a656 W32X86/SSFP102.ppd; put /usr/share/cups/drivers/cupsdrv5.dll W32X86/cupsdrv5.dll; put /usr/share/cups/drivers/cupsui5.dll W32X86/cupsui5.dll; put /usr/share/cups/drivers/cups5.hlp W32X86/cups5.hlp' Domain=[STEYR-SSF] OS=[Unix] Server=[Samba 3.0.2-Debian] NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86 ...no problem. putting file /var/spool/cups/tmp/40404c740a656 as \W32X86/SSFP102.ppd putting file /usr/share/cups/drivers/cupsdrv5.dll as \W32X86/cupsdrv5.dll putting file /usr/share/cups/drivers/cupsui5.dll as \W32X86/cupsui5.dll putting file /usr/share/cups/drivers/cups5.hlp as \W32X86/cups5.hlp ...good. Running command: rpcclient localhost -N -U'%' -c 'adddriver Windows NT x86 SSFP102:cupsdrv5.dll:SSFP102.ppd:cupsui5.dll:cups5.hlp:NULL:RAW:NULL' Printer Driver SSFP102 successfully installed. ...good. Running command: rpcclient localhost -N -U'%' -c 'setdriver SSFP102 SSFP102' result was WERR_INVALID_PRINTER_NAME This means that Samba doesn't see yet your printer.SSFP102 However, it has installed a driver named SSFP102. tdbdump ntdrivers.tdb shows that the drivers are installed Does rpcclient -U'uuu%' -c enumprinters localhost show your printer SSFP102? If not, re-start Samba or do a kill -HUP `pidof smbd` and try the enumprinters command again. If now you see SSFP102 recognized, you can repeat the cupsaddsmb with complete success. Or just run rpcclient -N -U'%' -c 'setdriver SSFP102 SSFP102' localhost or rpcclient -d 5 -N -U'%' -c 'setdriver SSFP102 SSFP102' localhost from the commandline. There is a bug in Samba which prevents newly searching on google doesn't show any solution :-( Google is *bad*. It should know all my previous answers to that queston...;-) any hints? Hmmm;-) Chris -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Printer settings reset problems
? Like Windows NT. With the different versions of the drivers in the 2 and 3 subdirs, and with additional info in various *.tdb files... Do Samba make difference between different Windows platforms when storing the settings? Why are our settings reseted? Is this a known problem and is there any way to make it work better? As it is now we can't use Samba as a print server frontend for both Windows 2000 and NT4 clients. I *might* be able to come up with a workaround suggestion to solve your problem, but it needs time to work it out and test I have recently started to use the tdbutil to look on the database files, but haven't come to any conclusions yet. Regards, -- Anders KarlssonEmail: anders.karlsson at cendio.se Cheers, Kurt -- +--+ | .--. CUPS + ESP PrintPro: | | |o_o | | | ~ |:_/ |Unix/Linux Printing made fun and easy | | // \ \ http://www.danka.de/printpro/faq.html | |/V\(| | ) .~. Kurt Pfeifle, Danka Deutschland GmbH | | // \\ /'\_ _/`\ /V\Tel.: +49-172-715.7017| | /( )\ \___)=(___ )/( )\ mailto:[EMAIL PROTECTED]| | ^`~'^ ^^~^^ | | Network Printing Services: Consulting+Training+Workshops+Troubleshooting | +--+ -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Solaris 8 and cups issues
[Samba] Solaris 8 and cups issues Tim Russell timrussell at rocketmail.com Fri Feb 6 01:09:37 GMT 2004 [] The windows share is set up with raw and the client then uses it's own driver. The Solaris queue is set to HP and the generic laserjet.ppd. The windows queue prints fine but the unix queue prints nothing (it just shows up as a cancelled job under the cups web interface). ...which means that you are asking this question in the wrong newsgroup. Better see if http://www.cups.org/newsgroups.php; is for you... ;-) A few things you could check and tell the folks at cups.org: * output of ls -l /usr/lib/cups/filter/ * output of gs -h * output of grep '*cupsFilter' /etc/cups/ppd/* You can set LogLevel debug in /etc/cups/cupsd.conf, restart cupsd and see what now goes into /var/log/cupa/error_log. If I change the Solaris queue to raw as well, it prints out garbage (but it does at least print something). One final note, we can't use the configure option in the cups gui (localhost:631 and then printers) on shared printers. It gives a client-error. raw queues don't have a PPD associated to them. raw queues can't be configured. raw queues spawn that error We don't specify individual printers in the smb.conf file (we just tell it to share all of them) so I'm guessing that the few printers I can do this too will stop allowing me to use the configure option once I restart samba. This has nothing to do with Samba. Do we need to go grab gimp-print for more drivers or is this some other problem? No need for gimp-print If your HP is a PostScript model (you didn't name the type at all, so I can't provide you with an exact download link...) use the PPD file coming with the Windows driver CD (or download the PPD from the HP website). If it is a non-PS printer, use a PPD from the Linuxprinting.org website, alongside the HP hpijs driver.. Which also requires a newer version of Ghostscript -- best is ESP Ghostscript -- that has the ijs-device compiled in (check with gs -h | grep ijs) Sorry for the long post (we're very close to getting this completely working and I'm rambling now :) Thanks, -Tim Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] CUPS printing from Windows
[Samba] CUPS printing from Windows Alan Becker beckera at softrends.com Tue Feb 17 05:03:19 GMT 2004 I have replaced a WinNT4 PDC with a Samba server. [] Problem: Windows clients (using downloaded drivers from print$) don't seem to have full or proper control of printing. Example 1: An excel user has to click on Print to fit in Page setup in order for the page to be scaled properly. Otherwise it prints on multiple pages in very large type. This can also happen in a Windows-only environment. Example 2: Another Excel user attempts to set Landscape orientation. The setting is accepted. no error is generated, but the page continues to print in portrait orientation. Are your printer drivers installed locally or via Point'n'Print? Are you using the native Windows drivers from the vendor or are you using the CUPS or Adobe PostScript drivers (and let CUPS convert the PS for you)? To begin with, this unit is based on RedHat 9 with all current updates (kernel 2.4.20-28.9, Samba 2.2.7a-8.9.0, Cups 1.1.17-13.3.0.3). After discovering that CUPS was the only printing system that RH9 installed, I went to the documentation and read the HOWTO chapters 18 (Classical printing support) and 19 (CUPS printing support). I then did the following: (1) Create the print queues using the RH/Gnome Printing control applet (2) Test printing from Linkx (ok) (3) Obtain the Windows drivers from the NT4 PDC (copied the whole c:\winnt\...\w32x86 structure to a scratch area. (4) Obtain the detailed descriptions of each installed driver using the rpcclient utility from the Samba server, querying the old NT4 server (temporarily attached) with the getdriver queue_name function. Route the query results to a file. Repeat for all queues. (5) Write a script to parse the output of (4) and automate steps 4-10 of Manual Driver Installation in 15 Steps from Chapter 19. (6) Run the script for each print queue. Drivers appear to be added without problem. OK -- this seems to indicate that you are using the native drivers for Windows provided by the vendor, just as you did on your NT print server (7) Join a WinNT workstation to the Samba domain ??? (8) As Administrator, connect to the laser print queue. Succeeds, no error message. (9) Bring up Excel, attempt to print Landscape as noted above. This fails. What do you mean... fails?? -- Does printing fail altogether? -- Or is it just not printing in landscape mode? If it is the latter, and if you are using a PostScript driver on the Windows clients, check out the Release Notes for CUPS: http://www.cups.org/relnotes.php I seem to remember that there was a landscape/portrait bugfix in the latest 1.1.20 release... Also, printing from Excel is sucking. Are you sure you had the correct settings. Questions:: (A) The failure to command the printer properly suggests a problem with the uploaded drivers. Not necessarily. These things happen in Windows-only places also Are there any other common explanations for this type of behavior?? Yes -- user error, driver bug Did it for sure work (using the same driver settings) with the previous NT print server? (B) I attempted to set the dot-matrix queues to the Generic printer/Raw device. In this mode, I printed a short text file (in Linux), and copied a test file to the network queue (under Windows). In either case, the file was printed, but the paper was not advanced to the next page. Why should it? If you send ASCII text, with no page advance command at the end, the printer wouldn't know that you want the page advance In other words, this queue is so raw that it doesn't even recognise the end of a print job, It does what you tell it. You don't tell it that there is a page advance needed. You should send an appropriate Escape code to the dot matrix printer. so multiple print jobs can be printed on the same page. Is there any middle ground, where inter-job pagination occurs, but no other filtering is enabled?? Yes. For a first insight see the CUPS documentation about writing filters.(*) (If it is too much work for you, you could go to the new printing consultant's page at http://www.linuxprinting.org/consultants.html where you can buy some support. (If our company does it, 10% go to Linuxprinting.org as sponsorship money). (*) You need a filter for the dot-matrix which just adds the page advance command to any ASCII text file. It can also be done via an interface script. See man lpadmin and the -i paramter TIA for your attention. A. Becker Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Easy Answer to DIFFICULT printing question SAMBA/WinXP/Cups
[Samba] DIFFICULT printing question SAMBA/WinXP/Cups Michael Gasch gasch at eva.mpg.de Mon Feb 2 12:14:47 GMT 2004 [] my problem: samba should just be the driver provider and not spool print jobs...those should go directly to the printers What you want to do is not possible for Samba, [] my script: rundll32 printui.dll,PrintUIEntry /in /n \\sambapdc\copy07.my.domain /r IP_192.168.1.1 192.168.1.1 = TCP/IP Port of the Printer copy07 but it doesn't work - the printer maps perfectly but the port is Samba Printer Port and i can't add a new port, because this request is not supported ...and it tells you so. Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Fwd: smbspool
[Samba] Fwd: smbspool zynkx skydive at megamail.pt Wed Feb 18 21:31:02 GMT 2004 - Mensagem encaminhada por zynkx skydive at megamail.pt - Date: Tue, 17 Feb 2004 20:25:26 + From: zynkx skydive at megamail.pt Reply-To: zynkx skydive at megamail.pt Subject: smbspool To: samba at lists.samba.org i am using this command line from a linux client to try to print to my linux samba server with a shared printer, that is printing ok from windows clients. the test page prints ok from this same linux host. here is the command i am using:smbspool smb://printserver/neptuno/hp_670C 1 nobody 1 test OK, I don't really understand why you need to do it, but here you go: * Try with no arguments first: [EMAIL PROTECTED]: smbspool network smb Unknown Windows Printer via SAMBA * Try with one dummy-argument: [EMAIL PROTECTED]: smbspool dummy Usage: smbspool [DEVICE_URI] job-id user title copies options [file] The DEVICE_URI environment variable can also contain the destination printer: smb://[username:[EMAIL PROTECTED]/]server/printer * Aa-h... The command wants to use the DEVICE_URI environment variable, plus 5 or 6 arguments (5 if it gets input from stdin, 6 if the printjob is a file). * Try this: DEVICE_URI=smb://skydive:[EMAIL PROTECTED]/piper/hp_670C skydive2 An SMB Print Job 2 sides=two-sided-long-edge /etc/samba/smb.conf skydive - username happylanding - password cessnaclub - workgroupname piper - servername hp_670C - printersharename - job-ID (you may invent one) skydive2 - user (you may invent one) An SMB Print Job - job title (you may set one) 2 - number of requested copies sides=two-sided-long-edge - print job options (you may set more, comma-separated, if CUPS is the printing system underneath the Samba print server (*)) /etc/samba/smb.conf - the file you want to print (*) won't work against a Windows print server! * Works for me! where hp670c is the name of the printer as it is configured in the smb.conf and nobody the name of the user wich ii am not sure if it is right... it connects to the print server but it does not print any ideia? No more than the above... Cheers happy printing! Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Sharing A Windows Printer server printer queues With Linux Machines using samba
Sharing A Windows Printer server printer queues With Linux Machines using samba Ihab Khoury ikhoury at yahoo.com Thu Feb 12 23:36:17 GMT 2004 UPDATE:- I was able to print using smbclient with a username and use my PDC server pssword. You don't exactly describe what configuration you used so you can't expect an exact answer to your problem. I am not even suire which Unix printing system your Samba (client) uses Has anyone set it up so that they sync PDC passwords with samba passwords? Or any other way so I do not have to enter password everytime I print? No. If you use CUPS, it allows you to print thru an smb backend device URI of smb;//username:[EMAIL PROTECTED]/servername/printersharename It spares you from typing in the username/password pair. But this is grossly unsecure, It sends your password over the wire unenecrypted. It stores your username/password combo in cleartext in /etc/cups/printers.conf and may even reveal it i n the process list (but makes some attempts to leave that part from the obvious displays Samba simply isn't exactly designed to print as a Windows client to a Windows print server. It works, somehow, but that's just it. The idea for Samba is to take the Windows client print jobs as a *server* ;-) Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba / CUPS / Drivers
[Samba] Samba / CUPS / Drivers Anders Norrbring anders at norrbring.biz Wed Jan 28 16:13:43 GMT 2004 I'm trying to figure out if it's possible to use different driver file downloads for different printers on the system? As of what I can see in all doc-files I can only use ONE set of drivers for all added printers? F.x. I have one printer that is handled by CUPS' PPD system, and one printer that uses RAW. So, the first printer (PPD) should have its feed in postscript format from the Windows clients, so they get the Adobe PS driver ...or the CUPS PostScript Driver for Win NT/2K/XP Clients... set by download when they add the printer to the system. But the second printer that should be fed by the Windows clients already processed stream, that is, they need the printer manufacturers native printer driver for Windows. So, they should NOT get the Adobe friver, but a different set. Is it doable? Yes. The most easy way to do it is like this: * install the native driver locally on the Windows client (use as the print port LPT1, just temporarily, for the sake of installation) * then re-map the port by typing net use LPT1: \\sambaserver\printersharename into a DOS box You can't set up Samba to download the raw printer driver. If you set up a printer on CUPS with no assigned Samba/Win-client driver deposited in [print$], your Win-clients will always be prompted to install a local native driver upon their first connection attempts... I run CUPS v1.2.0b1 and Samba 2.2.5. CUPS v1.2.0b1 ??? Are you really sure? This is by no means meant for production use. It is for hard-core beta testers only, who know what they're doing, and know how CUPS works. I'd rather recommend CUPS 1.1.20 for you. Samba 2.2.5?? This is rather old (nearly 2 years)... Can't you switch to 3.0.x? Anders Norrbring Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] W9x doesn't download printer drivers
[Samba] W9x doesn't download printer drivers Francesco Malvezzi malvezzi at unimo.it Thu Jan 29 09:02:18 GMT 2004 My W9x clients cannot download printer driver from samba 3.0.2rc1 with cups 1.1.17, while w2k clients do. Your posting doesn't contain any helpful details about your problem. So only one idea crosses my mind: there is a difference in the supported length of printer names to be used by WIN40 (== NT/2K/XP) and W32X86 (== 95/98/ME) clients Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] CUPS postscript driver - setting up **ERRATA**
[Samba] CUPS postscript driver - setting up **ERRATA** Chris Aitken chris at ion-dreams.com Thu Jan 29 12:14:02 GMT 2004 Hi All, Following instructions from here: http://samba.mirror.ac.uk/samba/docs/man/CUPS-printing.html#id2942237 and also in the Official Samba Howto book, I tried to install the CUPS PS driver using cupsaddsmb. It failed due to various reasons, and then I finally got it to work. When I unpacked the latest tar.gz file (cups-samba-5.0rc3.tar.gz) it doesn't unpack the files as: cupsdrvr.dll cupsui.dll cups.hlp but as cupsdrv5.dll(5 instead of r) cupsui5.dll (extra 5) cups5.hlp (extra 5). That version 5 of the CUPS PostScript Driver is not (yet) meant to be used with cupsaddsmb. (Unfortunately its docu doesn't make that really clear). It is meant to be used by the CUPS IPP Client for Win NT/2K/XP (which allows driver and printer installation on the clients without and independently of Samba. Also, it is a version 3 driver (non-Kernel mode), IIRC (but I might err). This causes the cupsaddsmb to fail. If the files are renamed, then it works OK. This is the first workaround. The other one is to use the smbclient..., rpcclient...adddriver and rpcclientsetdriver series of commands to upload and register the driver files into [print$] of Samba. Regards, Chris Aitken Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Print via print command while using 3.0
[Samba] Print via print command while using 3.0 Stefan Klein stefan.klein at materna.de Thu Jan 29 12:27:58 GMT 2004 [] So i think you have to use: = [global] ... printing = cups ... [pdfprinter] printing = bsd comment = PDF Drucker, druckt nach H:\print print command = /usr/bin/tps2file.sh %s %U pdf pdfwrite path = /tmp printable = yes valid users = @users = (Not sure if it works to redefine the printing inside a subsection) It used to, but now it doesn't any more. I think we should ask our Samba Team coding gurus to change printing = ... to become a service level instead of a global parameter. This way it would be much easier to achieve what people want to achieve here. The only way to do it now, is to set printing = sysv or printing = bsd as the global setting, which in turn looses you all the convenient functions of CUPS library integration into Samba. Of course, one could waive your custom print command altogether and go down the use the CUPS pdf:/-backend way of PDF generation, as is described here (and in related thread) in much detail: http://lists.samba.org/archive/samba/2003-March/064650.html http://lists.samba.org/archive/samba/2003-April/064653.html regards, -- Stefan Klein, Systems Engineer Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] smbprngenpdf printer driver?
[Samba] smbprngenpdf printer driver? Anders Norrbring anders at norrbring.biz Fri Jan 30 09:48:12 GMT 2004 Hiya! Can anybody recommend what the best Windows XP printer driver is to generate pdf documents with the generator smbprngenpdf which is included in SuSE's smb-client package? What does *SuSE* recommend? BTW -- which version of SuSE? Could it be the CUPS printer driver, or the Adobe? Or something completely different? What is your actual *problem*? Have you tried to set it up and it didn't work? Did it work but the results weren't like you wanted them? Anders Norrbring Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] (Idiot outside) - smbprngenpdf printer driver?
[Samba] (Idiot outside) - smbprngenpdf printer driver? Anders Norrbring anders at norrbring.biz Fri Jan 30 10:57:58 GMT 2004 Well, I wasn't really awake I guess.. It's just a script that calls GhostScript for pdf generation.. But the question still stands, what IS the best quality printer driver to use for GhostScript - pdf printing? We need both colours and high resolution.. You need to make sure that your driver produces good PostScript. If you use the wrong PPD alongside the base PS driver, you'll end up with a PostScript which doesn't contain color info, but only b+w/grayscale. In this case your PDF will be grayscale too. (Happens if you use a HP-LaserJet-8000.ppd or similar). I'd recommend any generic PS printer PPD (like the Adobe distiller.ppd), which doesn't have model specific info in it, but only page size, color/grayscale and raster resolution selections. Also, make sure to embed the TT fonts into the PostScript, and let the driver create DSC-conforming PostScript. The name of the settings in the driver GUI varies, depending whether you use the Adobe or the CUPS or the Microsoft base PS driver underneath your PPD (quoting from memory): DSC-Conformance: * Page Independence: Yes(instead of Page Independence: No) * Optimize for Portability (instead of Optimize for Speed) Font Embedding: * Use printer fonts: no * Download as True Type (instead of Download as Outline/Bitmap) * Slower, but nore exact... * and, maybe a few others... Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba] Samba3 Printer drivers installation
Andrei Mikhailovsky wrote: [] | When I was initially installing the drivers, I was following a how-to | that didn't specify that you need exact order for the driver files. | | | It does. It does so in very much detail. I spent my complete annual | holiday last summer to find everything out and write it down as a | documentation. So don't tell me it doesn't specify the exact order, | because I know it went into my draft at more than 1 place. | Sorry for not making it clear earlier on, I have followed a 3rd party how-to that i've found by google-ing. So why am *I* receiving the support call for that 3rd party doco?? [...] As far as i can see from the how-to the server side setup is finished. Now, from the client side, i should double click on the printer This is not a piece I ever advocated, exactly because it doesn't work reliably. Re-read the docu and find the following steps (quoted from memory). * browse to Samba in network neighbourhood. * open Printers and Faxes folder * right-click printer and select Connect... or Install... and windows should fetch the driver and install it. When I do this, windows 2000/XP responds that unable to find driver, do you want to make a local search for driver. However, if i check the properties for the printer, i can see that the driver is there and that it is available for the right architecture. Find the different places which (redundantly) hint to the need to... * make sure to do the first installation on any Win client as a printer admin user, and * tickle the driver into a valid device mode by executing it once on a Win machine, before you start offering it to normal users for download/installation -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba] Samba3 Printer drivers installation
[Samba] Samba3 Printer drivers installation Andrei Mikhailovsky andrei at arhont.com Tue Jan 20 11:52:41 GMT 2004 Hello, I am having problems installing printer drivers for Samsung ML-4500 printer, so windows workstation can just fetch them from print$ share. When I run rpcclient with -d 4 i get the following error: whale:/home/samba/home# rpcclient -d 4 -Uroot% -c 'adddriver Windows NT x86 SSGK2:ssgk2.cnt:ssgk2.dat:ssgk2.dll:ssgk2.hlp:ssgk2.ini:ssgk2.sdd:ssgk2su.dll:ssgk2ui.dll:ssgk2um.dll' WHALE Your command is wrong. I can see this by just counting the colons in it. There must be exactly 7 colons -- yours has 9! [] result was WERR_INVALID_PARAM Does anyone know what the problem is Yes. and how to fix it? Use the correct syntax :-) It is described here http://samba.vernstok.nl/htmldocs/CUPS-printing.html#id2562523 in very great detail, as well as at many other places, like man rpcclient (search for adddriver). Admittedly, it is not very simple, so I'll try to explain again. The man page quotes this: adddriver arch config [version] arch is the Win architecture family. It may be either Windows NT x86 (which stands for Windows NT 4.0, Windows 2000/2003 and Windows XP) or Windows 4.0 (which represents Windows 95/98/ME). You need to use the quotes because of the spaces in the string. config is the long string, containing 8 separate fields, separated by 7 colons. The last field may contain either NULL, or a list of additional driver files *separated by commas*. All this 8 fields must be filled in, none may be empty (in which case the NULL needs to go in), and they need to be filled in in the correct order. The correct order is this: LongDriverName:DriverFileName:DataFileName:ConfigFileName:HelpFileName:LanguageMonitorName:DefaultDataType:Comma-Separated-list-of-Files The LanguageMonitorName field should contain NULL. The DefaultDataType for Samba and NT72K/XP clients is RAW. To find out which files are which type, use one of these commands to query an existing NT/2000/XP workstation with the same driver installed locally (and sharing the printer): rpcclient -U'Administrator' -c 'enumdrivers 3' name-of-remote-win-workstation rpcclient -U'Administrator' -c 'getdriver printername 3' name-of-remote-win-workstation The output should show you the correct mapping of driver files to the types described above (using similar nomenclatura, albeit not exactly the same, but enough to guess). Note that the list of the Dependent Files is what needs to go, comma-separated, into the last of the 8 mentioned fields in the adddriver subcommand to rpcclient. Lastly (AND VERY IMPORTANT!!): all the files you name in the adddriver command need to be present in [print$]/W32X86/ *before* you run the command. Note, that the successful command will create a sub-directory named 2 (or 3, if you use a version 3, non-kernel-mode driver for 2000/XP) and move the files there. A partially successful adddriver command could have moved away a part of the files, and therefor you need to put the files again into the original location, before you can try again: Finally, here are 4 examples for a working rpcclient adddriver command: 1 --- rpcclient -U'Administrator%' -c 'adddriver Windows NT x86 \ HP LaserJet 8100:\ cupsdrvr.dll:\ mopi.ppd:\ cupsui.dll:\ cups.hlp:\ NULL:\ RAW:\ NULL'\ TURBO_XP # This command installs the NT/2000/XP CUPS driver into a Windows XP # Professional workstation named TURBO_XP, when it is run from any # Samba machine, and if the files had been placed into (UNC-Notation follows) # \\turbo_xp\print$\W32X86\ previously (by, for example an appropriate # smbclient command) or (path specific to my own system follows) # into C:\WINDOWS\SYSTEM32\SPOOL\drivers\W32X86\ -- - 2 -- rpcclient -U'Administrator%' -c 'adddriver Windows 4.0 \ HP LaserJet 8100:\ ADOBEPS4.DRV:\ mopi.PPD:\ NULL:\ ADOBEPS4.HLP:\ PSMON.DLL:\RAW:\ ADOBEPS4.DRV,mopi.PPD,ADOBEPS4.HLP,PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL'\ TURBO_XP # This command installs the Win95/98/ME Adobe PostScript driver into the # Windows XP Professional workstation named TURBO_XP, when it is run from # any Samba machine, and if the files had been placed into (UNC-Notation follows) # \\turbo_xp\print$\WIN40\ previously (by, for example an appropriate # smbclient command) or (path specific to my own system follows) # into C:\WINDOWS\SYSTEM32\SPOOL\drivers\WIN40\ -- - 3 -- rpcclient -U'root%' -c 'adddriver Windows NT x86 \ HP LaserJet 8100:\ cupsdrvr.dll:\ mopi.ppd:\ cupsui.dll:\
[Samba] Samba PDC and Automatic Printer Install
Michael Aldrich maldrich at i-centrix.com Wed Jan 14 15:35:11 GMT 2004 Hello, I am trying to install automatic printer driver download and install. I am running Samba 3, as a PDC, on RedHat 7.3. Sorry, Mike, I'm currently not able to follow the mails on this list one by one. Just an occasional glance. So I haven't looked deeply into your problem either... It seems everything is setup correctly, No. Not completely. You are trying to use a driver downloaded from the Samba server, yet you still have set smb.comf to use client driver = Yes. Delete this line. Restart smbd. Then try again. [...] rpcclient $ setdriver lp HP LaserJet 2300 Series PCL 6 SetPrinter call failed! [] Snip from my smb.conf: [printers] [] printing = cups use client driver = Yes ^^^ [] [lp] [] use client driver = Yes ^^^ oplocks = No [] Why do I get WERR_ACCESS_DENIED from SetPrinter? What you try to do is not compatible with use client driver = Yes Thanks Mike And thanks to Kurt for getting me this far ;-) Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Printer on WinXP
Thomas Bergstam thomas at acat.se Sat Jan 3 18:10:22 GMT 2004 Hi all, Is it possible to use a printer attached to a WinXP computer from Linux (Suse) using only console mode, ie. no graphic mode? Yes. 1. Make sure your WinXP-attached printer is shared. 2. Make sure you use CUPS as a printing system. 3. Make sure you know about CUPS and PPDs. 4. Know that WinXP (Prof!) is capable of using IPP as a print protocol 5. Know that Microsoft, in their unlimited wisdom decided to use as a printer URI this: http://[IP-address of WinXP]:80/[printer-sharename]/.printer 6. Install the printer (assuming IP for WinXP is 11.12.13.14 and printer-sharename of printer is my_printer): lpadmin -p printername -v http://11.12.13.14:80/my_printer/.printer -E -P /path/to/PPD 7. Print to your heart's limits fromt the commandline: lp -d printername /path/to/printfile Cheers, Kurt P.S:: Please bear in mind, that you may not receive anyone's attention to your question, if you continue to miss providing *any* details about your system, like XP Home or XP Prof?, Version of SuSE? etc. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Problems with printers
Rob Sell lists at facnd.com Mon Dec 22 17:46:29 GMT 2003 I have samba 3.0.1 running and have successfully set it up to be a print spooler, which is working great, until I tried to add more than 5 printers. I am using cups, using the cups web interface to add printers, today I added 2 more printers. They do not show up in samba, I have restarted cups, smb nmb, everything except the machine itself. Samba is set to load /etc/printcap printers, my /etc/printcap is as follows. # This file was automatically generated by cupsd(8) from the # /etc/cups/printers.conf file. All changes to this file # will be lost. 7th_Dock_Laser: Edgeley_Inkjet: Edgeley_Laser: Eng_Laser: Eng_Laser_Color: Front_Office_Big_Laser: Front_Office_Laser: Michigan_Plotter: Any ideas why only the 1st 5 printers show up in samba? The first 5 printers have max. 15 characters in their name. The last 3 printers have min. 16 characters in their name. You may have crossed a limit (bug or feature?). Rob Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] pdf-generator
[Samba] pdf-generator Thomas Spuhler thomas at btspuhler.com Sat Dec 27 03:01:22 GMT 2003 I am having difficulties to set up the pdf printservice on samba. You may want to look at these postings and related threats from the Samba archives: http://lists.samba.org/archive/samba/2003-April/064652.html -- http://lists.samba.org/archive/samba/2003-April/064653.html http://lists.samba.org/archive/samba/2003-March/064646.html http://lists.samba.org/archive/samba/2003-March/064650.html http://lists.samba.org/archive/samba/2003-March/064652.html They provide a step-by-step procedure about how to set that service up with CUPS, so that even it may be even shared out to Win-Clients. Cheers, Kurt -- +++ GMX - die erste Adresse für Mail, Message, More +++ Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Add Printer Wizard Plus CUPS
[Samba] Add Printer Wizard Plus CUPS Jeffrey M. Hardy hardyjm at potsdam.edu Wed Dec 10 22:28:12 GMT 2003 I'm having some problems with our Samba Add-Printer-Wizard setup and CUPS. Everything is working fine (drivers upload, download, configured) except for one thing. Both my addprinter and deleteprinter scripts are forced to restart Samba in order to successfully complete their respective adding and deleting. Because of this, sometimes Samba will not come back up correctly. I read that normally Samba will re-read smb.conf and pick up any printer entries and complete the process. However, when dealing with CUPS as the printing subsystem, the printers are stored separately in (usually) /etc/cups/printers.conf. If I do not restart Samba during this process, the client receives an Access denied error message. Is there a way to get Samba to read the CUPS printers conf info without restarting Samba? Dunno if that is good enough for you: kill -HUP `pidof smbd` Or submit a bug report to http://bugzilla.samba.org/. Or wait till it's fixed. I agree it is a bug. BTW -- I've written a very rough add printer script also. Do you mind sending yours to me in exchange of mine? (I didn't dare to publish mine yet, since I am a terribly new into shell scripting) Thank you. CUPS 1.1.19 Samba 3.0 Red Hat 8.0 -- Jeff Hardy Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] No joy adding a CUPS printer
[Samba] No joy adding a CUPS printer Gary Thomas gary at chez-thomas.org Thu Dec 11 00:09:26 GMT 2003 I'm trying to change my Samba setup from LPD to CUPS, with little success. I've followed [and re-followed] the setup documentation from CUPS and I just can't get Samba to recognize my printer. The catch is - it sort of recognizes it :-( [] [root samba]# rpcclient localhost -Uroot% -c 'getdriver lp' cmd = getdriver lp Error opening printer handle for lp! result was NT_STATUS_UNSUCCESSFUL Alas, I'm stuck :-( Windows (XP Home if it matters) Home *might* matter... but most likely not with the symptoms you described. What does your (remaining) smb.conf look like? (Please send it without the comments...) stalls trying to install this printer, telling me I don't have the proper drivers installed. Most likely because of the 'getdriver' issue above. What do you get for [root samba]# rpcclient localhost -Uroot% -c 'enumprinters' [root samba]# rpcclient localhost -Uroot% -c 'enumprinters 2' [root samba]# rpcclient localhost -Uroot% -c 'enumprinters 3' ?? IIRC, the getdriver in some late 2.2.x versions had problems I'm running Samba 2.2.7a-7.9.0 - stock from Red Hat 9.0 Any ideas or help would be appreciated. 1/ Try to run cupstestppd against the PPD in question. Fix problems by editing it. If your stock install doesn't have this cupstestppd utility available, then try the online version here: http://www.cups.org/testppd.php 2/ It could still be a problem with the PPD, even if it passes the cupstestppd test. I've 2 PPDs here which I can't get to work even with Samba-3.0.1rc1. As soon as I change the PPD to a different one, it works! (Will submit a bugzilla report as soon as I can figure out details again) 3/ Try to change the printer name to another one than lp (wild guess) 4/ Check at http://www.linuxprinting.org/; if you can find a newer PPD. Is the current one still calling for cupsomatic as its *cupsFilter? (See at head of PPD file...) In that case read the linuxprinting.org docu (or the section in the HOWTO Collection for 3.0 -- it is applicable to 2.2.7a also!) and download the newer PPDs + foomatic-rip (foomatic-rip replaces cupsomatic). Might work then My wife really wants her printer back :-) Oh -- its not wants her husband back ?? ;-) Thanks -- Gary Thomas gary at chez-thomas.org Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] rpcclient / adddriver returns WERR_ACCESS_DENIED
Arnst, Rainer Rainer.Arnst at ee-consultants.de Tue Dec 9 09:59:20 GMT 2003 Hi, I am trying to prepare downloadable printer drivers for Windows-Clients with Samba 3.0.0-final. Everything worked fine so far. But I found no way to add the printer driver files to the samba database. The method using the Add Printer Wizard in W2k did not work for me. This is what I tried: linux4:/# rpcclient -U'root%secret' -c 'adddriver Windows NT x86 LJ6:HPBLEF2.DLL:HPBLEF49.PMD:HPBLEF0.DLL:HPBLEFJE.HLP:NULL:RAW:HPBLEF1.DLL,HPBLEF3.DLL,HPBLEF7.DLL,hpbafd32.dll,hpbftm32.dll,HPBLEF41.DLL,HPBLEF42.DLL,HPDCMON.DLL ' localhost result was WERR_ACCESS_DENIED This error typically occurs, if you haven't any driver files waiting to be adddriver-ed, laying in [print$]/W32/X86/ Once you run rpcclientadddriver, and it fails, you will have to re-assure that *all* the original files are still in place. (A partially succeeding adddriver may have moved the files already to the 2 or 3 subdirectories! But your description is not clear at all. On the one hand you say you had used the APW, on the other you are quoting the rpcclient... ...adddriver command in isolation. An isolated adddriver will never work. There needs to be a step of putting the files (somehow) into the [print$]/W32X86/ directory *beforehand*. The HOWTO Collection (version for Samba-3.0) suggests to employ smbclient for this job. I suggest you painstakingly follow the steps described in chapters 18.6. or 19.10./19.11. of the HOWTO Collection. See here: http://de.samba.org/samba/docs/Samba-HOWTO-Collection.pdf http://de.samba.org/samba/docs/man/ Any hints are very welcome!! [] [printers] comment = All Printers path = /var/spool/samba browseable = no public = yes guest ok = yes writable = yes printable = yes You want here writeable = no printable = yes printer admin = root,arnstr,guest [print$] comment = Printer Drivers path = /etc/samba/drivers browseable = yes guest ok = yes read only = yes write list = root I suggest you read man cupsaddsmb and set up your config as suggested there. Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba 3.0.0, CUPS support - Unable to open printcap file cups for read!
[Samba] Samba 3.0.0, CUPS support - Unable to open printcap file cups for read! Fran Fabrizio fran at cis.uab.edu Tue Dec 9 20:06:56 GMT 2003 A couple more data points: # smbclient //ds119b/ps4 Password: tree connect failed: NT_STATUS_BAD_NETWORK_NAME # It means Samba doesn't know about a printer share named ps4 (nor a file share of that name) The syslog shows this as a result: Dec 9 13:46:47 ds119b smbd[21284]: [2003/12/09 13:46:47, 0] printing/pcap.c:pcap_printername_ok(282) Dec 9 13:46:47 ds119b smbd[21284]: Unable to open printcap file cups for read! This message might be bogus in your context and not lead to your real problem... Dec 9 13:46:47 ds119b smbd[21284]: [2003/12/09 13:46:47, 0] smbd/service.c:make_connection(850) Dec 9 13:46:47 ds119b smbd[21284]: ds119b (192.168.2.232) couldn't find service ps4 See? I can successfully print to this printer from the samba linux host via the standard lpr -Pps4 approach. I checked my cupsd.conf to make sure it had a Printcap = /etc/printcap and PrintcapFormat = BSD entries and it does. Have you also checked your smb.conf for an entry of load printers = yes ?? The generated /etc/printcap has only one non-comment line, ps4:. That's OK. -Fran -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0.0, CUPS support - Unable to open printcap file cups for read!
Kurt Pfeifle wrote: [Samba] Samba 3.0.0, CUPS support - Unable to open printcap file cups for read! Fran Fabrizio fran at cis.uab.edu Tue Dec 9 20:06:56 GMT 2003 A couple more data points: # smbclient //ds119b/ps4 Password: tree connect failed: NT_STATUS_BAD_NETWORK_NAME # It means Samba doesn't know about a printer share named ps4 (nor a file share of that name) The syslog shows this as a result: Dec 9 13:46:47 ds119b smbd[21284]: [2003/12/09 13:46:47, 0] printing/pcap.c:pcap_printername_ok(282) Dec 9 13:46:47 ds119b smbd[21284]: Unable to open printcap file cups for read! This message might be bogus in your context and not lead to your real problem... Dec 9 13:46:47 ds119b smbd[21284]: [2003/12/09 13:46:47, 0] smbd/service.c:make_connection(850) Dec 9 13:46:47 ds119b smbd[21284]: ds119b (192.168.2.232) couldn't find service ps4 See? I can successfully print to this printer from the samba linux host via the standard lpr -Pps4 approach. I checked my cupsd.conf to make sure it had a Printcap = /etc/printcap and PrintcapFormat = BSD entries and it does. Have you also checked your smb.conf for an entry of load printers = yes ?? The generated /etc/printcap has only one non-comment line, ps4:. That's OK. -Fran I forgot: should you have created the ps4 printer while smbd was already running, Samba might not yet know about the printer (Samba bug -- it *should* update its list of available printer shares just like it does with file shares). Sending a kill -HUP `pidof smbd` might help. Or restart smbd. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0.0, CUPS support - Unable to open printcap file cups for read!
Fran Fabrizio wrote: I've restarted the daemons many times since altering my smb.conf. My smb.conf definitely has load printers = yes (see the smb.conf excerpt I sent in my initial post Sorry, hadn't seen it for the rest of the relevant configuration entries). So I *did* read now what *you* wrote into smb.conf. But... is Samba reading the same thing? Use testparm -v smb-conf-as-seen-by-samba.txt (hit ENTER twice) and then investigate smb-conf-as-seen-by-samba.txt. You mention that it complains that it can't find the share - I think it makes perfect sense that Samba complains that it doesn't know about a share called 'ps4' right after it complained that it couldn't open the CUPS configuration. :-) It complained about this: Unable to open printcap file cups for read! This means that *your* Samba tries to look for a printcap file with the *name* cups to read. However, if smbd is compiled against libcups, *and* if printing = cups and printcap = cups smbd doesn't really need a printcap file and it wouldn't look for one with that name either (It just means that it should rely on the CUPS-API to find out available printers) Unless you found a real bug, that is! I have set Printcap /dev/null in cupsd.conf and re-started cupsd first then smbd. Guess what? smbclient -L localhost still lists all my printers! And I can still print from my Windows apps. (I can't print anymore from OpenOffice, since that one *does* look for a printcap) It stands to reason that it doesn't know it exists because it can't read the config. What are the access rights on that printcap file, anyway? I'm more asking about the root problem of why it is complaining that it was Unable to open printcap file cups for read!. Maybe you are not running the smbd you think you are? Maybe you compiled yourself, and are still starting the previous smbd in a different path (not having libcups support compiled in?) What is which smbd giving you? Thanks for the reply - it looks like I've covered all of the gotchas that you mentioned. Something else seems to be at work here... It's strange, true. That's why I come up with strange ideas. -Fran -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] adding printers from netlogon script
[Samba] adding printers from netlogon script Andrew Gaffney agaffney at technaut.darktalker.net Tue Dec 9 21:28:45 GMT 2003 Kurt Pfeifle wrote: [Samba] adding printers from netlogon script Andrew Gaffney agaffney at technaut.darktalker.net Tue Dec 9 20:10:07 GMT 2003 While this doesn't relate specifically to Samba, I need to do this in a netlogon .bat file in a Samba domain. In my network, I have a printer hooked to a JetDirect so that it is a TCP/IP printer. Is there a way I can automatically have this printer mapped/added when the user is logged on? Test this command from a DOS box: rundll32 printui.dll,PrintUIEntry /in /n \\printerserver\printersharename If it works, it can go into the logon script. (Of course printersharename needs to exist on printerserver and must have printer driver deposited on the server's [print$]-share for point'n'print download...). And: rundll32 printui.dll,PrintUIEntriy /? will show up a full man page (hehe...) See also http://de.samba.org/samba/docs/man/printing.html#id2931140 Will this same method work to add a TCP/IP printer instead of a SMB printer? No. This method adds a network printer (Microsoft terminology for a printer that is hanging off or is served via a print server). I assume you want a JetDirect printer (or LPD or IPP) with a network card of its own? This, in Microsoft-speak, is a local printer. Assuming you have already a local printer port present on your system named my_printer_tcpip_port (know that you can give local ports any name you want in Win2K and WinXP, if you use the Standard TCP/IP Port they offer; usually it tries to suggest a name like IP_192.168.1.1 if you choose to use an IP address for the printername or IP Adress field...), here is the commandline (untested): rundll32 printui.dll,PrintUIEntry /if /b My Printer Name /f %windir%\inf\ntprint.inf /r my_printer_tcpip_port /m AGFA-AccuSet v52.3 Note that you can use any *.inf file describing a printer driver installation and the associated driver name. The one I've choosen here should be present on each WinNT/2K/XP system and work for everyone to test... But again; please take the trouble to read that Microsoft man page... -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SOLVED Samba 3.0.0, CUPS support - Unable to open printcap file cups for read!
Fran Fabrizio wrote: I have set Printcap /dev/null in cupsd.conf and re-started cupsd first then smbd. Guess what? smbclient -L localhost still lists all my printers! And I can still print from my Windows apps. (I can't print anymore from OpenOffice, since that one *does* look for a printcap) In desperation I tried printcap = /etc/printcap even though the HOWTO recommended printcap = cups and Kurt's advice above is that you could even redirect to /dev/null. Guess what, it worked. At least on my install, it seems to require that you do have a real, live printcap even for CUPS printing support. I then added another printer via the redhat printer config tool, which added it to CUPS. I restarted smb and the new printer showed up on my Windows clients. So, the residual question is why does it require a real printcap file even under CUPS support? I think you should submit a bug report to http://bugzilla.samba.org/ The docs don't seem to feel that it should. Now I need to solve the You do not have sufficient access to your computer to connect to this printer problem from the Windows clients. :-) Thanks for the help, Fran -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] samba+cups+page_log
[Samba] samba+cups+page_log Mandar Deodhar mandar at netcore.co.in Wed Dec 3 10:13:40 GMT 2003 I have set up a samba server which i also want to use as printserver using cups. I have configured a samsung printer using cups and am also sharing it via samba by having the printer share in smb.conf file. Now the problem is that when i configure this printer on the windows machine and then send job to this server machine the page_log file is not being updated. Hence i m losing on the printer accounting which is my main aim. I have googled on this problem and found out the the windows is sending a raw printout to this server machine and hence the page_log file is not being updated. But i was unable to find any help as to how to prevent this. You should try and check the new Samba HOWTO Collection (both chapters on printing) for help. Could somebody please guide me on this matter ?? I am using cups-1.1.19-1 samba-3.0.0 compiled with cups ( shows libcups.so when i do ldd `which smbd`)do have printing=cups in smb.conf Printer Samsung ML-1210 with the driver installed locally on windows machine. Driver provided by vendor samsung The HOWTO Collection advices you to use the CUPS PostScript Printer Driver For Windows NT/2K/XP on the clients, if you require reliable accounting. However, there is a newcomer on the scene, which you can use as an add-on to CUPS, and which seems to be able to do accounting for your current setup and drivers. It is called Pycota and is under GPL: http://www.librelogiciel.com/software/PyKota/action_Presentation I haven't had the time to check it out, but it looks very promising. Also, CUPS 1.2 (betas will be out soon) will have better support for accounting Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Getting and providing help on this list (was Printing on Samba with WinNT...)
Re: [Samba] Printing on Samba with WinNT... * To: Rainer Hantsch rainer at hantschdotcodotat * Subject: Re: [Samba] Printing on Samba with WinNT... * From: John H Terpstra jht at sambadotorg * Date: Thu, 20 Nov 2003 15:29:34 + (GMT) [...] I know that noone owes an answer to anyone, but get into my situation: You have some angry people sitting in your neck, permamently telling you that they still cannot do this and that. Googleing around results in useless things. Finally you decide to subscribe this list to get help, ask more than 3 times - in kindly words - and get no useful answer, if any, only suggestions which sound in the best meaning as patches. :-/ Anyway, I beg your pardon. This is a volunteer list. I spend over 3 hours per day helping people. It would take an army of people like me to answer fully all requests we receive. I very, very, very much appreciate John T.'s answers on this list. He is most of the time giving very precise, hitting on the nail's top answers, and he also very often gives enough background info to not only reproduce the solution by slavishly copying the settings he suggests, but also understand *why* it works this way. That means that many questions go unanswered. We would all like to see more help activity. It would change dramatically if at least 25% of people who successfully acquired help on this list would feel obliged to give the same help to other newbies only on one occasion. A significant number of people subscribe to this list in the hope of getting a quick and painless answer to their spacific problem. It may take someone 15-30 minutes to think through what they want and to offer a simple reply. The alternatives to do this are: 1. Do not repsond - leave the person to sort their own way through our documentation. Usualy, that does cause frustration. 2. Point them to the HOWTO - but that irritates someone who just wants an instant answer so they can get on with life. One other options is this: -- anybody who ever got real quick and to the point help on this list should feel obliged to give back that help. He should stay and watch for another newbie to appear, and answer a questions he knows to answer. This could safe some time to John and others to work on the perfections of the written documentation, or of other Samba developers to work on the code and bugfixing We would love to learn what can be done to provide perfect documentation so that everyone can find instant answers. :-)) Until that time, the best advice is that there is no substitute for doing your own research - and I do not mean to offend with that statement. ...and give back what you learned in that research to any newbie asking a simple question. - John T. Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba 3 multible deamons running
[Samba] Samba 3 multible deamons running * To: samba at listsdotsambadotorg * Subject: [Samba] Samba 3 multible deamons running * From: Benjamin Stssel Berick at gmxdotnet * Date: Thu, 20 Nov 2003 15:35:29 +0100 (MET) Hi there something strange is going on on my server. Everytime when i am on a samba share the server starts another smbd This is normal Samba behaviour. Every connection is handled by a separate smbd process. (The important thing is that the processes go away again if you close the connection. Otherwise it is a bug) but i dont want that this happens! Really?;-) (Probably the Samba developers do very much welcome any patches which make this happen without loosing stability and functionality...). ;-) Can i turn that of in the config or is this an issue? You cant turn off and it isn't an issue... With kind regards Ben Cheers, Kurt [ who not *too* long ago learned about this himself ] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba 3.0 and the HP PSC 750 printer (printing over cups)
X-Enigmail-Version: 0.76.7.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit [Samba] Samba 3.0 and the HP PSC 750 printer (printing over cups) * To: samba at listsdotsambadotorg * Subject: [Samba] Samba 3.0 and the HP PSC 750 printer (printing over cups) * From: Grosswiler Roger roger at gwchdotnet * Date: Wed, 19 Nov 2003 13:34:27 +0100 (CET) hi all, i have samba 3.0 on a fedora-linux running. almost everyting works fine, except one printer, my hp psc 750 (connected via usb) is not printing via samba. I get pages printed (via cups or whatever) if i print from the localhost. So, here a few data from my smb.conf: printcap name = cups printing = cups load printers = yes [printers] comment = All Printers path = /var/spool/samba browseable = no # Set public = yes to allow user 'guest account' to print public = yes guest ok = yes writable = no printable = yes any idea?? If there is a PPD file involved with your printing setup, have you by any chance checked it against the online CUPS PPD validator? See here: http://www.cups.org/testppd or run the cupstestppd program yourself Which version of CUPS are you using? Which drivers are you using on the Windows client side? If you are using by any chance the client sends PostScript, CUPS converts for non-PS target printer-approach, then: which PostScript driver are you using on the clients? There is a little issue with the PPD generated by PPD-o-matic (on http://www.linuxprinting.org/): The user visible translation strings, indicating the print options for the various GUIs, may contain more than 40 characters (which is legal according to the Adobe PPD specification), but the CUPS PostScript driver for WinNT/2k/XP does not correctly work with these PPDs There are 3 possible workarounds: * enable the checkbox of the online-PPD-generator at Linuxprinting.org to limit the strings to 40 chars per line and generate a new PPD for the HP PSC 750: http://www.linuxprinting.org/show_driver.cgi?driver=hpijs (don't forget to check the GUI texts limited to 39 characters box!) * use the Adobe PostScript drivers instead of the CUPS PostScript driver (may give you some other drawbacks) * upgrade to the current RC1 of the version 5 of the CUPS PostScript driver (which now is digesting 80 characters per string) Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printer.tdb (tdb_oob len errors) and Quirkiness: Solaris 9, Samba 3.0.0
Jeff Gardiner wrote: Kurt, thank for taking the time to answer my questions. I very much appreciate it, and of course, you've opened my eyes up to a new part of the learning curve by introducing me to new and effective ways to use of the rpcclient command. [] What are you getting with these commands: rpcclient -Uroot -c enumprinters SUPERSERVER(if you have in the description lines two commas, there are no drivers recognized by Samba) When I first issued this command there were two commas - despite the fact that I had previously associated drivers (and installed them) with this printer After the command rpcclient. adddriver there will *still* be the 2 commas at that place. However, a rpcclient enumdrivers... will show up the new driver. Only *after* rpcclient setdriver drivername printername will you see appearing the drivername associated with the printqueue printername in question, and printed between these 2 commas. [] # rpcclient -Uroot -c enumdrivers 3 superserver Password: [Windows NT x86] Printer Driver Info 3: Version: [3] Driver Name: [Lexmark Optra T614] Architecture: [Windows NT x86] Driver Path: [\\superserver\print$\W32X86\3\LMPCL2A.DLL] Datafile: [\\superserver\print$\W32X86\3\LMPCL2AC.DLL] Configfile: [\\superserver\print$\W32X86\3\LMPCL2AC.DLL] Helpfile: [\\superserver\print$\W32X86\3\LMPCLNA.HLP] Dependentfiles: [\\superserver\print$\W32X86\3\mergepfm.dfm] Dependentfiles: [\\superserver\print$\W32X86\3\C910BM.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\C750BM.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\E32XBM.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\T62XBM.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\J110BM.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\C720BM.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\T61XBM.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\C710BM.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\W820BM.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\W810BM.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\M410BM.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\E855BM.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\OC1200BM.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\K1220BM.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\SC1275BM.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\OPTRASBM.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\LMPCLTHK.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\LMHB.HLP] Dependentfiles: [\\superserver\print$\W32X86\3\LMHBNDX.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\LMHBNDD1.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\LMPCL2AX.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\LMPCL2DD.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\LEXUNST.ZIP] Dependentfiles: [\\superserver\print$\W32X86\3\PTZIPW32.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\LEXEDF.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\LMNET2PP.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\LEXDRVX.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\LEXCFI.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\LMPCL2A.ALL] Dependentfiles: [\\superserver\print$\W32X86\3\LEXDRVIN.EXE] Dependentfiles: [\\superserver\print$\W32X86\3\DRVNPANT.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\LEXMV95.HLP] Dependentfiles: [\\superserver\print$\W32X86\3\PTRESW32.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\PTGUIW32.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\PTAPIW32.DLL] Dependentfiles: [\\superserver\print$\W32X86\3\LMPCLHOW.HLP] Dependentfiles: [\\superserver\print$\W32X86\3\LMPCLNA.CNT] Dependentfiles: [\\superserver\print$\W32X86\3\LMPCL2A$.INI] Monitorname: [] Defaultdatatype: [RAW] Oh b -- this is a hge driver! With 39 dependent files there are good chances it drives your soundcard to voice a nice women's announcememt saying Yeer printjeeeb is reaaad [] I had read over a number of the man pages and other documentation including John T. excellent book, but was not familiar with this use of the rpcclient command. These should be in the book also, in the chapters dealing with printing I found (and find) them to be extremely useful tools, and will have to reread the man pages. I recognized that familiarity with the command line tools that allow you to get to Samba's underbelly really helps in resolving problems. Thanks for posting them. [] Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions:
[Samba] Printerassistent.
[Samba] Printerassistent. * To: samba at listsdotsambadotorg * Subject: [Samba] Printerassistent. * From: StefandotIven at voessingdotde * Date: Tue, 18 Nov 2003 10:43:26 +0100 Hi there, Ok. My last postings about my problems with printerinstalation over controlpanel were still not answered. So maybe I have to ask my question in an other way. Is someone able to install a printer shared by Samba 3/Samba pre3 x over the controlpanel? I don't clearly understand your question. Please describe exactly what you want to achieve. From what I guess, it is that you want start the Add Printer Wizard on a Win workstation and add a printer to the Samba server. This is not possible -- or only possible if you provide a custom script and call it with the add printer command in smb.conf. The script would have to draw its input parameters from the fields filled in by the user running the Add Printer Wizard and then create a printer to the real Unix print subsystem of your Samba server (not just add it to the smb.conf) What is possible is to add a driver to the Samba server and associate it to a pre-existing (raw) print queue of the Unix print subsystem (this queue may, in the case of CUPS, have been created with the help of the CUPS web interface sitting behind port 631). Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] printer.tdb (tdb_oob len errors) and Quirkiness: Solaris 9, Samba 3.0.0
[Samba] printer.tdb (tdb_oob len errors) and Quirkiness: Solaris 9, Samba 3.0.0 * To: samba at listsdotsambadotorg * Subject: [Samba] printer.tdb (tdb_oob len errors) and Quirkiness: Solaris 9, Samba 3.0.0 * From: Jeff Gardiner gardiner at imagingdotrobartsdotca * Date: Tue, 18 Nov 2003 11:39:28 -0500 I set up printing IAW: What does IAW mean? http://us4.samba.org/samba/docs/man/printing.html This side is currently unavailable to me. I hope it contains the same document as http://us3.samba.org/samba/docs/man/printing.html, which I *can* see... I've confirmed the drivers are being installed to /etc/samba/drivers/W32X86. More exactly, they should end up in /etc/samba/drivers/W32X86/2/ or in /etc/samba/drivers/W32X86/3/ (depending on which type of driver you chose to install. Yet I am unable to print even a test page. I get the following error: Test page failed to print. Would you like to view the print trouble shooter for assistance? Access is denied. What are you getting with these commands: rpcclient -Uroot -c enumprinters SUPERSERVER(if you have in the description lines two commas, there are no drivers recognized by Samba) rpcclient -Uroot -c enumdrivers SUPERSERVER rpcclient -Uroot -c enumdrivers 2 SUPERSERVER rpcclient -Uroot -c enumdrivers 3 SUPERSERVER rpcclient -Uroot -c enumports SUPERSERVER This checks if Samba exports the kind of stuff Windows clients are looking for And I get the following errors in my samba log file: tdb(/usr/local/samba/var/locks/printing/irl.tdb): tdb_oob len 1600941951 beyond eof at 67552 [2003/11/18 11:05:20, 0] tdb/tdbutil.c:tdb_log(724) tdb(/usr/local/samba/var/locks/printing/irl.tdb): tdb_oob len 858730825 beyond eof at 67552 [2003/11/18 11:05:20, 0] tdb/tdbutil.c:tdb_log(724) tdb(/usr/local/samba/var/locks/printing/irl.tdb): tdb_oob len 1600941951 beyond eof at 67552 The following is my smb.conf file: [global] netbios name = SUPERSERVER workgroup = WINZOMBIES os level = 99 preferred master = yes domain master = yes local master = yes security = user domain logons = yes logon path = \\%N\%u\profile logon drive = H: logon home = \\%L\%U logon script = startup.bat guest account = nobody map to guest = bad user time server = yes admin users = root @sysgrp smb passwd file = /etc/samba/smbpasswd log file = /var/log/samba/log.%m printing = lprng load printers = yes show add printer wizard = yes printcap name = /etc/samba/lib/printcap printer admin = @ntadmin root lpq cache time = 20 use client driver = no [netlogon] path = /var/lib/samba/netlogon read only = yes write list = ntadmin [profiles] path = %H/profile read only = no create mask = 0600 directory mask = 0700 [homes] comment = Home Directories read only = No browseable = No [print$] comment = Printer Driver Download Area path = /etc/samba/drivers browseable = yes guest ok = yes read only = yes printable = yes Where it you find the advice to tag your [print$] share as printable?? This is wrong. It means that Samba tries to export a printer with the name of print$, while it should be just a special file share holding the driver files for clients to download. (If it is a typo in above document, quick-quick!, provide a pointer to the exact place where it occurs so it may be corrected) Instead of printable = yes insert a write list = @ntadmingroup, username1, username2 to make it writeable to these users. (root gets write access in any case, if he is in the smbpasswd file (or backend). Doesn't it work if you copy the print-related settings as suggested in the document you quoted? Start there and then work from that point to make your modifications, and you'll see which of your settings (like create mode etc.) may break it [printers] comment = All Printers browseable = no printable = yes public = yes writable = no guest ok = yes create mode = 0700 path = /var/spool/samba [irl] path=/tmp comment = Main Lab Lexmark Printer browseable = yes printable = yes public = yes create mode = 0700 lpq command = lpq -Plp-std lprm command = lprm -Plp-std %j print command = /irus/bin/lpr -r -h -Plp-std %s Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Printerassistent.
Antwort: [Samba] Printerassistent. * To: samba at listsdotsambadotorg * Subject: Antwort: [Samba] Printerassistent. * From: StefandotIven at voessingdotde * Date: Tue, 18 Nov 2003 16:35:35 +0100 Hello Kurt, first I like to thank you that you try to help me. I will try to explain my problem exactly. Here is what I have done. I set up Samba as an PDC. I generated shares and printershares. I browsed my network over the Networkneighborhood down to my Sambaserver. There I can see all File and Printershares. I doubleclicked Which client Win OS are you using? the printerfolder where I then can see only shared printers and one folder calld new printer. I then rightclicked a shared printer and went to the process for uploading the printerdriver in the Sambaserver. So far so good. Everything is ok. No errors Now i will install the printer on the client machine. One way is to browse the Networkneighborhood. So I browsed one folder up, there where I can see printer- and fileshares. I rightclick the printer for wich I first installed the drivers in the server and choosed connect. The drivers were downloaded from the server and printer is installed an the client. The client is able to print correctly. Browsing the Network is one way to install a printer on a client. And this is the recomended way in the HOWTO An other way to install a printer on a client is to use the controlpanal. Well, at least in the HOWTO this is nowhere recommended... (It is even in a pure MS Windows environment a much slower way to do it, if you have more than a few dozen PCs and printers...) This doesn't say that there might not be a bug with that part of the Samba-Code, however...) So I clicked the startbutton on the client, went to the controlpanel, clicked Printers, clicked Add new Printer, choosed Networkprinter, left the printername empty to search for the printer, clicked continue button, and then -- there I can see the domain, some clients wich belong to the domain and wich offers printer, but not my samba server. You'd need to post your smb.conf (minus comments) to get more advice on that I hope you now understand what I mean. Yes. Today I tried with Suse Sles8, the newest updates, but still the same problem. 2.2.8a worked right, but I'm not able to get this running with Samba3. I realy hope that I now have exactly explained what I mean. Thanks a lot, and I hope to hear you. MfG Stefan Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] 2k and 9x connect and print, XP won't
[Samba] 2k and 9x connect and print, XP won't * To: 'Samba Mailing List' samba at listsdotsambadotorg * Subject: [Samba] 2k and 9x connect and print, XP won't * From: Eric Geater 11/10/03 egeater at mscoincdotcom * Date: Mon, 17 Nov 2003 09:58:24 -0600 Good day! I am running Samba3 on a Mandrake 9.1 box. Right now, I have security = user, but am not using any password authentication yet. I have 95 and 98 computers that can reach the shares available and print to the installed printer, and even a Windows 2000 user can do all of this. However, an XP computer I have can't go there. I double-click DRAKEJAX (the netbios name), and it prompts me for a username and password. security = user *is* telling Samba to ask for username/password-type authentication. By default, WinXP uses the loginname of the user to try and authenticate to a remote service like Samba. If that doesn't work, you get the prompt. You can try this: * check if a user named nobody is set up on your system * set guest user = nobody in smb.conf * set map to guest = bad user in smb.conf This will automatically use the nobody credentials (=guest) and remove the prompt. Read what man smb.conf has to say about map to guest = bad user! Since you don't provide any config details this is all help you can expect here. No idea why your W2K can access the share. No matter what user/pass combo I use, from XP I cannot get there. Anyone have a similar experience? Maybe a solution, too? Thanks! Eric -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] samba (2.2.8a) driver download fails
[Samba] samba (2.2.8a) driver download fails * To: samba at listsdotsambadotorg * Subject: [Samba] samba (2.2.8a) driver download fails * From: Gernot Hueber hueber at riicdotat * Date: Mon, 17 Nov 2003 13:34:54 +0100 Hi there, I have a problem with the rpc driver stuff: I have copied the driver files to //atlas/print$/W32X86 and WIN40 (via filesystem copy), added and set the driver without errors. But getdriver reports no driver associatet with the printer?! So reports below. I am sure, this was working on this system. When? What changed? You mean it was working with Samba-2.2.8a? I tried to reinit the ntprinters.tdb, printing.tdb, nt_forms.tdb and ntdrivers.tdb by removing and HUPPING all smbds (a plenty of users are on the server so I could not restart smbd cleanly). Can anybody give me some advice. Thanks Gernot PS Maybe an issue: I copied, added, and set the driver several times in a script (W32X86 WIN40 for each printer of the same type!) begin atlas# rpcclient -U root%sukt19wk -c 'getdriver HP_1200N_Kloib 1' atlas cmd = getdriver HP_1200N_Kloib 1 atlas# end enumdrivers is ok: That's one of the most important parts. begin atlas# rpcclient -U root%sukt19wk -c 'enumdrivers' atlas cmd = enumdrivers [Windows 4.0] Printer Driver Info 1: Driver Name: [hp4p] Printer Driver Info 1: Driver Name: [hp1200] Printer Driver Info 1: Driver Name: [hp4050n] [Windows NT x86] Printer Driver Info 1: Driver Name: [hp1200] Printer Driver Info 1: Driver Name: [hp4050n] Printer Driver Info 1: Driver Name: [hp4p] end enumprinters is ok too That's the other important part. begin atlas# rpcclient -U root%sukt19wk -c 'enumprinters' atlas cmd = enumprinters flags:[0x80] name:[\\atlas\HP_1200N_Kas] description:[\\atlas\HP_1200N_Kas,hp1200,HP LJ 1200 Kastler] comment:[HP LJ 1200 Kastler] flags:[0x80] name:[\\atlas\HP_1200N_Kloib] description:[\\atlas\HP_1200N_Kloib,hp1200,HP_1200N_Kloib] comment:[HP_1200N_Kloib] flags:[0x80] name:[\\atlas\HP_4050N] description:[\\atlas\HP_4050N,,HP 4050] comment:[HP 4050] flags:[0x80] name:[\\atlas\HP_4050N_2fach] description:[\\atlas\HP_4050N_2fach,hp4050n,HP 4050 2.Fach] comment:[HP 4050 2.Fach] flags:[0x80] name:[\\atlas\HP_4050N_Konto] description:[\\atlas\HP_4050N_Konto,hp4050n,HP_4050N_Konto] comment:[HP_4050N_Konto] flags:[0x80] name:[\\atlas\HP_Laserjet4+Buchm] description:[\\atlas\HP_Laserjet4+Buchm,hp4p,HP_Laserjet4 +Buchm] comment:[HP_Laserjet4+Buchm] flags:[0x80] name:[\\atlas\HP_LaserJet4_Holz] description:[\\atlas\HP_LaserJet4_Holz,hp4p,HP_LaserJet4_Holz] comment:[HP_LaserJet4_Holz] flags:[0x80] name:[\\atlas\Minolta_DI350] description:[\\atlas\Minolta_DI350,,Minolta_DI350] comment:[Minolta_DI350] atlas# end enumdrivers 3 crashes :-( IIRC, this is a not-yet-fixed bug in the 2.2.x series (where x = 4). begin atlas# rpcclient -U root%sukt19wk -c 'enumdrivers 3' atlas cmd = enumdrivers 3 [Windows 4.0] Segmentation fault (core dumped) I remember this happening for me in Samba 2.2.8a also. atlas# end So what? The proof of the pudding lies in the eating. Does the driver download to your Win clients work? Do the Win clients see the drivers? (on W2K/XP workstations right-click the white background of the Samba Printers and Faxes folder as seen in network neighbourhood, select Server Properties, select Drivers tab and check if your drivers are visible. -- Dipl.-Ing. Gernot Hueber Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] printing / printcap name in samba-3.0.0 BUG
[Samba] printing / printcap name in samba-3.0.0 BUG * To: samba at sambadotorg * Subject: [Samba] printing / printcap name in samba-3.0.0 BUG * From: Joerg Pulz JoergdotPulz at frm2dottumdotde * Date: Wed, 12 Nov 2003 18:31:12 +0100 (CET) hi, i currently tried to setup a samba print server which uses cups as default printing system and for some special printers i want to use my own scripts. samba-3.0.0 is linked against libcups and printing via cups and the driver download works perfect. whe i try to specify a special printer with printing = bsd/lprng/sysv my own print command and a special printcap inside the service description, samba is always trying to print via cups and testparm shows the following warning: - -- Processing section [special-printer] Global parameter printcap name found in service section! - -- here are the minimum settings from smb.conf: - -- [global] load printers = yes printcap name = cups printing = cups [printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = no writable = no printable = yes [special-printer] comment = special printer path = /var/spool/samba-special printing = bsd printcap name = /usr/local/etc/samba/printcap.static print command = /path/to/command public = no writable = no printable = yes - -- the samba-howto-collection describes it this way, Actually, it recommended to use printcap = lpstat and printing = sysv. so it's eihter an error in the howto document or in the smb.conf file processing. I am responsible for that part of the HOWTO Collection, and I myself noticed last night that there is something not kosher with that part. I seem to remember that I just copied and pasted an example setup into that document's source (at the time HTML), which *definitely worked for me*. But I was using 2.2.8 and 3.0alpha24 and 3.0beta-something at the time... I'll try to investigate next week and come up with another working solution for this. Sorry, no time before that (and no environment to test it) Sorry for having co-caused your problem. Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] problems with cupsaddsmb
[Samba] problems with cupsaddsmb * To: samba at listsdotsambadotorg * Subject: [Samba] problems with cupsaddsmb * From: Marco Rben roeben at webdotde * Date: Wed, 12 Nov 2003 22:15:39 +0100 Hi! I'm using Suse 9.0 with cups 1.1.19 and Samba 3.0. I'm trying to share my printer on the network. Testparm runs without errors and I can see my printer in the network neighborhood. So the smb.conf should be fine. But when I try to install the driver with cupsaddsmb I get the following error. zwobot:/usr/sbin # ./cupsaddsmb -U root -a -v [] result was WERR_BAD_PASSWORD I have no clue what this mean and how I can fix it. Can somebody help? This would be great! regards Marco P.S. Here's my smb.conf [global] [] security = share Have you ever tried (like is suggested in the Samba HOWTO and the cupsaddsmb man page) to use security = user ?? Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] OT: English and French translations of Munich Migration Case Study seems to be available
Hi, all, I stumbled across this page (German language) announcing the availability of the Munich Migration Case Study (my translation of the title): http://www.muenchen.de/aktuell/ms_linux.htm What some of our international readers might be interested in is the last sentence of this paragraph: Da das Interesse an diesem Projekt sehr hoch ist, hat sich die LHM entschlossen, allen Interessierten auch die Kurzfassung der Studie (PDF-Datei 1,6 MB), die als Grundlage fr diese Entscheidung von der Fa. Unilog erstellt wurde, zum Download zur Verfgung zu stellen (http://www.muenchen.de/aktuell/clientstudie_kurz.pdf). Wenn Sie Interesse an einer englischen oder franzsischen Version haben, wenden Sie sich bitte direkt an die Fa. Unilog (georg dot unbehaun at unilog dot de). (Free) Translation: Since interest for this project is very large, the City of Munich has decided to offer the shortened version of the Study (PDF file of 1,6 MB) for public download. This version has been crafted by Unilog (http://www.unilog.de/) and served as the base for the political decision of the Munich City Council to migrate. -- If you are interested in an English or French version of the Study please contact Unilog directly (georg dot unbehaun at unilog dot de). Please note that I have santized the poor man's e-Mail address for obvious reasons. Cheers, and have fun! Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Guest Account - don't enter a password
[Samba] Guest Account - don't enter a password * To: samba at listsdotsambadotorg * Subject: [Samba] Guest Account - don't enter a password * From: Gabby James lizard092 at hotmaildotcom * Date: Tue, 11 Nov 2003 14:39:03 -0700 Hello, I am using samba 2.07-36 on a RedHat 7.1 linux system. I want to share a directory on my Linux system to various Windows operating systems (Windows 95, 98, 2000 etc). In the shares definition section I have: [MyShareDir] comment=My Shared Directoy on my Linux system path= /home/john public = yes writable = yes printable = no create mode = 0664 directory mask = 0775 browseable = yes guest ok = yes guest account = ftp guest only = yes At a DOS prompt on a Windows 2000 machine, I type: net use v: \\10.2.2.2\MyShareDir I get a message: The password or username is invalid for 10.2.2.2 then it prompts me for a username. Your Win2000 client doesn't know anything about the settings of your Samba server's smb.conf. (Unless you're logged into your Win2000 as user ftp:) Your client will by default attempt to the login to Samba with the current Win user name (john, james, whatever). And of course, Samba rejects this user and prompts you for another login There are 2 possible solutions: * You could add to your smb.conf's [global] section map to guest = bad user which will cause Samba silently to map to user ftp if Win2000 supplies a bad user name like john or james. (NOTE that this will happen with all users and shares). Please read the explanations for the map to guest parameter in man smb.conf. * simply change your DOS window command to read net use v: \\10.2.2.2\MyShareDir /USER:ftp You can get more MS help hints by typing net help and net help use Cheers, Kurt From reading about samba, I thought the guest account would login in user ftp and not prompt for a password since I have guest ok set to yes. Am I wrong in that idea or is something just wrong with my setup? Thanks -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Translation Dok to German, first file, deutsche bersetzung Der Samba Doku erste Datei
[Samba] Samba Translation Dok to German, first file, deutsche bersetzung Der Samba Doku erste Datei * To: samba at sambadotorg * Subject: [Samba] Samba Translation Dok to German, first file, deutsche bersetzung Der Samba Doku erste Datei * From: rruegner robowarp at gmxdotde * Date: Mon, 10 Nov 2003 22:10:20 +0100 * Cc: Hi @ll , the first file is now translated to German find it here http://www.robowarp.de/smb/trans/net.8.html thx for his work to Mr Stefan G. Weichinger mailto robowarp at gmxdotde if you want to be a part of the Translation Team you can view other files translation progress and the readme beyond http://www.robowarp.de/smb/trans/ Best Regards Robert Rgner Hi, all -- this is a really great initiative. Please keep us informed about your progress! One little question: are you aware that the *sources* of all English Samba documentation are now DocBook/XML? Have you considered to write the docu (or maybe convert it at a later stage) into that format? I know that DocBook/XML is rather difficult for people who are not used to it and it makes them slow down a lot. (I myself haven't written my part of the HOWTO Collection in XML. but in HTML and one kind soul did convert it for me). However, it makes it more easy to create PDFs and other formats from that input. Thanks again and Cheers! Kurt Hallo, die erste Datei der Samba Doku wurde ins Deutsche bersetzt http://www.robowarp.de/smb/trans/net.8.html Vielen Dank dafr an Stefan G. Weichinger falls ihr Euch beteiligen wollt mailt an robowarp at gmxdotde Ihr knnt den Fortschritt der bersetzung anderer Dateien unter http://www.robowarp.de/smb/trans/ einsehen MfG Robert Rgner -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] pdfs cause laserjet 4000s to hang - any workaround?
[Samba] pdfs cause laserjet 4000s to hang - any workaround? * To: samba at listsdotsambadotorg * Subject: [Samba] pdfs cause laserjet 4000s to hang - any workaround? * From: Steve Kersley stevedotkersley at kebdotoxdotacdotuk * Date: Fri, 31 Oct 2003 15:03:10 - Before I start, I know this isn't a Samba-related issue but it seems to be a widespread enough problem that someone else may have figured out a Samba-oriented workaround, or any other solution for that matter. Hi, Steve, not that I am sure about a solution. But I know about a similar problem with HP PS printers, if you use a particular setting of the HP-provided PPD file (part of the driver, as used f.e. by CUPS, but also by Windows clients). Since you are asking on the Samba list, I assume your Windows clients use the PS driver for the PDF files. v(PCL drivers on PDF files are dead-slow in any case). The drivers contain a setting called Scale Patterns. These should be set to Off, because the On is very buggy and may crash the printer. There seems to be a problem with certain models of HP Laserjet (including, but not limited, to the 4000 series and other models from the same era - it is apparently fixed in the 4100). Certain PDF files, when printed, cause the printer to crash - although outwardly it appears to be processing the job (data light flashing and so on), nothing ever happens until you reset the printer and delete the job. Resending it will cause it to crash again. I've asked around and it's not just us who suffer - I know of several other people with exactly the same problem, and all use different systems - we use Samba, another uses Windows Server and yet another just uses peer-to-peer with no server at all. The best help I've found on HP's support site is an article saying it happens on Apple Macs and is related to a certain font. Which font? Is it a font enumerated in the PPD? (In that case it may help to edit the PPD and delete that font from the list) No mention of it happening on Windows, but it does and is clearly a cross platform problem. The workarounds suggested are to either edit the PDF file and remove the offending font, or to print as an image. The latter works, but is incredibly slow (a couple of minutes per page) for even the simplest of documents. The printer I have most problems with is in a student computer room, and at times I have to go back and forth to power cycle the printer several times an hour. I also can't rely on the students following fairly complicated instructions to get round it - experience shows they just click print half a dozen times before giving up, leaving the print queue clogged up with corrupt jobs. So, does anyone have any suggested workarounds? Has anyone else actually seen this problem? I'm using Samba under Gentoo Linux on the server, LPRNG as my printing system and Windows 2000 on the workstations. Thanks in advance. Steve. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] samba3 and cups printserver
RE: [Samba] samba3 and cups printserver * To: samba at listsdotsambadotorg * Subject: RE: [Samba] samba3 and cups printserver * From: Ken Walker kendotwalker at textilesdotumistdotacdotuk * Date: Fri, 31 Oct 2003 18:49:23 - smbd invalid option --b and -b isnt in man smbd ? That means you are trying to run a version 2.2.x smbd. -b is one of the cool new (commandline-)options I discovered shipping with Samba-3. cups-demo: # smbd --help Usage: smbd [OPTION...] [] -b, --build-optionsPrint build options [] Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba3 and cups printserver
Kurt Pfeifle wrote: RE: [Samba] samba3 and cups printserver * To: samba at listsdotsambadotorg * Subject: RE: [Samba] samba3 and cups printserver * From: Ken Walker kendotwalker at textilesdotumistdotacdotuk * Date: Fri, 31 Oct 2003 18:49:23 - smbd invalid option --b and -b isnt in man smbd ? That means you are trying to run a version 2.2.x smbd. -b is one of the cool new (commandline-)options I discovered shipping with Samba-3. cups-demo: # smbd --help Usage: smbd [OPTION...] [] -b, --build-optionsPrint build options [] Cheers, Kurt Ooops -- I hit the Send button too early Another means to know if CUPS support is compiled in is provided by ldd (certainly on Linux platforms); it lists dynamic dependencies: cups-demo: # ldd `which smbd` | grep cups libcups.so.2 = /usr/lib/libcups.so.2 (0x40195000) Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] print job complete messages
[Samba] print job complete messages * To: samba at listsdotsambadotorg * Subject: [Samba] print job complete messages * From: Nick Pietraniec npietran at campbellcodotcom * Date: Tue, 28 Oct 2003 15:22:19 -0500 I know I've read something about this in the distant past, but i can't seem to find any info on it now. I'm hoping someone knows offhand... I'm using samba 2.2.8a and cups 1.1.17 to serve printing to some windows 2000 workstations. Cups is set up with raw queues and I'm using the windows drivers available from HP. When the clients print from the windows print server, they get a winpopup message that tells them when their job is done. We don't get this from the samba server. Does anyone know offhand where/how to integrate a script to send this message via winpopup to the clients? If I can figure it out, I promise to write a howto and stick it up on the web somewhere (if there isn't one). thanks in advance. -Nick -- Re-name your backend(s) for the printer(s) [see the device URI used]. -- create wrapper-script(s) that takes place of original backend(s). -- let your wrapper-script call the (now re-named) original backend and do its job (of sending away the file to the printer) -- make your wrapper-script check if job is completed (using a variant of lpstat -W completed -o) -- make your wrapper-script send the pop-up message to the win user -- exit 0 (or else) your wrapper-script. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: samba 2.27 as print server
[Samba] Re: samba 2.27 as print server * To: samba at listsdotsambadotorg * Subject: [Samba] Re: samba 2.27 as print server * From: Robert Robertedstrom at yahoodotcom * Date: Fri, 24 Oct 2003 21:30:40 -0500 My original post is http://lists.samba.org/archive/samba/msg72613.html. [global] [] printing = lprng print command = lpr -U%u -P%p -r %s As I said: you are missing a ;rm %s at the end of your print command... Let it be print command = lpr -U%u -P%p -r %s; rm %s and your problem should be gone... See also http://samba.vernstok.nl/htmldocs/Samba-HOWTO-Collection.html#printing lpq command = lpq -U%u -P%p lprm command = lprm -U%u -P%p %j lppause command = lpc -U%u hold %p %j lpresume command = lpc -U%u release%p %j queuepause command = lpq -U%u stop %p queueresume command = lpq -U%u start %p [ipc$] What do you need this for??? path = /tmp hosts allow = 192.168.0.0/24 127.0.0.1 hosts deny = 0.0.0.0/0 [Lexmark] comment = Lexmark Z22 Color JetPrinter use client driver = yes path = /etc/samba/printers/Lexmark That is not a good way to define the spool path /etc/ is for other things. Better use /var/spool/samba/ printable = Yes -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] samba 2.27 as print server
Phillip M. Bryant wrote on Samba-Digest: [Samba] samba 2.27 as print server * To: samba at listsdotsambadotorg * Subject: [Samba] samba 2.27 as print server * From: Bryant, Phillip -AES PhillipdotBryant at ittdotcom * Date: Thu, 23 Oct 2003 12:43:28 -0400 I'm running Samba 2.27 rather 2.2.7 on RH8 system. You should be telling us which print subsystem you have installed. CUPS? LPRng? Which version? I've got samba as the print spooler for Windows XP clients and using winbind as the user validation against my Win2K DC. Permissions on the spool directory are root root with the sticky bit on. Clients can delete their own jobs from the que, but the spool directory is not being expunged of print jobs and the last job constantly displays in the client que window. I have not been able to figure out how to resolve this as occasionally people freak out when they see older jobs in the print que and wonder if it is stuck. For whatever reason, the print process is unable to remove the print job from the spool directory after it is sent to the lpd process for printing. You should also be telling us, which smb.conf settings related to printing your Samba daemon is using. Try testparm -v | egrep '(print|lp|enumport|driv|spool|\[|path)' and hit ENTER twice It is well possible that you are using a customized print command, and have forgotten to include a ;rm %s at the end Cheers, Kurt Phillip M. Bryant ITT Industries, Advanced Engineering and Sciences Network Administrator Albuquerque, NM 87120 Ph 505-889-7016 Cell 505-385-8668 MCSE 2000, NT 4.0 MCP+I -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] advanced printing features setting not saved [Samba] advanced printing features setting not saved
Alexander Geraldy geraldy at informatikdotuni-kldotde wrote on Samba-Digest: [Samba] advanced printing features setting not saved * To: samba at listsdotsambadotorg * Subject: [Samba] advanced printing features setting not saved * From: Alexander Geraldy geraldy at informatikdotuni-kldotde * Date: Thu, 23 Oct 2003 20:59:21 +0200 Hello, we run SuSE8.2 with Samba 2.2.7a-78 (SuSE's own version?!) and Windows XP clients. After an update to 3.0.0, everything works well (user access on file services and printing), but we can't save the advanced printing features(?) (german: Erweiterte Druckfunktionen aktivieren) flag (WinXP - Settings - any printer - Advanced) anymore. It better doesn't! Since Samba nor the underlying Unix print subsystem (like CUPS or LPRng) can not process EMF-type print data from the Windows GDI (as are sent over the network from the clients to the print server if advanced printing features are on), it *should* be disabled. I am glad it is disabled by default now (wasn't the case in earlier versions, IIRC), and that you can not really enable it. It just makes no sense with Samba. Clients sending EMF expect the print server to execute the Windows driver (which Samba obviously can't) and generate PCL or PostScript or whatever from that EMF input. That is what the advanced printing features is for This holds for all our (HP-)printers while the duplex option is stored on the samba server. But duplex *printing* works for the clients? This one flag is always reset to disabled without any warning or error message. I think a warning would be even more confusing. (You are the first person in a very long time I see asking this on the list. A warning, or worse, an error message, would have provoked a myriad of investigations ;-) However, that is now explained in the much extended printing chapters of the Samba 3.0 HOWTO Collection. These chapters are well worth reading even if you don't plan to run Samba-3.0 in the near future, for most of the stuff applies 1:1 for Samba 2.2.x. A clean install of samba 3.0.0 did not change anything about this problem. Since no user can print duplex or n-to-1 with samba 3.0.0, I am confused now. Does duplex printing work or not? The n-to-1 printing depends on the driver type you are using for the clients and on the way you installed drivers and tried to save the settings. I had to install the old samba version again. Is there any known solution for this problem? In which files are the printer settings stored on the samba server? I didn't find anything about that topic. OK -- see the Samba-3.0 HOWTO Collection! thanks for your help! - Alexander Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing banner pages
Re: [Samba] Printing banner pages * To: Peter Blajev peter at castandcrewdotcom * Subject: Re: [Samba] Printing banner pages * From: Adam Williams adam at morrison-inddotcom * Date: Fri, 24 Oct 2003 05:51:09 -0400 * Cc: Samba List samba at sambadotorg In Samba 3.0.0 (may be in earlier versions too) if I specify printing = cups printcap name = cups then manually set print command is ignored. Well, without print command how can I force the printer to print banner page every time job is sent? Does simply enabling CUPS banners on the queue not work? If you want CUPS banner pages, use the CUPS PostScript Driver for Win NT/2K/XP. See the printing chapters of the Samba-3.0 HOWTO Collection about these drivers. Info applies to Samba 2.2.x also. Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Printing from Win2000
[Samba] Printing from Win2000 * To: samba at listsdotsambadotorg * Subject: [Samba] Printing from Win2000 * From: Garrett GaRogers at studentdotjjcdotedu * Date: Fri, 24 Oct 2003 01:56:58 -0500 Hello, I have just started using samba a couple of weeks ago. I am using Slackware 9.1 and windows 2000. i can see everything. on my windows box i can see my linux box and visa versa. but i have a HP deskjet 932c on my linux box and i want to be able to print from windows. windows can see the printer in network neighborhood but it says that it is unable to connect access denied. i have set the drivers right and everything. here is my smb.conf: [global] netbios name = MYSERVER server string = Is It Not Nifty? encrypt passwords = Yes log file = /var/log/samba.log socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = cups wins support = Yes hosts allow = 192.168.1.100 I suspect this setting could be a guilty one, should you try to access your Samba from a different host than 192.168.1.100 printing = cups What does testparm -v | grep security (hit ENTER twice) return? If it is security = share, change it to security = user [public] path = /home/garrett read only = No guest ok = Yes [printers] path = /var/spool/samba guest ok = Yes printable = Yes print command = /usr/bin/lpr -P%p -r %s If you have printing = cups and printcap = cups, correct builtin print commands should automatically be used. Your manually set ones are ignored. browseable = No [HPDeskjet] comment = HP DeskJet 932C, hpijs path = /home/garrett/hpspool read only = No guest ok = Yes printable = Yes print command = /usr/bin/lpr -P%p -r %s printer name = Garrett oplocks = No And when i type this command lpstat i get this: To test if you really have the *driver* for that printer ready when a clients tries to Connect..., use these commands: rpcclient -Uroot%[smbpassword] -c enumdrivers localhost rpcclient -Uroot%[smbpassword] -c enumprinters localhost (where [smbpassword] must first have been set with the smbpasswd -a root command...) garrett at garrett:~$ lpstat Printer 'Garrett at localhost' - cannot open connection - No such file or directory Make sure the remote host supports the LPD protocol and accepts connections from this host and from non-privileged (1023) ports Printer 'Garrett at localhost' - cannot open connection - No such file or directory Make sure the remote host supports the LPD protocol and accepts connections from this host and from non-privileged (1023) ports This means that you are running the lpstat command version shipping with LPRng, not the CUPS one! Your installation is broken. You need to decide: Do you want to use CUPS or LPRng? Remove the other one and re-install the desired package. Try again. (If you are trying to run both on the sam box, make sure your RedHat/Mandrake/Debian alternatives system is working correctly and that you have enabled the print subsystem you actually want to use at this moment.) Please help me if anyone knows what the problem is. Thanks a alot! -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] EU Linux migration document. -- German Gvt. Migration Guide
Re: [Samba] EU Linux migration document. -- German Gvt. Migration Guide * To: Kurt Pfeifle kpfeifle at dankadotde * Subject: Re: [Samba] EU Linux migration document. -- German Gvt. Migration Guide * From: Jeremy Allison jra at sambadotorg * Date: Fri, 24 Oct 2003 20:28:42 + * Cc: samba at listsdotsambadotorg samba at listsdotsambadotorg, samba-technical at listsdotsambadotorg On Fri, Oct 24, 2003 at 09:52:19PM +0200, Kurt Pfeifle wrote: Maybo someone with connections may be ablt to place a news item? I'm doing that now :-). Oh pain, oh pain: those poor web server admins coming back to work on Monday, suffering from being slashdotted for their first time... ;-) Maybe someone knows [EMAIL PROTECTED] and can forewarn them?;-) Jeremy. Cheers, Kurt P.S.: I now found some details about the publisher of that Guide as a book: it is MITP, and they say that it will be available in Oktober 2003 and gives these details: Hardcover ca. 448 pages, Format 17,0 x 24,0 cm ISBN 3-8266-1421-6 ca. 29,95 (http://www.mitp.de/vmi/mitp/detail/pWert/1421) -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Automatic printer driver installation - PLEASE urgently RESPONS
Adam Williams adam at morrison-ind.com wrote on Samba-Digest: Thu Oct 2 14:31:50 GMT 2003 Sorry to interrupt you guys, and I understand you are getting a lot of mail every day, but we having a big problems about to let Windows XP client automatic add printer driver from the Samba Server (2.2.8a), we can not More info would be useful. find any documentations on the internet, Google turns up a lot of links: http://us2.samba.org/samba/ftp/cvs_current/docs/htmldocs/ http://us2.samba.org/samba/ftp/cvs_current/docs/htmldocs/printing.html http://us2.samba.org/samba/ftp/cvs_current/docs/htmldocs/CUPS-printing.html http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/ http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Windows 2000 workstations can't open Excel files on Samba-2.2.7(a?) after ServicePack-ing 4 on them.
Hi, Samba-friends I am not very deep in Samba *file* services, so please bear with me. The network admins of my employer alarmed me (being the local Linux Guy) with this problem: * they run a 2-node fileserver cluster, based on RedHat (version?) with a Samba version announcing itself 2.2.7-security-rollout or similar. * Samba runs in a chrooted environment. It was set up and configured by some external contractor. Everything run smoothly and stable until recently. * The now have upgraded 100 Windows 2000 workstations to ServicePack 4 (after some testing, they say). * Now these workstations' users can't open any Excel files on the Samba shares any more. The error message speaks about missing memory. * If they copy the files to the local box, they are able to open them. The files also do open after being copied over to the previous WinNT 4.0 file server, which was resurrected now for the purpose. I was able to have a look at it last night. I took notes about versions, config settings etc, but - rats! - left the paper in the server room, so I can't be much more specific at the momeent. (My notes are locked in there now since it is a bank holiday in Germany.) One strange thing is this: -- After increasing the debuglevel to 5 (using smbcontrol), one workstation could open the files. *That* connection was made as root. Decreasing debuglevel to 1, 2, 3 and 4 re-produced the problem. Increasing to 5 and 10 made it go away again. -- Trying to repeat the same from a different workstation (where the connection was made as a normal user) recreated the problem, but in all debuglevels, including 5 and 10. My questions: * Is this an already known problem ? * What could possibly cause it? What could I do for a remedy ? * What exact tests could I run and what info could I give (apart from the obvious smb.conf, version no. etc.) to help trace it ? [I have the log files for levels 1, 2, 3, 4 and 5 reflecting attempts to open the Excel files from the workstation that connected as root]. Any help and hint is much appreciated. Thanks for your efforts. Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Why I can't set some default printer options for my HP 1015 + CUPS printer ??
Zhao You Bing zhaoyb at cad.zju.edu.cn Mon Sep 22 10:23:15 GMT 2003 [] but one problem I encountered is that I can't check the Advanced option on for the samba printer (I've tried to check them, but it does not take effect), while I can do it well for locally installed printers and I don't know where samba put the default options are, S -- that's because you haven't seen or read docments like the new Samba HOWTO Collection shipping with Samba CVS and 3.0rc-X. The relevant parts in the printing chapters are here (and they apply mostly to the late 2.2.x releases too): http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#11_1 http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#11_2_10 Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Access denied when printing to Samba printers
Ben Finney benfinney at thegoodguys.com.au Thu Aug 14 14:48:23 GMT 2003 Ben Finney wrote: Failure: - Printing anything to said printer shares. [...] [printers] comment = All printers path = /var/local/spool/samba create mask = 0700 guest ok = Yes printable = Yes Corey Hart asked me (off-list) to check the permissions on the spool directory. They are: $ ls -ld /var/local/samba/spool/ drwxrwxrwt 2 root nogroup 4096 Aug 7 13:24 /var/local/samba/spool/ Well -- but your path in smb.conf points to /var/local/spool/samba and *not* /var/local/samba/spool/ (This is based on advice to make a separate spool directory, with the same permissions as /tmp has.) Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Server-side printer settings?
Chris Nolan wrote: Date: Thu, 14 Aug 2003 07:34:33 +0200 From: Kurt Pfeifle [EMAIL PROTECTED] Subject: [Samba] Server-side printer settings? To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii; format=flowed Thu Aug 14 10:30:35 GMT 2003 Hi all! I have a situtation that I want to get happening: 0 We have just installed a colour photocopier with duplexing at a client's office. We're looking to have four printers pointing at this one device, I guess you mean four print*queues*... Sorry. :-) The funky setup that Mandrake provides has spoiled me. It's a welcome change from those damned OpenServer and UnixWare servers I have to take care of. with the following settings (one for each printer): * Black and White * Black and White, Duplexed * Colour * Colour Duplexed My question is, can we have server-side settings for this sort of thing? Yes. See http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#11_2_10 http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#11_1 My question is, do you know which Unix print sub-system your Samba server relies on? Do you mind telling? Do you know which kind of client Windows OS there are using this Samba server? I do not mind telling at all! CUPS is the print sub-system in use in this particular setup. OK. So what kind of client Windows OS'es are using this Samba server? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Problems with adding Windows printer drivers to a Samba box
Chris Nolan chris at itoperations.com.au
Thu Aug 14 10:22:11 GMT 2003
Hi all!
Here is an interesting problem:
I have installed Mandrake 9.0 on two server boxes, both of which are
running very happily and have been for a year now (and a year or two
before that on earlier versions of Mandrake). I was able to successfully
add printer drivers to one of these boxes (as it was the only one
running Samba at the time, called MAIN) without any problems.
Yesterday, I had to install some drivers for a Toshiba photocopier (for
all those considering Toshiba photocopier purchase/rental for network
printing *DON'T*. Their drivers are horrible, unstable bodies of code).
Ah, interesting. Do you have access to the source code?
On the existing Samba box and on the new one (with security = domain
pointing at MAIN), I could not add the driver. It turns out that one of
my administrator friends had previously added the driver to the MAIN
box, after setting the following options on the [Printers] and [print$]
shares:
nt acl support = no
write list = list of users
read list = list of users
Apparently, this resulted in the Toshiba driver spewing method call
failures to the screens of the workstations. He cleaned that up and
deleted the printer driver files from MAIN (but not the driver). I have
since used rpcclient to remove the driver entry.
Now, whether adding to the MAIN box or the newly setup Samba instance
(on a box called GRUNTMASTER), I always get Operation could not be
completed when attempting to add the driver. The logs show that Samba's
conversation with the client attempting to add the driver results in a
service (along the lines of ::{a34af-25df4-cdf4a-a65gc}) not being found.
Oh Samba gods of ye almighty list, do ye have any wisdom to bestow upon
us merely very experienced and grizzled administrators?
Oh ye miserable Samba user, do ye have the drive to make an effort of
providing us with some of the the setting bits and bytes you decided to
put on probe for our running smbd and nmbd services? Oh ye darn Samba
follower of mine, be ensured that our godmighty powers are still not
enough to read minds and remote smb.confs if no ethernal or seasonal
ether link is provided to lead into your machine, and if no devilish
SSH daemon accepts my very own password...;-)
The fact that my
Samba server at this client's premises has required more than 30 minutes
of my attention this year is very depressing!
Bah! What a shame!! Ye shall act in penance for 30 * 30 minutes now,
helping on this list more inexperienced users than you are to find
the divine way to their complete Samba enlightenment .
Regards,
Chris
Cheers,
Kurt
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Server-side printer settings?
Chris Nolan chris at itoperations.com.au Thu Aug 14 10:30:35 GMT 2003 Hi all! I have a situtation that I want to get happening: We have just installed a colour photocopier with duplexing at a client's office. We're looking to have four printers pointing at this one device, I guess you mean four print*queues*... with the following settings (one for each printer): * Black and White * Black and White, Duplexed * Colour * Colour Duplexed My question is, can we have server-side settings for this sort of thing? Yes. See http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#11_2_10 http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#11_1 My question is, do you know which Unix print sub-system your Samba server relies on? Do you mind telling? Do you know which kind of client Windows OS there are using this Samba server? My reading of the rpcclient man page says that servers can contain settings, but I would like to be able to do the following: * Specify which users can modify the settings for themselves and those that can't Every user can modify settings for themselves. * Specify which users can update the server-side settings Users listed in the printer admin setting of smb.conf (plus root) can modify the server-side settings. Server-side settings are used as defaults, in case users don't specify or change user-side settings. * (If possible but highly unlikely) Specify which parts of the printer settings can be modified in the first case Not possible. All responses that make me smarter welcome! Depending on *what* *exactly* you want to effectivly achieve by having different user groups access different parts of the printer admin, there might be workarounds. It would involve the editing of the printer driver's PPD, to remove options that are not meant to be user-selectable (and leaving only the one[s] which should be used). F.e. your Black and White queue would not have a Colour option, and your Colour Duplex not a black and white and simplex one. Of course, your users would still be able to switch queues if they wanted the other option in printing. (You could fiddle with the access to the queues too, of course), Smarter now?;-) Regards, Chris Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] cups addprinter fails dos error 0x00000013 (Samba 3b3)
Chris Puttick chris at centralmanclc.com wrote on Samba-Digest: Tue Aug 12 14:57:22 GMT 2003 Hi As per subject line... Samba 3 beta 3 installed and functional (e.g. appears in browse lists on windows, shares accessible etc.) on SuSE 8.2. CUPS 1.1.18 configured and functional, cups drivers installed. Using cupsaddsmb results in failure with DOS code 0x0013: Running command: rpcclient localhost -N -U'root%**' -c 'adddriver Windows NT x86 coloura3:cupsdrvr.dll:coloura3.ppd:cupsui.dll:cups.hlp:NULL:RAW:NULL' result was DOS code 0x0013 Attaching with rpcclient and running adddriver results in same error. The print$ subdirectory W32X86 is created, but not the expected 2 one. The cups drivers are successfully copied into W32X86, as is the ppd. Any thoughts? If further information is needed, let me know. smb.conf below. Regards Chris Puttick [global] workgroup = TRINITY netbios aliases = zulu2 server string = security = SHARE Try with setting security = USER and repeat cupsaddsmb -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Access denied when printing to Samba printers
Ben Finney benfinney at thegoodguys.com.au Thu Aug 14 10:46:41 GMT 2003 Howdy all, I'm setting up a print server machine to serve hosts in an Active Directory domain. Debian GNU/Linux (sarge, current testing branch), Samba 3.0.0beta2-1. Success so far: - All steps in the current DIAGNOSIS document http://au1.samba.org/samba/devel/docs/html/diagnosis.html - Sharing printer drivers from the [print$] share (yay!) - Connecting to the Samba server from a Win2000 host - Connecting to individual printer shares from a Win2000 host What exactly do you mean by Connectiong to individual printer share, but failure printing anything?? Failure: - Printing anything to said printer shares. The Win2000 client, when attempting to print a test page to the printer, immediately responds with Access denied and an offer to lead me through the printer troubleshooting help. Have you increased debuglevel to 3 or 5 and watched out for the exact messages *Samba* is logging around that Access denied event? You may find it usefull to also set debug timestamp = no for easier readability of log.smbd Selected portions of 'testparm -vs': And what's the output of a simple 'testparm'? = Processing section [printers] Processing section [print$] Load smb config files from /etc/samba/smb.conf Loaded services file OK. 'winbind separator = +' might cause problems with group membership. # Global parameters [global] workgroup = TGGLOCAL realm = netbios name = TGGSPS001 interfaces = bind interfaces only = No security = DOMAIN auth methods = encrypt passwords = Yes update encrypted = No client schannel = Auto server schannel = Auto allow trusted domains = Yes map to guest = Never null passwords = No obey pam restrictions = Yes password server = tggad001, tggad002, * private dir = /var/lib/samba passdb backend = tdbsam, guest guest account = nobody restrict anonymous = 0 lanman auth = Yes ntlm auth = Yes client NTLMv2 auth = No client lanman auth = Yes client plaintext auth = Yes protocol = NT1 acl compatibility = paranoid server security = Yes load printers = Yes printcap name = cups Have you really CUPS as your Unix print subsystem? In this case there should be an additional setting of printing = cups in your smb.conf. But your selected portions of 'testparm -vs' doesn't show up *any* setting for the printing. (So samba might be defaulting to bsd) disable spoolss = No idmap only = No idmap backend = idmap uid = 1-2 idmap gid = 1-2 winbind separator = + winbind cache time = 600 winbind enum users = Yes winbind enum groups = Yes winbind use default domain = No printer admin = @lpadmin, TGGLOCAL+Domain Admins [printers] comment = All printers path = /var/local/spool/samba create mask = 0700 guest ok = Yes printable = Yes print command = lp -c -d %p -o raw; rm %s lpq command = lpstat -o %p lprm command = cancel %p-%j These commands will not be used if you have both, printing = cups and printcap = cups browseable = No [print$] comment = Printer drivers path = /var/lib/samba/printers write list = root, @lpadmin, TGGLOCAL+Domain Admins guest ok = Yes = The frustrating part is that this was working briefly a week ago, but is not currently and I can't determine why. This is small comfort of course; but it does show that it's at least possible to get this working :-) So *what* did you change during that time, to the best of your memory? Settings, updates, hardware, clients, ? Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] cupsaddsmb claims to work but fails
Damien Bonvillain kame at cinemasie.com wrote on Samba-digest Tue Jul 29 00:58:38 GMT 2003 Case strange... I've past probably 30 hours by now on this, crawling the web, and doing attempts. I managed to make cupsaddsmb run without producing an error, but it fails. *Where* does it fail? *What* is not working for you? Ask me for anything, I am asking you for a detailed description of any error. Your mail only includes successfull commands and their output The enumdrivers 3 command is buggy in most versions of Samba 2.2.x. Just avoid level 3. Use plain enumdrivers and enumdrivers 2 full trace, versions and so on, but please, if someone has an idea, share it. Linux Debian Woody unstable Cups 1.1.19final-1 Samba 2.2.3a-14 smb.conf Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Using print$ / timeouts to port 445...
Ken Kleiner ken at cs.uml.edu wrote on Samba-digest: Tue Jul 29 16:52:53 GMT 2003 Hi... I have set up my smb.conf to use the print$ directive, and have shared 3 printers. I sucesfully added the printer drivers to the host, and can use them. But - opening up the printer connection from the windows host is slow, and causes the printer 'status' window to say 'initializing'. While that happens, my samba.log shows : 2003/07/29 16:44:40, 2] lib/access.c:check_access(327) Allowed connection from (myipaddress) [2003/07/29 16:45:02, 1] lib/util_sock.c:open_socket_out(860) timeout connecting to (myipaddress):445 [2003/07/29 16:45:22, 1] libsmb/cliconnect.c:cli_connect(782) Error connecting to (myipaddress) (Operation already in progress) [2003/07/29 16:45:22, 0] rpc_client/cli_spoolss_notify.c:spoolss_connect_to_client(91) connect_to_client: unable to connect to SMB server on machine MACHINE-NAME. Error was : SUCCESS - 0. [2003/07/29 16:45:22, 2] lib/access.c:check_access(327) Allowed connection from (myipaddress) I see that port 445 is MICROSOFT-DS, but am wondering how/why I can change this? I know I can set disable spoolss = yes in smb.conf, but that obviously breaks the auto driver download. Breaking the auto driver download doesn't allow a normal domain user to add a printer, as they get ' not sufficient access to local machine to add printer '. Thanks for any help you can shed on this... -- Ken Kleiner System Manager Computer Science Department Don't they teach there to give versions, OS, config and other system details, when asking for help in a newsgroup?;-) Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] WINS-Support
Marc Hansen wrote on Samba-digest: Message: 5 Date: Sun, 27 Jul 2003 16:06:26 +0200 From: Marc Hansen [EMAIL PROTECTED] Subject: [Samba] WINS-Support To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=US-ASCII Hi, does Samba use localhost as WINS-Server, if only wins support = yes is set? Since wins support = yes is a setting in your local smb.conf, and since the local smb.conf is read by your local Samba when starting up (and while running too): Yes - it will make your localhost a WINS server. Please note, that it will be nmbd (not smbd) acting as a WINS server. Also, make sure that you only have *one* (and never more than one) WINS servers (counting the Samba- as well as the MS Windows-based machines) in your environment. It should only be necessary in a multi-subnetted environment. Regards, Marc Hansen Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] How to recover the printer drivers?
Vizitiu, Ciprian CVizitiu at gbif.org Tue Jul 1 17:50:13 GMT 2003 Of course printcap is there in /etc and it is 644. Did I forgot to copy something? Yes, the Registry Anybody with a hint? Samba stores printer driver information (including DeviceMode etc.) in its own equivalent to the Windows Registry, the *.tdb files. These should also be restored to get everything up and running as before Hmmm... I've restored ALL the content of /etc/samba and /var/cache/samba. Please tell me that there are other places where samba keeps tdbs... This differs from distribution to distribution. It is a compile-time option. IIRC, on my other box some of the tdbs were in /usr/lib/samba/ Because otherwise I've restored them all. :-/ Is the printers registry different than the users one? I don't understand what you mean with users registry. The *.tdb files relevant for printing are printing.tdb, nt_forms.tdb, ntprinters.tdb, ntdrivers.tdb. The the *.tdb stuff has changed slightly from 2.2.x to 3.0. I guess you are running 2.2.x ? The only thing I can say is that I have successfully restored the whole printing setup covering dozens of printers already twice (some time ago) by restoring the *.tdbs plus the other Samba files. Because the rest of the samba seems to be working domain auth and like. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Recovering printer drivers ][
Vizitiu, Ciprian CVizitiu at gbif.org Wed Jul 2 20:12:57 GMT 2003 ... Since I got no answers to my previous post about forgotten printer drivers Sorry, I was away for a few days... that is printer drivers that disappear after you reinstall a samba and brig back all .tdb from back-up I said what a hell let's try adding the printer drivers again. You guessed, it didn't worked. After asking me for the printer driver location XP ws returns a message that Operation could not be completed. and later Access is denied. My only guess is that something is broken/corrupt with your restored *.tdb files The most strange thing, in the printers folder on samba I get a folder named __SKIP_0073. What does this mean? No idea. Never seen this. :-o 2.2.8a RH8. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] How to recover the printer drivers?
Vizitiu, Ciprian CVizitiu at gbif.org
Tue Jul 1 16:58:12 GMT 2003
Samba 2.2.8a-1, RH8.
... So, I had to reinstall. Fortunately I had a back-up copy. I've installed
everything and then went to back-up and brought back all the stuff from
/etc/samba and /var/cache/samba and all /etc/cups and /etc/printcap*.
Aparently samba is working corectly: All user/machine accounts are in place
winbind OK... It's just that although I've restored the /home/printers
folder in the previous state it looks like I've lost my printer drivers.
Rpcclient enumdrivers shows empty hands although the driver files are in the
corresponding folder! Printing directly to CUPS works without any problem
and using the same config files it worked before the move.
Logs for the machine trying to print looks like:
[2003/07/01 15:41:08, 0] printing/pcap.c:pcap_printername_ok(289)
Unable to open printcap file cups for read!
[2003/07/01 15:41:08, 0] smbd/service.c:make_connection(252)
ws130 (191.x.y.130) couldn't find service
::{2227a280-3aea-1069-a2de-08002b30309d}
[2003/07/01 15:42:00, 1] smbd/service.c:make_connection(636)
Of course printcap is there in /etc and it is 644. Did I forgot to copy
something?
Yes, the Registry
Anybody with a hint?
Samba stores printer driver information (including DeviceMode etc.)
in its own equivalent to the Windows Registry, the *.tdb files.
These should also be restored to get everything up and running as
before
Cheers,
Kurt
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Cups or Samba?
Halászy-Kiss Ágoston agoston at simeis.net Mon Jun 30 21:07:00 GMT 2003 [] What I discovered: - after linux box boot it didn't print from any winXP, booting process includes starting cupsd and smbd - but if I reload samba it starts to print - it seems to me samba didnt load printers at the boot process Any ideas, solutions? cupsd *must* be completely up and running for Samba to pick up the printer list. * Make sure that cupsd is started well before smbd (and make sure that you get a return code of 0 for the lpstat -r before you try to start smbd * Make sure that CUPS writes a printcap file by enabling the Printcap /etc/printcap directive in cupsd.conf. Please post me at : agoston at simeis.net Thanks in advance Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Cups or Samba?
David Morel david.morel at amakuru.net Mon Jun 30 21:09:57 GMT 2003 Le lun 30/06/2003 à 21:07, Halászy-Kiss Ã?goston a écrit : - after linux box boot it didn't print from any winXP, booting process includes starting cupsd and smbd - but if I reload samba it starts to print - it seems to me samba didnt load printers at the boot process I think cupsd takes a little time to populate the printers list at startup, but i would tend to think smbd would reload the list on a regular basis, is it not so ? Oh yes -- that's the *theory*. As far as the *practical* side of things goes, unfortunately a bug in most recent versions of Samba prevents this from happening Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] rpcclient returns NT_STATUS_NO_SUCH_DEVICE on adddriver
Damien Bonvillain kame at cinemasie.com Sun Jun 29 13:25:51 GMT 2003 Hi, samba 2.2.8a freshly compiled cups 1.1.19final-1 (debian) while using cupsaddsmb, all runs well until adddriver, when rpcclient returns a cryptic NT_STATUS_NO_SUCH_DEVICE. I've followed the SambaPrintHowto 3.0 from 7.11.6.1 to 7.11.6.6, Read 8.5 too... Also, 7.11.6 is describing the pure commandline installation of the driver files using smbclient and rpcclient. Your quotes below show your usage of cupsaddsmb, which is discussed in 7.10.x and it fails on the latest as well. Here is some more information. ===8=== cupsaddsmb -a -v [] Running command: rpcclient localhost -N -U'root%password' -c 'adddriver Windows NT x86 MomijiPrintingSystem:cupsdrvr.dll:MomijiPrintingSystem.ppd:cupsui.dll:cups.hlp:NULL:RAW:N ULL' INFO: Debug class all level = 3 (pid 20372 from pid 20372) session setup ok Domain=[NAVI] OS=[Unix] Server=[Samba 2.2.8a] cmd = adddriver Windows NT x86 MomijiPrintingSystem:cupsdrvr.dll:MomijiPrintingSystem.ppd:cupsui.dll:cups.hlp:NULL:RAW:N ULL adddriver Windows NT x86 MomijiPrintingSystem:cupsdrvr.dll:MomijiPrintingSystem.ppd:cupsui.dll:cups.hlp:NULL:RAW:N ULL result was NT_STATUS_NO_SUCH_DEVICE This one is your main problem, part 1. [] Running command: rpcclient localhost -N -U'root%password' -c 'adddriver Windows 4.0 MomijiPrintingSystem:ADOBEPS4.DRV:MomijiPrintingSystem.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RA W:ADOBEPS4.DRV,MomijiPrintingSystem.PPD,ADOBEPS4.HLP,PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,IC ONLIB.DLL' INFO: Debug class all level = 3 (pid 20376 from pid 20376) session setup ok Domain=[NAVI] OS=[Unix] Server=[Samba 2.2.8a] cmd = adddriver Windows 4.0 MomijiPrintingSystem:ADOBEPS4.DRV:MomijiPrintingSystem.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RA W:ADOBEPS4.DRV,MomijiPrintingSystem.PPD,ADOBEPS4.HLP,PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,IC ONLIB.DLL adddriver Windows 4.0 MomijiPrintingSystem:ADOBEPS4.DRV:MomijiPrintingSystem.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RA W:ADOBEPS4.DRV,MomijiPrintingSystem.PPD,ADOBEPS4.HLP,PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,IC ONLIB.DLL result was NT_STATUS_NO_SUCH_DEVICE This one is your main problem, part 2. Running command: rpcclient localhost -N -U'root%password' -c 'setdriver MomijiPrintingSystem MomijiPrintingSystem' INFO: Debug class all level = 3 (pid 20378 from pid 20378) session setup ok Domain=[NAVI] OS=[Unix] Server=[Samba 2.2.8a] cmd = setdriver MomijiPrintingSystem MomijiPrintingSystem setdriver MomijiPrintingSystem MomijiPrintingSystem SetPrinter call failed! result was NT_STATUS_ACCESS_DENIED This one is most likely caused by the previous error. ===8=== ===8=== /etc/samba/smb.conf # Global parameters [global] workgroup = NAVI server string = %h server (Samba %v) security = SHARE Try security = user... [] ===8=== I hope somebody can help me, it's been a month I started to try to add this printer :-) Your log level of 3 should be sufficient to uncover the problem. Scan the Samba log (probably in /var/log/samba/log.smbd) for *all* messages occuring during you run cupsaddsmb. You might discover an access denied or a similar problem Damien -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Printer drivers on a samba 2.2.8a server: how?
Fabio Muzzi liste at kurgan.org Wed Jun 25 18:10:33 GMT 2003 I'd like to set up my samba 2.2.8a server to serve printer drivers to clients when needed. I have set up the print$ share, in which I still have no drivers. Tried adding drivers from a win2000 workstation by using server properties command, I can't add anything since all buttons are greyed out. The user I am using is in the printer admin group in smb.conf. I can provide snippets of the config files if needed. Is there some docs I can read about my specific issue, http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/ or generally about printing with samba 2.2.8 and cups? most of above 3.0 doc applies to Samba 2.2.x too. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] 2.2.8a, printer driver download: need to use setdriver
X-Enigmail-Version: 0.71.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Brandon Lederer brandonl at hms4emc.com Thu Jun 26 09:27:32 GMT 2003 This is the EXACT problem I had. Haven't fixed it either if I have 10 printers upload all the drivers.. for all the OS's... how do I tell which drivers go with which printer? By using setdriver drivername printername... This is in the new 3.0 HOWTO very explicitely. http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/ Most of the printing chapter applies to 2.2.x too -Original Message- From: Andreas [mailto:andreas at conectiva.com.br] Sent: Thursday, June 26, 2003 9:24 AM To: samba at lists.samba.org Subject: [Samba] 2.2.8a, printer driver download: need to use setdriver Hello I'm setting up the automatic printer driver download feature, and it works nicelly except for one little thing: I have to use, on the samba machine, rpcclient's setdriver command to associate a printer with its driver. I didn't see this requirement in the Samba howto, it only mentions setdriver as a way to speed up large installations. Am I missing something? Should windows make this association automatically when it uploads the driver to the samba [print$] share? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Searching for Doku Samba with LDAP
Robert Einsle robert at einsle.de Wed Jun 25 08:31:53 GMT 2003 Hy * I'm searching for Doku acting as an PDC in an Windows environment. I was able to set up the Ldap-Directory itself, storing the Users in the Directory, this all is working. But was not able to let the Workstations join the Domain. Here i don't find Dokumentation about it. Can anyone send me links about Dokumentation about LDAP and Samba, acting as an PDC. Hi, Robert, have you ever checked out the new HOWTO Collection? It is here: http://samba.org/~jht/NT4migration/Samba-HOWTO-Collection.pdf Cheers, Kurt Thank you very much about your Help. \Robert -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] paid-for-print
[Samba] paid-for-print Julian Tzonev uli at naval-acad.bg Mon Jun 23 11:19:46 GMT 2003 Hi there, I'm newbie in Samba, so I beg for your excuse if my questions are stupid. Is it possible to use Samba as a paid-for-print server? Not out-of-the-box. I'd know how to do it if you give me to days to fiddle with it. If U know something about another free paid-for-print software, please let me know. 1. There is printbill -- now with initial, but still limited CUPS support: http://ieee.uow.edu.au/~daniel/software/printbill/ printbill is GPL and actively maintained and developed. 2. Then there is pycota -- developed for CUPS originally: http://www.librelogiciel.com/software/PyKota/action_Presentation pycota is GPL in source code, and you can compile and setup yourself, but it is poorly documented. The author sells a pre-compiled version plus documentation and support under a shareware type license, I believe. pycota is actively maintained and developed. 3. Lastly, printquota. It only supports LPRng: http://printquota.sourceforge.net/ printquota is GPL and actively maintained and developed. 10x in advance, -- Julian Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] paid-for-print
[Samba] paid-for-print Kurt Pfeifle kpfeifle at danka.de Mon Jun 23 11:43:09 GMT 2003 [Samba] paid-for-print Julian Tzonev uli at naval-acad.bg Mon Jun 23 11:19:46 GMT 2003 Hi there, I'm newbie in Samba, so I beg for your excuse if my questions are stupid. Is it possible to use Samba as a paid-for-print server? Not out-of-the-box. I'd know how to do it if you give me to days to fiddle with it. If U know something about another free paid-for-print software, please let me know. 1. There is printbill -- now with initial, but still limited CUPS support: http://ieee.uow.edu.au/~daniel/software/printbill/ printbill is GPL and actively maintained and developed. 2. Then there is pycota -- developed for CUPS originally: http://www.librelogiciel.com/software/PyKota/action_Presentation pycota is GPL in source code, and you can compile and setup yourself, but it is poorly documented. The author sells a pre-compiled version plus documentation and support under a shareware type license, I believe. pycota is actively maintained and developed. This may sound a bit too unfriendly towards pycota. Let me put it straight: to me pycota looks like the *first* choice for anybody needing external print accounting support in CUPS. (Future CUPS versions may have their built-in accounting capabilities improved) 3. Lastly, printquota. It only supports LPRng: http://printquota.sourceforge.net/ printquota is GPL and actively maintained and developed. 10x in advance, -- Julian Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Trouble with CUPS/SAMBA
[Samba] Trouble with CUPS/SAMBA Bo Mellberg bo.mellberg at jolife.se Mon Jun 23 10:34:12 GMT 2003 Hi all, I'm new to this list, as to SAMBA, and I'm struggling with getting a printer to work as a shared printer in a Windows network with a redhat 9 server. The printer is a HP 4550 Color LaserJet, installed with CUPS to the server, via JetDirect (port 9100). It prints testpages fine from the Linux-server. It was installed with the install-printer-utility in RedHat9. I have then shared the printer via samba, to be able to access it from the Windows machines (2000, XP). It shows up fine, and accept print jobs, but nothing happens after the jobs has been processed, and no errors are being generated. Please refer to this document (PDF or HTML) http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/ and see if it answers your questions. I would be grateful for any help. /Bo Mellberg Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Trouble with CUPS/SAMBA
Bo Mellberg bo.mellberg at jolife.se Mon Jun 23 10:34:12 GMT 2003 Hi all, [] I have then shared the printer via samba, to be able to access it from the Windows machines (2000, XP). It shows up fine, and accept print jobs, What kind of driver are you using on the Windows side? Are you aware of the various methods to install drivers on Windows clients to be used with Samba/CUPS printing? but nothing happens after the jobs has been processed, and no errors are being generated. I would be grateful for any help. [] [printers] comment = All Printers path = /var/spool/samba Does this directory exist? public = yes guest ok = yes printable = yes printer admin = root, @ntadmins [] cups error_log: E [23/Jun/2003:09:51:31 +0200] Scheduler shutting down due to SIGTERM. E [23/Jun/2003:09:51:31 +0200] Unknown directive AuthType on line 729. What is written into line 729 of cupsd.conf?? I [23/Jun/2003:09:51:31 +0200] Sending browsing info to :631 I [23/Jun/2003:09:51:31 +0200] Listening to 0:631 I [23/Jun/2003:09:51:31 +0200] Configured for up to 100 clients. I [23/Jun/2003:09:51:31 +0200] Allowing up to 10 client connections per host. I [23/Jun/2003:09:51:31 +0200] LoadPPDs: Read /etc/cups/ppds.dat, 13 PPDs... I [23/Jun/2003:09:51:31 +0200] LoadPPDs: No new or changed PPDs... I [23/Jun/2003:09:51:47 +0200] Job 30 queued on 'hp4550' by 'bosse'. I [23/Jun/2003:09:51:47 +0200] Started filter /usr/lib/cups/filter/cupsomatic (PID 32466) for job 30. You should never use cupsomatic for a real PostScript printer. Who adviced you to do so? The new Samba Printing HOWTO is very specific about real PostScript printers: _Use_ _the_ _vendor_ _provided_ _PPDs_ !! I [23/Jun/2003:09:51:47 +0200] Started backend /usr/lib/cups/backend/socket (PID 32467) for job 30. I [23/Jun/2003:10:02:06 +0200] Job 31 queued on 'hp4550' by 'bosse'. I [23/Jun/2003:10:02:06 +0200] Started filter /usr/lib/cups/filter/cupsomatic (PID 335) for job 31. I [23/Jun/2003:10:02:06 +0200] Started backend /usr/lib/cups/backend/socket (PID 336) for job 31. If you are still having trouble, use LogLevel debug. Some advice about this is also at http://www.cups.org/cups-help.html Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Trouble with CUPS/SAMBA - Solved
SV: [Samba] Trouble with CUPS/SAMBA - Solved Bo Mellberg bo.mellberg at jolife.se Mon Jun 23 18:21:05 GMT 2003 I solved the problem by using: Which versions of CUPS and Samba are you using? And are you *really* still using the cupsomatic-PPD from Linuxprinting.org for that *PostScript*-printer?? [global] printing = cups printcap name = lpstat load printers = yes and in [printers]-section: [printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = yes writable = no printable = yes create mode = 0700 print command = lpr -P %p -o raw %s -r lpq command = lpstat -o %p lprm command = cancel %p-%j printer admin = @users With great help from: http://www.buberel.org/linux/cups-samba.php Hope it helps someone... I fear it does more confuse than help -- unless your version info is forthcoming Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Trouble with CUPS/SAMBA
Bradley W. Langhorst brad at langhorst.com Mon Jun 23 21:34:26 GMT 2003 On Mon, 2003-06-23 at 04:34, Bo Mellberg wrote: ;[fredsprn] ; comment = Fred's Printer ; valid users = fred ; path = /home/fred ; printer = freds_printer ; public = no ; writable = no ; printable = yes you should'nt need this ... the printers will automatically get loaded from the printcap or cups api... But he had all this commented out ;[fredsdir] ; comment = Fred's Service ; path = /usr/somewhere/private ; valid users = fred ; public = no ; writable = yes ; printable = no ;[pchome] ; comment = PC Directories ; path = /usr/local/pc/%m ; public = no ; writable = yes ;[public] ; path = /usr/somewhere/else/public ; public = yes ; only guest = yes ; writable = yes ; printable = no ;[myshare] ; comment = Mary's and Fred's stuff ; path = /usr/somewhere/shared ; valid users = mary fred ; public = no ; writable = yes ; printable = no ; create mask = 0765 [jolife shared] comment = Shared Jolife documents path = /home/jolife/ writeable = yes guest ok = yes do you really want all these? the homes share does it automatically... This is also commented out [bosse] [lennart] [martin] [peter] [semmy] [steven] cups error_log: He should set LogLevel debug in cupsd.conf E [23/Jun/2003:09:51:31 +0200] Scheduler shutting down due to SIGTERM. E [23/Jun/2003:09:51:31 +0200] Unknown directive AuthType on line 729.your config file for cups is bad at line 729... I [23/Jun/2003:09:51:47 +0200] Job 30 queued on 'hp4550' by 'bosse'. I [23/Jun/2003:09:51:47 +0200] Started filter /usr/lib/cups/filter/cupsomatic (PID 32466) for job 30. I [23/Jun/2003:09:51:47 +0200] Started backend /usr/lib/cups/backend/socket (PID 32467) for job 30. I [23/Jun/2003:10:02:06 +0200] Job 31 queued on 'hp4550' by 'bosse'. I [23/Jun/2003:10:02:06 +0200] Started filter /usr/lib/cups/filter/cupsomatic (PID 335) for job 31. I [23/Jun/2003:10:02:06 +0200] Started backend /usr/lib/cups/backend/socket (PID 336) for job 31. these lines look like your job has made it to cups and is failing in there... This is likely, but not conclusive. Is it really a job originating from a Windows client? Only LogLevel debug would show... Also, LogLevel debug would show if and why job 30 failed. (There is not yet an error in this part of the log. It would appear on the next few lines, but these were not provided) so you don't need to mess with your samba configuration. if this doesn't work - take it to the cups lists... one problem you may have is that the windows pcs are sending jobs that are ready for printing with no ripping... you could try setting up your printer in cups as a raw printer instead of pcl5 or whatever you set it up as. best wishes! Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Trouble with CUPS/SAMBA - Solved
Bo Mellberg bosse at mellberg.org Mon Jun 23 23:31:26 GMT 2003 Yeah, it really helps me that you come after I managed to get ANYTHING out of that printer, I am so very sorry, that I have not been *constatntly* watching the list for your feedback, and that once I had responded to your second mail also, your SOLVED mail appeared within a minute in my mailbox. Now that *some* feedback from you is forthcoming, it is not what was asked for, unfortunately. and say that all I do is wrong. Did I say so? Did I say All? You have been asked a few very specific questions to help solve your problem which you never bothered to answer. The versions are the the one installed by RedHat Linux 9 (shrike). Now, if I knew by heart which versions of CUPS and Samba RH9 do install, I wouldn't need to ask further... I installed the printer using the redhat utility, and I configured samba using, first the redhat utility, and then fiddling with the smb.conf. Any drivers used by the Windows clients are their own (postscript). Dont ask me how cupsomatic got in there, 'cause I dont know. Until you can come up with a better idea of installing the printer, I'll manage with this one, thank you very much. And just how is getting this to work properly confusing to others? I tell you: * You was posting a smb.conf with a print command = lpr -P %p -o raw %s -r and some other manually set commands. * Your posted smb.conf is quite in opposition to what the smb.conf man page advices. * The man page says this: ...If SAMBA is compiled against libcups, then printcap = cups uses the CUPS API to submit jobs, etc. Otherwise it maps to the System V commands with the -oraw option for printing, i.e. it uses lp -c -d%p -oraw; rm %s. With printing = cups, and if SAMBA is com- piled against libcups, any manually set print command will be ignored. So *your* questions have been ansered. Maybe not well enough... /Bo Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Setting up a cups printer
Message: 24 Date: Sat, 21 Jun 2003 12:59:57 +0100 From: Darrell Blake [EMAIL PROTECTED] Subject: [Samba] Setting up a cups printer To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii I'm trying to set up a cups printer but I don't know much about printing in linux and am a bit confused. Here is the document you are looking for: http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/ (PDF and HTML). I've installed a printer in cups using the web interface and it works fine. All the tutorials I've read though refer to /var/spool/lpd/lp You've read the wrong tutorials for your case ;-) but on my system this doesn't exist. I'm guessing this is because I'm not using lpd, I'm using cups. There are a few files in /var/spool/cups but they're c1 to c5. Can someone shed some light on my problem? My [printer] section on smb.conf currently looks like this... [printer] browseable = yes path = /var/spool/lpd/lp Don't use the same spool dir for Samba as you use for the printing daemon! (since CUPS uses /var/spool/cups/ yours is OK, but I'd suggest to use telling names) read only = yes printable = yes guest ok = yes Please help, Probably all that is missing is the load printers = yes (in the [global] section. Then your printer should at least be visible. Installing a driver for the Win clients then is the next step... (See link above). Darrell Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Fwd: [Foomatic] Foomatic PPD files and Windows clients
Hi, I am forwarding this from the foomatic-devel list to the Samba users and the Samba developers lists in the hope to broaden the potential of feedback on this crucial (for everyone who prints through *NIX) topic. Cheers, Kurt --- From: Till Kamppeter till.kamppeter at gmx.net Newsgroups: linuxprinting.foomatic.devel Organization: LinuxPrinting.org Cc: cups at easysw.com To: foomatic-devel at linuxprinting.org Subject: [Foomatic] Foomatic PPD files and Windows clients Date: Sat, 21 Jun 2003 19:42:55 +0200 Oi, all PPD files generated by Foomatic are Adobe-compliant. You can test this by running them through cupstestppd of CUPS 1.1.19 or newer. If you dont have cupstestppd on your box, run it on the CUPS web site: http://www.cups.org/testppd.php But Adobe-compliance does not mean that the PPDs work necessarily also on Windows clients. There are even issues with Adobes PostScript driver for Windows. Several postings from users (on the CUPS list, but also private mails to me) revealed the following problems: - *ShortNickname and *Nickname should not contain + and , - UI strings (translations) of option and choice names should not contain more than 40 characters I will fix that soon in the PPD-O-Matic PPD generator of the Foomatic system. I ask you to test and report if you have access to a Windows machine which could serve as a client. Please try the different PostScript drivers which are available for Windows (Microsoft, Adobe, CUPS) at first with the original PPDs from linuxprinting.org or from your distro. Which Windows drivers work? Now edit the PPD files according to one of the points mentioned above. Which drivers work now? If not all drivers work, make the PPD according to both points and test again. Are all the drivers working now? If not give us as much info as possible to fix a probably remaining issue. Especially tell us what you did when you made it working by further editing. If the CUPS driver for Windows causes problems with the PPDs as they are available now on linuxprinting.org, please report on http://www.cups.org/str.php as the CUPS driver should work with all PPDs which pass cupstestppd, Reporting bugs (and getting them fixed) in the Microsoft or Adobe drivers is not so easy. So please post your results here, so that the Foomatic PPDs can be made compatible by modifications in the PPD generator. I also suggest a modification in cupstestppd: One could add a command line switch with which the PPD is also checked for compatibility with Windows clients. The web interface could have an appropriate checkbox then. Till ___ Foomatic-devel mailing list [EMAIL PROTECTED] http://www.linuxprinting.org/cgi-bin/mailman/listinfo/foomatic-devel -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba3 and winxp printing problem...
cyroreal cyroreal at bol.com.br Fri Jun 20 12:06:36 GMT 2003 Hello all, I am using the samba3 package from debian unstable, on my debian box, and i am trying to let another machine (winXP) to access the printer o the samba box, but it is not working, i have no experience with samba3, but i have some experience with samba2, so what are the diferences about sharing a printer on these samba releases? Do i have to apply the registry patch on the winXP box with samba3 too? I am using cups on the samba box and the printer is printing fine on linux. Help please... Cyro Hi Cyro, please tell me if this document http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/ helps you to solve your problem. The differences in configuration are described in section 6.3.5. CUPS printing is described in very much detail, in all of chapter 7. Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] 'Little' problems with Samba v2.2.3a-12.3 (Debian Woody)and PRINTERS !!
Farget Vincent farget at olfac.univ-lyon1.fr Fri Jun 20 15:14:50 GMT 2003 Le Jeudi 19 Juin 2003 17:15, vous avez écrit : But you have not read the samba-howto-collection.pdf, which has a chapter on this, which tells you *exactly* not to do this. I have read the 6th chapter of theSamba-HOWTO-Collection paper and above all the 6.2.2th chapter named 'Setting Drivers for Existing Printers'. You should also refer to the new version for Samba 3.0, temporarily located here: http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/ It is also valid for most of Samba 2.2.x printing, but much more detailed and offers some troubleshooting tips also. Another point: Since the days of 2.2.3a there have been going a lot of printing code improvements into 2.2.4, 2.2.4a, 2.2.5, 2.2.6, 2.2.7, 2.2.8, 2.2.8a and 2.2.9. Think about updating! (And 3.0 is even better) Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] cupsaddsmb NT_STATUS_NO_SUCH_DEVICE
[Samba] cupsaddsmb NT_STATUS_NO_SUCH_DEVICE Shanti Katta katta at csee.wvu.edu Tue Jun 17 21:01:43 GMT 2003 Hello, I am using cups-1.1.19final-1.deb and samba-2.2.3a. When I was working with cups-1.1.15 before, cupsaddsmb worked fine, but now with cups-1.1.19 it gives me: Running command: smbclient //localhost/print\$ -N -U'root%secret?' -c 'mkdir WIN40;put /var/spool/cups/tmp/3eef829eea1b8 WIN40/ps948esb.PPD;put /usr/share/cups/drivers/ADFONTS.MFM [] putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL (10909.1 kb/s) (average 16587.7 kb/s) /usr/share/cups/drivers/PSMON.DLL does not exist Have you investigated this line? Running command: rpcclient localhost -N -U'root%secret?' -c 'adddriver [] result was NT_STATUS_NO_SUCH_DEVICE [] I checked the permissions on /var/spool/samba and other related directories, but couldn't resolve the error for 2 days now. Any help is highly appreciated. Shanti Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Slow windows - cups print - CONCLUSION
Miguel Manso mmanso at amplitudenet.pt Thu Jun 19 01:46:59 GMT 2003 Hi list, I've just figured it out. When we're installing the drivers from adobe there's a part where we must Select the Printer Model. By default it uses the Generic Postscript Printer (it has an associated PPD for that). We must get a PPD for our printer (installed on the linux server) from the www.linuxprinting.org, click the Browse button and select that PPD. After that you'll have a new printer installed an all will work like a charm. Note: Inside the PPD of my printer (HP OfficeJet 5110) I had these line (despite all the others :) ): *ShortNickName: HP OfficeJet 5110, hpijs *NickName: HP OfficeJet 5110, Foomatic + hpijs (recommended) On the instalation of the Adobe drivers I had erros saying my printed had illegal chars on it's name. The illegal chars were the commas. It indicates that your Linuxprinting.org retrieved PPDs were not the current version. Current versions don't have this issue any more. So, I've replaced the previous lines with: *ShortNickName: HP OfficeJet 5110 *NickName: HP OfficeJet 5110 Hope this helps anyone. Bye, -- Miguel Manso mmanso at amplitudenet.pt Cheers, Kurt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
