Filter
Top Products
TROUBLESHOOTING THE M208: Novell Problems 163
?
somewhere in the print path.
Any printing from PCs should have a “raw” setup.
Some other things to consider when garbled data persists are:
• tab expansion (xtab) set on with graphic jobs,
• cable used between the M208 and the printer,
• type of flow control being used on the M208 and a serial printer.
If you cannot eliminate the garbling, you may want to try printing without the Print
Server to see if the problem persists.
Novell Problems
Communication Related
No connection is made with the M208 after you have completed the print
setup
Whether you have configured the Print Server as a PSERVER or as an RPRINTER,
there are several things to confirm:
• Have you tried repowering the M208 Wait about a minute before checking to see
if it has logged in and attached to a queue.
• Is the network connector fastened tightly to the unit?
• When going through the setup steps, did you name the M208 M_xxxxxx where
xxxxxx equals the last six digits of the Ethernet address? This is the default format
of the unit’s name whether it is acting as a PSERVER or as an RPRINTER.
This M_xxxxxx name must have six digits after the “_” so if necessary, pad out each
byte with a zero (0).
• Has the M208’s name been changed from its default of M_xxxxxx and if so, have
you incorporated this new name into your setup?
• When setting the M208 up as a PSERVER, did you specify a destination on the
M208 (e.g. d1prn) for the printer name and did you remember this name is case
sensitive?
N
o
t
e
N
o
t
e
?