I am using SAMBA/Lprng to do printer accounting for charge-back. There are two technical issues I have not been able to resolve. 1. When attempting to connect to the printer from a Windows box in the domain (the SAMBA server is simply a server that's a member of the domain, it is not the PDC) I get the message that the server does not have the appropriate driver and then it pops up a setup wizard. Since some several hundred machines may end up using any one of 10 different printers, what do I need to do in SAMBA to prevent this? 2. Even though I can print to the SAMBA shared printer without any problem, the box that gives printer status claims that it cannot connect to the printer. What setting in SAMBA will take care of that? Thanks, Rob Rob Tanner UNIX Services Manager Linfield College, McMinnville OR
Hello, I am running Samba 2.2.8a on RH Linux 8.0. I currently have over 1000 machines that I wish to add to /etc/passwd using the following line: add user script = /usr/sbin/useradd -d /dev/null -g 527 -c Machine -s /bin/false -M %u This works fine when adding a machine into domain (from WindowsXP) and using root / rootpwd . I would like to setup other users to be able to add machines into the domain from the desktop but have been unable to do so. I have tried the following admin users = root coreyh This did not have any affect. I then tried Domain Admin Group = @tempadmin and in /etc/group place my user names in tempadmin group. Does anyone have any ideas? Am I overlooking something very easy? -- ---- Corey Hart Systems/Security Analyst St. Edward's University coreyh@admin.stedwards.edu 512/428-1038 - voice 512/448-8492 - fax 512/470-8462 - cell
Try adding : use client driver = yes to your printer share. Joel On Wed, Jul 23, 2003 at 11:24:17AM -0700, Rob Tanner wrote:> 2. Even though I can print to the SAMBA shared printer without any > problem, the box that gives printer status claims that it cannot connect > to the printer. What setting in SAMBA will take care of that?
Don't you have to set up your clients to talk to each of the ten printers? Joel On Wed, Jul 23, 2003 at 11:24:17AM -0700, Rob Tanner wrote:> I am using SAMBA/Lprng to do printer accounting for charge-back. There > are two technical issues I have not been able to resolve. > > 1. When attempting to connect to the printer from a Windows box in the > domain (the SAMBA server is simply a server that's a member of the domain, > it is not the PDC) I get the message that the server does not have the > appropriate driver and then it pops up a setup wizard. Since some several > hundred machines may end up using any one of 10 different printers, what > do I need to do in SAMBA to prevent this? >
Rob Tanner wrote on Thursday, 24 July 2003 6:24 a.m.:> 1. When attempting to connect to the printer from a Windows box in > the domain (the SAMBA server is simply a server that's a member of > the domain, it is not the PDC) I get the message that the server does > not have the appropriate driver and then it pops up a setup wizard. > Since some several hundred machines may end up using any one of 10 > different printers, what do I need to do in SAMBA to prevent this?You can upload drivers to the server using the Add Printer wizard, so that clients will be able to download them. See the Samba HOWTO collection chapter 18 (search the document for "printer drivers"): http://samba.org/~jht/NT4migration/Samba-HOWTO-Collection.pdf Cheers, Paul
> > Any suggestions as how to give the Windows XP permissions to > see and delete their own jobs?This may depend on which printing system you have on the linux box. A lot of people seem to be using cups, about which I know nothing. I use lprng. There is a file called lpd.perms, which hangs out in /etc on my system. This is the most convoluted, unix like configuration file I have ever seen. But, it is flexible. See man lpd.perms for info about it. If you don't like the man pager, then: man -t lpd.perms > junk.ps ps2pdf junk.ps junk.pdf acroread junk.pdf To make everything work as expected, without any particular security or usage limitation, I just put: DEFAULT ACCEPT as the first and only line in my lpd.perms file. Joel