doc/help/network.html

   1 <HTML>
   2 <!-- SECTION: Getting Started -->
   3 <HEAD>
   4         <TITLE>Using Network Printers</TITLE>
   5 </HEAD>
   6 <BODY>
   7
   8 <P>This help document describes how to discover, configure, and use TCP/IP network printers with CUPS.</P>
   9
  10 <H2 CLASS="title"><A NAME="ADDRESS">Getting the IP Address</A></H2>
  11
  12 <P>Every network printer or print server has a unique Internet Protocol (IP) address associated with it. This address is either configured manually or set using an automatic network protocol such as the <A HREF="#BOOTP">Boot Protocol (BOOTP)</A>, <A HREF="#DHCP">Dynamic Host Control Protocol (DHCP)</A>, Reverse Address Resolution Protocol (RARP), or ZeroConf.</P>
  13
  14 <P>You can normally find the IP address of a printer on the printer's control panel or by printing the configuration or status page. The <A HREF="#SNMP">Simple Network Management Protocol (SNMP)</A> can also be used to get the IP address remotely, which happens automatically when you visit the CUPS administration web page or choose an available CUPS device when adding a printer.</P>
  15
  16
  17 <H2 CLASS="title"><A NAME="CONFIG">Configuring the IP Address</A></H2>
  18
  19 <P>When you first install a network printer or print server on your LAN, you need to set the Internet Protocol ("IP") address. Most higher-end "workgroup" printers allow you to set the address through the printer control panel. However, if you have many printers you will want to assign the addresses remotely - this makes administration a bit easier and avoids assigning duplicate addresses accidentally.</P>
  20
  21 <P>To setup your printer or print server for remote address assignment, you'll need the Ethernet Media Access Control ("MAC") address, also sometimes called a node address, and the IP address you want to use for the device. The Ethernet MAC address can often be found on the printer test page or bottom of the print server.</P>
  22
  23 <H3><A NAME="DHCP">Configuring the IP Address Using DHCP</A></H3>
  24
  25 <P>The DHCP protocol is the usual way of setting the IP address of a printer on a managed network. Using the standard <TT>dhcpd(8)</TT> program supplied with UNIX you simply need to add a line to the <VAR>/etc/dhcpd.conf</VAR> file:</P>
  26
  27 <PRE CLASS="command">
  28 host <I>hostname</I> {
  29   hardware ethernet <I>mac-address</I>;
  30   fixed-address <I>ip-address</I>;
  31 }
  32 </PRE>
  33
  34 <P>Make sure that the hostname you use is also listed in the <VAR>/etc/hosts</VAR> file or is registered with your DNS server.</P>
  35
  36 <H3><A NAME="BOOTP">Configuring the IP Address Using BOOTP</A></H3>
  37
  38 <P>The BOOTP protocol is used when you need to provide additional information such as the location of a configuration file to the network interface. Using the standard <TT>bootpd(8)</TT> program supplied with UNIX you simply need to add a line to the <VAR>/etc/bootptab</VAR> file; for IRIX:</P>
  39
  40 <PRE CLASS="command">
  41 myprinter 08:00:69:00:12:34 192.0.2.2 <VAR>myprinter.boot</VAR>
  42 </PRE>
  43
  44 <P>Newer versions of <TT>bootpd</TT> use a different format:</P>
  45
  46 <PRE CLASS="command">
  47 myprinter:ha=080069001234:ip=192.0.2.2:<VAR>t144=myprinter.boot</VAR>
  48 </PRE>
  49
  50 <P>The <VAR>myprinter.boot</VAR> file resides in the <VAR>/usr/local/boot</VAR> directory by default. If you do not need to provide a boot file you may leave the last part of the line blank.</P>
  51
  52 <BLOCKQUOTE><B>Note:</B> Some versions of UNIX do not enable the BOOTP service by default. The <VAR>/etc/inetd.conf</VAR> or <VAR>/etc/xinetd.d/bootp</VAR> file usually contains a line for the BOOTP service that can be uncommented if needed.</BLOCKQUOTE>
  53
  54
  55 <H2 CLASS="title"><A NAME="VERIFY">Verifying the Printer Connection</A></H2>
  56
  57 <P>To test that the IP address has been successfully assigned and
  58 that the printer is properly connected to your LAN, type:</P>
  59
  60 <PRE CLASS="command">
  61 <KBD>ping ip-address</KBD>
  62 </PRE>
  63
  64 <P>If the connection is working properly you will see something
  65 like:</P>
  66
  67 <PRE CLASS="command">
  68 <KBD>ping myprinter</KBD>
  69 PING myprinter (192.0.2.2): 56 data bytes
  70 64 bytes from 192.0.2.2: icmp_seq=0 ttl=15 time=5 ms
  71 64 bytes from 192.0.2.2: icmp_seq=1 ttl=15 time=3 ms
  72 64 bytes from 192.0.2.2: icmp_seq=2 ttl=15 time=3 ms
  73 64 bytes from 192.0.2.2: icmp_seq=3 ttl=15 time=3 ms
  74 </PRE>
  75
  76 <P>If not, verify that the printer or print server is connected
  77 to the LAN, it is powered on, the LAN cabling is good, and the IP
  78 address is set correctly. You can usually see the current IP
  79 address and network status by printing a configuration or test
  80 page on the device.</P>
  81
  82
  83 <H2 CLASS="title"><A NAME="PROTOCOLS">Network Protocols Supported by CUPS</H2>
  84
  85 <P>CUPS supports most network printers using one of three TCP/IP-based protocols. Printer discovery is currently accomplished using the SNMP protocol, however future versions of CUPS will also include support for multicast DNS service discovery as well.</P>
  86
  87 <H3><A NAME="SOCKET">AppSocket Protocol</A></H3>
  88
  89 <P>The AppSocket protocol (sometimes also called the JetDirect protocol, owing to its origins with the HP JetDirect network interfaces) is the simplest, fastest, and generally the most reliable network protocol used for printers. AppSocket printing normally happens over port 9100 and uses the <tt>socket</tt> URI scheme:</P>
  90
  91 <PRE>
  92 socket://<i>ip-address-or-hostname</i>
  93 socket://<i>ip-address-or-hostname</i>?waiteof=false
  94 socket://<i>ip-address-or-hostname</i>:<i>port-number</i>
  95 socket://<i>ip-address-or-hostname</i>:<i>port-number</i>?waiteof=false
  96 </PRE>
  97
  98 <P>The "waiteof" option controls whether the <tt>socket</tt> backend waits for the printer to complete the printing of the job. The default is to wait.</P>
  99
 100 <H3><A NAME="IPP">Internet Printing Protocol (IPP)</A></H3>
 101
 102 <P>IPP is the only protocol that CUPS supports natively and is supported by some network printers and print servers. However, since many printers do not implement IPP properly, only use IPP when the vendor actually documents official support for it. IPP printing normally happens over port 631 and uses the <tt>http</tt> and <tt>ipp</tt> URI schemes:</P>
 103
 104 <PRE>
 105 http://<i>ip-address-or-hostname</i>:<i>port-number</i>/<i>resource</i>
 106 http://<i>ip-address-or-hostname</i>:<i>port-number</i>/<i>resource</i>?<i>option=value</i>
 107 http://<i>ip-address-or-hostname</i>:<i>port-number</i>/<i>resource</i>?<i>option=value&option=value</i>
 108 ipp://<i>ip-address-or-hostname</i>/<i>resource</i>
 109 ipp://<i>ip-address-or-hostname</i>/<i>resource</i>?<i>option=value</i>
 110 ipp://<i>ip-address-or-hostname</i>/<i>resource</i>?<i>option=value&option=value</i>
 111 ipp://<i>ip-address-or-hostname</i>:<i>port-number</i>/<i>resource</i>
 112 ipp://<i>ip-address-or-hostname</i>:<i>port-number</i>/<i>resource</i>?<i>option=value</i>
 113 ipp://<i>ip-address-or-hostname</i>:<i>port-number</i>/<i>resource</i>?<i>option=value&option=value</i>
 114 </PRE>
 115
 116 <P>The <tt>ipp</tt> backend supports many options, which are summarized in <A HREF="#TABLE2">Table 2</A>.</P>
 117
 118 <DIV CLASS="table"><TABLE SUMMARY="IPP URI Options">
 119 <CAPTION>Table 2: <A NAME="TABLE2">IPP URI Options</A></CAPTION>
 120 <THEAD>
 121 <TR>
 122         <TH>Option</TH>
 123         <TH>Description</TH>
 124 </TR>
 125 </THEAD>
 126 <TBODY>
 127 <TR>
 128         <TD><TT>compression=gzip</TT></TD>
 129         <TD>Specifies that print data should be compressed before sending.</TD>
 130 </TR>
 131 <TR>
 132         <TD><TT>encryption=always</TT></TD>
 133         <TD>Specifies that the connection to the IPP server should be encrypted using SSL.</TD>
 134 </TR>
 135 <TR>
 136         <TD><TT>encryption=ifrequested</TT></TD>
 137         <TD>Specifies that the connection to the IPP server should only be encrypted if the server requests it.</TD>
 138 </TR>
 139 <TR>
 140         <TD><TT>encryption=never</TT></TD>
 141         <TD>Specifies that the connection to the IPP server should not be encrypted.</TD>
 142 </TR>
 143 <TR>
 144         <TD><TT>encryption=required</TT></TD>
 145         <TD>Specifies that the connection to the IPP server should be encrypted using TLS.</TD>
 146 </TR>
 147 <TR>
 148         <TD><TT>version=1.0</TT></TD>
 149         <TD>Specifies that version 1.0 of the IPP protocol should be used instead of the default version 1.1.</TD>
 150 </TR>
 151 <TR>
 152         <TD><TT>version=2.0</TT></TD>
 153         <TD>Specifies that version 2.0 of the IPP protocol should be used instead of the default version 1.1.</TD>
 154 </TR>
 155 <TR>
 156         <TD><TT>version=2.1</TT></TD>
 157         <TD>Specifies that version 2.1 of the IPP protocol should be used instead of the default version 1.1.</TD>
 158 </TR>
 159 <TR>
 160         <TD><TT>waitjob=false</TT></TD>
 161         <TD>Specifies that the IPP backend should not wait for the job to complete.</TD>
 162 </TR>
 163 <TR>
 164         <TD><TT>waitprinter=false</TT></TD>
 165         <TD>Specifies that the IPP backend should not wait for the printer to become idle before sending the print job.</TD>
 166 </TR>
 167 </TBODY>
 168 </TABLE></DIV>
 169
 170 <H3><A NAME="LPD">Line Printer Daemon (LPD) Protocol</A></H3>
 171
 172 <P>LPD is the original network printing protocol and is supported by many network printers. Due to limitations in the LPD protocol, we do not recommend using it if the printer or server supports one of the other protocols. LPD printing normally happens over port 515 and uses the <tt>lpd</tt> URI scheme:</P>
 173
 174 <PRE>
 175 lpd://<i>ip-address-or-hostname</i>/<i>queue</i>
 176 lpd://<i>username@ip-address-or-hostname</i>/<i>queue</i>
 177 lpd://<i>ip-address-or-hostname</i>/<i>queue</i>?<i>option=value</i>
 178 lpd://<i>username@ip-address-or-hostname</i>/<i>queue</i>?<i>option=value</i>
 179 lpd://<i>ip-address-or-hostname</i>/<i>queue</i>?<i>option=value&option=value</i>
 180 lpd://<i>username@ip-address-or-hostname</i>/<i>queue</i>?<i>option=value&option=value</i>
 181 </PRE>
 182
 183 <P><A HREF="#TABLE3">Table 3</A> summarizes the options supported by the <tt>lpd</tt> backend.</P>
 184
 185 <DIV CLASS="table"><TABLE SUMMARY="LPD URI Options">
 186 <CAPTION>Table 3: <A NAME="TABLE3">LPD URI Options</A></CAPTION>
 187 <THEAD>
 188 <TR>
 189         <TH>Option</TH>
 190         <TH>Description</TH>
 191 </TR>
 192 </THEAD>
 193 <TBODY>
 194 <TR>
 195         <TD><TT>banner=on</TT></TD>
 196         <TD>Specifies that a banner page should be printed by the server.</TD>
 197 </TR>
 198 <TR>
 199         <TD><TT>contimeout=<I>seconds</I></TT></TD>
 200         <TD>Specifies the number of seconds to wait for the connection to the server to complete.</TD>
 201 </TR>
 202 <TR>
 203         <TD><TT>format=c</TT></TD>
 204         <TD>Specifies that the print data is a CIF file.</TD>
 205 </TR>
 206 <TR>
 207         <TD><TT>format=d</TT></TD>
 208         <TD>Specifies that the print data is a DVI file.</TD>
 209 </TR>
 210 <TR>
 211         <TD><TT>format=f</TT></TD>
 212         <TD>Specifies that the print data is a plain text file.</TD>
 213 </TR>
 214 <TR>
 215         <TD><TT>format=g</TT></TD>
 216         <TD>Specifies that the print data is a Berkeley plot file.</TD>
 217 </TR>
 218 <TR>
 219         <TD><TT>format=l</TT></TD>
 220         <TD>Specifies that the print data is a raw (preformatted) print file.</TD>
 221 </TR>
 222 <TR>
 223         <TD><TT>format=n</TT></TD>
 224         <TD>Specifies that the print data is a ditroff file.</TD>
 225 </TR>
 226 <TR>
 227         <TD><TT>format=o</TT></TD>
 228         <TD>Specifies that the print data is a PostScript file.</TD>
 229 </TR>
 230 <TR>
 231         <TD><TT>format=p</TT></TD>
 232         <TD>Specifies that the print data is a plain text file that should be "pretty" printed with a header and footer.</TD>
 233 </TR>
 234 <TR>
 235         <TD><TT>format=r</TT></TD>
 236         <TD>Specifies that the print data is a FORTRAN carriage control file.</TD>
 237 </TR>
 238 <TR>
 239         <TD><TT>format=t</TT></TD>
 240         <TD>Specifies that the print data is a troff Graphic Systems C/A/T phototypesetter file.</TD>
 241 </TR>
 242 <TR>
 243         <TD><TT>format=v</TT></TD>
 244         <TD>Specifies that the print data is a Sun raster file.</TD>
 245 </TR>
 246 <TR>
 247         <TD><TT>order=data,control</TT></TD>
 248         <TD>Specifies that the print data files should be sent before the control file.</TD>
 249 </TR>
 250 <TR>
 251         <TD><TT>reserve=none</TT></TD>
 252         <TD>Specifies that the backend should not reserve a source port.</TD>
 253 </TR>
 254 <TR>
 255         <TD><TT>reserve=rfc1179</TT></TD>
 256         <TD>Specifies that the backend should reserve a source port from 721 to 731 as required by RFC 1179.</TD>
 257 </TR>
 258 <TR>
 259         <TD><TT>sanitize_title=no</TT></TD>
 260         <TD>Specifies that the job title string should not be restricted to ASCII characters.</TD>
 261 </TR>
 262 <TR>
 263         <TD><TT>sanitize_title=yes</TT></TD>
 264         <TD>Specifies that the job title string should be restricted to ASCII characters.</TD>
 265 </TR>
 266 <TR>
 267         <TD><TT>timeout=<I>seconds</I></TT></TD>
 268         <TD>Specifies the number of seconds to wait for LPD commands to complete.</TD>
 269 </TR>
 270 </TBODY>
 271 </TABLE></DIV>
 272
 273
 274 <H3><A NAME="URI">Common Network Printer URIs</A></H3>
 275
 276 <P>Once you have set the IP address you can access the printer or print server using the <TT>ipp</TT>, <TT>lpd</TT>, or <TT>socket</TT> backends. <A HREF="#TABLE1">Table 1</A> shows a list of common network interfaces and printer servers and the settings you should use with CUPS:</P>
 277
 278 <DIV CLASS="table"><TABLE SUMMARY="Common Device URIs">
 279 <CAPTION>Table 1: <A NAME="TABLE1">Common Device URIs</A></CAPTION>
 280 <THEAD>
 281 <TR>
 282         <TH>Model/Manufacturer</TH>
 283         <TH>Device URI(s)</TH>
 284 </TR>
 285 </THEAD>
 286 <TBODY>
 287 <TR>
 288         <TD>Apple LaserWriter</TD>
 289         <TD>lpd://<I>address</I>/PASSTHRU</TD>
 290 </TR>
 291 <TR>
 292         <TD>Axis w/o IPP<BR>
 293         Axis OfficeBasic<BR>
 294         <A HREF="#AXIS">(see directions)</A></TD>
 295         <TD>socket://<I>address</I>:9100<BR>
 296         socket://<I>address</I>:9101<BR>
 297         socket://<I>address</I>:9102</TD>
 298 </TR>
 299 <TR>
 300         <TD>Axis w/IPP</TD>
 301         <TD>ipp://<I>address</I>/LPT1<BR>
 302         ipp://<I>address</I>/LPT2<BR>
 303         ipp://<I>address</I>/COM1</TD>
 304 </TR>
 305 <TR>
 306         <TD>Castelle LANpress<SUP>TM</SUP></TD>
 307         <TD>lpd://<I>address</I>/pr1<BR>
 308         lpd://<I>address</I>/pr2<BR>
 309         lpd://<I>address</I>/pr3</TD>
 310 </TR>
 311 <TR>
 312         <TD>DPI NETPrint</TD>
 313         <TD>lpd://<I>address</I>/pr1<BR>
 314         lpd://<I>address</I>/pr2<BR>
 315         lpd://<I>address</I>/pr3</TD>
 316 </TR>
 317 <TR>
 318         <TD>DLink DP-301P+</TD>
 319         <TD>socket://<I>address</I></TD>
 320 </TR>
 321 <TR>
 322         <TD>EFI&reg; Fiery&reg; RIP</TD>
 323         <TD>lpd://<I>address</I>/print</TD>
 324 </TR>
 325 <TR>
 326         <TD>EPSON&reg; Multiprotocol Ethernet Interface Board</TD>
 327         <TD>socket://<I>address</I></TD>
 328 </TR>
 329 <TR>
 330         <TD>Extended System ExtendNET</TD>
 331         <TD>lpd://<I>address</I>/pr1<BR>
 332         lpd://<I>address</I>/pr2<BR>
 333         lpd://<I>address</I>/pr3</TD>
 334 </TR>
 335 <TR>
 336         <TD>Hewlett Packard JetDirect</TD>
 337         <TD>socket://<I>address</I>:9100<BR>
 338         socket://<I>address</I>:9101<BR>
 339         socket://<I>address</I>:9102</TD>
 340 </TR>
 341 <TR>
 342         <TD>Intel&reg; NetportExpress XL, PRO/100</TD>
 343         <TD>lpd://<I>address</I>/LPT1_PASSTHRU<BR>
 344         lpd://<I>address</I>/LPT2_PASSTHRU<BR>
 345         lpd://<I>address</I>/COM1_PASSTHRU</TD>
 346 </TR>
 347 <TR>
 348         <TD>Lexmark<SUP>TM</SUP> MarkNet</TD>
 349         <TD>lpd://<I>address</I>/ps</TD>
 350 </TR>
 351 <TR>
 352         <TD>Linksys EtherFast&reg;<BR>
 353         <A HREF="#LINKSYS">(see directions)</A></TD>
 354         <TD>socket://<I>address</I>:4010<BR>
 355         socket://<I>address</I>:4020<BR>
 356         socket://<I>address</I>:4030</TD>
 357 </TR>
 358 <TR>
 359         <TD>Linksys PSUS4</TD>
 360         <TD>lpd://<I>address</I>/lp</TD>
 361 </TR>
 362 <TR>
 363         <TD>Kodak&reg;</TD>
 364         <TD>lpd://<I>address</I>/ps</TD>
 365 </TR>
 366 <TR>
 367         <TD>Netgear WGPS606</TD>
 368         <TD>lpd://<I>address</I>/L1<BR>
 369         lpd://<I>address</I>/L2</TD>
 370 </TR>
 371 <TR>
 372         <TD>QMS&reg; CrownNet<SUP>TM</SUP></TD>
 373         <TD>lpd://<I>address</I>/ps</TD>
 374 </TR>
 375 <TR>
 376         <TD>Tektronix&reg; PhaserShare<SUP>TM</SUP></TD>
 377         <TD>socket://<I>address</I>:9100</TD>
 378 </TR>
 379 <TR>
 380         <TD>XEROX&reg; 4512 NIC</TD>
 381         <TD>lpd://<I>address</I>/PORT1</TD>
 382 </TR>
 383 <TR>
 384         <TD>XEROX&reg; XNIC</TD>
 385         <TD>lpd://<I>address</I>/PASSTHRU</TD>
 386 </TR>
 387 <TR>
 388         <TD>XEROX&reg; (most others)</TD>
 389         <TD>socket://<I>address</I>:5503</TD>
 390 </TR>
 391 </TBODY>
 392 </TABLE></DIV>
 393
 394
 395 <H2 CLASS="title"><A NAME="SNMP">Troubleshooting SNMP Discovery Problems</A></H2>
 396
 397 <P>Whenever you view the administration web page or a list of supported device URIs, the <tt>snmp</tt> backend will probe the local network(s) using Simple Network Management Protocol (SNMP) broadcasts. Printers that respond to these broadcasts are then interrogated for the make and model and supported protocols, yielding a device URI that can be used to add the printer.</P>
 398
 399 <P>That said, the SNMP requests sometimes expose problems in vendor SNMP or IPP implementations. If you are experiencing long delays in loading the CUPS web interface administration page, or if you don't see your printer listed, the following instructions will help you to diagnose those problems and/or provide important feedback to the CUPS developers so that we can correct problems and improve the SNMP backend in future releases.</P>
 400
 401 <H3>Quick Fixes</H3>
 402
 403 <P>If you don't use "public" as your community name, create a text file called <VAR>/etc/cups/snmp.conf</VAR> and put the following line in it:</P>
 404
 405 <PRE CLASS="command">
 406 Community <I>your community name</I>
 407 </PRE>
 408
 409 <P>If you have more than one community name, list them all on separate lines.</P>
 410
 411 <P>If you don't support SNMP v1 on your network, you are currently "out of luck". That said, we will be adding v2, v2c, and v3 support in future CUPS releases once we have a handle on the actual requirements people have for such things. Please file or update an <A HREF="http://www.cups.org/str.php">SNMP enhancement request</A> with <em>specific</em> requirements you have - what you need supported, why you need it supported, and how you would like to see the functionality provided/exposed - so that we can do it "right" the first time.</P>
 412
 413 <H3>Basic Debugging</H3>
 414
 415 <P>The SNMP backend supports a debugging mode that is activated by running it from a shell prompt. If you are using Bash (/bin/bash), Bourne shell (/bin/sh), Korn shell (/bin/ksh), or Z shell (/bin/zsh), you can run the following command to get a verbose log of the SNMP backend:</P>
 416
 417 <PRE CLASS="command">
 418 CUPS_DEBUG_LEVEL=2 /usr/lib/cups/backend/snmp 2>&amp;1 | tee snmp.log
 419 </PRE>
 420
 421 <P>For C shell (/bin/csh) and TCsh (/bin/tcsh), use the following command instead:</P>
 422
 423 <PRE CLASS="command">
 424 (setenv CUPS_DEBUG_LEVEL 2; /usr/lib/cups/backend/snmp) |& tee snmp.log
 425 </PRE>
 426
 427 <P>On MacOS X you'll find the SNMP backend in /usr/libexec/cups/backend instead:</P>
 428
 429 <PRE CLASS="command">
 430 CUPS_DEBUG_LEVEL=2 /usr/libexec/cups/backend/snmp 2>&amp;1 | tee snmp.log
 431 </PRE>
 432
 433 <P>The output will look something like this:</P>
 434
 435 <PRE STYLE="margin-left: 36pt">
 436  1  INFO: Using default SNMP Address @LOCAL
 437  2  INFO: Using default SNMP Community public
 438  3  DEBUG: Scanning for devices in "public" via "@LOCAL"...
 439  4  DEBUG: 0.000 Sending 46 bytes to 192.168.2.255...
 440  5  DEBUG: SEQUENCE 44 bytes
 441  6  DEBUG:     INTEGER 1 bytes 0
 442  7  DEBUG:     OCTET STRING 6 bytes "public"
 443  8  DEBUG:     Get-Request-PDU 31 bytes
 444  9  DEBUG:         INTEGER 4 bytes 1149539174
 445 10  DEBUG:         INTEGER 1 bytes 0
 446 11  DEBUG:         INTEGER 1 bytes 0
 447 12  DEBUG:         SEQUENCE 17 bytes
 448 13  DEBUG:             SEQUENCE 15 bytes
 449 14  DEBUG:                 OID 11 bytes .1.3.6.1.2.1.25.3.2.1.2.1
 450 15  DEBUG:                 NULL VALUE 0 bytes
 451 16  DEBUG: 0.001 Received 55 bytes from 192.168.2.229...
 452 17  DEBUG: community="public"
 453 18  DEBUG: request-id=1149539174
 454 19  DEBUG: error-status=0
 455 20  DEBUG: SEQUENCE 53 bytes
 456 21  DEBUG:     INTEGER 1 bytes 0
 457 22  DEBUG:     OCTET STRING 6 bytes "public"
 458 23  DEBUG:     Get-Response-PDU 40 bytes
 459 24  DEBUG:         INTEGER 4 bytes 1149539174
 460 25  DEBUG:         INTEGER 1 bytes 0
 461 26  DEBUG:         INTEGER 1 bytes 0
 462 27  DEBUG:         SEQUENCE 26 bytes
 463 28  DEBUG:             SEQUENCE 24 bytes
 464 29  DEBUG:                 OID 11 bytes .1.3.6.1.2.1.25.3.2.1.2.1
 465 30  DEBUG:                 OID 9 bytes .1.3.6.1.2.1.25.3.1.5
 466 31  DEBUG: add_cache(addr=0xbfffe170, addrname="192.168.2.229",
 467     uri="(null)", id="(null)", make_and_model="(null)")
 468 32  DEBUG: 0.002 Sending 46 bytes to 192.168.2.229...
 469 33  DEBUG: SEQUENCE 44 bytes
 470 34  DEBUG:     INTEGER 1 bytes 0
 471 35  DEBUG:     OCTET STRING 6 bytes "public"
 472 36  DEBUG:     Get-Request-PDU 31 bytes
 473 37  DEBUG:         INTEGER 4 bytes 1149539175
 474 38  DEBUG:         INTEGER 1 bytes 0
 475 39  DEBUG:         INTEGER 1 bytes 0
 476 40  DEBUG:         SEQUENCE 17 bytes
 477 41  DEBUG:             SEQUENCE 15 bytes
 478 42  DEBUG:                 OID 11 bytes .1.3.6.1.2.1.25.3.2.1.3.1
 479 43  DEBUG:                 NULL VALUE 0 bytes
 480 44  DEBUG: 0.003 Received 69 bytes from 192.168.2.229...
 481 45  DEBUG: community="public"
 482 46  DEBUG: request-id=1149539175
 483 47  DEBUG: error-status=0
 484 48  DEBUG: SEQUENCE 67 bytes
 485 49  DEBUG:     INTEGER 1 bytes 0
 486 50  DEBUG:     OCTET STRING 6 bytes "public"
 487 51  DEBUG:     Get-Response-PDU 54 bytes
 488 52  DEBUG:         INTEGER 4 bytes 1149539175
 489 53  DEBUG:         INTEGER 1 bytes 0
 490 54  DEBUG:         INTEGER 1 bytes 0
 491 55  DEBUG:         SEQUENCE 40 bytes
 492 56  DEBUG:             SEQUENCE 38 bytes
 493 57  DEBUG:                 OID 11 bytes .1.3.6.1.2.1.25.3.2.1.3.1
 494 58  DEBUG:                 OCTET STRING 23 bytes "HP LaserJet 4000
 495     Series"
 496 59  DEBUG: 1.001 Probing 192.168.2.229...
 497 60  DEBUG: 1.001 Trying socket://192.168.2.229:9100...
 498 61  DEBUG: 192.168.2.229 supports AppSocket!
 499 62  DEBUG: 1.002 Scan complete!
 500 63  network socket://192.168.2.229 "HP LaserJet 4000 Series"
 501     "HP LaserJet 4000 Series 192.168.2.229" ""
 502 </PRE>
 503
 504 <H3>Dissecting the Output</H3>
 505
 506 <P>The first two lines are just informational and let you know that the default community name and address are being used. Lines 3-15 contain the initial SNMP query for the device type OID (.1.3.6.1.2.1.25.3.2.1.2.1) from the Host MIB.</P>
 507
 508 <P>Lines 16-31 show the response we got from an HP LaserJet 4000 network printer. At this point we discover that it is a printer device and then send another SNMP query (lines 32-43) for the device description OID (.1.3.6.1.2.1.25.3.2.1.3.1) from the Host MIB as well.</P>
 509
 510 <P>Lines 44-58 show the response to the device description query, which tells us that this is an HP LaserJet 4000 Series printer.</P>
 511
 512 <P>On line 59 we start our active connection probe and discover that this print server supports the AppSocket (JetDirect) protocol on port 9100.</P>
 513
 514 <P>Finally, line 63 shows the device information line for the print server that is sent to CUPS.</P>
 515
 516 <H3>Reporting Problems</H3>
 517
 518 If you don't see your printer listed, or the wrong information is listed, then you need to gather more information on the printer. The easiest way to do this is to run the snmpwalk command:
 519
 520 <PRE CLASS="command">
 521 snmpwalk -Cc -v 1 -c public <I>ip-address</I> | tee snmpwalk.log
 522 </PRE>
 523
 524 <P>where "ip-address" is the IP address of the printer or print server. You should see a <em>lot</em> of values stream by - the ones you want to see are:</P>
 525
 526 <PRE STYLE="margin-left: 36pt">
 527 HOST-RESOURCES-MIB::hrDeviceType.1 = OID: HOST-RESOURCES-TYPES::hrDevicePrinter
 528 HOST-RESOURCES-MIB::hrDeviceDescr.1 = STRING: HP LaserJet 4000 Series
 529 </PRE>
 530
 531 <P>The hrDeviceType line should show hrDevicePrinter; if not, then your printer or print server doesn't identify itself as a printer. The hrDeviceDescr line should provide a human-readable string for the make and model of the printer, although in some cases you'll just see something less useful like "Axis OfficeBASIC Parallel Print Server".</P>
 532
 533 <P>Once you have collected the snmpwalk output, you should go to the  <A HREF="http://www.cups.org/str.php">CUPS Bugs &amp; Features page</A> to submit a feature request to support your printer or print server. Be sure to attach those two log files you created - they will help us to identify the SNMP values we need to look for.</P>
 534
 535
 536 <H2 CLASS="title"><A NAME="SERVERS">Configuring Print Servers</A></H2>
 537
 538 <H3><A NAME="AXIS">Configuring Axis Print Servers</A></H3>
 539
 540 <P>The Axis print servers can be configured using BOOTP or DHCP. However, on models that do not provide IPP support an additional step must be performed to configure the TCP/IP portion of the print server for use with CUPS.</P>
 541
 542 <P>Each print server contains a configuration file named <VAR>config</VAR> that contains a list of network parameters used by the server. To modify this file you must first download it from the print server using the <TT>ftp(1)</TT> program:</P>
 543
 544 <PRE CLASS="command">
 545 <KBD>ftp ip-address</KBD>
 546 Connected to ip-address.
 547 220 Axis NPS ### FTP Printer Server V#.## MON DD YEAR ready.
 548 ftp> <KBD>user root</KBD>
 549 331 User name ok, need password
 550 Password: <KBD>pass</KBD> <I>(this is not echoed)</I>
 551 230 User logged in
 552 ftp> <KBD>get config</KBD>
 553 local: config remote: config
 554 200 PORT command successful.
 555 150 Opening data connection for config (192,0,2,2),
 556 (mode ascii).
 557 226 Transfer complete.
 558 ##### bytes received in #.## seconds (##### Kbytes/s)
 559 ftp> <KBD>quit</KBD>
 560 221 Goodbye.
 561 </PRE>
 562
 563 <P>Next, edit the file with your favorite text editor and locate the lines beginning with:</P>
 564
 565 <PRE CLASS="command">
 566 RTN_OPT.     : YES
 567 RTEL_PR1.    : 0
 568 RTEL_PR2.    : 0
 569 RTEL_PR3.    : 0
 570 RTEL_PR4.    : 0
 571 RTEL_PR5.    : 0
 572 RTEL_PR6.    : 0
 573 RTEL_PR7.    : 0
 574 RTEL_PR8.    : 0
 575 </PRE>
 576
 577 <P>Change the <TT>RTN_OPT</TT> line to read:</P>
 578
 579 <PRE CLASS="command">
 580 RTN_OPT.     : <KBD>NO</KBD>
 581 </PRE>
 582
 583 <P>This disables the Reverse TELNET protocol and enables the standard TELNET protocol on the print server. Next, assign a port number for each parallel and serial port on the server as follows:</P>
 584
 585 <PRE CLASS="command">
 586 RTEL_PR1.    : <KBD>9100</KBD>
 587 RTEL_PR2.    : <KBD>9101</KBD>
 588 RTEL_PR3.    : <KBD>9102</KBD>
 589 RTEL_PR4.    : <KBD>9103</KBD>
 590 RTEL_PR5.    : <KBD>9104</KBD>
 591 RTEL_PR6.    : <KBD>9105</KBD>
 592 RTEL_PR7.    : <KBD>9106</KBD>
 593 RTEL_PR8.    : <KBD>9107</KBD>
 594 </PRE>
 595
 596 <P>This essentially makes the Axis print server look like a Hewlett Packard JetDirect EX print server. Save the file and then upload the new <VAR>config</VAR> file using the <TT>ftp</TT> command:</P>
 597
 598 <PRE CLASS="command">
 599 <KBD>ftp ip-address</KBD>
 600 Connected to ip-address.
 601 220 Axis NPS ### FTP Printer Server V#.## MON DD YEAR ready.
 602 ftp> <KBD>user root</KBD>
 603 331 User name ok, need password
 604 Password: <KBD>pass</KBD> <I>(this is not echoed)</I>
 605 230 User logged in
 606 ftp> <KBD>put config CONFIG</KBD>
 607 local: config remote: CONFIG
 608 200 PORT command successful.
 609 150 Opening data connection for config (192,0,2,2), (mode ascii).
 610 226 Transfer complete.
 611 ##### bytes received in #.## seconds (##### Kbytes/s)
 612 ftp> <KBD>get hardreset</KBD>
 613 local: hardreset remote: hardreset
 614 200 PORT command successful.
 615 421 Axis NPS ### hard reset, closing connection.
 616 ftp> <KBD>quit</KBD>
 617 221 Goodbye.
 618 </PRE>
 619
 620 <P>Your Axis print server is now ready for use!</P>
 621
 622 <H3><A NAME="LINKSYS">Configuring Linksys Print Servers</A></H3>
 623
 624 <P>The Linksys print servers can be configured using BOOTP or DHCP. Like older Axis print servers, an additional step must be performed to configure the TCP/IP portion of the print server for use with CUPS.</P>
 625
 626 <P>Each print server contains a configuration file named <VAR>CONFIG</VAR> that contains a list of network parameters used by the server. To modify this file you must first download it from the print server using the <TT>ftp(1)</TT> program:</P>
 627
 628 <PRE CLASS="command">
 629 <KBD>ftp -n ip-address</KBD>
 630 Connected to ip-address.
 631 220 Print Server Ready.
 632 Remote system type is Print.
 633 ftp> <KBD>get CONFIG</KBD>
 634 local: CONFIG remote: CONFIG
 635 200 Command OK.
 636 150 Open ASCII Mode Connection.
 637 WARNING! 68 bare linefeeds received in ASCII mode
 638 File may not have transferred correctly.
 639 226 Transfer complete.
 640 ##### bytes received in #.## seconds (##### Kbytes/s)
 641 ftp> <KBD>quit</KBD>
 642 221 Goodbye.
 643 </PRE>
 644
 645 <P>Next, edit the file with your favorite text editor and locate the lines beginning with:</P>
 646
 647 <PRE CLASS="command">
 648 0100 L1_PROUT:P1
 649 0120 L2_PROUT:P1
 650 0140 L3_PROUT:P1
 651 </PRE>
 652
 653 <P>Change the port number for each parallel and serial port on the server as follows:</P>
 654
 655 <PRE CLASS="command">
 656 0100 L1_PROUT:<KBD>P1</KBD>
 657 0120 L2_PROUT:<KBD>P2</KBD>
 658 0140 L3_PROUT:<KBD>P3</KBD>
 659 </PRE>
 660
 661 <P>This maps each virtual printer with a physical port. Save the file and then upload the new <VAR>CONFIG</VAR> file using the <TT>ftp</TT> command:</P>
 662
 663 <PRE CLASS="command">
 664 <KBD>ftp -n ip-address</KBD>
 665 Connected to ip-address.
 666 220 Print Server Ready.
 667 Remote system type is Print.
 668 ftp> <KBD>put CONFIG</KBD>
 669 local: CONFIG remote: CONFIG
 670 200 Command OK.
 671 150 Open ASCII Mode Connection.
 672 226 Transfer complete.
 673 ##### bytes received in #.## seconds (##### Kbytes/s)
 674 ftp> <KBD>quit</KBD>
 675 221 Goodbye.
 676 </PRE>
 677
 678 <P>Your Linksys print server is now ready for use!</P>
 679
 680 </BODY>
 681 </HTML>