[printing] configuration of networked printer under Linux

Hello everyone,

I am trying to print to my department's main networked printer, a Xerox

Document Center 470ST, from my Linux laptop. My problem is that the
IT department "naturally" doesn't support Linux and won't even tell me
how everything is configured...

The only information I have is:

- when I send a print job from my Windows machine, the printed pages
show up under a cover sheet which has my Windows/Novell username
written across it in big letters

- going to the Windows control panel of a computer which can print to
the Xerox, selecting this printer, "Properties" and then "Ports" shows
that it is "talking" to the printer over "Standard TCP/IP Protocol" to
the address 128.122.182.248 on port 9100. The selected protocol is
"raw" (rather than "LPR").

Does this mean that this is a Windows printer and I should be using
Samba? Or that it is using Novell? (If so, can I still use CUPS?) I
tried configuring CUPS to send jobs over either IPP or LPR to
socket://128.122.182.248:9100 using the recommended PPD for the
Document Center 400
(http://www.linuxprinting.org/show_pr...rox-Document_C...)
but always get an "server-error-internal-error" message.

The /var/log/cups/error_log file is filled with nothing but

E [24/Oct/2005:13:37:25 -0400] AddCert: Unable to create certificate
file /etc/cups/certs/0 - File exists

I would be really grateful for any guidance.

Best

Mack

MackS schrub am Montag, 23. Januar 2006 15:39
folgendes:

> Hello everyone,
>
> I am trying to print to my department's main
> networked printer, a Xerox
>
> Document Center 470ST, from my Linux laptop. My
> problem is that the IT department "naturally" doesn't
> support Linux and won't even tell me how everything
> is configured...

I don't know your model, but I have a XEROX Printer
working with Linux (in a network)

As long as a Printer "speaks" PostScript , which is
common for Printers in this price range, there is no
problem using it from Linux.

If you have Cups, simply add a new Printer, and use
"Generic Postscript" as Driver.

If your XEROX supports ipp-Protocol (don't know, our
WorkCentre 2424 does) the Printer URL is something in
the line of "http://<ip-address>:631" or
"ipp://<ip-address>"

I'm sure it supports at least LPD, so the URL would be
"lpd://<ip-address>:515/some_name_you_can_look_up_in_the_printer_documenta tion"

Hope this helps

--
greetz Karlheinz Klingbeil (lunqual)
http://www.lunqual.de oder http:www.lunqual.net

MackS wrote:
> Hello everyone,
>
> I am trying to print to my department's main networked printer, a Xerox
>
> Document Center 470ST, from my Linux laptop. My problem is that the
> IT department "naturally" doesn't support Linux and won't even tell me
> how everything is configured...
>
> The only information I have is:
>
> - when I send a print job from my Windows machine, the printed pages
> show up under a cover sheet which has my Windows/Novell username
> written across it in big letters
>
> - going to the Windows control panel of a computer which can print to
> the Xerox, selecting this printer, "Properties" and then "Ports" shows
> that it is "talking" to the printer over "Standard TCP/IP Protocol" to
> the address 128.122.182.248 on port 9100. The selected protocol is
> "raw" (rather than "LPR").
The chances are that your printer uses the HP JetDirect socket interface.

Using netcat, if you type:

nc 128.122.182.248 9100 < printfile.ps

where printfile.ps is a PostScript file, then your page should appear.

Your CUPS configured to send the job to socket://128.122.182.248:9100
should also work, of course. Does your printer not know the route to
your Linux machine, by any chance? If not, telnet into it and set its
gateway address.

Robert

>
> Does this mean that this is a Windows printer and I should be using
> Samba? Or that it is using Novell? (If so, can I still use CUPS?) I
> tried configuring CUPS to send jobs over either IPP or LPR to
> socket://128.122.182.248:9100 using the recommended PPD for the
> Document Center 400
> (http://www.linuxprinting.org/show_pr...rox-Document_C...)
> but always get an "server-error-internal-error" message.
>
> The /var/log/cups/error_log file is filled with nothing but
>
> E [24/Oct/2005:13:37:25 -0400] AddCert: Unable to create certificate
> file /etc/cups/certs/0 - File exists
>
> I would be really grateful for any guidance.
>
> Best
>
> Mack
>

Have you looked at the Xerox Linux support page for that printer?

http://www.support.xerox.com/go/resu...Xtype=download

MackS wrote:

> Hello everyone,
>
> I am trying to print to my department's main networked printer, a Xerox
>
> Document Center 470ST, from my Linux laptop. My problem is that the
> IT department "naturally" doesn't support Linux and won't even tell me
> how everything is configured...
>
> The only information I have is:
>
> - when I send a print job from my Windows machine, the printed pages
> show up under a cover sheet which has my Windows/Novell username
> written across it in big letters
>
> - going to the Windows control panel of a computer which can print to
> the Xerox, selecting this printer, "Properties" and then "Ports" shows
> that it is "talking" to the printer over "Standard TCP/IP Protocol" to
> the address 128.122.182.248 on port 9100. The selected protocol is
> "raw" (rather than "LPR").
>
> Does this mean that this is a Windows printer and I should be using
> Samba? Or that it is using Novell? (If so, can I still use CUPS?) I
> tried configuring CUPS to send jobs over either IPP or LPR to
> socket://128.122.182.248:9100 using the recommended PPD for the
> Document Center 400
> (http://www.linuxprinting.org/show_pr...rox-Document_C...)
> but always get an "server-error-internal-error" message.
>
> The /var/log/cups/error_log file is filled with nothing but
>
> E [24/Oct/2005:13:37:25 -0400] AddCert: Unable to create certificate
> file /etc/cups/certs/0 - File exists
>
> I would be really grateful for any guidance.
>
> Best
>
> Mack
>
If none of the other suggestions work try opening a web browser on it
"http://128.122.182.248" it may very well have a mini web server. If it
does it likely has a browse to any file "raw" interface.
--
JosephKK
Gegen dummheit kampfen Die Gotter Selbst, vergebens.
--Shiller

Joseph2k wrote:
> MackS wrote:
>
>> Hello everyone,
>>
>> I am trying to print to my department's main networked printer, a Xerox
>>
>> Document Center 470ST, from my Linux laptop. My problem is that the
>> IT department "naturally" doesn't support Linux and won't even tell me
>> how everything is configured...
>>
>> The only information I have is:
>>
>> - when I send a print job from my Windows machine, the printed pages
>> show up under a cover sheet which has my Windows/Novell username
>> written across it in big letters
>>
>> - going to the Windows control panel of a computer which can print to
>> the Xerox, selecting this printer, "Properties" and then "Ports" shows
>> that it is "talking" to the printer over "Standard TCP/IP Protocol" to
>> the address 128.122.182.248 on port 9100. The selected protocol is
>> "raw" (rather than "LPR").
>>
>> Does this mean that this is a Windows printer and I should be using
>> Samba? Or that it is using Novell? (If so, can I still use CUPS?) I
>> tried configuring CUPS to send jobs over either IPP or LPR to
>> socket://128.122.182.248:9100 using the recommended PPD for the
>> Document Center 400
>> (http://www.linuxprinting.org/show_pr...rox-Document_C...)
>> but always get an "server-error-internal-error" message.
>>
>> The /var/log/cups/error_log file is filled with nothing but
>>
>> E [24/Oct/2005:13:37:25 -0400] AddCert: Unable to create certificate
>> file /etc/cups/certs/0 - File exists
>>
>> I would be really grateful for any guidance.
>>
>> Best
>>
>> Mack
>>
> If none of the other suggestions work try opening a web browser on it
> "http://128.122.182.248" it may very well have a mini web server. If it
> does it likely has a browse to any file "raw" interface.

Some windows printers do indeed just accept raw data over a TCP
connection...

I am not sure how to make Linux talk it, but someone must have arranged
for it to be possible.
http://www.linuxprinting.org/direct-doc.html

seems to have some info. something call nc seems to do the final direct
port printing
Try man nc.