Kodak 3H0610, Kodak 10/100 Network Interface Card manual Troubleshooting Netware

Novell NetWare

4.6Troubleshooting Netware

The printer/NIC does not log in to bindery Novell 3.x server

The server may not have the bindery emulation mode enabled. To verify that the bindery emulation is enabled, Þnd the following line in the autoexec.ncf Þle in the system directory:

Set Bindery Context=<context>

where <context> is the name of the company to be used by bindery emulation. If it is not there, bindery emulation is not running. Refer to the NetWare userÕs manual for instructions on bindery emulation.

The printer/NIC does not login to the Þle server

¥Use FastManage to see the messages sent by the printer/NIC.

¥Use the userlist command (in NetWare 4.x, this is nlist user) to see whether an assigned user to the printer/NIC has logged in.

¥Use PCONSOLE to force a conÞguration Þle server to direct the printer/NIC to search for a speciÞc server.

¥Use a speciÞc frame type (refer to FastManage).

File server displays an Incomplete Packet error message

By default, the printer/NIC Þnds NetWare servers using repeated broadcasts of different frame types. If a server is bound to a speciÞc frame type, the server issues error messages for frames it does not understand. Use FastManage to set a speciÞc frame type.

NotiÞcation not working when created with PCONSOLE

Verify that the printer type is DeÞned Elsewhere and not any other type. Select the Print Servers menu and change the settings in the Printers submenu.

N O V E L L

N

E

T

W A R E

July 1998 4-11