Cellen
Luke Warm

Joined: 14 Oct 2003 Posts: 234
|
Posted: 02/12/05 - 17:26 Post subject: Problem with Samba/CUPS network printer...
|
|
|
I setup CUPS and I already had Samba running on my linux box in my house. My printer is a Brother HL-1440, and the recommended driver is the hl1250. The printer itself seems to be set up fine, I can print test pages from the CUPS web interface until the cows come home. My problem appears to be configuring Samba so that users can just follow the "Add Printer" wizard and have it do its magic. I managed to get it working on my Win2k machine, but another user's machine gives some memory address error (I don't have the exact error handy) after installing the printer and trying to right-click and view properties on the installed printer. If I try to print from the other users' PCs, the application that's trying to print will crash.
My smb.conf [printers] section looks like this:
| Code: | [printers]
comment = All Printers
path = /var/spool/samba
#path = /var/spool/cups
browseable = yes
guest ok = yes
printable = yes
read only = no
writable = yes
|
I tried a bunch of stuff and eventually got it working on one other user's PC, but a third user still can't print and gets the errors. I was getting some Windows error like "The server on which the printer resides does not have the correct driver" (like the dude here) for a while, and nothing I tried could fix that, and I ended up just creating another share on the linux box that had the windows drivers in it, and that's how I got the driver onto the one user whose PC can now print to it. But that doesn't work for the third user.
A related problem was the way you "install" the windows driver onto samba so that users can install it. One guy explained the process - in Windows you right-click in the white space of the "Printers on (Servername)" window and select Server Properties, then under the Drivers tab click "Add..." (this requires that your samba user be listed as a print admin in smb.conf). The problem is that I can't add a driver here, it keeps asking me for a f*****g Windows NT4 CD when I try to add the NT4/2000 version of my driver. Anybody know how to get around that? It seems to be looking for a \NT4\I386 folder.
|
|