Brother International HL 1270N Network Users Manual - English - Page 97

UNIX Troubleshooting

Get Brother International HL 1270N - B/W Laser Printer PDF manuals and user guides
UPC - 012502526001
View all Brother International HL 1270N manuals
Add to My Manuals
Save this manual to your list of manuals

Page 97 highlights

UNIX Troubleshooting 1. 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. 2. If you are using a Linux operating system, the X-Window Print tool program that is included with Linux may not properly configure the etc/printcap file for lpd operation, then you might also edit the etc/printcap file and change the following line in the entry for the printer. if :lp = /dev/null: \ then to :lp = :\ 3. 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. 4. 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). 5. 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). 6. If you are having trouble printing more than one job at a time, try increasing the IP timeout using the SET IP TIMEOUT command or using BRAdmin32. 7. If text or PCL jobs are run together, try setting the service (remote printer) with EOT set to string number 2 (E). For example: SET SERVICE BRN_xxxxxx_P1 EOT 2 8. If PostScript jobs fail to print or are run together, try setting the service (remote printer) with EOT set to string number 3 (control-D). For example: SET SERVICE BRN_xxxxxx_P1 EOT 3 9. 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. 10. If you are using Sun Solaris V2.4 or earlier, there is a bug which causes long print jobs to fail when using a print server. If you are having trouble printing long jobs (over 1MB), add the line mx#0 to your etc/printcap file entry. 10-5

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
10-5
UNIX Troubleshooting
1.
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.
2.
If you are using a Linux operating system, the X-Window Print tool program that is
included with Linux may not properly configure the etc/printcap file for lpd operation,
then you might also edit the etc/printcap file and change the following line in the entry
for the printer.
if
:lp = /dev/null: \
then to
:lp = :\
3.
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.
4.
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).
5.
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).
6.
If you are having trouble printing more than one job at a time, try increasing the IP
timeout using the SET IP TIMEOUT command or using BRAdmin32.
7.
If text or PCL jobs are run together, try setting the service (remote printer) with EOT
set to string number 2 (<ESC>E). For example:
SET SERVICE BRN_xxxxxx_P1 EOT 2
8.
If PostScript jobs fail to print or are run together, try setting the service (remote printer)
with EOT set to string number 3 (control-D). For example:
SET SERVICE BRN_xxxxxx_P1 EOT 3
9.
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.
10.
If you are using Sun Solaris V2.4 or earlier, there is a bug which causes long print jobs
to fail when using a print server. If you are having trouble printing long jobs (over
1MB), add the line
mx#0
to your
etc/printcap
file entry.