Lantronix LPS1-T EPS Reference Manual - Page 96

NDS Print Queue Troubleshooting

Page 96 highlights

Troubleshooting NetWare Host Setup Table 8-1: NetWare Host Troubleshooting, cont. Things to Check Suggestion Verify that the NetWare access table will By default, only local (non-routed) file servers are scanned allow access to the specified file server. for queues. See Access Lists on page 8-1 for more informa- tion on manipulating the NetWare access lists. Verify that the login password on the Server and the queue password on the file server match. If necessary, change the password on the Server. Unless the passwords match, the Server will not be able to log into file servers to scan for jobs. Look for poor printing performance in general. If there is a significant delay between NetWare jobs, the delay may be a result of scanning too many file servers. This delay is often increased if the file servers are distributed across a wide area network. Configure the NetWare access list to only allow scanning for jobs on the file servers of interest. To configure the NetWare access list, see Access Lists on page 8-1. 8.6.2 NDS Print Queue Troubleshooting The following section assumes that the Novell queue was created using PCONSOLE's Quick Setup option. If you experience NDS printing problems, try the following steps: 1 To check that the print server has successfully attached to the queue, enter the Netstat command at the Local> prompt. This will display information about file servers, printers, and queues that the print server has found. If a queue is in JobPoll then the print server has successfully attached to the queue. 2 Type Show Protocol NetWare NDS. This command shows the tree and the context that you have configured, a failure code, and an NDS error code for each NDS server. Ensure that the tree and context are correct. The context should be where the print server object is located. The following are failure codes that may be displayed along with suggested remedies. Table 8-2: NDS Printing Errors Bit Failure Code Meaning Remedy 0 OK. None needed. 1 Print server ran out of memory. Cycle power on the box. If the problem persists, disable the unused protocols and change the NetWare access list to only include file servers which have print queues associated with them. 2, 3 Unexpected response from file server. Report the problem to Lantronix Technical Support. 4 No printers found for the print server. Check to make sure that there are printers for the print server and the printer names match the service names on the print server. 5 No queue found for the printer. Check to make sure that the printers have associated queues. 8-16

  • 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
NetWare Host Setup
8-
16
8.6.2
NDS Print Queue Troubleshooting
The following section assumes that the Novell queue was created using PCONSOLE’s Quick Setup option.
If you experience NDS printing problems, try the following steps:
1
To check that the print server has successfully attached to the queue, enter the
Netstat
command at
the Local> prompt. This will display information about file servers, printers, and queues that the print
server has found. If a queue is in JobPoll then the print server has successfully attached to the queue.
2
Type
Show Protocol NetWare NDS
. This command shows the tree and the context that you have
configured, a failure code, and an NDS error code for each NDS server. Ensure that the tree and con-
text are correct. The context should be where the print server object is located.
The following are failure codes that may be displayed along with suggested remedies.
Verify that the NetWare access table will
allow access to the specified file server.
By default, only local (non-routed) file servers are scanned
for queues. See
Access Lists
on page 8-1 for more informa-
tion on manipulating the NetWare access lists.
Verify that the login password on the
Server and the queue password on the
file server match.
If necessary, change the password on the Server. Unless the
passwords match, the Server will not be able to log into file
servers to scan for jobs.
Look for poor printing performance in
general.
If there is a significant delay between NetWare jobs, the delay
may be a result of scanning too many file servers. This delay
is often increased if the file servers are distributed across a
wide area network. Configure the NetWare access list to only
allow scanning for jobs on the file servers of interest. To con-
figure the NetWare access list, see
Access Lists
on page 8-1.
Table 8-2:
NDS Printing Errors
Bit
Failure Code Meaning
Remedy
0
OK.
None needed.
1
Print server ran out of memory.
Cycle power on the box. If the problem persists,
disable the unused protocols and change the Net-
Ware access list to only include file servers which
have print queues associated with them.
2, 3
Unexpected response from file server.
Report the problem to Lantronix Technical Support.
4
No printers found for the print server.
Check to make sure that there are printers for the
print server and the printer names match the service
names on the print server.
5
No queue found for the printer.
Check to make sure that the printers have associated
queues.
Table 8-1:
NetWare Host Troubleshooting, cont.
Things to Check
Suggestion