I think Sylvestre is still away on business for the rest of this week, so I will field this one for the moment.
Steven Mackenzie wrote: > 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. Note that we have applied some patches (from samba_2_2 cvs that were supposed to fix the samba race on printer queries). > 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). > Unfortunately, I don't have enough machines available (at work) to be able to test your exact setup, but I have recompiled 2.2.3a-6mdk for Mandrake 8.1 (using rpm --rebuild --with mdk81 on the srpm), and tested it on our (non pdc) production print server. It has been running for a week with no problems. I tested installing drivers on our production PDC (which is running 2.2.3a-1mdk on Mandrake 8.0) with no problems. I have done test prints with Office 2000 sp1 running on Windows 2000sp2 to an HP2100 using the Microsoft drivers. Please note that we had problems with our DJ970 (crashing of MS Word 97 in printer setup) when we were using the NT4 HP supplied drivers with Windows 2000 on samba-2.2.2. This stopped after we used the drivers supplied with Windows. I believe from your mails on the samba list that you were using the same drivers with samba-2.2.2 and samba-2.2.3a? Is this correct? > 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) Unfortunately 2.2.2 is itself not without problems. There is a locking race (gave us a number of problems here), and issues with winbind (memory leak, domain controller hits) that we would prefer to avoid. The samba team has promised a good 2.2.4 soon, but it is already too late I fear .... > > Good luck with the release, > Steven > > === > > Here is part of a message a sent to the Samba developers detailing a repro > scenario: > Off list (but cc'ed to [EMAIL PROTECTED]), could you please send me your /etc/samba/smb.conf, please list the version of the client yuo are running, plus any service packs etc. > 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 ... ?!?) This is incorrect, Windows 2000 believes you need the CD, but only to convince you you need Windows 2000 Server. You should point it at the drivers, or if you have installed the printer driver locally, or if they came with Windows 2000, you can point it at %windir%\inf (ie C:\WINNT\Inf) > > 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 If you have the option to look at this again, could you just run top on the samba box at this stage, and see if your smb is racing? > 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. It worked for me now, but I have domain admin rights ... I will have to test later, but I haven't heard any complaints from our users .... > > Another issue: > using 'rpcclient prawn -Usjm', 'enumprinters' will show me printer > information, but 'enumdrivers' does not show me anything. > OK, this I can verify, it was working in 2.2.2, not in 2.2.3a. I will see if I can do a full test (setting up printer from scratch) of this at home tonight (don't have time to test it here) with 8.2beta4. > Any ideas? > > None yet ... I will go and test some of this at home ... -- |----------------Registered Linux User #182071-----------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 8828820x202 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/gpg.key
