2010-06-09, 08:50 | Link #21 | |
AS Oji-kun
Join Date: Nov 2006
Age: 74
|
Quote:
You'll probably have to modify the file /etc/cups/cupsd.conf to allow CUPS to bind to the server's IP address. You should see a line that reads Listen localhost:631 Replace "localhost:631" with "*:631" so the server can accept jobs over the network. 2) You don't need to share any directories with Samba. It all depends on what shares are defined in /etc/samba/smb.conf. By default, Samba usually shares all printers and all the home directories, but you can disable the latter by commenting out the [homes] definition in smb.conf. Using Samba requires that the Windows machine have the correct driver for your HP printer. The page-description file is created in Windows then shipped to the Linux box for printing without any further modification.
__________________
|
|
2010-06-09, 20:12 | Link #22 | |
Junior Member
Join Date: Dec 2005
|
Quote:
|
|
2010-06-09, 21:17 | Link #23 |
AS Oji-kun
Join Date: Nov 2006
Age: 74
|
Windows 7 is a real problem it appears according to Adobe. You can try one of the other manufacturer's drivers. All the ones that have "PS" at the end are Postscript; the "PCL" drivers use HP's proprietary "printer control language."
You might be better off using Samba if you can find an appropriate driver for the Windows machines.
__________________
|
2010-06-09, 23:31 | Link #24 | |
Junior Member
Join Date: Dec 2005
|
Quote:
So I somehow manage to add the printer in Windows 7 using drivers for the OfficeJet 4300 series (I guess it's compatible with the PSC 1310 series). But since I can't seem to do the same on XP, I'm sharing the printer from Windows 7 to all the XP computers in my network. It's a bit awkward to have to use Windows 7 just to print from an XP computer to a printer connected to a Linux computer, but at least someone else can print while I'm on Linux. Anyway, thanks for your time. I'll see how this goes for now. |
|
2010-08-01, 12:25 | Link #25 |
Junior Member
Join Date: Dec 2005
|
Well, after deciding to tackle the issue once again, I was finally able to install the printer using the generic driver for MS Publisher Color Printer that comes by default with Windows XP. I guess it really is just a matter of using a postscript driver. Thanks SeijiSensei.
The only issue now is that while everything went fine with the desktop client, on the laptop client, the printer printed two copies of the test page. Is that just a one time thing or should I be worried about that? |
2010-08-01, 18:13 | Link #26 | |
AS Oji-kun
Join Date: Nov 2006
Age: 74
|
Quote:
If you always get two copies from one machine and not the other, it's likely that your defaults are configured differently on the two machines. If one machine always prints two copies of every document, create a test document in Wordpad on it and look at all the printing options. Is the default number of copies set to two? If so, you'll need to fix the default in the driver properties under Control Panel > Printers. It's also quite likely that you tried to print a test document before when the connection to the remove printer was configured properly. In that case the printable image of the test document remained in the printer queue awaiting reconnection with the remote machine. When you fixed the problem, both the queued copy and the new copy of the test document were sent to the printer, and you ended up with both copies. Remember, you can't really "break" your computer. Windows System Restore is a nice feature for the faint of heart.
__________________
|
|
2010-08-01, 23:06 | Link #27 | |
NYAAAAHAAANNNNN~
Join Date: Nov 2007
Age: 35
|
Quote:
I always turn off system restore because of modern viruses : almost all of them attack SR.
__________________
|
|
2010-08-02, 01:07 | Link #28 | |
Junior Member
Join Date: Dec 2005
|
Quote:
Oh, and I'm not worried about breaking the computer. At worst, this would've been more of an annoyance, but I'm just happy at getting them to print. |
|
Tags |
hardware, printers |
|
|