OkiLAN 6200e Plus User’s Guide
TCP/IP
132
•
If you are able to
ping
to the Network Print Server,
but are unable to
telnet
, the IP address is probably
being shared with another device that does not
support
telnet
.
OkiNet for TCP/IP—Winsock Errors
•
If you see an error before OkiNet for TCP/IP
appears on the screen, try setting a host name in
the host’s file in the Windows directory (check the
documentation for your Windows TCP/IP stack).
•
If you have difficulty seeing a particular Network
Print Server, try moving the device onto the same
subnet as the computer running the utility.
•
If OkiNet for TCP/IP gives you the Winsock error:
“Could not bind to socket,” use the Special Options
dialog under the File menu to change the Discov-
ery UDP Port to a different port number.
Hardware Error Messages
ST: Cable not connected
Self test has determined that the network cable is not
connected.
•
Check the cable connection to the Network Print
Server.
•
Move the Network Print Server to another known
working node.
If you find the cable is connected and you are still
receiving this message or any other “ST:” error mes-
sage, power cycle the Network Print Server. If the
error continues, call Oki Data Customer Support at 1-
800-OKI-DATA (1-800-654-3282).
