Normally, when you configure a PrintKit queue, you can use KITCP's interactive configuration dialog to supply correct settings for the queue's communications attributes. Once you indicate the printer model for the queue, PrintKit's database of model definitions supplies the correct settings for the printer in its standard network configuration.
However, when your printer is configured with a non-standard network interface, is accessed through a server system, or has other special communications requirements, you will need to override the default settings.
The following examples describe common special configurations, and discuss the adjustments required for PrintKit to work correctly with them.
This is a DRAFT document. To the best of our knowledge, the information it provides is correct. However, many of the configuration settings cover entire product families, and vendors update their products on a regular basis, making it difficult to capture complete and current information. If you are not successful in making PrintKit to work with your configuration, please contact us.
The Emulex NetJet MIO interface card for Hewlett-Packard printers provide additional protocol support, LAT and lpr/lpd in particular. Their settings for the TCP/IP socket protocol are slightly different than the standard JetDirect interface.
Configuration of a NetJet interface using the LAT protocol requires the following settings:
| Protocol | LAT |
| LAT node name | NJAxxxxxx |
| LAT port name | "PORT_1" |
| Status returned | STATUS |
| Synchronization | SYNCH |
Notes:
Use the LAT node name of your printer in place of NJAxxxxxx – it appears on the configuration page printed when you perform a printer self-test. The xxxxxx field is the last six digits of the interface Ethernet address.
Configuration of a NetJet interface using the TCP/IP socket protocol requires the following settings:
| Protocol | TCP_SOCKET |
| IP address | n.n.n.n |
| Port number | 2501 |
| Status returned | STATUS |
| Synchronization | SYNCH |
Notes:
Use the TCP/IP address of your printer in place of n.n.n.n – it appears on the configuration page printed when you perform a printer self-test.
Configuration of a NetJet interface using the lpr/lpd protocol requires the following settings:
| Protocol | TCP_LPR |
| IP address | n.n.n.n |
| Remote lpr queue | "PASSTHRU" |
| Needs byte count | YES |
| Spool directory | SYS$COMMON:[SYSMGR] |
Notes:
Use the TCP/IP address of your printer in place of n.n.n.n – it appears on the configuration page printed when you perform a printer self-test.
The XCd XJet MIO and EIO network interface cards for Hewlett-Packard printers provide additional protocol support, LAT in particular.
Configuration of an XJet interface using the LAT protocol requires the following settings:
| Protocol | LAT |
| LAT node name | XCD_xxxxxx |
| LAT port name | "P1" |
| Status returned | STATUS |
| Synchronization | SYNCH |
Notes:
Use the LAT node name of your printer in place of XCD_xxxxxx – it appears on the configuration page printed when you perform a printer self-test. The xxxxxx field is the last six digits of the interface Ethernet address.
Configuration of an XJet interface using the TCP/IP Socket protocol is the same as for a standard JetDirect interface.
The Emulex NETQue print servers are external interfaces that provide network connectivity for printers with parallel connections.
What protocols (LAT, lpr/lpd, socket)???
Configuration of an NetQue interface using the TCP/IP socket protocol requires the following settings:
| Protocol | TCP_SOCKET |
| IP address | n.n.n.n |
| Port number | 2501 |
| Status returned | STATUS |
| Synchronization | SYNCH |
Notes:
Use the TCP/IP address of your print server in place of n.n.n.n.
The correct synchronization setting depends on the type of parallel connection used by your printer. For BITRONICS, which allows bi-directional communications, specify SYNCH; for CENTRONICS, which is send-only, specify ASYNCH.
TCP/IP port 2501 corresponds to parallel port 1, and 2502 to port 2.
The Hewlett-Packard JetDirect EX print servers are external interfaces that provide network connectivity for printers with parallel connections.
Configuration of an JetDirect EX interface using the TCP/IP socket protocol requires the following settings:
| Protocol | TCP_SOCKET |
| IP address | n.n.n.n |
| Port number | 9100 |
| Status returned | STATUS |
| Synchronization | SYNCH |
Notes:
Use the TCP/IP address of your print server in place of n.n.n.n – it appears on the configuration page printed when you perform a print server self-test.
To select the correct synchronization setting, check the print server configuration page to determine the type of parallel connection used by your printer. For BITRONICS, which allows bi-directional communications, specify SYNCH; for CENTRONICS, which is send-only, specify ASYNCH.
TCP/IP port 9100 corresponds to parallel port 1, 9101 to port 2, and 9102 to port 3.
The Intel NetportExpress print servers are external interfaces that provide network connectivity for printers with parallel or serial connections.
Configuration of a Netport interface using the TCP/IP socket protocol requires the following settings:
| Protocol | TCP_SOCKET |
| IP address | n.n.n.n |
| Port number | 3002 |
| Status returned | STATUS |
| Synchronization | SYNCH |
Notes:
Use the TCP/IP address of your print server in place of n.n.n.n.
The correct synchronization setting depends on the type of parallel connection used by your printer. For BITRONICS, which allows bi-directional communications, specify SYNCH; for CENTRONICS, which is send-only, specify ASYNCH.
TCP/IP port 3001 corresponds to parallel port 1, and 3002 to port 2; 2501 corresponds to the serial port.
The Lantronix EPS print servers are external interfaces that provide network connectivity for printers with parallel connections.
Configuration of an EPS interface using the TCP/IP socket protocol requires the following settings:
| Protocol | TCP_SOCKET |
| IP address | n.n.n.n |
| Port number | 3002 |
| Status returned | STATUS |
| Synchronization | SYNCH |
Notes:
Use the TCP/IP address of your print server in place of n.n.n.n.
The correct synchronization setting depends on the type of parallel connection used by your printer. For BITRONICS, which allows bi-directional communications, specify SYNCH; for CENTRONICS, which is send-only, specify ASYNCH.
TCP/IP port 3002 corresponds to parallel port 1, and 3003 to port 2.
The PrintKit software can act as an lpr/lpd client to a UNIX system acting as an lpr/lpd server.
Configuration using a UNIX lpr/lpd server requires the following settings:
| Protocol | TCP_LPR |
| IP address | n.n.n.n |
| Remote lpr queue | "remote-printer-name" |
| Needs byte count | YES |
| Spool directory | SYS$COMMON:[SYSMGR] |
Notes:
Use the TCP/IP address of your server system in place of n.n.n.n.
Set the spooled option – this allows PrintKit to calculate the job data size, required by the server.
Supply the name of the remote printer to which jobs are to be directed. Be sure to enclose the name in quotes to preserve lowercase letters.
The PrintKit software can act as an lpr/lpd client to a Windows NT system acting as an lpr/lpd server.
Configuration using a Windows NT lpr/lpd server requires the following settings:
| Protocol | TCP_LPR |
| IP address | n.n.n.n |
| Remote lpr queue | "remote-printer-name" |
| Needs byte count | YES |
| Spool directory | SYS$COMMON:[SYSMGR] |
Notes:
Use the TCP/IP address of your server system in place of n.n.n.n.
Set the spooled option – this allows PrintKit to calculate the job data size, required by the server.
Supply the name of the remove printer to which jobs are to be directed. Be sure to enclose the name in quotes to preserve lowercase letters.