User guide

IOPRINT+ Print Servers User guide
Printing problems
Page 291
QUICKSET timed out when
checking if the device had
logged in to the file servers.
This means that the IOPRINT+ Print Server did not log in the master file
server. It might be that the Ethernet frame types do not match. If so, the
following steps should solve the problem.
Try to find a workstation that use the same frame type as the IOPRINT+
Print Server so that PSCONFIG can see the device. Or load the NetBEUI
protocol on your PC and use WPCONFIG to connect to the device.
Enable the IOPRINT+ Print Server'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.
Make sure you are a Notify member of the Print Server.
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
"Print 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. Ensure the IOPRINT+ Print Server is ON.
2. Delete the print server object of the IOPRINT+ Print Server.
3. Install the IOPRINT+ Print Server 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.
1. Check the length of the control strings. No string can exceed 15
characters.
2. Check that the control strings are in HEX.
Problem Solution