Brother International HL-6050DW Network Users Manual - English - Page 118

UNIX® Troubleshooting, con the etc/printcap file for lpd operation, then you might

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

Page 118 highlights

4 If you used rarp, make sure that you started the rarp daemon on any workstation using the rarpd, rarpd-a, or equivalent command. Verify that the /etc/ethers file contains the correct Ethernet address and that the print server name matches the name in the /etc/hosts file. 5 If you used bootp, make sure that you started the bootp daemon on any UNIX® workstation and bootp is enabled (i.e., the "#" is removed from the bootp entry) in the /etc/bootptab file is correctly configured. 6 Also verify that host computer and the print server are either on the same subnet, otherwise that the router is properly configured to pass data between the two devices. 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). TROUBLESHOOTING 10 - 11

  • 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
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
TROUBLESHOOTING 10 - 11
4
If you used rarp, make sure that you started the rarp daemon on
any workstation using the rarpd, rarpd-a, or equivalent
command. Verify that the
/etc/ethers
file contains the
correct Ethernet address and that the print server name
matches the name in the
/etc/hosts
file.
5
If you used bootp, make sure that you started the bootp daemon
on any UNIX
®
workstation and bootp is enabled (i.e., the "#" is
removed from the bootp entry) in the
/etc/bootptab
file is
correctly configured.
6
Also verify that host computer and the print server are either on
the same subnet, otherwise that the router is properly
configured to pass data between the two devices.
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).