Lantronix LPS1-T EPS Reference Manual - Page 97

Failure code meaning, Remedy, Failure Code Meaning

Page 97 highlights

NetWare Host Setup Troubleshooting Table 8-2: NDS Printing Errors, cont. Bit Failure Code Meaning Remedy 6 Login failed. Check to make sure there is a print server object configured with the same name as the print server. 7 Authentication failed. Check that the login password on the print server is the same as the password for the print server object. If the login password on the print server is the default (access) then there should be no password for the print server object. 8 Print server cannot attach to queue. Check the NDS partitions, replicas, and volumes to make sure that the file server where the queue actu- ally lives has the information about the print server and printers. The following errors may be received from the file server. Table 8-3: NDS Errors from the File Server Code 0 fffffda7 fffffda5 fffffd69 fffffd63 fffffd54 Failure code meaning Remedy OK. None needed. Object could not be found in the given context. Check the print server name, dscontext, and dstree to make sure that the printer server is set up correctly with PCONSOLE. Requested attribute could not Use PCONSOLE to make sure that the print be found. server has associated printers and that the print- ers have associated queues. DS Database locked. An administrator is probably updating the database. Wait a few minutes and issue the Set Protocol NetWare Reset command. Invalid password. Make sure the password for the print server object under PCONSOLE is the same as the login password for the print server. If the login password on the print server is the default (access) then there should be no password for the print server object. If the login password is something other than the default, then the password for the print server object should match. Secure NCP violation. The file server is probably requiring NCP packet signature, which is currently not supported. Turn down the NCP packet signature level so that it is not required from the server. 3 Reboot the print server to force it to rescan the NDS tree. If you have changed printer and queue setups, it may take a few minutes for the changes to propagate through the directory tree. 8-17

  • 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

NetWare Host Setup
Troubleshooting
8-
17
The following errors may be received from the file server.
3
Reboot the print server to force it to rescan the NDS tree. If you have changed printer and queue set-
ups, it may take a few minutes for the changes to propagate through the directory tree.
6
Login failed.
Check to make sure there is a print server object
configured with the same name as the print server.
7
Authentication failed.
Check that the login password on the print server is
the same as the password for the print server object.
If the login password on the print server is the
default (access) then there should be no password
for the print server object.
8
Print server cannot attach to queue.
Check the NDS partitions, replicas, and volumes to
make sure that the file server where the queue actu-
ally lives has the information about the print server
and printers.
Table 8-3:
NDS Errors from the File Server
Code
Failure code meaning
Remedy
0
OK.
None needed.
fffffda7
Object could not be found in
the given context.
Check the print server name, dscontext, and
dstree to make sure that the printer server is set
up correctly with PCONSOLE.
fffffda5
Requested attribute could not
be found.
Use PCONSOLE to make sure that the print
server has associated printers and that the print-
ers have associated queues.
fffffd69
DS Database locked.
An administrator is probably updating the data-
base. Wait a few minutes and issue the
Set Pro-
tocol NetWare Reset
command.
fffffd63
Invalid password.
Make sure the password for the print server
object under PCONSOLE is the same as the
login password for the print server. If the login
password on the print server is the default
(access) then there should be no password for
the print server object. If the login password is
something other than the default, then the pass-
word for the print server object should match.
fffffd54
Secure NCP violation.
The file server is probably requiring NCP packet
signature, which is currently not supported. Turn
down the NCP packet signature level so that it is
not required from the server.
Table 8-2:
NDS Printing Errors, cont.
Bit
Failure Code Meaning
Remedy