Allied Telesis FastPrint Server, Руководство пользователя, Страница: 87 / 100

Appendix A.
Troubleshooting
FastPrint Server User’s Guide
77
I used the Capture command to print a job, but the job was separated
into two parts.
The timeout setting in the Capture command may be too short. You should increase the
timeout value of the Capture command.
Use the option /TI=n of the Capture command to increase the time out value, where n is
the value of timeout.
PSCONFIG shows "No Response."
This may be due to the following:
•
The network traffic is busy now. Wait for a minute and then try it again.
•
The FastPrint is not powered on. Power it on.
•
The network cable is disconnected. Check the cable.
•
The node address of the FastPrint may be the same as the node address of another
device on the network.
QUICKSET timed out while checking if the FastPrint Server had logged
in to the file servers.
This means that the FastPrint Server did not log in the master file server. It might be
that the Ethernet frame types do not match.
1. Try to find a workstation that uses the same frame type as the FastPrint so that
PSCONFIG can see the FastPrint. Or load the NetBEUI protocol on your PC and use
WPCONFIG to connect to the FastPrint Server.
2. Set the FastPrint’s frame type to the frame type that the master file server uses and
disable all other frame types.
I cannot receive Notify message in NetWare 4.x environment.
1. Make sure you are a Notify member of the FastPrint.
2. Run NetAdmin and set the name of the Default Server to receive notification.
I cannot use PCONSOLE to see Printer Status. or
The current server status in FastPrint Server Information is showing
Down
in the NetWare 4.x environment.
It may be that you created the Print Server object in NetWare 3.x environment and used
PCONSOLE in NetWare 4.x to view the status. Try the following:
1. Make sure the FastPrint is ON.
2. Delete the Print Server object of the FastPrint.
3. Install the FastPrint again in NetWare 4.x NDS environment.
The “String Before Job” and/or “String After Job” settings in the
logical printers don’t work properly.
•
Check the length of the control strings. No string can exceed 15 characters.
•
Check that the control strings are in HEX.
A.5. Printing - Unix
FastPrint Server is not recognized.
Check the following: