From: "Buchan Milne" <[EMAIL PROTECTED]> > I think Sylvestre is still away on business for the rest of this week, > so I will field this one for the moment.
Thanks ... > 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. Off topic, but: I'd been using the verison from cooker on our PDC which is/was an 8.0 install. Why bother rebuilding the src RPM? Anyway, the testing I'm describing here is with a clean 8.2 beta 3, as I mentioned before. It is on a machine that is configured as a member of the domain, sharing drivers for the same network printer as the PDC. > 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. This sounds more like my situation, except I have no problems with 2.2.2 :/ The Windows drivers don't normally offer all the features (ie booklet printing), although I've not looked at them for this particular printer. > 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? On the samba list I described problems on a Mandrake 8.0 PDC server with the samba-2.2.3a-[356]mdk (from cooker) vs samba-2.2.2-3.2mdk (from updates/8.1/RPMS), both with exactly the same drivers (from the HP CDrom, I think). Then I replicated the 2.2.3a behaviour with a clean install of MD8.2b3, 2.2.3a-6mdk Samba RPM, and the latest drivers from the HP web site. (The new test PC is a member of the domain, not the PDC). The printer is an HP2200dn plugged straight in to our LAN. > 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. My troubles with 2.2.2 have been less visible that this printing problem :( > > 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) Well, first I tried pointing Windows at the downloaded drivers, and the drivers loaded on to the Samba server didn't work. When I supplied an MSDN Win2K install DVD, they did work. I wasn't concentrating very hard at that point, so feel free to be sceptical :) Thanks for the %windir%\inf tip - that will be useful in the future. > 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? It generated 5Mb of *compressed* logs, so it was doing something! If I get the chance, I'll check with top. I'll send the samba and client configs seperately ... Thanks for your time, Steven
