User manual OKI OKIPAGE 6EX NETWORK CARD

[. . . ] OkiLAN 6010e® Pocket Print Server User's Guide High Performance Ethernet Network Print Server Copyright and Trademark Information Printing History Every effort has been made to ensure that the information in this document is complete, accurate, and up-to-date. Okidata assumes no responsibility for the results of errors beyond its control. Okidata also cannot guarantee that changes in products made by other manufacturers and referred to in this handbook will not affect the applicability of the information in it. This handbook is subject to change without notification. ©1998 by Okidata. [. . . ] If your specific system is not addressed in this appendix, follow the instructions outlined below. You should also refer to your operating system or computer manual for information about configuring remote network printing. If you are still unable to configure your computer system to print to the OkiLAN 6010e, contact Okidata Customer Support at 1-800-OKIDATA (1-800-654-3282). OKI OkiLAN 6010e User's Guide IV - 17 TCP/IP Section IV - TCP/IP Configuring for TCP/IP Network Printing Most computers that support TCP/IP network printing use the Remote Line Printer Daemon (LPD) protocol. This protocol was originally part of the Berkeley Software Distribution (BSD) version of the UNIX operating system. Remote LPD was quickly adopted as a de facto standard. As a result, Remote LPD is now supported by most versions of the UNIX operating system and by many TCP/IP packages available for other operating systems. Configuration of Remote LPD printing varies among vendors who supply TCP/IP. You may also use the File Transfer Protocol (FTP) for printing. Typically FTP is used to transfer files between computers on a TCP/IP network. The OkiLAN 6010e simply prints the files it receives from FTP. Remote Print Queue Name The Remote Print Queue Name determines which printer port will service the print job. The Remote Print Queue Name may also be used to specify ASCII print jobs. Both Remote LPD and FTP have provisions for specifying a Remote Print Queue Name. The OkiLAN 6010e looks at the last character of the Remote Print Queue Name to determine which printer port will service the print job. All Remote Print Queue Names should end with the number 1, 2, 3 or 4. If a number is not specified, the OkiLAN 6010e will use printer port 1. IV - 18 OKI OkiLAN 6010e User's Guide Section IV - TCP/IP The OkiLAN 6010e is designed to handle many different types of printers and print data. Typically you will select the printer type for your printer in telnet under the Configure Port option. However, if you are connecting to an ASCII printer, you may wish to use the OkiLAN 6010e to format the print data for your printer. The OkiLAN 6010e will parse the remote queue name and search for certain characters at the end which tell how to convert an ASCII print job. The print server uses FF, LF and NF as ASCII conversion specifiers and uses the last number as an output port. The FF, LF and NF specifiers must be the last letters in the queue name. Example: LaserWriterFF, SalesColorLaserNF, ChemDeptLF2 FF Use the FF suffix at the end of the Remote Print Queue Name, before the port number. Example: queueFF2 If the last character in the print job is not a form feed, the OkiLAN 6010e appends a form feed. [. . . ] This feature is enabled on the local subnet 7. You will now be able to use OkiLAN 6010e Connect for TCP/IP. Whenever you print to the printer configured with OkiLAN 6010e Connect, your print job will go directly to the OkiLAN 6010e print server port. Port Settings If you have printing problems while using the OkiLAN 6010e Connect printing port, you may check the status of the port by selecting Port Settings under the Details tab in the Properties screen. OKI OkiLAN 6010e User's Guide V - 23 Windows Printing Section V - Windows Printing Section V - Windows Printing OkiLAN 6010e Connect for DLC OkiLAN 6010e Connect for Data-Link Control (DLC) provides a direct printing solution for users in Microsoft Windows 95 serverless environments with the DLC/ LLC protocol. [. . . ]