Hello! Where is info about printer drivers stored? I mean that driver is installed for this printer? I played with 2.2.0 configuration- remake srpm with different options and after rpm installation I needed to install printers again and again- files are in place, but NT4 said that NO DRIVER :( btw, sometimes I get error that alternate driver can't be installed when installed drivers for win9x from nt4, another try is always succesfull. Is this only my problem? :) -- Wire connection and Windows reinstallation senior engineer Dmitry Melekhov http://www.belkam.com/~dm 2:5050/11.23@fidonet
In order for Windows clients to automagically download printer drivers for network printers, I have to put the drivers in a share called print$. What files exactly should I put here - should it be an .inf file and related files for each printer? Should each different printer's driver be in a seperate subdirectory? What about for different client OSes? The printers are an HP DeskJet 720C, and HP DeskJet 850C, a Brother HL-1250 laser, and a Panasonic KXP-1124 dot matrix. Client machines are running Windows 2000 Pro, Windows XP Pro, Windows 98, and Windows NT4 Workstation. TIA for any help, Alex. -------------- Mr Alex Meaden Computer Science Undergraduate University of Kent at Canterbury http://meaden.dyndns.org
What happens when you run testparm? Do you see any error messages?> -----Original Message----- > From: mark [mailto:mark@mebrosius.com] > Sent: Monday, June 10, 2002 4:09 PM > To: Alex Meaden > Cc: samba@lists.samba.org > Subject: Re: [Samba] printer drivers > > > When I open the printer folder I see the printer there. It is not > shaded (indicating that the printer is offline). I can > actually see it > in Network Neighborhood. If I use the the 720c drivers > provided by HP, > I get an error message stating: > There was an error writing to \\server\printer for the > printer (driver): > Your file waiting to be printed was deleted > > I am trying the basic HP Deskjet driver now just to see what > happens. > > Mark > > Alex Meaden wrote: > > >----- Original Message ----- > >From: "mark" <mark@mebrosius.com> > >To: "Alex Meaden" <alex@meaden.net>; <samba@lists.samba.org> > >Sent: Tuesday, June 11, 2002 12:02 AM > >Subject: Re: [Samba] printer drivers > > > > > > > > > >>Alex, > >>Thank for your help but I still can't print. Here is my > smb.conf file. > >> My file sharing works but not my printer. Can you see > what I'm doing > >>wrong? > >> > >> > > > >I'm not that you should have a "[Printer]" share in your > smb.conf. If you > >open \\mark from a Windows PC, and then double-click the > Printers folder, > >what if anything is listed? > > > >Alex. > > > > > > > >>[global] > >> workgroup = K9PC > >> netbios name = MARK > >> server string = Samba Server %v > >> encrypt passwords = Yes > >> log file = /var/log/samba/log.%m > >> max log size = 50 > >> socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 > >> printcap name = lpstatShould this be /etc/printcap or /usr/local/etc/printcap? I'm not sure which one cups uses :-(> >> dns proxy = No > >> wins support = Yes > >> hosts allow = 127.0.0. 192.168.1. > >> printing = cups > >> > >>[homes] > >> comment = Home Directories > >> read only = No > >> browseable = No > >> > >>[printers] > >> comment = All Printers > >> path = /var/spool/samba > >> create mask = 0700 > >> guest ok = Yes > >> printable = Yes > >> print command = lpr-cups -P %p -o raw %s -r # using client > >>side printer drivers. > >> lpq command = lpstat -o %p > >> lprm command = cancel %p-%j > >> browseable = NoI think the samba spool dir needs to be 777 or 1777 try #'ing this entry to see if it changes anything. then: chown root.daemon /var/spool/samba chmod 777 /var/spool/samba Come to think of it, if you have an entry for the printer, you don't need the [printers] entry. Rename the [printers] section to [Printer], and delete the other [Printer] entry. Modify it to read: [Printer] comment = HP720C path = /var/spool/samba guest ok = Yes printable = Yes print command = lpr-cups -P %p -o raw %s -r # using client side printer drivers. lpq command = lpstat -o %p lprm command = cancel %p-%j browseable = No What I think is happening is that you can see the Printer share, but samba and cups aren't talking correctly. Samba spools the job, and sends it to cups. Each print process must be working in order for the job to be processed. Look at your printcap entry for the printer, and make sure it matches what you have in the smb.conf [Printer] and [Global] sections. You may consider creating the printcap entry as hp720 or something similar; chances are you're going to end up servicing more than one printer via your server. Create /var/spool/samba/hp720 and make the [Printer] section [HP720C]. Modify the path=/var/spool/samba/hp720 as well. As you add more printers, you'll be able to give them names that match their model. Printer, Printer2, etc. will add confusion instead of clarity... If the HP720C driver won't work, try the HP550C driver. It's what I have to use for our networked OfficeJet 570, and HP mentions it as a solution for other networked DeskJets. Hope this helps, Jim
I think I've lost the big picture...time to step back and look at what you're trying (and unable) to do. 1. Is \\server\Printer being added to the clients as a Network or Local Printer? 2. If Network, are you trying to install the printer drivers from the server? 3. Are you a member of the Linux admins group? 4. Did you delete the default printer apps on the Linux box, and create symlinks to the cups equivalents? (e.g. lpr, lprm, lpd, lpq) (This has bitten me on OpenBSD upgrades; the upgrade overwrites the symlinks with executables, and I have to go back and redo the LPRng symlinks) 5. Re-read the doc's and HOW-TOs for printing setup-a lot has changed in 2.2.x...maybe something will pop up that you missed. 6. If you're not interested in the spoolss support, or it gives you more pain than pleasure (my case!!!) use "disable spoolss=yes" and "use printer driver=no" in smb.conf's [Global], remove all connections to \\server\Printer in your workstations' Printers and the Registry. Then re-install \\server\Printer as a Network Printer, and the Port it attaches to should show up listed in the Properties as a LAN Manager Printer Port. This is the pre-spoolss type of printer connection, and I think the easier to set up/manage. 7. Linux prints via cups, and you can see the share- you're almost there... Good luck! Jim
> -----Original Message----- > From: Mark Brosius [mailto:mark@mebrosius.com] > Sent: Tuesday, June 11, 2002 9:13 AM > To: Van Sickler, Jim > Cc: samba@lists.samba.org > Subject: RE: RE: [Samba] printer drivers > > > Thanks for responding. > On Tue, 11 Jun 2002, Van Sickler, Jim wrote: > > > I think I've lost the big picture...time to > > step back and look at what you're trying > > (and unable) to do. > > > > 1. Is \\server\Printer being added to > > the clients as a Network or Local Printer? > > Network >Okay> > 2. If Network, are you trying to install > > the printer drivers from the server > > I am installing the drivers from the client >If disable spoolss=yes, or pre-2.2.1a(I think) this is your only choice. I found it works best...for my setup, at least. Others may feel free to offer different advice. No two setups are the same.> > 3. Are you a member of the Linux admins > > group? > > Good question. I don't think so.If you're not sure, you probably aren't. This is an issue with spoolss support enabled.> > > 4. Did you delete the default printer > > apps on the Linux box, and create symlinks > > to the cups equivalents? (e.g. lpr, lprm, lpd, lpq) > > (This has bitten me on OpenBSD upgrades; the > > upgrade overwrites the symlinks with executables, > > and I have to go back and redo the LPRng symlinks) > > I did not delete the printer apps on the Linux boxEnabling cups in smb.conf has no effect if cups isn't installed on the server. You may want to return to the default settings for printing, and see if that changes anything. Remarking out the printer entries (with # at the start of the line) will allow the defaults to be used.> > > 5. Re-read the doc's and HOW-TOs for printing > > setup-a lot has changed in 2.2.x...maybe something > > will pop up that you missed. > > Okay. Dumb question, where are they. I can't seem to find them. >If you've got SWAT running, you can get to some of the documentation through the home page; more doc's are available through the samba.org documentation link - e.g. http://us4.samba.org/samba/docs/> > 6. If you're not interested in the spoolss support, > > or it gives you more pain than pleasure (my case!!!) > > use "disable spoolss=yes" and "use printer driver=no" > > in smb.conf's [Global], remove all connections to > > \\server\Printer in your workstations' Printers and > > the Registry. Then re-install \\server\Printer as > > a Network Printer, and the Port it attaches to should > > show up listed in the Properties as a LAN Manager > > Printer Port. This is the pre-spoolss type of printer > > connection, and I think the easier to set up/manage. > > I haven't even considered spoolss.If you installed 2.2.3a, I think it was enabled by default. I'm not sure about 2.2.1a, but I'd put disable spoolss=yes just in case. If testparm complains about an invalid entry, delete it.> > > 7. Linux prints via cups, and you can see the share- > > you're almost there... > > To be honest, I'm not sure how I am printing from linux. > Maybe it is cups...maybe not. Sorry. I am able to see > the share from the windows client though.A visible share is just that, unfortunately. If the printing subsystem is defective, it won't change anything. But you already knew that ;-)> > > Good luck! > > Thanks, I think I need it. I appreciate your help! >You're welcome-I've gotten a lot of help from the list in the past. Eventually you'll get the answers you need, either from the list or your own efforts. Jim