Brother International HL 1850 Service Manual - Page 227

TCP/IP, Troubleshooting

Page 227 highlights

HL-1850/1870N SERVICE MANUAL 8.3 TCP/IP Troubleshooting If you are using TCP/IP and cannot print to the print server and you have checked the hardware and network as described in the previous steps, then check the following: NOTE: It is always a good idea to try the following in order to eliminate the possibility of setup errors. • Turn off the printer and then on again, • Delete and recreate the print server and create a new print queue in order to eliminate the possibility of setup errors. (1) The problem may be the result of mismatched or duplicate IP address. Verify that the IP address is correctly loaded into the print server (via the configuration page). Make sure that no other nodes on the network have this address (DUPLICATE IP ADDRESS ARE THE BIGGEST CAUSE OF TCP/IP PRINTING PROBLEMS). (2) If you used BRCONFIG to enter the IP address, make sure that you exited the remote console properly with a CTRL-D or EXIT and that you turned the printer off and then on again (it may take up to two minutes for the IP address to take effect). (3) Make sure that the TCP/IP protocol of the print server is enabled. (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 on the same subnet, if the printer is on a different subnet, make sure that the router is configured correctly and ensure that the GATEWAY address is configured to match the IP address of the router. 8.4 UNIX Troubleshooting (1) Make sure that the /etc/printcap file (if applicable) is typed in correctly. In particular, look for missing ":" and "t" 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 1pd 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 Ipc start printer, where printer is the name of the local print queue. 6-61

  • 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
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277

HL
-1850/1870N
SERVICE
MANUAL
8.3
TCP/IP
Troubleshooting
If
you
are
using
TCP/IP
and
cannot
print
to
the
print
server
and
you
have
checked
the
hardware
and
network
as
described
in
the
previous
steps,
then
check
the
following:
NOTE:
It
is
always
a
good
idea
to
try
the
following
in
order
to
eliminate
the
possibility
of
setup
errors.
Turn
off
the
printer
and
then
on
again,
Delete
and
recreate
the
print
server
and
create
a
new
print
queue
in
order
to
eliminate
the
possibility
of
setup
errors.
(1)
The
problem
may
be
the
result
of
mismatched
or
duplicate
IP
address.
Verify
that
the
IP
address
is
correctly
loaded
into
the
print
server
(via
the
configuration
page).
Make
sure
that
no
other
nodes
on
the
network
have
this
address
(DUPLICATE
IP
ADDRESS
ARE
THE
BIGGEST
CAUSE
OF
TCP/IP
PRINTING
PROBLEMS).
(2)
If
you
used
BRCONFIG
to
enter
the
IP
address,
make
sure
that
you
exited
the
remote
console
properly
with
a
CTRL
-D
or
EXIT
and
that
you
turned
the
printer
off
and
then
on
again
(it
may
take
up
to
two
minutes
for
the
IP
address
to
take
effect).
(3)
Make
sure
that
the
TCP/IP
protocol
of
the
print
server
is
enabled.
(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.
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
on
the
same
subnet,
if
the
printer
is
on
a
different
subnet,
make
sure
that
the
router
is
configured
correctly
and
ensure
that
the
GATEWAY
address
is
configured
to
match
the
IP
address
of
the
router.
(
5
)
8.4
UNIX
Troubleshooting
(1)
Make
sure
that
the
/etc/printcap
file
(if
applicable)
is
typed
in
correctly.
In
particular,
look
for
missing
":"
and
"t"
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
1pd
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
Ipc
start
printer,
where
printer
is
the
name
of
the
local
print
queue.
6-61