TROY Group 100S manual SET Service BINARYP1 EOT

Section 9 Troubleshooting

TCP/IP Trouble- shooting (cont.)

Also verify that the host computer and the print server are either on the same subnet (for example, if the print server has a subnet mask of 255.255.255.0, the host must have the same subnet mask) or that the router is properly configured to pass data between the two devices.

Make sure that the /etc/printcap file (if applicable) is typed in correctly. In particular, look for missing ":" and "\" characters, because a small error anywhere in the file can have major consequences. Also check the /usr/spool directory to make sure that you have created a valid spool directory.

If you are using a Berkeley-based UNIX, make sure that the daemon is started on Berkeley based systems with the command lpc start printer, where printer is the name of the local print queue.

If you are using an AT&T-based UNIX, make sure the printer is enabled (enable printer, where printer is the name of the local print queue).

Make sure that the lpr/lpd remote line printer service are running on the host computer (refer to your host computer documentation for information on how to do this).

If jobs are run together or do not eject from the printer, try setting the service (remote printer) with EOT set to the appropriate printer reset string. This string is number 4 (<ESC>%-12345X) for all newer HP printers. For example:

SET SERVICE BINARY_P1 EOT 4

NOTE: Do not use the above command if you have a LaserJet II, IID, III, or IIID printer. Instead, use an EOT 2 for PCL jobs or 3 for PostScript jobs.

If the lines of a text file are staggered, make sure that you have specified a remote printer (rp) name of TEXT in your /etc/printcap file.If you are having trouble printing long jobs (over 1MB), add the line mx#0 to your /etc/printcap file entry.

NOTE: Sun Solaris has a bug with lpr/lpd printing and long jobs. This bug affects any diskless print server, not just TROY. The solution is to use the HP JetDirect UNIX host printing utilities as described in the Raw TCP Port section at the end of Section 3.

If you are using the raw TCP port and are experiencing intermittent queue stalling problems, make sure that queueing is enabled on the service (do a SHOW SERVICE command from the remote console, and note if "Q" is listed in the OPT column for the desired service). If it is not, enable queueing with the command SET SERVICE servicename QUE ENA command.

PocketPro 100S Administrator’s Guide -- Document #40165-110 Rev. A 9-5