HP Jet Direct login

[kdeans]

Netware 4.11 SP 9
From time to time, some of my HP 4 printers have a hard time attaching to the server. They are various incarnations of HP 4s with various MIO versions and not all of them have this problem. There seems to be no pattern as to when this happens and it began a couple of years back that no one can think of what changes might have precipitated it. The Jet Direct Card will show all the proper settings from the front panel, it shows up in JetAdmin, and it has no problem with IP. When they are having trouble they seem to sit in an "initializing" state. A test page shows "trying to connect to server" or "cannot sense net number". If I reboot the server, I must make sure that all printers are recognized by the Novell Print Server. If they aren't, I reboot until they are. Not the way I would like this to work. Print Server is version 5.00 PTF v1.11 (000505) May 5, 2000. Any body have any ideas?

 

[TheLad]

Have you tried updating JetDirect firmware? -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[damonuk]

try setting the frame type in Jet Admin to the same as the servers rather than auto and disbling other protocol stacks (Appletalk etc though not IP obviously!), especially if you are running 802.3 on your servers (in the LAN card LOAD line in AUTOEXEC.NCF, or IPXCONFIG.NCF)and AUTO on your workstations. NT/95/2K/XP and HP MIO autodetect by broadcasting and 802.2 packet first (the client detects NW4 or later by the TREE being set) as this is the 'default' for NW 4 and later. If the MIO card picks this 802.2 broadcast up as it 'autodetects' then the MIO sets it's frame type to 802.2 and won't communicate.

If it is the same printers all the time, try reflashing and factory resetting. Power off the printer/MIO. Delete the queues in NWAdmin and leave to replicate for AT LEAST 30 mins. Then recreate the NW side first followed by the MIO. Depending on MIO revision and Jet Admin version, the card may show up as 'NEW' or as NPxxxxxxx.

 

[TheLad]

You could also try forcing your network ports to the speed/duplex of the JetDirect card. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[salserocito]

Also,

Make sure that when you configure these devices for use with NetWare, only create NDS objects!

I've seen so many people neglect the checkbox and end up creating both Bindery AND NDS objects for their Print Servers.

Good Luck!