]> git.ipfire.org Git - thirdparty/cups.git/blob - doc/help/network.html
Load cups into easysw/current.
[thirdparty/cups.git] / doc / help / network.html
1 <HTML>
2 <!-- SECTION: Getting Started -->
3 <HEAD>
4 <TITLE>Using Network Printers</TITLE>
5 </HEAD>
6 <BODY>
7
8 <H2 CLASS="title"><A NAME="URI">Network Printer URIs</A></H2>
9
10 <P>Once you have set the IP address you can access the printer or
11 print server using the <CODE>ipp</CODE>, <CODE>lpd</CODE>, or
12 <CODE>socket</CODE> backends. The following is a list of common
13 network interfaces and printer servers and the settings you
14 should use with CUPS:</P>
15
16 <DIV CLASS="table"><TABLE WIDTH="50%">
17 <TR VALIGN="TOP" ALIGN="LEFT">
18 <TH>Model/Manufacturer</TH>
19 <TH>Device URI(s)</TH>
20 </TR>
21 <TR ALIGN="LEFT" VALIGN="TOP">
22 <TD>Apple LaserWriter</TD>
23 <TD>lpd://<I>address</I>/PASSTHRU</TD>
24 </TR>
25 <TR ALIGN="LEFT" VALIGN="TOP">
26 <TD>Axis w/o IPP<BR>
27 Axis OfficeBasic<BR>
28 <A HREF="#AXIS">(see directions)</A></TD>
29 <TD>socket://<I>address</I>:9100<BR>
30 socket://<I>address</I>:9101<BR>
31 socket://<I>address</I>:9102</TD>
32 </TR>
33 <TR ALIGN="LEFT" VALIGN="TOP">
34 <TD>Axis w/IPP</TD>
35 <TD>ipp://<I>address</I>/LPT1<BR>
36 ipp://<I>address</I>/LPT2<BR>
37 ipp://<I>address</I>/COM1</TD>
38 </TR>
39 <TR ALIGN="LEFT" VALIGN="TOP">
40 <TD>Castelle LANpress<SUP>TM</SUP></TD>
41 <TD>lpd://<I>address</I>/pr1<BR>
42 lpd://<I>address</I>/pr2<BR>
43 lpd://<I>address</I>/pr3</TD>
44 </TR>
45 <TR ALIGN="LEFT" VALIGN="TOP">
46 <TD>DPI NETPrint</TD>
47 <TD>lpd://<I>address</I>/pr1<BR>
48 lpd://<I>address</I>/pr2<BR>
49 lpd://<I>address</I>/pr3</TD>
50 </TR>
51 <TR ALIGN="LEFT" VALIGN="TOP">
52 <TD>DLink DP-301P+</TD>
53 <TD>socket://<I>address</I></TD>
54 </TR>
55 <TR ALIGN="LEFT" VALIGN="TOP">
56 <TD>EFI&reg; Fiery&reg; RIP</TD>
57 <TD>lpd://<I>address</I>/print</TD>
58 </TR>
59 <TR ALIGN="LEFT" VALIGN="TOP">
60 <TD>EPSON&reg; Multiprotocol Ethernet Interface Board</TD>
61 <TD>socket://<I>address</I></TD>
62 </TR>
63 <TR ALIGN="LEFT" VALIGN="TOP">
64 <TD>Extended System ExtendNET</TD>
65 <TD>lpd://<I>address</I>/pr1<BR>
66 lpd://<I>address</I>/pr2<BR>
67 lpd://<I>address</I>/pr3</TD>
68 </TR>
69 <TR ALIGN="LEFT" VALIGN="TOP">
70 <TD>Hewlett Packard JetDirect w/o IPP</TD>
71 <TD>socket://<I>address</I>:9100<BR>
72 socket://<I>address</I>:9101<BR>
73 socket://<I>address</I>:9102</TD>
74 </TR>
75 <TR ALIGN="LEFT" VALIGN="TOP">
76 <TD>Hewlett Packard JetDirect w/IPP</TD>
77 <TD>ipp://<I>address</I>/ipp<BR>
78 ipp://<I>address</I>/ipp/port1<BR>
79 ipp://<I>address</I>/ipp/port2<BR>
80 ipp://<I>address</I>/ipp/port3</TD>
81 </TR>
82 <TR ALIGN="LEFT" VALIGN="TOP">
83 <TD>IntelĀ® NetportExpress XL, PRO/100</TD>
84 <TD>lpd://<I>address</I>/LPT1_PASSTHRU<BR>
85 lpd://<I>address</I>/LPT2_PASSTHRU<BR>
86 lpd://<I>address</I>/COM1_PASSTHRU</TD>
87 </TR>
88 <TR ALIGN="LEFT" VALIGN="TOP">
89 <TD>Lexmark<SUP>TM</SUP> MarkNet</TD>
90 <TD>lpd://<I>address</I>/ps</TD>
91 </TR>
92 <TR ALIGN="LEFT" VALIGN="TOP">
93 <TD>Linksys EtherFast&reg;<BR>
94 <A HREF="#LINKSYS">(see directions)</A></TD>
95 <TD>socket://<I>address</I>:4010<BR>
96 socket://<I>address</I>:4020<BR>
97 socket://<I>address</I>:4030</TD>
98 </TR>
99 <TR ALIGN="LEFT" VALIGN="TOP">
100 <TD>Linksys PSUS4</TD>
101 <TD>lpd://<I>address</I>/lp</TD>
102 </TR>
103 <TR ALIGN="LEFT" VALIGN="TOP">
104 <TD>Kodak&reg;</TD>
105 <TD>lpd://<I>address</I>/ps</TD>
106 </TR>
107 <TR ALIGN="LEFT" VALIGN="TOP">
108 <TD>QMS&reg; CrownNet<SUP>TM</SUP></TD>
109 <TD>lpd://<I>address</I>/ps</TD>
110 </TR>
111 <TR ALIGN="LEFT" VALIGN="TOP">
112 <TD>Tektronix&reg; PhaserShare<SUP>TM</SUP></TD>
113 <TD>socket://<I>address</I>:9100</TD>
114 </TR>
115 <TR ALIGN="LEFT" VALIGN="TOP">
116 <TD>XEROX&reg; 4512 NIC</TD>
117 <TD>lpd://<I>address</I>/PORT1</TD>
118 </TR>
119 <TR ALIGN="LEFT" VALIGN="TOP">
120 <TD>XEROX&reg; XNIC</TD>
121 <TD>lpd://<I>address</I>/PASSTHRU</TD>
122 </TR>
123 <TR ALIGN="LEFT" VALIGN="TOP">
124 <TD>XEROX&reg; (most others)</TD>
125 <TD>socket://<I>address</I>:5503</TD>
126 </TR>
127 </TABLE></DIV>
128
129 <H2 CLASS="title"><A NAME="ADDRESS">Getting the IP Address</A></H2>
130
131 <P>When you first install a network printer or print server on
132 your LAN, you need to set the Internet Protocol ("IP") address.
133 On most higher-end "workgroup" printers, you can set the address
134 through the printer control panel. However, in most cases you
135 will want to assign the addresses remotely from your workstation.
136 This makes administration a bit easier and avoids assigning
137 duplicate addresses accidentally.</P>
138
139 <P>To setup your printer or print server for remote address
140 assignment, you'll need the Ethernet Media Access Control ("MAC")
141 address, also sometimes called a node address, and the IP address
142 you want to use for the device. The Ethernet MAC address can
143 often be found on the printer test page or bottom of the print
144 server.</P>
145
146 <H3>Configuring the IP Address Using ARP</H3>
147
148 <P>The easiest way to set the IP address of a network device is
149 to use the <CODE>arp(8)</CODE> command. The <CODE>arp</CODE>
150 sends an Address Resolution Protocol ("ARP") packet to the
151 specified Ethernet MAC address, setting the network device's IP
152 address:</P>
153
154 <PRE CLASS="command">
155 <KBD>arp -s ip-address ethernet-address</KBD>
156 <KBD>arp -s host.domain.com 08:00:69:00:12:34</KBD>
157 <KBD>arp -s 192.0.2.2 08:00:69:00:12:34</KBD>
158 </PRE>
159
160 <H3>Configuring the IP Address Using RARP</H3>
161
162 <P>The most flexible way to remotely assign IP addresses under
163 UNIX is through the Reverse Address Resolution Protocol ("RARP").
164 RARP allows a network device to request an IP address using its
165 Ethernet MAC address, and one or more RARP servers on the network
166 will respond with an ARP packet with the IP address the device
167 can use.</P>
168
169 <P>RARP should be used when you have to manage many printers or
170 print servers, or when you have a network device that does not
171 remember its IP address after a power cycle. If you just have a
172 single printer or print server, the <CODE>arp</CODE> command is
173 the way to go.</P>
174
175 <P>Some UNIX operating systems use a program called
176 <CODE>rarpd(8)</CODE> to manage RARP. Others, like Linux, support
177 this protocol in the kernel. For systems that provide the
178 <CODE>rarpd</CODE> program you will need to start it before RARP
179 lookups will work:</P>
180
181 <PRE CLASS="command">
182 <KBD>rarpd</KBD>
183 </PRE>
184
185 <P>Under IRIX you can enable this functionality by default
186 using:</P>
187
188 <PRE CLASS="command">
189 <KBD>chkconfig rarpd on</KBD>
190 </PRE>
191
192 <P>Both the <CODE>rarpd</CODE> program and kernel RARP support
193 read a list of Ethernet and IP addresses from the file
194 <VAR>/etc/ethers</VAR>. Each line contains the Ethernet address
195 (colon delimited) followed by an IP address or hostname like:</P>
196
197 <PRE CLASS="command">
198 08:00:69:00:12:34 myprinter.mydomain.com
199 08:00:69:00:12:34 192.0.2.2
200 </PRE>
201
202 <P>Add a line to this file and cycle the power on the printer or
203 print server to set its address.</P>
204
205 <H3>Configuring the IP Address Using BOOTP</H3>
206
207 <P>The BOOTP protocol is used when you need to provide additional
208 information such as the location of a configuration file to the
209 network interface. Using the standard <CODE>bootpd(8)</CODE>
210 program supplied with UNIX you simply need to add a line to the
211 <VAR>/etc/bootptab</VAR> file; for IRIX:</P>
212
213 <PRE CLASS="command">
214 myprinter 08:00:69:00:12:34 192.0.2.2 <VAR>myprinter.boot</VAR>
215 </PRE>
216
217 <P>Newer versions of <CODE>bootpd</CODE> use a different
218 format:</P>
219
220 <PRE CLASS="command">
221 myprinter:ha=080069001234:ip=192.0.2.2:<VAR>t144=myprinter.boot</VAR>
222 </PRE>
223
224 <P>The <VAR>myprinter.boot</VAR> file resides in the
225 <VAR>/usr/local/boot</VAR> directory by default. If you do not
226 need to provide a boot file you may leave the last part of the
227 line blank.</P>
228
229 <BLOCKQUOTE><B>Note:</B>
230
231 <P>Some versions of UNIX do not enable the BOOTP service by
232 default. The <VAR>/etc/inetd.conf</VAR> usually contains a line
233 for the BOOTP service that can be uncommented if needed.</P>
234
235 </BLOCKQUOTE>
236
237 <H2 CLASS="title"><A NAME="VERIFY">Verifying the Printer Connection</A></H2>
238
239 <P>To test that the IP address has been successfully assigned and
240 that the printer is properly connected to your LAN, type:</P>
241
242 <PRE CLASS="command">
243 <KBD>ping ip-address</KBD>
244 </PRE>
245
246 <P>If the connection is working properly you will see something
247 like:</P>
248
249 <PRE CLASS="command">
250 <KBD>ping myprinter</KBD>
251 PING myprinter (192.0.2.2): 56 data bytes
252 64 bytes from 192.0.2.2: icmp_seq=0 ttl=15 time=5 ms
253 64 bytes from 192.0.2.2: icmp_seq=1 ttl=15 time=3 ms
254 64 bytes from 192.0.2.2: icmp_seq=2 ttl=15 time=3 ms
255 64 bytes from 192.0.2.2: icmp_seq=3 ttl=15 time=3 ms
256 </PRE>
257
258 <P>If not, verify that the printer or print server is connected
259 to the LAN, it is powered on, the LAN cabling is good, and the IP
260 address is set correctly. You can usually see the current IP
261 address and network status by printing a configuration or test
262 page on the device.</P>
263
264 <H2 CLASS="title"><A NAME="AXIS">Configuring Axis Print Servers</A></H2>
265
266 <P>The Axis print servers can be configured using ARP, RARP, or
267 BOOTP. However, on models that do not provide IPP support an
268 additional step must be performed to configure the TCP/IP portion
269 of the print server for use with CUPS.</P>
270
271 <P>Each print server contains a configuration file named
272 <VAR>config</VAR> that contains a list of network parameters used
273 by the server. To modify this file you must first download it
274 from the print server using the <CODE>ftp(1)</CODE> program:</P>
275
276 <PRE CLASS="command">
277 <KBD>ftp ip-address</KBD>
278 Connected to ip-address.
279 220 Axis NPS ### FTP Printer Server V#.## MON DD YEAR ready.
280 ftp> <KBD>user root</KBD>
281 331 User name ok, need password
282 Password: <KBD>pass</KBD> <I>(this is not echoed)</I>
283 230 User logged in
284 ftp> <KBD>get config</KBD>
285 local: config remote: config
286 200 PORT command successful.
287 150 Opening data connection for config (192,0,2,2),
288 (mode ascii).
289 226 Transfer complete.
290 ##### bytes received in #.## seconds (##### Kbytes/s)
291 ftp> <KBD>quit</KBD>
292 221 Goodbye.
293 </PRE>
294
295 <P>Next, edit the file with your favorite text editor and locate
296 the lines beginning with:</P>
297
298 <PRE CLASS="command">
299 RTN_OPT. : YES
300 RTEL_PR1. : 0
301 RTEL_PR2. : 0
302 RTEL_PR3. : 0
303 RTEL_PR4. : 0
304 RTEL_PR5. : 0
305 RTEL_PR6. : 0
306 RTEL_PR7. : 0
307 RTEL_PR8. : 0
308 </PRE>
309
310 <P>Change the <CODE>RTN_OPT</CODE> line to read:</P>
311
312 <PRE CLASS="command">
313 RTN_OPT. : <KBD>NO</KBD>
314 </PRE>
315
316 <P>This disables the Reverse TELNET protocol and enables the
317 standard TELNET protocol on the print server. Next, assign a port
318 number for each parallel and serial port on the server as
319 follows:</P>
320
321 <PRE CLASS="command">
322 RTEL_PR1. : <KBD>9100</KBD>
323 RTEL_PR2. : <KBD>9101</KBD>
324 RTEL_PR3. : <KBD>9102</KBD>
325 RTEL_PR4. : <KBD>9103</KBD>
326 RTEL_PR5. : <KBD>9104</KBD>
327 RTEL_PR6. : <KBD>9105</KBD>
328 RTEL_PR7. : <KBD>9106</KBD>
329 RTEL_PR8. : <KBD>9107</KBD>
330 </PRE>
331
332 <P>This essentially makes the Axis print server look like a
333 Hewlett Packard JetDirect EX print server. Save the file and then
334 upload the new <VAR>config</VAR> file using the <CODE>ftp</CODE>
335 command:</P>
336
337 <PRE CLASS="command">
338 <KBD>ftp ip-address</KBD>
339 Connected to ip-address.
340 220 Axis NPS ### FTP Printer Server V#.## MON DD YEAR ready.
341 ftp> <KBD>user root</KBD>
342 331 User name ok, need password
343 Password: <KBD>pass</KBD> <I>(this is not echoed)</I>
344 230 User logged in
345 ftp> <KBD>put config CONFIG</KBD>
346 local: config remote: CONFIG
347 200 PORT command successful.
348 150 Opening data connection for config (192,0,2,2), (mode ascii).
349 226 Transfer complete.
350 ##### bytes received in #.## seconds (##### Kbytes/s)
351 ftp> <KBD>get hardreset</KBD>
352 local: hardreset remote: hardreset
353 200 PORT command successful.
354 421 Axis NPS ### hard reset, closing connection.
355 ftp> <KBD>quit</KBD>
356 221 Goodbye.
357 </PRE>
358
359 <P>Your Axis print server is now ready for use!</P>
360
361 <H2 CLASS="title"><A NAME="LINKSYS">Configuring Linksys Print Servers</A></H2>
362
363 <P>The Linksys print servers can be configured using ARP, RARP,
364 or BOOTP. Like older Axis print servers, an additional step must
365 be performed to configure the TCP/IP portion of the print server
366 for use with CUPS.</P>
367
368 <P>Each print server contains a configuration file named
369 <VAR>CONFIG</VAR> that contains a list of network parameters used
370 by the server. To modify this file you must first download it
371 from the print server using the <CODE>ftp(1)</CODE> program:</P>
372
373 <PRE CLASS="command">
374 <KBD>ftp -n ip-address</KBD>
375 Connected to ip-address.
376 220 Print Server Ready.
377 Remote system type is Print.
378 ftp> <KBD>get CONFIG</KBD>
379 local: CONFIG remote: CONFIG
380 200 Command OK.
381 150 Open ASCII Mode Connection.
382 WARNING! 68 bare linefeeds received in ASCII mode
383 File may not have transferred correctly.
384 226 Transfer complete.
385 ##### bytes received in #.## seconds (##### Kbytes/s)
386 ftp> <KBD>quit</KBD>
387 221 Goodbye.
388 </PRE>
389
390 <P>Next, edit the file with your favorite text editor and locate
391 the lines beginning with:</P>
392
393 <PRE CLASS="command">
394 0100 L1_PROUT:P1
395 0120 L2_PROUT:P1
396 0140 L3_PROUT:P1
397 </PRE>
398
399 <P>Change the port number for each parallel and serial port on
400 the server as follows:</P>
401
402 <PRE CLASS="command">
403 0100 L1_PROUT:<KBD>P1</KBD>
404 0120 L2_PROUT:<KBD>P2</KBD>
405 0140 L3_PROUT:<KBD>P3</KBD>
406 </PRE>
407
408 <P>This maps each virtual printer with a physical port. Save the
409 file and then upload the new <VAR>CONFIG</VAR> file using the
410 <CODE>ftp</CODE> command:</P>
411
412 <PRE CLASS="command">
413 <KBD>ftp -n ip-address</KBD>
414 Connected to ip-address.
415 220 Print Server Ready.
416 Remote system type is Print.
417 ftp> <KBD>put CONFIG</KBD>
418 local: CONFIG remote: CONFIG
419 200 Command OK.
420 150 Open ASCII Mode Connection.
421 226 Transfer complete.
422 ##### bytes received in #.## seconds (##### Kbytes/s)
423 ftp> <KBD>quit</KBD>
424 221 Goodbye.
425 </PRE>
426
427 <P>Your Linksys print server is now ready for use!</P>
428
429
430 </BODY>
431 </HTML>