Brother International 4200CN Network Users Manual - English - Page 58

UNIX Troubleshooting, If you are using an AT&T-based UNIX

Get Brother International 4200CN - Color Laser Printer PDF manuals and user guides
UPC - 012502607458
View all Brother International 4200CN manuals
Add to My Manuals
Save this manual to your list of manuals

Page 58 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 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. 7 If you cannot print from DEC TCP/IP Service for VMS (UCX), make sure that you have version 2.0B or later of this software, because earlier versions will not work with Brother print servers. TROUBLESHOOTING 10 - 4

  • 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
TROUBLESHOOTING
10 - 4
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 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.
7
If you cannot print from DEC TCP/IP Service for VMS (UCX), make sure that you have version 2.0B
or later of this software, because earlier versions will not work with Brother print servers.