Lantronix MPS100 EPS Reference Manual - Page 203

RARP Troubleshooting, Printing Problems, PostScript Problems

Page 203 highlights

Troubleshooting RARP Troubleshooting B.4 RARP Troubleshooting Table B-4: RARP Troubleshooting Area to Check Explanation The Server name and hardware address in the host's /etc/ethers file The Server name and IP address in the /etc/hosts file The operating system The Server name and hardware address must be in this file for the host to answer a RARP request. The Server name and IP address must be in this file for the host to answer a RARP request. Many operating systems do not start a RARP server at boot time. Check the host's RARPD documentation for details, or use the ps command to see if there is a RARPD process running. B.5 Printing Problems Table B-5: General Printing Problems Area to Check Explanation Physical connections Service characteristics The IP address Queue Status and Port counters To test a non-PostScript printer, use the Test Port Server Count 100 command. This command will send 100 lines of test data out the parallel port so you can see if the printer is receiving data. Use the Show Service Local Characteristics command from the Server Local> prompt to see if the desired service is available and to verify that the appropriate protocols are enabled on the service. The IP address must be unique on the network. Many problems can occur when there are duplicate IP addresses. Use the Monitor Queue command to ensure queue entries appear in the job list. Use the Monitor Port 1 Counters command to verify that the counter is incrementing with each job. If it is not, verify the connection between the Server and the printer. B.6 PostScript Problems B-3

  • 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

Troubleshooting
RARP Troubleshooting
B-
3
B.4
RARP Troubleshooting
B.5
Printing Problems
B.6
PostScript Problems
Table B-4:
RARP Troubleshooting
Area to Check
Explanation
The Server name and hardware
address in the host’s
/etc/ethers
file
The Server name and hardware address must be
in this file for the host to answer a RARP
request.
The Server name and IP address
in the
/etc/hosts
file
The Server name and IP address must be in this
file for the host to answer a RARP request.
The operating system
Many operating systems do not start a RARP
server at boot time. Check the host’s RARPD
documentation for details, or use the
ps
com-
mand to see if there is a RARPD process run-
ning.
Table B-5:
General Printing Problems
Area to Check
Explanation
Physical connections
To test a non-PostScript printer, use the
Test Port Server
Count 100
command. This command will send 100 lines of
test data out the parallel port so you can see if the printer is
receiving data.
Service characteristics
Use the
Show Service Local Characteristics
command
from the Server Local> prompt to see if the desired service
is available and to verify that the appropriate protocols are
enabled on the service.
The IP address
The IP address must be unique on the network. Many prob-
lems can occur when there are duplicate IP addresses.
Queue Status and Port
counters
Use the
Monitor Queue
command to ensure queue entries
appear in the job list.
Use the
Monitor Port 1 Counters
command to verify that
the counter is incrementing with each job. If it is not, verify
the connection between the Server and the printer.