Nope, close but no cigar. With 2.2.6Pre2 Word started to behave itself but Outlook acts as though landscape is a foreign concept(i.e everything prints portrait regardless of page setup). Spoolsv also crashes on the Win2K workstations requiring a manual restart of the spooler service. We will downgrade to 2.2.5 and try Jerry's patch. In another message Jerry talks about "running" the driver on the server to set DevMode, etc. I assume we've been doing what's needed although I haven't seen anything laid out in a step-by-step fashion, so to confirm: 1. Define your printer as a share or in CUPS as needed. 2. Define PRINT$ share with only admin users having write access. 3. Restart Samba and make sure printer appears in the server Printers folder 4. Right-click on the printer in question and choose Properties. 5. Respond "NO" to the "Install Driver now prompt" - Question: Why respond "No" at this point? All docs say to do so without explanation. 6. Once in the driver dialog go to the Advanced Tab and click on "New Driver" 7. Select your driver from wherever and make sure it copies to \\Server\PRINT$\W32X86\... 8. Click on Apply to make sure dialog gets updated with printer-specific configuration tabs. 9. On General tab, choose Printing Preferences - Basics and switch page layouts between portrait and landscape clicking OK in between to update the driver. - I assume at this point the driver Devmode is being set, correct? 10. The printer is now ready to install on Workstations. General Questions: 1. If the printer was already installed on a workstation and the driver is re-installed should the user re-install the printer? 2. What could cause the spooler to crash so often when updating drivers? 3. When a driver is changed or updated on the server I see many (sometimes up to 15) print events in the workstation system event log noting drivers being updated but listing the same drivers each time. Normal? 4. The ability to delete drivers, forms, etc from Server Properties in a server's Printers folder is disabled on a Samba server. Is this an interface that hasn't been implemented yet? 5. Many problems seem to occur when the server has multiple versions of different printer model drivers installed. Should this make any difference? 6. Related to #4, Cleaning out the Samba-side printer driver environment seems to be an all-or-nothing proposition. I.e. You have to stop Samba, delete nt*.tdb and everything under W32X86. Is there a better way? This weekend we will be moving servers around and will set the printing environment based upon whether I can get these problems resolved. If not I'll have to either install all printers as local using rundll32 or have printing handled by a Win2K server. Thanks. Greg -----Original Message----- From: Andrew Bartlett [mailto:abartlet@samba.org] Sent: Monday, October 07, 2002 4:03 AM To: SMITH Gregory C. Cc: 'samba@lists.samba.org' Subject: Re: [Samba] Win2K Printer Driver Problems - Landscape margins off, no collating. "SMITH Gregory C." wrote:> > Our environment: > > Samba 2.2.5 on RedHat 7.2 (Tried on two different servers) > Printing handled by Cups 1.1.14-15For printing, try jerry's post-2.2.5 printing patch, or Samba 2.2.6pre2. This is exactly the kind of issue that he and the rest of the HP folk have been working on. If not, I'm sure he will be very glad to figure out what's going on :-). Andrew Bartlett -- Andrew Bartlett abartlet@pcug.org.au Manager, Authentication Subsystems, Samba Team abartlet@samba.org Student Network Administrator, Hawker College abartlet@hawkerc.net http://samba.org http://build.samba.org http://hawkerc.net
daniel.jarboe@custserv.com
2002-Oct-08 17:13 UTC
[Samba] Win2K Printer Driver Problems - Hi Jerry!!
gsmith@ahbl.ca wrote:>We will downgrade to 2.2.5 and try >Jerry's patch. >"downgrade" to 2.2.5 from 2.2.5? If you are actually at 2.2.6pre2, the printing patches are already in and downgrading to 2.2.5 w/ jerry's printing patch isn't going to help (might hurt)>5. Respond "NO" to the "Install Driver now prompt" - Question: Why respond >"No" at this point? All docs say to do so without explanation. >If you click yes you'll be installing the drivers locally on the PC, you want them installed on the samba server by uploading a new driver.>9. On General tab, choose Printing Preferences - Basics and switch page >layouts between portrait and landscape clicking OK in between to update the >driver. - I assume at this point the driver Devmode is being set, correct? >Correct, this executes the driver so you don't have a null devmode> >2. What could cause the spooler to crash so often when updating drivers? >Not much help here, but probably at least 1 of the following: buggy print drivers, buggy client, buggy samba As for the rest of your questions, I'm just as anxious to hear the list's answers as you are :) ~ Daniel
We are on 2.2.6Pre2 and if the patches are in you've just saved us some time. Does smbstatus say 2.2.6Pre2? Ours displays only 2.2.5. However, as mentioned in another message we've found the problems occur if we have a combination of HP4 and HP4000 drivers on the server. Greg -----Original Message----- From: daniel.jarboe@custserv.com [mailto:daniel.jarboe@custserv.com] Sent: Tuesday, October 08, 2002 10:12 AM To: gsmith@ahbl.ca Cc: 'samba@lists.samba.org'; WEBSTER, Greg Subject: Re: [Samba] Win2K Printer Driver Problems - Hi Jerry!! gsmith@ahbl.ca wrote:>We will downgrade to 2.2.5 and try >Jerry's patch. >"downgrade" to 2.2.5 from 2.2.5? If you are actually at 2.2.6pre2, the printing patches are already in and downgrading to 2.2.5 w/ jerry's printing patch isn't going to help (might hurt)>5. Respond "NO" to the "Install Driver now prompt" - Question: Whyrespond>"No" at this point? All docs say to do so without explanation. >If you click yes you'll be installing the drivers locally on the PC, you want them installed on the samba server by uploading a new driver.>9. On General tab, choose Printing Preferences - Basics and switch page >layouts between portrait and landscape clicking OK in between to update the >driver. - I assume at this point the driver Devmode is being set, correct? >Correct, this executes the driver so you don't have a null devmode> >2. What could cause the spooler to crash so often when updating drivers? >Not much help here, but probably at least 1 of the following: buggy print drivers, buggy client, buggy samba As for the rest of your questions, I'm just as anxious to hear the list's answers as you are :) ~ Daniel
Gerald (Jerry) Carter
2002-Oct-10 20:49 UTC
[Samba] Win2K Printer Driver Problems - Hi Jerry!!
On Tue, 8 Oct 2002, SMITH Gregory C. wrote:> General Questions: > 1. If the printer was already installed on a workstation and the driver is > re-installed should the user re-install the printer?The client spooler will grab new files as needed from the server.> 2. What could cause the spooler to crash so often when updating drivers?Bad printer drivers, null devmodes, etc...> 3. When a driver is changed or updated on the server I see many > (sometimes up to 15) print events in the workstation system event log > noting drivers being updated but listing the same drivers each time. > Normal?My personal belief is that this is related to our lack of creation timestamps for files.> 4. The ability to delete drivers, forms, etc from Server Properties in a > server's Printers folder is disabled on a Samba server. Is this an > interface that hasn't been implemented yet?It works. Modifying forms as well. Fixed in 2.2.6rc2. You have to be connected as root or a printer admin though.> 5. Many problems seem to occur when the server has multiple versions of > different printer model drivers installed. Should this make any > difference?No. Should be fine. Samba handles 9x/NT/2k/XP drivers all alongside each other.> 6. Related to #4, Cleaning out the Samba-side printer driver environment > seems to be an all-or-nothing proposition. I.e. You have to stop Samba, > delete nt*.tdb and everything under W32X86. Is there a better way?See my comments on #4. Also note that 3.0alpha20 has the DeletePrinterDriverEx() RPC implemente which allows you to remove driver files as well as driver information programatically. cheers, jerry
OK, OK, got it now. Printer Admin is defined in the docs as a Share parameter, but to be able to modify server settings it needs to be in the Global section. I'm still getting 20+ print messages in the workstation's System Event log whenever a change to the server-based driver is made. Is this normal? Thanks much Jerry! Looks like our two-month nightmare is over. Greg -----Original Message----- From: Gerald (Jerry) Carter [mailto:jerry@samba.org] Sent: Thursday, October 10, 2002 1:39 PM To: daniel.jarboe@custserv.com Cc: gsmith@ahbl.ca; 'samba@lists.samba.org'; WEBSTER, Greg Subject: Re: [Samba] Win2K Printer Driver Problems - Hi Jerry!! On Tue, 8 Oct 2002 daniel.jarboe@custserv.com wrote:> "downgrade" to 2.2.5 from 2.2.5? If you are actually at 2.2.6pre2, the > printing patches are already in and downgrading to 2.2.5 w/ jerry's > printing patch isn't going to help (might hurt)Please test with 2.2.6rc2. Thanks.> >9. On General tab, choose Printing Preferences - Basics and switch page > >layouts between portrait and landscape clicking OK in between to updatethe> >driver. - I assume at this point the driver Devmode is being set,correct?> > > > Correct, this executes the driver so you don't have a null devmodeI think I've already mentioned this in anotehr post, but you need to do this on the "Advanced" tab to set the device mode on the server. The "General" tab sets the per user devmode on the client. You may need to install the driver on the server and click ok on the properties page, and then reopen before the "Printing Preferences" button shows up on the advanced tab. cheers, jerry --------------------------------------------------------------------- Hewlett-Packard http://www.hp.com SAMBA Team http://www.samba.org -- http://www.plainjoe.org "SAMS Teach Yourself Samba in 24 Hours" 2ed. ISBN 0-672-32269-2 --"I never saved anything for the swim back." Ethan Hawk in Gattaca--