X hits on this document

Word document

Every effort has been made to ensure that the information in this document is complete, - page 153 / 249

959 views

0 shares

0 downloads

0 comments

153 / 249

Static Route Entry

If the OkiLAN 6200e has printed a configuration page showing the default address, but it cannot be reached through telnet, check the following:

Ÿ

Display the host’s routing tables with the ‘netstat -r’ command. Verify the route has been set correctly.

Ÿ

If the route is set correctly, try pinging the device.

Ÿ

Verify the OkiLAN 6200e is on the same subnet as the host from which you are telneting. As a drastic measure, try creating an isolated subnet with your host and the OkiLAN 6200e. If you are using 10BASE2, run the cable directly from the host to the OkiLAN 6200e. If using 10/100BASE-T cabling, connect the host to the OkiLAN 6200e through a hub not connected to any other host.

Ÿ

If the static route has been set up and can telnet to the OkiLAN 6200e, but your changes do not seem to be saved, check the host’s routing tables. You might have telneted to a different OkiLAN 6200e than the one you intended. While in telnet, select the second menu option, Show Network/Printer Information. The hardware address and serial number are displayed. Verify they are the same as the unit you are configuring.

Ÿ

Turn off the OkiLAN 6200e you want to configure. Run telnet again. If you reach a different device, there is an IP address conflict.

Ÿ

If you are able to ping to the OkiLAN 6200e, 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 OkiLAN 6200e, 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 Discovery UDP Port to a different port number.

Document info
Document views959
Page views959
Page last viewedFri Dec 09 03:34:28 UTC 2016
Pages249
Paragraphs3453
Words36582

Comments