Brother International DCP 8045D Network Users Manual - English - Page 137

Tcp/ip Troubleshooting, Are The Biggest Cause Of Tcp/ip Printing Problems.

Get Brother International DCP 8045D - B/W Laser - All-in-One PDF manuals and user guides
UPC - 012502610335
View all Brother International DCP 8045D manuals
Add to My Manuals
Save this manual to your list of manuals

Page 137 highlights

TCP/IP Troubleshooting If you are using TCP/IP and cannot print to the Print/Fax server and you have checked the hardware and network as described in the previous steps, then check the following: It is always a good idea to try following in order to eliminate the possibility of setup errors. Turning off the printer and then on again, Deleting and recreating the Print server and creating 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/ Fax 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 Make sure that the TCP/IP protocol of the Print/Fax server is enabled. 3 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/Fax server name matches the name in the /etc/hosts file. 4 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. 5 Also verify that host computer and the Print/Fax 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. 13 - 5 TROUBLESHOOTING

  • 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
13 - 5 TROUBLESHOOTING
TCP/IP Troubleshooting
If you are using TCP/IP and cannot print to the Print/Fax server and
you have checked the hardware and network as described in the
previous steps, then check the following:
Turning off the printer and then on again, Deleting and recreating the Print server and
creating 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/
Fax 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
Make sure that the TCP/IP protocol of the
Print/Fax
server is
enabled.
3
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/Fax server name
matches the name in the
/etc/hosts
file.
4
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.
5
Also verify that host computer and the Print/Fax 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.
It is always a good idea to try following in order to eliminate
the possibility of setup errors.