What is Digg?11 Comments
- crdlb, on 10/12/2007, -0/+4This guide is OK, but I got much better results by downloading the adobe postscript driver from here:
http://www.adobe.com/support/downloads/product.jsp?product=44&platform=Windows
On Windows XP and 2000, you are still using the builtin windows postscript driver, but adobe's installer seems to set it up more reliably.
When you run the installer and select network printer, it will ask for a ppd file. You can simply copy the file from your linux server at /etc/cups/ppd/. Cups will even fetch it for you remotely if you type http://serverhostname:631/printers/printername.ppd
Also a guide I read recommended defining the server's hostname in the windows version of the /etc/hosts file (IIRC it is somewhere in the system32 directory). Windows apparently has issues printing directly to an IP address (as odd as that sounds)
Ever since setting it up this way for my aunt, it has been working perfectly. - geronimo, on 10/12/2007, -1/+4I had a tough time getting windows configured with my linux print server. I got it half-way working with samba but half the time there were odd permission problems. So I read this howto and learned about IPP printing, just tried that and it printed a test page. I don't know what people mean when they say IPP printing is buggy, but I'm betting it's a driver problem. With my HP laserjet, IPP is working just fine.
- BlackAdderIII, on 10/12/2007, -0/+2CUPS a pain in the ass? Nah. Set it up, watch it go, works forever and a day.
Users will still break their windows clients' ability to print by pouring coffee in their computers and stuff, but CUPS is pretty solid stuff.
Your other comments about it are... weird. Projects do not need paradigm shifts every 3 months to be considered usable. You're thinking of MSN messenger or something. - uzytkownik, on 10/12/2007, -0/+1I don't know which distro they use (probably some user friendly), but it's 2 times more difficult then on my Gentoo system (which is definitely not UF distro): http://www.gentoo.org/doc/en/printing-howto.xml
If you remove gentoo-specific things it should be:
a) Installing samba, cups, foomatic
b) Configure cups (via web page wizard where you put where printer is connected (ipp, net, usb...) driver (choose by prudent and model)) and samba (a little bit more difficult, but with Windows ipp support).
c) Install Windows driver.
- cups-windows: Fast good but some specific pictures it prints wrong (I haven't scanner and I can't send a bug)
- standard (from proficient): Fast but prints wrong everything ;)
- adobe: Extremely slow and print everything since now (It was printed nearly nothing) - kickarse, on 10/12/2007, -1/+2Yeah windows support sucks horribly. We tried using it in a OS X enviro with a couple of pc's shared to it... yikes!
- drag, on 10/12/2007, -2/+2Carefull.
Windows support for IPP is *****. Be sure to test all this out before trying to use it in a workplace or whatnot. Your probably best off using Samba since your probably going to use that for file sharing to your windows clients anyways.
But otherwise IPP is great. Just use it if you only have Linux and OS X clients... - satipip, on 10/12/2007, -1/+1Microsoft implemented for Windows only IPP version 1.0.
IPP protocol version 1.0 never became an IETF standard, it always remained a "draft". IPP 1.0 does not provide for authentication.
Only IPP 1.1 made it into an IETF standard.
Microsoft bolted their own authentication schemes on top of their IPP implementation (NLTM et al.), and they use port 80, not 631. - mjh2901, on 10/12/2007, -2/+1clarkconnect.com
Great CUPS print server without any real work - never102, on 10/12/2007, -6/+1I actually thought they meant like... a cup... you know... a cup of water...
- inactive, on 10/12/2007, -7/+2lol sometimes I think printing subsystem is the most outdated part of un*x, a really pain in the ass :D this cups pathetic, the page what you see in the howto was the same in 2000 :D
I could laugh by reading the changelog how many thing doesn't changed since cups started.
Check out the new & improved 
© Digg Inc. 2009
— Content created and posted by Digg users is