3.Troubleshooting a Novell implementation
The tables in this chapter describe some ways to troubleshoot a Novell implementation from the log messages that appear in the var/log/DocuPrint.
The following table describes how to troubleshoot PSERVER problems.
Table 3-1. PSERVER problems
Problem | Probable Cause | Resolution |
|
|
|
Log message says there | NPS/IPS is not getting SAP packets for | If there is an external connectivity |
is a problem locating a | the server. | problem: |
NetWare server. | • There is a basic connectivity or | • Check Novell file server |
| ||
| routing problem. | console screen for messages. |
| • The framing type has been set | • Check that the server is |
| incorrectly during installation. | running and connected to the |
| • The file server name has been set | network. |
| If it is an incorrect framing type or | |
| incorrectly during installation. | |
|
| server name, your Xerox service |
|
| representative must change the |
|
| configuration on the printer |
|
| controller. |
|
|
|
Log message says there | NPS/IPS is getting SAP packets with | If there is an external connectivity |
is an error in connecting to | information about the server, but | problem: |
the file server. | cannot communicate with it. | • Check Novell file server |
|
| |
| • There is a basic connectivity or | console screen for messages. |
| routing problem. | • Check that the server is |
|
| |
| • NPS/IPS has an incorrect network | running and connected to the |
| number. | network. |
|
| If it is an incorrect network number, |
|
| your Xerox service representative |
|
| must change the configuration on |
|
| the printer controller. |
|
|
|
Troubleshooting Guide |
