Hello, I've been having trouble with printing from Windows clients when printer drivers are supplied by a Samba server. From traffic on the samba mailling lists, I think this is a problem with the current Samba release.
I've taken a clean machine, installed Mandrake 8.2 beta 3, updated Samba to the 2.2.3a-6mdk rpm (plus required drakx tools for configuring printing), configured printing, installed Windows drivers on the server, and am unable to print from Word97 on NT4 clients (printing test pages, or from other apps works, but sometimes slower than it should be). I've sent a set of smb logs to Gerald Carter on the Samba team, but I've not heard anything back yet. I've seen a few more complaints about the printing RPCs on the samba mailing lists too, and IMHO, 2.2.2 would be the best version to ship with MD8.2 right now ... (I have 30 Windows clients and 1 Samba PDC here) Good luck with the release, Steven === Here is part of a message a sent to the Samba developers detailing a repro scenario: The Samba server is a clean install of Linux Mandrake 8.2 beta3, plus updated Samba rpms. The drivers for the printer are the latest from www.hp.co.uk - a 6.2Mb lj985en.exe which is a set that contains drivers for all MS OSes since 95. I installed them while logged in to a Win2000 workstation as user sjm. (A pain in the ass - I had to find a Windows 2000 server CD to complete the install ... ?!?) The sequence of events that I logged is Start Samba Open Word97 on the client PC Open a document Open the print ... dialogue box Chose the shared printer (\\prawn\Laser in this case) Word locks at this point Wait for 120 seconds Stop samba (Word becomes responsive again a few seconds later) Send Jerry the very big logs Drivers are in [root@prawn 2]# pwd /var/lib/samba/printers With permissions [root@prawn printers]# ls -l total 20 drwxrwxr-x 2 root adm 4096 Feb 27 12:56 W32ALPHA/ drwxrwxr-x 2 root adm 4096 Feb 27 12:56 W32MIPS/ drwxrwxr-x 2 root adm 4096 Feb 27 12:56 W32PPC/ drwxrwxr-x 4 root adm 4096 Mar 4 16:51 W32X86/ drwxrwxr-x 3 root adm 4096 Mar 4 10:50 WIN40/ [root@prawn printers]# cd W32X86/ [root@prawn W32X86]# ls -l total 8 drwxr-xr-x 2 sjm sjm 4096 Mar 4 10:51 2/ drwxr-xr-x 2 sjm sjm 4096 Mar 4 10:15 3/ [root@prawn W32X86]# cd 2 [root@prawn 2]# ls -l total 3652 -rwxr-xr-x 1 sjm sjm 45056 Sep 16 12:52 HPBAFD32.DLL* -rwxr-xr-x 1 sjm sjm 1829648 Sep 16 12:52 HPBF3220.DLL* -rwxr-xr-x 1 sjm sjm 47439 Sep 16 12:52 HPBF3220.HLP* -rwxr-xr-x 1 sjm sjm 1412368 Sep 16 12:52 HPBF3222.DLL* -rwxr-xr-x 1 sjm sjm 71889 Sep 16 12:52 HPBF3224.PMD* -rwxr-xr-x 1 sjm sjm 99840 Sep 16 12:52 HPBFTM32.DLL* -rwxr-xr-x 1 sjm sjm 94274 Sep 16 12:52 HPBHEALR.DLL* -rwxr-xr-x 1 sjm sjm 40960 Sep 16 12:52 HPBMMON.DLL* -rwxr-xr-x 1 sjm sjm 58368 Sep 16 12:52 HPDOMON.DLL* Another issue: I can "Add" the printer to a client machine if I am logged on to the domain as sjm, but not when logged in as testuser. The client machine reports that there incorrect drivers on the server, even though they are world readable. Another issue: using 'rpcclient prawn -Usjm', 'enumprinters' will show me printer information, but 'enumdrivers' does not show me anything. Any ideas?
