Windows Nt/Lan Server Troubleshooting - Brother NC-series User Manual

9. 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).
10. 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).
11. If you cannot print from DEC TCP/IP Services 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.
12. If you are having trouble printing more than one job at a time, try
increasing the IP timeout using the SET IP TIMEOUT command.
13. 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 BRO_xxxxxx_P1 EOT 2
14. 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 BRO_xxxxxx_P1 EOT 3
15. 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.
16. If you are having trouble printing long jobs (over 1MB), add the line
mx#0 to your /etc/printcap file entry. If you are using Sun
Solaris V2.4 or earlier, there is a bug with long print jobs on any
diskless print server, including the print server.

Windows NT/LAN Server Troubleshooting

If you are having trouble printing with Windows NT or LAN Server, check
the following:
1. Make sure that you can ping the print server using the DOS or OS/2
command PING ipaddress , where ipaddress is the IP address of
the print server. If you cannot ping it, you will not be able to print.
2. Make sure that the TCP/IP protocol is enabled.
3. Make sure that TCP/IP is installed and running on the Windows NT
system or the LAN Server file server.
CHAPTER 12 TROUBLESHOOTING
12-7