![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
So, I bought one of these off ebay for about £180 incl next-day delivery. I'm currently working on getting it going with linux.
It's on its own bit of ethernet, hanging off eth3 (currently setup as it came). I used
TODO:
renumber the ethernet address of the printer
sort the permissions issue with smb (any ideas?)
review cupsd.conf to make sure access etc is sensible.
[1]
It's on its own bit of ethernet, hanging off eth3 (currently setup as it came). I used
lpadmin and foomatic-configure to get the system to know about it, and then the CUPS web interface to set some sensible defaults (use the large paper tray, use duplex). I frobbed samba (as per the cupsaddsmb man-page) to export the printer. This currently means making /var/spool/samba writable by anyone, as otherwise smbd complains it can't write to the directory to create a spool file[1].TODO:
renumber the ethernet address of the printer
sort the permissions issue with smb (any ideas?)
review cupsd.conf to make sure access etc is sensible.
[1]
[2007/11/14 22:14:52, 1] smbd/service.c:make_connection_snum(642)
jpl-111 (172.16.22.237) connect to service lj2300dtn initially as user sac48 (
uid=1053, gid=1053) (pid 27773)
[2007/11/14 22:15:30, 0] printing/printing.c:print_job_start(2297)
print_job_start: insufficient permissions to open spool file /var/spool/samba/
smbprn.00000008.C6UOEZ.
[2007/11/14 22:15:30, 0] printing/printing.c:print_job_start(2297)
print_job_start: insufficient permissions to open spool file /var/spool/samba/
smbprn.00000009.9R2Oen.
[2007/11/14 22:15:30, 1] smbd/service.c:close_cnum(835)
jpl-111 (172.16.22.237) closed connection to service lj2300dtn
(no subject)
(no subject)
(no subject)
(no subject)
http://machine:631/printers/printername
in the 3rd box in the "add new printer" wizard's first dialogue)
(no subject)
(no subject)
Niggles are:
a) no authentication / user accounting
b) you can't do the magic "here's your printer driver" thing you can do with samba (as far as I'm aware)
c) there's a failure mode where windows and cups refuse to talk to each other, either at the last stage of installing the printer, or on the first attempt to print to it, and then attempts to print cause Explorer to hang. This happens to a random subset of our Windows XP boxes with no readily apparent common cause and has been driving me mad. A colleague has suggested that the problem lies in Windows trying to use http proxies for IPP stuff, but I'm not completely convinced from my observations. But if this is going to break for you, it'll be obvious when you first test the printer (and at that point, I think I'd recommend not pursuing this line of investigation, as doing so has given me nasty headaches ...)
So summary: worth a try, if it works it'll do so immediately; if it doesn't work first time, run away.